Abstract. Avaya Solution & Interoperability Test Lab

Transcription

1 Avaya Solution & Interoperability Test Lab Configuring Avaya Message Networking 3.1 with Avaya Modular Messaging Integration using Avaya Message Storage Server and Microsoft Exchange Server Issue 1.0 Abstract Avaya Message Networking is a server-based solution that allows customers to link their stand-alone, multi-vendor messaging systems into one company-wide messaging network. Using a store-and-forward approach to networking, Avaya Message Networking receives messages, performs the necessary protocol conversions, and simultaneously delivers messages to one or more recipients on one or more messaging systems. These Application Notes describe the administrative steps required to configure Avaya Message Networking 3.1 to interconnect two stand-alone messaging systems - Avaya Modular Messaging with Avaya Message Storage Server (MM/MSS) and Avaya Modular Messaging with Microsoft Exchange Server (MM/Exchange). 1 of 33

2 1. Introduction Avaya Message Networking provides a solution for enterprise customers to streamline and leverage their communications investments by linking stand-alone, multi-vendor messaging systems, into one company-wide messaging network that delivers the power of messaging to their entire enterprise. Using a store-and-forward approach to networking, Avaya Message Networking receives messages, performs the necessary protocol conversions (if required), and simultaneously delivers messages to one or multiple recipients on one or many messaging systems. Avaya Message Networking provides a clear path to bringing new IP standards-based messaging systems to enterprise networks. Avaya Message Networking has the capability to translate different message transmission protocols and transcodes the various speech compression techniques, so customers can network almost any messaging system in their environment. Since all transmission protocol translations are performed within Avaya Message Networking, there is no need to reconfigure each individual end-point or equip them with translation software. Avaya Message Networking can network any messaging system that supports the industry-standard VPIM (Voice Profile for Internet Mail) v2 and SMTP-MINE (Simple Mail Transfer Protocol- Multipurpose Internet Mail Extensions) for digital transmission protocols or AMIS (Audio Message Interchanges Specification) for analog transmission protocols. These Application Notes detail the administrative steps required to configure Avaya Message Networking 3.1 to interconnect two stand-alone message systems - Avaya Modular Messaging with Avaya Message Storage Server (MM/MSS) and Avaya Modular Messaging with Microsoft Exchange Server (MM/Exchange). The network configuration consists of two locations; Site A and Site B. Site A has an Avaya Message Networking 3.1 Server, Avaya Modular Messaging with Microsoft Exchange for message storage, and a redundant set of Avaya S8710 Media Servers controlling a G650 Media Gateway. Site B consists of Avaya Modular Messaging with Avaya Message Storage Server and an Avaya G350 Media Gateway. A H.323 trunk is established between these two locations. An Avaya Message Networking Server, in Site A, provides message networking between these two stand-alone message systems. Subscribers at site A have 7 digit extensions and mailbox numbers. Subscribers at site B have 5 digit extensions with 7 digits mailbox number. Figure 1 is the network configuration used for these Application Notes. 2 of 33

3 Figure 1: Network Configuration for Message Networking Site A Modular Messaging system uses QSIG integration with Avaya Communication Manager and Site B Modular Messaging system uses SIP integration via an Avaya SIP Enablement Services (SES) server with Avaya Communication Manager. These Application Notes will not cover the configurations for Avaya Modular Messaging, Avaya SES and Avaya Communication Manager. For resources regarding to these configurations, refer to [1], [2] and [3] listed in reference section. 3 of 33

4 2. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment Avaya Message Networking Avaya Modular Messaging System Messaging Application Server Messaging Storage Server Avaya Modular Messaging System Messaging Application Server Microsoft Exchange Server Avaya S8710 Media Servers G650 Media Gateway Avaya TN2312BP Avaya TN799DP Avaya TN2302AP MEDPRO Avaya S8300 Media Server Avaya G350 Media Gateway Software MN Avaya SES R Microsoft DNS Avaya 9630 IP Telephone Avaya 4620 IP Telephone R3.1 build ( ) R R3.1 build ( ) V5.2 with Service Pack 1 Communication Manager 4.0 Load R014x FW036 FW017 FW115 Communication Manager 4.0 Load R014x Microsoft 2003 Server with Service Pack 1 Version R1.2 (H.323) R2.7 (H.323) Table 1: Equipment and Software Version The dial plan extension and mailbox range used for both sites are as shown in Table 2 below. Location Extension Range Mailbox Pilot Number Site A 222xxxx 222xxxx (7 digits) Site B 66xxx 2266xxx (7 digits) Table 2: Dial Plan for Site A and Site B 4 of 33

