Download
Share
Print this page
  1. Manuals
  2. Brands
  3. Avaya Manuals
  4. Gateway
  5. AudioCodes MP-118
  6. Configuring

Avaya AudioCodes MP-118 Configuring

Analog voip gateway
Hide thumbs

Advertisement

Quick Links

Download this manual
Avaya Solution & Interoperability Test Lab
Application Notes for Configuring the AudioCodes MP-118
Analog VoIP Gateway with Avaya SIP Enablement Services
and Avaya Communication Manager - Issue 1.0
These Application Notes describe the procedure for configuring the AudioCodes MP-118
Analog VoIP Gateway with Avaya SIP Enablement Services and Avaya Communication
Manager.
The AudioCodes MP-118 Analog VoIP Gateway serves as a gateway between legacy analog
endpoints/trunks at a branch location and a VoIP infrastructure at a main location using the
Session Initiation Protocol (SIP). The MP-118 has 4 FXS (analog endpoint) ports and 4 FXO
(POTS trunk) ports. The compliance test focused on the interoperability of the FXS ports. The
FXO ports were configured only as a failover path to the PSTN if the data WAN is unavailable
and SIP calls can not be made. The ability of these FXO ports to provide local PSTN access
for the branch as part of normal operation is not covered by these Application Notes.
Information in these Application Notes has been obtained through DeveloperConnection
compliance testing and additional technical discussions.
DeveloperConnection Program at the Avaya Solution and Interoperability Test Lab.
CTM; Reviewed:
SPOC 11/29/2007
Abstract
Solution & Interoperability Test Lab Application Notes
©2006 Avaya Inc. All Rights Reserved.
Testing was conducted via the
AudioCodesMP118.doc
1 of 51

Advertisement

loading

Related Manuals for Avaya AudioCodes MP-118

