Avaya Solution & Interoperability Test Lab Application Notes for Configuring the ESNA Telephony Office-LinX v8.0 with Avaya Business Communications Manager Release 6.0 - Issue 1.0 Abstract These Application Notes describe the procedure for configuring the ESNA Telephony OfficeLinX v8.0 to interoperate with the Avaya Business Communications Manager Release 6.0.
1. Introduction These Application Notes describe the procedure for configuring the ESNA Telephony OfficeLinX v8.0 (TOL) to interoperate with Avaya Communications Manager (BCM) Release 6.0. The objective of this compliance testing is to verify that TOL can connect via SIP trunk to the BCM and provide unified communication services like greetings, messaging and transfer functionalities. 1.1.
F Figure 1: Sollution Conffiguration 3. Equipmentt and So oftware Validate V ed The folloowing equipm ment and sofftware/firmw ware were ussed for the saample configguration providedd: Equipmentt Avaya BCM 450 Avaya Telephones M7310 (D Digital) Link (Analog) I2007 (IP P) ESNA Telephony Office-LinX O X Softtware/Firmw ware Syystem softwaare version : 10.0.1.02.1220 Software version : Avaya BCM450 B Rlls 6 Maanufacturer s/w s version : 450.06 06P PAF20 06A AEB00 06221C7G 8.00.0.0163 4.
.1. SIP Trunking Configuration This section explains the steps to configure a SIP trunk routing entry that will access the TOL server from the BCM. After logging into the BCM element manager, configure a private routing entry for the SIP trunking by selecting, Configuration > Resources > IP Trunks > SIP Trunking Select the tab Private > Routing Table to add a routing entry as shown in Figure 2 below. Figure 2: Routing Table • • • • Destination digits represent the pilot number used to call the TOL.
To configure the SIP Trunking URI Map, go to: Configuration > Resources > IP Trunks > SIP Trunking Select the tab Private > URI Map as shown in Figure 3 below. Figure 3: URI Map Do note here that some values need to be blank for the TOL to integrate correctly with the BCM. Entering any values here will cause the integration to fail since TOL does not recognize these values. For example if you populate Private/CDP field with cdp.
To configure the SIP Trunking Global settings go to: Configuration > Resources > IP Trunks > SIP Trunking Select the tab Global Settings as shown in Figure 4 below. Figure 4: Global Settings • Local Domain is the defined domain that the TOL system is assigned to. RS; Reviewed: SPOC 11/8/2010 Solution & Interoperability Test Lab Application Notes ©2010 Avaya Inc. All Rights Reserved.
4.2. IP Trunks Configuration This section describes how to configure the general IP trunk settings. To configure the general IP trunk settings, go to: Configuration > Resources > IP Trunks > General In the Figure 5 shown below, select the IP Trunk Settings tab and change the Forward redirected OLI value to First Redirect. Figure 5: IP Trunk Settings RS; Reviewed: SPOC 11/8/2010 Solution & Interoperability Test Lab Application Notes ©2010 Avaya Inc. All Rights Reserved.
4.3. Dialing Plan Configuration This section describes how to configure the dialing plan that will be used by the BCM to communicate with the TOL server. To configure the dialing plan, select: Configuration > Telephony > Dialing Plan > Routing Add a route and classify it under BlocA pool as shown in Figure 6 below under the Routes tab. Figure 6: Routes RS; Reviewed: SPOC 11/8/2010 Solution & Interoperability Test Lab Application Notes ©2010 Avaya Inc. All Rights Reserved.
To configure the destination code that the newly added route will use, go to: Configuration > Telephony > Dialing Plan > Routing Add a destination code as shown in Figure 7 below under the Destination Codes tab. Figure 7: Destination Codes The destination code 77 is chosen because the TOL pilot number used in the example is 77777. RS; Reviewed: SPOC 11/8/2010 Solution & Interoperability Test Lab Application Notes ©2010 Avaya Inc. All Rights Reserved.
To configure the private network that this newly added route will use, go to: Configuration > Telephony > Dialing Plan > Private Network Configure the private network as shown in Figure 8 below. Figure 8: Dialing Plan – Private Network The BCM used for compliance testing is set to 5 digit DN length and therefore the same format is used when entering the values for the DN length under the private network. The private network type can be either CDP or UDP depending on the site’s requirement.
4.4. Target Lines Configuration This section describes how to configure target lines which will be assigned to telephones that will be used as endpoints connected to the BCM. To configure a target line, go to: Configuration > Telephony > Lines > Target Lines Select a line, and assign a DN. For example in the Figure 9 shown below, line 410 has been selected and a DN 22624 has been assigned by clicking on the Add button under the Assigned DNs tab.
Also for the assigned set to generate busy tone while it is busy, the Busy tone option in If Busy field found under the Preferences tab has to be selected as shown in Figure 10 below. Figure 10: Busy Tone RS; Reviewed: SPOC 11/8/2010 Solution & Interoperability Test Lab Application Notes ©2010 Avaya Inc. All Rights Reserved.
4.5. Active Sets Configuration This section describes the steps to configure the sets that has been assigned to a line as explained in section 4.4 To configure the Active sets, go to: Configuration > Telephony > Sets > Active Sets In the example shown in Figure 11 below, DN 22624 is assigned to line 410. The Fwd No Answer and Fwd Busy fields under Line Access tab has been populated with 77777, which is the pilot number of the TOL.
Figures 12 and 13 below show the additional configurations to be done to the selected DN which has to be member of the BlocA pool found in the Line Pool Access tab and fields DND on Busy and Allow redirect boxes needs to be enabled. These latter two fields can be found under the Capabilities and Preferences tab. Figure 12: Line Pool RS; Reviewed: SPOC 11/8/2010 Solution & Interoperability Test Lab Application Notes ©2010 Avaya Inc. All Rights Reserved.
Figure 13: Capabilities RS; Reviewed: SPOC 11/8/2010 Solution & Interoperability Test Lab Application Notes ©2010 Avaya Inc. All Rights Reserved.
5. Configuring the ESNA Telephony Office-LinX ESNA installs, configures, and customizes the TOL application for their end customers. Thus, this section only describes the interface configuration, so that the TOL can talk to the BCM R6. Highlighted values are the ones that were configured for the compliance test. For further details on the TOL configuration steps not covered in this document, refer to section 9. The integration of TOL with BCM R6 is done from the TOL’s SIP Configuration Tool.
• • IP Address refers to the IP address of the BCM R6. Port 5060 is the default SIP port value. Figure 15: Advanced • Enable Internal Bridging should be checked. RS; Reviewed: SPOC 11/8/2010 Solution & Interoperability Test Lab Application Notes ©2010 Avaya Inc. All Rights Reserved.
Figure 16: Channels • • Extension No 77777 is the TOL’s pilot number. IP Address is the IP address of the BCM R6. RS; Reviewed: SPOC 11/8/2010 Solution & Interoperability Test Lab Application Notes ©2010 Avaya Inc. All Rights Reserved.
Figure 17: Register • Leave values as default. RS; Reviewed: SPOC 11/8/2010 Solution & Interoperability Test Lab Application Notes ©2010 Avaya Inc. All Rights Reserved.
Figure 18: MWI • Force MWI should be checked. RS; Reviewed: SPOC 11/8/2010 Solution & Interoperability Test Lab Application Notes ©2010 Avaya Inc. All Rights Reserved.
Figure 19: ANI • Integration mode must be set to 0 for the BCM R6 6. General Test Approach and Test Results The general test approach was to place calls to ESNA Telephony Office-LinX, and the main objectives were to verify that the user can: • Successfully establish calls to ESNA Telephony Office-LinX from/to the BCM R6 end points. • Successfully transfer from ESNA Telephony Office-LinX. • Successfully leave messages for subscribers and to retrieve the same.
For serviceability testing, failures such as disconnecting the TOL ELNK cable from the network and rebooting the TOL server were applied. The test objectives were verified. For serviceability testing, ESNA Telephony Office-LinX operated properly after recovering from failures such as cable disconnects, and resets of ESNA Telephony Office-LinX server. 7.
©2010 Avaya Inc. All Rights Reserved. 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.