5 3. Assumptions and Limitations It is assumed that Avaya Communication Manager and Avaya Modular Messaging systems are configured and operational in both site A and site B. Users at both sites can place calls to each other. Subscribers have their mailboxes created on their local message system. Avaya Message Networking uses Octel Analog Networking (OAN) to perform remote updates from Microsoft Exchange. OAN does not support dynamic updates, meaning subscriber information from Avaya Message Networking can not be pushed down to Microsoft Exchange. Remote subscribers from other messaging systems will have to be manually added as a contact in Microsoft Exchange. This will be discussed in greater detail in section Configure Avaya Message Networking 3.1 In order to network these two messaging systems, each message storage server (MSS and Exchange) needs to be added to Avaya Message Networking as a remote node. Sections 4.2 and 4.3 will demonstrate the steps to add the Avaya Modular Messaging Storage Server and Microsoft Exchange Server to the Avaya Message Networking system Configure IP Address, System Parameters and Customer Options Assume that the Avaya Message Networking software has been installed and is functional. System administrator and other user accounts have been configured on the system. For software installation and user setup, refer to [4] listed in the reference section. Avaya Message Networking can be accessed via a console connection before an IP address is assigned. After logging into Avaya Message Networking with a proper user name and password, the messaging administration menu is shown below. From the left side panel navigation tree, Click TCP/IP Network Configuration under the Server Administration. Enter all information as shown below. In this configuration, the domain is retail.com and the DNS server IP address is Make sure that the host name entered (mmnk1) with IP has been created on DNS server. Click Save. 5 of 33

6 After an IP address has been assigned to the Avaya Message Networking server, administrators can configure the system using a web-browser from any computer that has connectivity to the Avaya Message Networking server. The remaining configuration steps are preformed via this method. Launch a web browser from a computer and point to Log into the Avaya Message Networking system using a proper user name and password. The Message Networking Messaging Administration menu is shown below. All administration steps are performed by clicking links in navigation tree on the left side of the screen. 6 of 33

7 As mentioned in Section 3, Avaya Message Networking uses Octel Analog Networking to exchange information with a Microsoft Exchange Server. This feature must be licensed in Avaya Message Networking. To verify license options, click Customer Options to display the customer option settings. Verify that Octel Analog Nodes is set to ON. If Octel Analog Nodes is set to OFF, contact an authorized Avaya sales representative to add OAN to the configuration. 7 of 33

8 From the navigation tree, click System Parameters. 8 of 33

9 Click General Parameters to open the configuration page and enter the following parameters as shown below. Select TCP/IP as Connection Type. Leave channel 0 as default or select other channel. Leave LDAP Port as default. This port number must match the port number defined on the Avaya MSS storage system in Site B, as described in Section 5.1. Enter a password for LDAP Password. This password must also match the password entered on all remote machines that will access Avaya Message Networking via LDAP. Select no for Block MM to MM Updates. Select Network Address Length 7 to match the user s mailbox length. Select yes for UPDATES In and UPDATES Out. Selecting no will block the ability for Avaya Message Networking to exchange subscriber updates with remote machines. Leave for Octel Analog Serial Number as default. The number ranges are from to and are used by the Octel Analog Networking protocol for this Message Networking system. The serial number can be up to 10 digits. Leave default for other fields. Click Save. 9 of 33

10 4.2. Add Avaya Modular Messaging Storage Server The following configurations show the steps to add an Avaya Modular Messaging Storage Server (MSS) as a remote machine on Avaya Message Networking. From the navigation tree, click Remote Machine Add a Remote Machine. Enter a descriptive name for New Machine Name and click Next Step. MM-MSS was used as the remote machine name in these Application Notes. Under Machine Type, select Avaya Modular Messaging from the drop down menu for Machine Type. Enter a valid IP address in the IP address field for this message storage server. An IP of was used in these Application Notes. Click Next Step. Enter the mailbox length in the Mailbox ID Length field. For these Application Notes, a mailbox length of 7 was entered. Select en-us (English-US) as Default Language. Leave default values for other fields as shown. Click Next Step. 10 of 33