Summary of Contents for Avaya AudioCodes MP-118

  • Page 1 Analog VoIP Gateway with Avaya SIP Enablement Services and Avaya Communication Manager. The AudioCodes MP-118 Analog VoIP Gateway serves as a gateway between legacy analog endpoints/trunks at a branch location and a VoIP infrastructure at a main location using the Session Initiation Protocol (SIP).
  • Page 2 Figure 1 illustrates the configuration used in these Application Notes. In the sample configuration, two sites are connected via an IP network. The main site has an Avaya SES and an Avaya S8300 Media Server running Avaya Communication Manager in an Avaya G350 Media Gateway.
  • Page 3 POTS line is mapped to an extension at the Branch Site which could be used if the data WAN is unavailable. Figure 1: MP-118 Test Configuration CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 3 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...

  • Page 4: Equipment And Software Validated

    All SIP signaling for calls between Avaya Communication Manager and the MP-118 passes through Avaya SES via this trunk group. This section describes the steps for configuring this trunk group and associated signaling group. In addition, this section describes the configuration of stations as OPS stations, which is required for each analog telephone, and fax machine connected to the MP- 118.
  • Page 5 Use the change node-name ip command to assign the node name and IP address for Avaya SES at the enterprise site. In this case, SES and 50.1.1.50 are being used, respectively. The node name SES will be used throughout the other configuration forms of Avaya Communication Manager.
  • Page 6 IP network region. If different IP network regions are used for the Avaya S8300 Media Server and the Avaya SES server, then Page 3 of each IP Network Region form must be used to specify the codec set for inter-region communications.
  • Page 7 Use the change ip-codec-set n command, where n is the codec set value specified in Step 3, to enter the supported audio codecs for calls routed to Avaya SES. Multiple codecs can be listed in priority order to allow the codec to be negotiated during call establishment.
  • Page 8 IP codec set assigned for the inter-region connectivity for the pair of network regions. Enter the domain name of Avaya SES in the Far-end Domain field. In this configuration, the domain name is devcon.com. This domain is specified in the Uniform Resource Identifier (URI) of the SIP “To”...
  • Page 9 ACA Assignment? n Measured: none Maintenance Tests? y Numbering Format: public Prepend '+' to Calling Number? n Replace Unavailable Numbers? n CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 9 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...
  • Page 10 Grp(s) Prefix Create a route pattern that will use the SIP trunk that connects to Avaya SES. In general, a route pattern is not required for calling between SIP endpoints registered to the Avaya SES. This includes the dialing scenarios performed in the compliance test.
  • Page 11 In the compliance test, all SIP endpoints whether at the main or branch site are part of a single location defined in Avaya Communication Manager. This location uses the default name of Main and is shown in the example below. Enter the route pattern number from the previous step in the Proxy Sel.
  • Page 12 Select Last Used Appearance? n Coverage After Forwarding? s Direct IP-IP Audio Connections? y Emergency Location Ext: 40108 IP Audio Hairpinning? n CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 12 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...
  • Page 13 On Page 3, under BUTTON ASSIGNMENTS, create the appropriate number of call appearances for the SIP endpoint being configured. In general, the appropriate number of call appearances on Avaya Communication Manager is the same as the number of call appearances supported by the endpoint. To create a call appearance, enter call- appr as the button assignment.
  • Page 14 (x40110). In this configuration, the MP-118 gateway itself must also be registered as a separate endpoint. For the compliance test, extension 44444 was created for this purpose with the same characteristics as the Avaya SIP telephones at this site.
  • Page 15 4. Configure Avaya SES This section covers the configuration of Avaya SES. Avaya SES is configured via an Internet browser using the administration web interface. It is assumed that Avaya SES software and the license file have already been installed on the server. During the software installation, the installation script is run from the Linux shell of the server to specify the IP network properties of the server along with other parameters.
  • Page 16 Step Description The Avaya SES Administration Home Page will be displayed as shown below. CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 16 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...
  • Page 17 Update link found in the bottom of the blue navigation bar on the left side of any of the Avaya SES administration pages as shown below. It is recommended that this be done after making each set of changes described in the following steps.
  • Page 18 SES Version field and the network properties entered during the installation process. On the Edit System Properties page: Enter the SIP Domain name assigned to Avaya SES. This must match the Authoritative Domain field configured on Avaya Communication Manager shown in Section 3, Step 3.
  • Page 19 Edit link under the Commands section of the subsequent page that is displayed. In the Host IP Address field, enter the IP address of the Avaya SES. Enter the DB Password that was specified during the system installation.
  • Page 20 From the left pane of the administration web interface, expand the Media Servers option and select Add to add the Avaya Media Server to the list of media servers known to Avaya SES. Adding the media server will create the Avaya SES side of the SIP trunk previously created in Avaya Communication Manager.
  • Page 21 Step Description A user must be added on Avaya SES for each of the extensions at the branch office created on Avaya Communication Manager in Section 3, Steps 13 – 17 including the extension created for the MP-118 gateway itself. From the left pane, navigate to Users Add.
  • Page 22 Click the Add button to complete the operation. Repeat Steps 7 - 8 for each of the remaining stations at the branch office. CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 22 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...
  • Page 23 The following pop-up window will appear. Login with the proper credentials. The MP-118 main page will appear as shown below. CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 23 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...
  • Page 24 Address, Subnet Mask and Default Gateway Address were set to values consistent with the test configuration shown in Figure 1. The Media Premium QoS must match the Audio PHB Value set on Avaya Communication Manager in Section 3, Step 3. Default values may be retained for all other values.
  • Page 25 To access these parameters, select Protocol Management in the left pane and navigate to Protocol Definition in the right pane. The pull-down choices for Protocol Definition are shown below. CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 25 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...
  • Page 26 For the Enable Proxy Keep Alive field, select Using Options from the pull- down menu. The MP-118 will use the SIP OPTIONS message as a handshake mechanism with the Avaya SES to determine if the SIP connection is up. If the connection is down, the MP-118 will failover to the FXO ports.
  • Page 27 Description Configure the parameters as described below. In the Gateway Name field, enter the IP address of the Avaya SES. In this configuration, the MP-118 requires that a separate extension be assigned to the gateway itself. In the User Name field, enter the extension created for this purpose in Section 3, Step 18.
  • Page 28 Default values may be retained for all other fields. Scroll down to the bottom of the page and click Submit (not shown). CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 28 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...
  • Page 29 This list must have an overlap with the list provided on Avaya Communication Manager in Section 3, Step 4. The codec is selected from the pull-down menu under the Coder Name field.
  • Page 30 Select 127 as the RFC 2833 Payload Type to match the value used by the Avaya SIP Telephones. Media may not be redirected (shuffled) in all scenarios from Avaya Communication Manager to the endpoints if this value is not the same as the SIP Telephones.
  • Page 31 To access these parameters, select Protocol Management in the left pane and navigate to Advanced Parameters in the right pane. The pull-down choices for Advanced Parameters are shown below. CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 31 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...
  • Page 32 For the compliance test, there were 4 FXS ports and 4 FXO ports. Default values may be retained for all other fields. Click Submit. CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 32 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...
  • Page 33 Default values may be retained for all other fields. Scroll down to the bottom of the page and click Submit (not shown). CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 33 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...
  • Page 34 To access these parameters, select Protocol Management in the left pane and navigate to Manipulation Tables in the right pane. The pull-down choices for the Manipulation Tables are shown below. CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 34 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...
  • Page 35 9 + the 11-digit PSTN number for an outbound call. The call is forwarded to the Avaya Communication Manager where the 9 is stripped off before being routed to the PSTN. If the data WAN is unavailable, the call is still originated as an IP call but can not be sent to the Main site.
  • Page 36 To access these parameters, select Protocol Management in the left pane and navigate to Routing Tables in the right pane. The pull-down choices for the Routing Tables are shown below. CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 36 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...
  • Page 37 This table defines the mapping of analog calls to an IP address that will process the IP leg of the call if the proxy defined in Step 6 (Avaya SES) is not available. The Dest. Phone Prefix and Source Phone Prefix columns define which calls are mapped to the IP address in the Dest.
  • Page 38 40108 - 40111. The second entry routes any other call to hunt group 2. Even though Avaya Communication Manager will not route any other calls to the MP-118 except calls to the extensions 40108 –...
  • Page 39 5 is set to the Caller ID information received from the PSTN trunk. Click Submit. CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 39 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...
  • Page 40 FXO ports since it is not intended that the FXO ports be accessed using the gateway extension. Click Submit. CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 40 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...
  • Page 41 Authentication. The Authentication page defines a username and password combination for authentication of each MP-118 port with the Avaya SES. Enter a User Name and Password that matches the values configured on Avaya SES in Section 4, Step 7. Click Submit.
  • Page 42 FXO port was connected. The destination extension is placed in the Destination Phone Number column. Click Submit. CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 42 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...
  • Page 43 Select Yes for Answer Supervision. Default values may be retained for all other fields. Click Submit. CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 43 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...
  • Page 44 To access these parameters, select Advanced Configuration in the left pane and navigate to Media Settings in the right pane. The pull-down choices for Media Settings are shown below. CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 44 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...
  • Page 45 Select T.38 Relay for the Fax Transport Mode to support faxing across the data WAN. Select Enable Bypass for the V.22 – V.34 Modem Transport Types to support modem calls over SIP planned in future Avaya Communication Manager releases. Select G711Mulaw for the Fax/Modem Bypass Coder Type.
  • Page 46 Step Description For proper modem interoperability over SIP planned for future Avaya Communication Manager releases, an additional parameter must be changed in the ini file. From a web browser, enter <ip_address>/AdminPage in the Address field where <ip_address> is the IP address of the MP-118. The main page will appear as shown below.
  • Page 47 To save the configuration, return to the administrative web page and select Maintenance in the left pane. Click the BURN button. CTM; Reviewed: Solution & Interoperability Test Lab Application Notes 47 of 51 SPOC 11/29/2007 ©2006 Avaya Inc. All Rights Reserved. AudioCodesMP118.doc...

  • Page 48: Interoperability Compliance Testing

    PBX features. This testing included the analog telephones, and Avaya SIP telephones. The calls were made to/from the main site, the PSTN and within the branch site. The same test cases, where applicable, were repeated with a simulated data WAN outage.

  • Page 49: Verification Steps

    • From the Avaya Communication Manager SAT, use the status trunk-group command to verify that the SIP trunk group is in-service. • From the Avaya SES web administration interface, verify that all endpoints behind the MP- 118 are registered with the Avaya SES.
  • Page 50 [8] LTRT-65406 MediaPack SIP User’s Manual, Version 5.0. [9] LTRT-65607 MediaPack & Mediant 1000 SIP Analog Gateways Release Notes, Version 5.0. Product documentation for Avaya products may be found at http://support.avaya.com. Product documentation for AudioCodes MP-118 Analog VoIP Gateway products may be found at http://www.audiocodes.com. CTM; Reviewed: Solution &...
  • Page 51 2006 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.