11 Leave u for Default NameNet Type. This field is used for aging purposes by the remote machine. Type p if directory entries are permanent. Type u if entries are usage-based, which indicates that directory entries are temporarily available based on the network traffic of a particular remote machine. The default for this field is u. Enter the fully qualified host name (FQHN) of the Avaya MSS in both the Domain Name and LDAP Server fields. For these Application Notes, MM-MSS.retail.com is the FQHN. Use the drop down window to select G.711 ulaw as Preferred Encoding Type. Select Yes for UPDATES In and UPDATES Out. Enter the password for LDAP Password. This password should match the password entered back in Section 4.1. Leave default values for other fields as shown. Click Next Step. 11 of 33

12 Clicking Add this Machine will add this machine to Avaya Message Networking without adding dial plan mapping. To add this machine with dial plan mapping, Click Next Step. Enter an appropriate range in the Start and End fields for the MAILBOX ID NUMBER RANGE. In these Application Notes, the mailbox ID range used on the Avaya MSS is Click Save. In the sample configuration used for these Application Notes, both sites use 7 digits for mailbox numbers. Therefore, network address mapping is not needed in Avaya Message Networking. 12 of 33

13 4.3. Add Microsoft Exchange Server Follow the same steps outlined in section 4.2 to add Microsoft Exchange Server as a remote machine. From the navigation tree, click Remote Machine Add a Remote Machine. Enter a descriptive name for New Machine Name and click Next Step. MSEXCHANGE was used as the remote machine name in these Application Notes. Click Next Step. 13 of 33

14 Select UM Analog as Machine Type as Message Networking currently only uses Octel Analog Networking protocol to communicate with Microsoft Exchange Server via an analog port. Enter the Avaya Modular Messaging pilot number for Site A in the Dial String field. For these Application Notes, the pilot number for Site A in this configuration is Click Next Step. Enter 7 for Mailbox ID Length. Select en-us (English-US) as Default Language. Select dynamic as Subscriber Updates Type. This field does not apply to a machine type of UM Analog and Modular MM/Exchange using OAN systems because those systems cannot request remote updates from Avaya Message Networking and Avaya Message Networking cannot push remote updates to these remote machines. The value dynamic is default setting for this field and can be left unchanged. Select yes for UPDATES In. Select yes to allow Avaya Message Networking to accept updated user information from this remote machine. Select no for UPDATES Out. This field does not apply to a machine type of UM Analog using OAN because Avaya Message Networking cannot push remote updates to these remote machines. Leave this field at the default, no. Select yes for ASCII Name Confirmation. Select yes for the system to verify the ASCII name when a subscriber sends a message. If the name does not match, the Avaya Message Networking system requests an update. Select yes for Admin Node. Select yes to automatically request a subscriber update when Avaya Message Networking delivers a message to a remote machine using the Octel Analog Networking gateway. Enter the Octel Analog Serial Number. This number must match the number defined on MS Exchange server. The serial number can be either 4 or 5 digits. For these Application Notes, Microsoft Exchange uses a 5 digit serial number of Leave other fields as default as shown below. Click Next Step to add Dial Plan Mapping. 14 of 33

15 Clicking Add this Machine will add this machine to Avaya Message Networking without adding dial plan mapping. To add this machine with dial plan mapping, Click Next Step. Enter an appropriate range in the Start and End fields for the MAILBOX ID NUMBER RANGE. In these Application Notes, the mailbox ID range used on the Avaya MSS is Click Save. In the sample configuration used for these Application Notes, both sites use 7 digits for mailbox numbers. Therefore, network address mapping is not needed in Avaya Message Networking. 15 of 33

16 Assign Service to Channel for Octel Analog Networking Under the Voice System Administration from the configuration navigation tree, Click Assign Services/Chans. Enter 0 for Channel. For these Application Notes, only one channel will be used for Octel Analog Networking. Select acr for Service. Click Save. 16 of 33

17 5. Configure Avaya Modular Messaging Systems for Avaya Message Networking 5.1. Add Avaya Message Networking to Avaya Messaging Storage Server (MSS) Avaya Message Networking uses LDAP to exchange information with an Avaya MSS. In order to use LDAP to exchange subscribers information, Avaya Message Networking is added as a networked machine in the Avaya MSS. The following steps describe the configuration. Log into the Avaya MSS with a proper user name and password with administrative privileges. Click Networked Machines from the left side navigation tree. Click Add a New Networked Machine. 17 of 33

18 Enter a descriptive name in the Machine Name field. For these Application Notes, the Avaya Message Networking machine name of MMNK1 was entered. Enter a password into Password and Confirm Password fields. This is the same password entered for the LDAP password in Avaya Message Networking back in Section 4.1. Enter the Avaya Message Networking IP address in the IP Address field. Use the drop down window to select ldap as Machine Type. Select 7 for Mailbox Number Length. Select yes for both Updates In and Updates Out. Select yes to allow this machine to send and accept updated users information from Avaya Message Networking. Leave for LDAP Port as default. This value should match the LDAP port defined for the Avaya Message Networking server back in Section 4.1. Leave Must use SSL or encrypted SASL for Inbound LDAP Security as default. Enter as Starting Mailbox Number and as Ending Mailbox Number. Click Save at the bottom of the page. 18 of 33

19 5.2. Add Avaya Message Networking to Microsoft Exchange Server Avaya Message Networking uses Octel Analog Networking to communicate with a Microsoft Exchange Server. An analog line needs to be configured between Avaya Message Networking (machine name MMNK1) and the Avaya G650 Media Gateway controlled by the Avaya S8710 Media Servers at site A. The Avaya Message Networking Server has a 4-port analog interface installed on board. A TN793B analog circuit is used on the Avaya G650 Media Gateway. The following two sections detail the configuration on Avaya Communication Manager and Microsoft Exchange Server Configure Hunt Group and Analog Station on Avaya Communication Manager Assume that an IP trunk, dial plan and route pattern have been configured on both Avaya Communication Manager systems at site A and site B. Users from both sites can place calls to each other. An analog station is added here for communication to Avaya Message Networking. Use the command add station to add an analog station. Select 2500 for station Type. Type the physical connection on the TN793 card for Port. add station Page 1 of 4 STATION Extension: Lock Messages? n BCC: 0 Type: 2500 Security Code: TN: 1 Port: 01A0607 Coverage Path 1: COR: 1 Name: analog to MN Coverage Path 2: COS: 1 Hunt-to Station: Tests? y STATION OPTIONS Time of Day Lock Table: Loss Group: 1 Message Waiting Indicator: none Off Premises Station? n Survivable COR: internal Survivable Trunk Dest? Y Use the command add hunt-group 10 to create a hunt group for Exchange Server to dial. Assign Group Extension Leave other fields as default. add hunt-group 10 Page 1 of 60 HUNT GROUP Group Number: 10 ACD? n Group Name: Message Networking Queue? n Group Extension: Vector? n Group Type: ucd-mia Coverage Path: TN: 1 Night Service Destination: COR: 1 MM Early Answer? n Security Code: Local Agent Preference? n ISDN/SIP Caller Display: 19 of 33

20 On page 3, add the extension as a member of hunt group 10. add hunt-group 10 Page 3 of 60 HUNT GROUP Group Number: 10 Group Extension: Group Type: ucd-mia Member Range Allowed: Administered Members (min/max): 1 /1 Total Administered Members: 1 GROUP MEMBER ASSIGNMENTS Ext Name(19 characters) Ext Name(19 characters) 1: analog to MN 14: 2: 15: 3: 16: 4: 17: 5: 18: Type saves translation when done Configure Octel Analog Networking on Microsoft Exchange Server Assume that the Octel analog networking has been enabled during the Modular Messaging installation on the Exchange Server. From the Microsoft Exchange Server desktop, Select Start Programs Microsoft Exchange System Manager. Expand the Connectors folders to display Octel Analog Networking Gateway as shown below. 20 of 33

21 Right click the icon and select Properties. Under the Local Node tab, enter as Serial number for this configuration. This is the same serial number entered for Microsoft Exchange in Section 4.3. For customers who follow these Application Notes, enter the unique serial number, which can be found in the shipment with the Avaya Modular Messaging system. Select the Avaya Modular Messaging Application Server for Sending Server. If multiple MAS machines exist, click Browse to select one. In this configuration, Exchangemas1 is the only MAS available, so it appears in the window below. 21 of 33

22 Click the Remote Nodes tab. Enter the machine name in the Name field for Avaya Message Networking. In these Application Notes, mmnk1 represents the machine name for Avaya Message Networking. Leave Serial Number as default. This number should match the serial number for Octel Analog Networking configured on Avaya Message Networking back in Section 4.1. Check boxes Allow messages to be sent to this remote node and Allow messages to be received from this remote node. Click this icon to add as the access phone number. The number entered is the hunt group extension created in Avaya Communication Manager back in Section Click this icon to configure Addressing schemes. Enter 22 for Prefix. The Prefix is required for Microsoft Exchange Server to route calls with 22 as starting digits to Avaya Message Networking. Enter 5 for Additional Digits and 7 for Mailbox Length. The Mailbox Length equals the Prefix length plus the Additional Digits. 22 of 33

23 Click the Advanced tab and check all boxes as shown below. Use the default values for the remaining fields. Click OK. 23 of 33

24 Add Remote Subscribers as Microsoft Exchange Users. Octel Analog Networking does not support dynamic updates. All remote subscribers from other voice systems have to be added manually as a contact on Microsoft Exchange Server. From the Microsoft Exchange Server desktop, Select Start Programs Microsoft Exchange Active Directory Users and Computers. Expand the retail.com DNS. 24 of 33

25 In the console tree, right-click folder Users. Click New Contact. The system displays the New Object Contact dialog box. Enter the First name, Initials (middle initial), and Last name for the new user. The full name is populated automatically. Click Next. 25 of 33

26 Check the Create an Exchange address box. Click the Modify button next to the address field. The system displays the New Address dialog box. Highlight Custom Address and click OK. The system displays the Other Address Properties dialog box. 26 of 33

27 In the address field enter the recipient s Octel Analog Networking address. The address includes both the prefix, and mailbox number, without a separator. The address is used in this example. In the type field, Enter OCTELAN. Click OK. 27 of 33

28 The screen is back to New Object Contact. Click Next. Click Finish. 28 of 33

29 After the Microsoft Exchange server creates this new contact, click the Addresses tab to verify that the OCTELAN address is Repeat the steps above to add additional remote subscribers as needed. 29 of 33

30 6. Verification Steps The following steps can be used to verify Avaya Message Networking operation. Remote user update: 1. Select Remote Directory from the Avaya Message Networking 3.1 navigation tree and click Demand Remote Updates as shown below. 2. Select MSEXCHANGE as Remote Machine Name and enter Start Extension and End Extension Click Update to initiate the process. 3. From the Avaya MSS ( ), click Subscriber Management Manage to display the remote subscribers. 30 of 33

31 SiteA-User1 and SiteA-User2 are shown as remote subscribers from Remote Machine mmnk1 (Avaya Message Networking). 31 of 33

32 4. Record a new message from subscriber and send this message to subscriber Verify that subscriber receives this message and the MWI is on. 5. Log into the subscriber mailbox and play the message. Verify that the message is from subscriber by listening to the message envelope information. 6. Reply this message with comments to sender. Verify that subscriber receives this message and the MWI on the station is on. 7. Create an enterprise list on MM/Exchange and add subscribers , and as members. Record a new message from subscriber and send the message to the enterprise list. Verify that all three members on the enterprise list receive this message and all MWI are on. 7. Conclusion These Application Notes have provided the administrative details on configuring Avaya Message Networking to link two independent Avaya messaging systems. As illustrated in these Application Notes, Avaya Message Networking can provide voice messaging networking for users to share messages across stand-alone messaging systems. 8. Additional References See the following Application Notes addressing Avaya Modular Messaging configuration at [1] Configuring Voice Message Networking Between Avaya Modular Messaging, Avaya Intuity Audix, and Nortel CallPolit Using Avaya Message Networking Issue 1.0 [2] Configuring SIP IP Telephony Using Avaya Enablement Services, Avaya Communication Manager, and Cisco 7940/7960 SIP Telephones Issue 1.0 [3] Configuring a QSIG Centralized Messaging Solution using Avaya Modular Messaging and Avaya Communication Manager Issue 1.0 Avaya Message Networking product documentation available at [4] Avaya Message Networking Release 2.0 Installation Print Guide [5] Avaya Message Networking Release.2.0 Administration Print Guide [6] Avaya Message Networking Release 2.0 Concepts and Features Print Guide 32 of 33

33 Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please any questions or comments pertaining to these Application Notes along with the full title name and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at 33 of 33