Configuring The Innomedia Mta 3328-8 Gateway

Transcript

Avaya Solution & Interoperability Test Lab Configuring the InnoMedia MTA 3328-8 Gateway with Avaya SIP Enablement Services and Avaya Communication Manager - Issue 1.0 Abstract These Application Notes describe the procedures for configuring the InnoMedia MTA 3328-8 Gateway to communicate via a SIP interface with Avaya SIP Enablement Services and Avaya Communication Manager. The InnoMedia MTA 3328-8 functions as an analog/SIP gateway between IP-based PBX systems and analog devices such as telephones, fax machines and modems. When connected to the InnoMedia MTA 3328-8 in a test configuration representing a hosted telephony environment, analog endpoints at the customer enterprise site are able to register as SIP endpoints with Avaya SIP Enablement Services at the service provider data center. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 1 of 47 Innomedia_SIP.doc 1. Introduction These Application Notes describe the procedures for configuring the InnoMedia MTA 3328-8 Gateway to communicate via a SIP interface with Avaya SIP Enablement Services and Avaya Communication Manager. The InnoMedia MTA 3328-8 functions as an analog/SIP gateway between IP-based PBX systems and analog devices such as telephones, fax machines and modems. When connected to the InnoMedia MTA 3328-8 in a test configuration representing a hosted telephony environment, up to eight analog endpoints at the customer enterprise site are able to register as SIP endpoints with Avaya SIP Enablement Services at the service provider data center. 2. Test Configuration Figure 1 illustrates the reference configuration used for these Application Notes. This configuration approximates a hosted telephony environment, with a service provider data center supporting two customer enterprise sites. Located at the service provider data center are an Avaya SIP Enablement Services server, Avaya Communication Manager (on an Avaya S8500 Media Server), and an Avaya G650 Media Gateway. The enterprise customer sites connect to the service provider data center over an IP network. Each enterprise customer site includes an InnoMedia MTA 3328-8 analog/SIP gateway with a variety of analog endpoint devices (telephones, fax, modem) connected to it, as well as a set of Avaya 4600 Series IP telephones. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 2 of 47 Innomedia_SIP.doc Figure 1: Reference Configuration DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 3 of 47 Innomedia_SIP.doc 3. Equipment and Software Validated The following equipment and software/firmware were used for the reference configuration provided: Equipment Avaya S8500 Media Server Avaya G650 Media Gateway • C-LAN • Media Processor Avaya SIP Enablement Services Avaya 4610SW IP Telephones Avaya 4620SW IP Telephones InnoMedia MTA 3328-8 Analog/SIP Gateway Analog Telephones Fax Machines PCs with Modem Software/Firmware Avaya Communication Manager 3.1.2 (R013x.01.0.632.1) HW01 FW017 HW20 FW110 3.1 (3.1.0.0-018.0) 2.2 (H.323) 2.4 (H.323) Image:V2.8.116 Controller: V1.18.117 SIPMTA 3328 (t38 test) Thu Jun 1 DSP Code: V2.4.22 BBS: V7.1.38 SIP Stack: V2.9.127 Windows 2000 Professional 4. Configure Avaya Communication Manager This section details the administration on Avaya Communication Manager to integrate with Avaya SIP Enablement Services and to enable the analog telephones connected to the InnoMedia MTA 3328-8 to register as SIP endpoints. The commands listed in the following sections were issued at the Avaya System Access Terminal (SAT) screen to configure the Avaya S8500 Media Server. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 4 of 47 Innomedia_SIP.doc 4.1. Configure Integration with Avaya SIP Enablement Services A SIP network interface must be configured between Avaya Communication Manager and Avaya SIP Enablement Services. This interface is a trunk group that handles all SIP signaling between Avaya SIP Enablement Services (which interfaces with the InnoMedia MTA 3328-8 gateways as a SIP proxy) and Avaya Communication Manager. The steps described below enable the features and create the administrative objects necessary to support this interface. Step 1. Description Enter display system-parameters customer-options and advance to Page 2. Under the IP PORT CAPACITIES section, confirm that the Maximum Administered SIP Trunks is enough to support the expected traffic to and from each InnoMedia MTA 3328-8 gateway. Any call involving a SIP endpoint (e.g., an analog telephone connected to an InnoMedia MTA 3328-8) will use a SIP trunk per SIP endpoint. If the capacity indicated is deemed insufficient, an authorized Avaya support technician will need to install an appropriately enabled license file. display system-parameters customer-options OPTIONAL FEATURES Page IP PORT CAPACITIES Maximum Administered H.323 Trunks: Maximum Concurrently Registered IP Stations: Maximum Administered Remote Office Trunks: Maximum Concurrently Registered Remote Office Stations: Maximum Concurrently Registered IP eCons: Max Concur Registered Unauthenticated H.323 Stations: Maximum Video Capable H.323 Stations: Maximum Video Capable IP Softphones: Maximum Administered SIP Trunks: Maximum Number of DS1 Boards with Echo Cancellation: Maximum TN2501 VAL Boards: Maximum G250/G350/G700 VAL Sources: Maximum TN2602 Boards with 80 VoIP Channels: Maximum TN2602 Boards with 320 VoIP Channels: Maximum Number of Expanded Meet-me Conference Ports: 800 2400 0 0 0 0 0 0 800 USED 0 4 0 0 0 0 0 0 200 0 1 0 0 0 0 0 0 0 0 0 0 2 of 10 (NOTE: You must logoff & login to effect the permission changes.) DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 5 of 47 Innomedia_SIP.doc Step 2. Description Enter change node-names ip to add the name (in this example, ses) and IP address (in this example, 192.168.10.50) for Avaya SIP Enablement Services. Note also the administered CLAN IP interface in the Avaya G650 Media Gateway (CLAN, 192.168.10.43); this will be used in Section 5, Step 5 to create the Media Server Interface in Avaya SIP Enablement Services. change node-names ip Name CLAN MEDPRO default procr ses DH; Reviewed: SPOC 9/27/06 Page IP Address 192.168.10 .43 192.168.10 .42 0 .0 .0 .0 192.168.10 .40 192.168.10 .50 . . . . . . . . . IP NODE NAMES Name Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 1 of 1 IP Address . . . . . . . . . . . . . . . . . . . . . . . . 6 of 47 Innomedia_SIP.doc Step 3. Description Enter change ip-codec-set n (where n is the number of the codec set specified in Step 4 below) to specify the audio codecs to be used for calls routed to and from the InnoMedia MTA 3328-8 via Avaya SIP Enablement Services. The order of the codecs listed will determine the negotiating preference for each call established. A prime consideration is whether voice quality is more important than bandwidth utilization (e.g., the higher bandwidth used by the G.711 codecs corresponds to better quality). The codecs must be among those supported by the InnMedia MTA 3328-8. For advanced configuration, see Section 7.2. change ip-codec-set 1 Page 1 of 2 IP Codec Set Codec Set: 1 Audio Codec 1: G.711MU 2: G.729AB 3: 4: 5: 6: 7: Silence Suppression n n Frames Per Pkt 2 2 Packet Size(ms) 20 20 On Page 2, enter t.38-standard in the FAX field if T.38 will be used for fax transmissions. Data modem calls are supported with the default value (off) in the Modem field. change ip-codec-set 1 Page 2 of 2 IP Codec Set Allow Direct-IP Multimedia? n FAX Modem TDD/TTY Clear-channel DH; Reviewed: SPOC 9/27/06 Mode t.38-standard off US n Redundancy 0 0 3 0 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 7 of 47 Innomedia_SIP.doc Step 4. Description Enter change ip-network-region n, where n is the IP network region where the Avaya SIP Enablement Services server will reside, to define the connectivity settings for all VoIP resources and IP endpoints within that region. In this example, region 1, the default region for the Media Server running Avaya Communication Manager, was used. The following fields should be considered: • • • Authoritative Domain: Enter a value that matches the SIP Domain of the Avaya SIP Enablement Services server (in this example, abcd.com). Intra-region IP-IP Direct Audio, Inter-region IP-IP Direct Audio: Keep the default value of yes for each of these fields to allow audio traffic to be sent directly between IP endpoints without using media resources in the Avaya G650 Media Gateway (a feature known as “shuffling”). Codec Set: Enter the IP codec set specified in Step 3. This determines the set of codecs to be used for calls within this IP network region. Since the Avaya S8500 Media Server and the Avaya SIP Enablement Services server are in the same region in this example, all calls to and from any IP phone (H.323 or SIP) within the enterprise will use this codec set. If the Avaya S8500 Media Server and the Avaya SIP Enablement Services server are placed in separate regions, then calls between analog telephones connected to the InnoMedia MTA 3328-8 and other IP phones (such as the Avaya 4600 Series IP telephones in this example) would be subject to the codec set specifications on Page 3 of the corresponding IP Network Region forms. change ip-network-region 1 Page 1 of 19 IP NETWORK REGION Region: 1 Location: Authoritative Domain: abcd.com Name: CM MEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes Codec Set: 1 Inter-region IP-IP Direct Audio: yes UDP Port Min: 2048 IP Audio Hairpinning? n UDP Port Max: 65531 DIFFSERV/TOS PARAMETERS RTCP Reporting Enabled? y Call Control PHB Value: 46 RTCP MONITOR SERVER PARAMETERS Audio PHB Value: 46 Use Default Server Parameters? y Video PHB Value: 26 802.1P/Q PARAMETERS Call Control 802.1p Priority: 6 Audio 802.1p Priority: 6 Video 802.1p Priority: 5 AUDIO RESOURCE RESERVATION PARAMETERS H.323 IP ENDPOINTS RSVP Enabled? n H.323 Link Bounce Recovery? y Idle Traffic Interval (sec): 20 Keep-Alive Interval (sec): 5 Keep-Alive Count: 5 DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 8 of 47 Innomedia_SIP.doc Step 5. Description Enter add signaling-group n to create a new SIP signaling group (to be used by the SIP trunk group to be created in Step 6). In this example, signaling group 1 was created. The following fields should be considered: • • • • • • • • Group Type: Enter sip. Near-end Node Name: Enter the node name for the CLAN supporting the Avaya S8500 Media Server (in this example, CLAN). For Media Server platforms that do not use CLAN boards, procr would be specified here. Far-end Node Name: Enter the node name for the Avaya SIP Enablement Services server (in this example, ses). Far-end Listen Port: Enter 5061 (the recommended TLS port value). Far-end Network Region: Enter the IP Network Region from Step 4. This determines which IP network region contains the Avaya SIP Enablement Services server. Far-end Domain: Enter the domain name of the Avaya SIP Enablement Services server (in this example, abcd.com). DTMF over IP: Enter rtp-payload. This allows Avaya Communication Manager to send DTMF tones using RFC 2833, which will be enabled as well on the InnoMedia MTA 3328-8 (see Section 6, Step 6). Direct IP-IP Audio Connections: Enter y to enable shuffling between the nearend and far-end IP endpoints. add signaling-group 1 Page 1 of 1 SIGNALING GROUP Group Number: 1 Group Type: sip Transport Method: tls Near-end Node Name: CLAN Near-end Listen Port: 5061 Far-end Node Name: ses Far-end Listen Port: 5061 Far-end Network Region: 1 Far-end Domain: abcd.com Bypass If IP Threshold Exceeded? y DTMF over IP: rtp-payload Direct IP-IP Audio Connections? y IP Audio Hairpinning? y Session Establishment Timer(min): 120 DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 9 of 47 Innomedia_SIP.doc Step 6. Description Enter add trunk-group n to create a new SIP trunk group. In this example, trunk group 1 was created. On Page 1, enter the following values: • • • • • • Group Type: Enter sip. Group Name: Enter a descriptive name. TAC: Enter a valid trunk access code. Service Type: Enter tie. Signaling Group: Enter the number of the signaling group created in Step 5. Number of Members: Enter an appropriate number of SIP trunks, not exceeding the maximum number of available SIP trunks as indicated in Step 1. add trunk-group 1 Page 1 of 21 TRUNK GROUP Group Number: Group Name: Direction: Dial Access? Queue Length: Service Type: 1 siproute two-way n 0 tie Group Type: sip COR: 0 Outgoing Display? n TN: 1 CDR Reports: y TAC: 701 Night Service: Auth Code? n Signaling Group: 1 Number of Members: 100 On Page 3, specify the following value: • Numbering Format: Enter public. This determines the outgoing calling party number format. change trunk-group 1 TRUNK FEATURES ACA Assignment? n Page 3 of 21 Measured: none Maintenance Tests? y Numbering Format: public Prepend '+' to Calling Number? n Replace Unavailable Numbers? n DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 10 of 47 Innomedia_SIP.doc Step 7. Description Enter change route-pattern n to administer the route pattern that will be used to direct outgoing SIP calls to Avaya SIP Enablement Services. In this example, route pattern 1 was used. Enter the following values: • • • Pattern Name: Enter a descriptive name. Grp No: Enter the number of the SIP trunk group created in Step 6. FRL: Enter a Facility Restriction Level for this entry in the route pattern, from 0 (least restrictive, i.e., all originating SIP endpoints can used this entry) to 7 (most restrictive). change route-pattern 1 Pattern Number: 1 Pattern Name: siproute SCCAN? n Secure SIP? n Grp FRL NPA Pfx Hop Toll No. Inserted No Mrk Lmt List Del Digits Dgts 1: 1 0 2: 3: 4: 5: 6: 1: 2: 3: 4: 5: 6: DH; Reviewed: SPOC 9/27/06 BCC VALUE TSC CA-TSC 0 1 2 3 4 W Request ITC BCIE Service/Feature PARM y y y y y y rest rest rest rest rest rest y y y y y y y y y y y y y y y y y y y y y y y y n n n n n n n n n n n n Page 1 of 3 DCS/ QSIG Intw n n n n n n IXC user user user user user user No. Numbering LAR Dgts Format Subaddress none none none none none none Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 11 of 47 Innomedia_SIP.doc Step 8. Description Enter change locations to assign the above-configured route pattern to a location. This assignment is necessary to enable SIP endpoints to use certain features, such as Transfer. The reference configuration as a whole is in the default location (Main). Enter the following value: • Proxy Sel. Rte. Pat.: Enter the number of the route pattern configured in Step 7. change locations Page 1 of 16 LOCATIONS ARS Prefix 1 Required For 10-Digit NANP Calls? y Loc. Name No. 1: Main 2: 3: 4: 5: 6: 7: 8: DH; Reviewed: SPOC 9/27/06 Timezone Rule Offset + 00:00 0 : : : : : : : NPA ARS FAC Attd FAC Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. Prefix Proxy Sel. Rte. Pat. 1 12 of 47 Innomedia_SIP.doc 4.2. Configure Analog/SIP Endpoints This section provides the steps to enable analog endpoints connected to the InnoMedia MTA 3328-8 gateway to be treated as SIP stations by Avaya Communication Manager. These endpoints are administered as Off-PBX Station (OPS) extensions that are accessed via a SIP trunk group. For more details, see [6] and [7]. Step 1. Description Enter display system-parameters customer-options and examine Page 1 to confirm that the license file has allocated enough OPS extensions (Maximum Off-PBX Telephones – OPS) to support all enterprise sites. If not, an authorized Avaya support technician will need to install an appropriately enabled license file. display system-parameters customer-options OPTIONAL FEATURES G3 Version: V13 Location: 1 Platform: 12 Page 1 of 10 RFA System ID (SID): 1 RFA Module ID (MID): 1 Platform Maximum Ports: Maximum Stations: Maximum XMOBILE Stations: Maximum Off-PBX Telephones - EC500: Maximum Off-PBX Telephones OPS: Maximum Off-PBX Telephones - SCCAN: 3200 2400 0 2400 2400 0 USED 231 21 0 0 16 0 (NOTE: You must logoff & login to effect the permission changes.) DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 13 of 47 Innomedia_SIP.doc Step 2. Description Enter change off-pbx-telephone configuration-set n to assign call treatment options to Off-PBX telephones. In this example, configuration set 1 was administered. Modify the following value: • Fast Connect on Origination?: Enter y. This enables Avaya Communication Manager to carry out some additional processing before establishing a call. change off-pbx-telephone configuration-set 1 Page 1 of 1 CONFIGURATION SET: 1 Configuration Set Description: Calling Number Style: CDR for Origination: CDR for Calls to EC500 Destination? Fast Connect on Origination? Post Connect Dialing Options: Cellular Voice Mail Detection: Barge-in Tone? Calling Number Verification? Identity When Bridging: 3. 1 network phone-number y y dtmf none n y principal Enter add station x (where x is an available valid extension in the dial plan) to create a station extension for an analog/SIP endpoint. Enter the following values on Page 1: • • • Type: Set to 6408D+ (the default). Port: Enter X. This indicates that the station is Administered Without Hardware (AWOH), i.e., not assigned to a specific port on Avaya Communication Manager. Name: Enter a descriptive name. add station 2346240 Page 1 of 4 STATION Extension: Type: Port: Name: 2346240 6408D+ X CM CustA A1 STATION OPTIONS Loss Group: Data Module? Speakerphone: Display Language: Lock Messages? n Security Code: Coverage Path 1: Coverage Path 2: Hunt-to Station: 2 n 2-way english BCC: TN: COR: COS: 0 1 1 1 Personalized Ringing Pattern: 2 Message Lamp Ext: 2346240 Mute Button Enabled? y Media Complex Ext: IP SoftPhone? n DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 14 of 47 Innomedia_SIP.doc Step 4. Description On Page 2 of this Station form, enter the following value: • Direct IP-IP Audio Connections: Enter y to enable shuffling calls involving this station. add station 2346240 Page 2 of 4 STATION FEATURE OPTIONS LWC Reception: LWC Activation? LWC Log External Calls? CDR Privacy? Redirect Notification? Per Button Ring Control? Bridged Call Alerting? Active Station Ringing: spe y n n y n y single H.320 Conversion? n Service Link Mode: as-needed Multimedia Mode: basic MWI Served User Type: AUDIX Name: Emergency Location Ext: 2346240 DH; Reviewed: SPOC 9/27/06 Auto Select Any Idle Appearance? Coverage Msg Retrieval? Auto Answer: Data Restriction? Idle Appearance Preference? Bridged Idle Line Preference? Restrict Last Appearance? Conf/Trans on Primary Appearance? n y none n n n y n Per Station CPN - Send Calling Number? Display Client Redirection? n Select Last Used Appearance? n Coverage After Forwarding? s Direct IP-IP Audio Connections? y IP Audio Hairpinning? y Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 15 of 47 Innomedia_SIP.doc Step 5. Description On Page 3 of this Station form, enter the following BUTTON ASSIGNMENTS: • • • Add at least two call appearances (call-appr) to enable the station to originate a second call, carry out a call transfer, etc. Add a no-hold-conference (no-hld-cnf) button to allow the station to activate the Conference on Answer feature. Add an auto-callback (auto-cback) button to allow the station to activate the Automatic Callback feature. add station 2346240 Page 3 of 4 STATION SITE DATA Room: Jack: Cable: Floor: Building: Headset? Speaker? Mounting: Cord Length: Set Color: ABBREVIATED DIALING List1: group BUTTON ASSIGNMENTS 1: call-appr 2: call-appr 3: call-appr 4: no-hld-cnf DH; Reviewed: SPOC 9/27/06 1 List2: n n d 0 List3: 5: auto-cback 6: 7: 8: Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 16 of 47 Innomedia_SIP.doc Step 6. Description Enter add off-pbx-telephone station-mapping to map the new station extension to an OPS station. Enter the following values in the first available row: • • • • • Station Extension: Enter the extension of the station created in Step 3. Application: Enter OPS. Phone Number: Enter the phone number of the associated Off-PBX Telephone, i.e. the analog telephone connected to the InnoMedia MTA 3328-8. Trunk Selection: Enter the number of the SIP trunk group created in Section 4.1, Step 6 (in this example, 1). Configuration Set: Enter the number of the Configuration set administered in Step 2. add off-pbx-telephone station-mapping 2346240 STATIONS WITH OFF-PBX TELEPHONE INTEGRATION Station Extension 2346240 7. Application OPS Dial Phone Number Prefix - 2346240 - Trunk Selection 1 Page 1 of 2 Configuration Set 1 Repeat Steps 3-6 for each additional analog/SIP endpoint connected to the InnoMedia MTA 3328-8 gateway. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 17 of 47 Innomedia_SIP.doc Step 8. Description Enter change off-pbx-telephone feature-name-extensions to administer the FNEs that will be used by the analog/SIP endpoints to activate certain Avaya Communication Manager features. The FNEs shown in bold were the subset that were tested in the reference configuration. change off-pbx-telephone feature-name-extensions EXTENSIONS TO CALL WHICH ACTIVATE FEATURES BY NAME Active Appearance Select: Automatic Call Back: Automatic Call-Back Cancel: Call Forward All: Call Forward Busy/No Answer: Call Forward Cancel: Call Park: Call Park Answer Back: Call Pick-Up: Conference on Answer: Calling Number Block: Calling Number Unblock: Directed Call Pick-Up: Drop Last Added Party: Exclusion (Toggle On/Off): Extended Group Call Pickup: Held Appearance Select: DH; Reviewed: SPOC 9/27/06 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 Page Idle Appearance Select: Last Number Dialed: Malicious Call Trace: Malicious Call Trace Cancel: Off-Pbx Call Enable: Off-Pbx Call Disable: Priority Call: Send All Calls: Send All Calls Cancel: Transfer On Hang-Up: Transfer to Voice Mail: Whisper Page Activation: Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 1 of 1 327 328 331 332 333 334 335 336 337 338 18 of 47 Innomedia_SIP.doc 5. Configure Avaya SIP Enablement Services This section addresses the administrative steps to be performed on Avaya SIP Enablement Services. The installation of the Avaya SIP Enablement Services software and license file, as well as the initial configuration of the server, is beyond the scope of this document. Please see [3] for the details of these procedures. Step 1. Description To administer Avaya SIP Enablement Services, navigate to http:///admin (where is the IP address of the Avaya SIP Enablement Services server) from a Web browser. After logging in with an appropriate login and password, the main page appears. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 19 of 47 Innomedia_SIP.doc Step 2. Description Click on the Launch Administration Web Interface link. The Administration Home Page appears. NOTE: After making each of the changes described in this section, use the Update link, found at the bottom of the blue navigation pane, or the Update button, at the end of the completed form, to commit the changes to the Avaya SIP Enablement Services database. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 20 of 47 Innomedia_SIP.doc Step 3. Description From the blue navigation pane, select Server Configuration → System Properties. On the Edit System Properties page, enter the following values: ƒ ƒ SIP Domain: This must match the Authoritative Domain field configured on the IP Network Region form in Avaya Communication Manager shown in Section 4.1, Step 4. In this example, abcd.com is used. License Host: Enter the host name, the fully qualified domain name, or the IP address of the WebLM server where the license file for this Avaya SIP Enablement Services server is installed. In this example, the WebLM server is co-resident with the Avaya SIP Enablement Services server (IP address 192.168.10.50). The completed form appears as follows. Click Update to submit the form. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 21 of 47 Innomedia_SIP.doc Step 4. Description From the blue navigation pane, select Hosts, then select Edit on the next page. The Edit Host page appears. Enter the following values: • • • • Host IP Address: Enter the Logical IP or Logical Name (from the Edit System Properties form in Step 3). DB Password: This is the password that was entered during execution of the system installation script. (See [3] for details.) Host Type: This field indicates whether this Avaya SIP Enablement Services server functions as a “home” or “edge” server. Since, in this example, only a single Avaya SIP Enablement Services server is used, enter home/edge. Keep all other default values. The completed form appears as follows. Click Update to submit the form. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 22 of 47 Innomedia_SIP.doc Step 5. Description From the blue navigation pane, select Media Server → Add. The Add Media Server page appears. Enter the following values: ƒ ƒ ƒ ƒ ƒ Media Server Interface Name: Enter a descriptive name (in this example, S8500clan). Host: Select the name or IP address of the Avaya SIP Enablement Services server from the drop-down menu (in this example, 192.168.10.50). SIP Trunk Link Type: Select TLS (Transport Link Security). SIP Trunk IP Address: Enter the IP address of an Avaya Communication Manager’s CLAN board from Section 4.1, Step 5. (For Media Server platforms that do not use CLAN boards, the IP address of the Avaya Media Server (i.e. the processor) would be specified here.) Keep all other default values. The completed form appears as follows. Click Add to submit the form. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 23 of 47 Innomedia_SIP.doc Step 6. Description SIP users (identified by their corresponding telephone extensions) must be added. From the blue navigation pane, select User → Add. Enter the following values: ƒ ƒ ƒ ƒ ƒ ƒ ƒ Primary Handle: This specifies a user in Avaya SIP Enablement Services (in this example, 2346240). While not required, it is recommended that the Primary handle be the same as the User ID. User ID: The User ID (together with the Password) is used to authenticate a user in Avaya SIP Enablement Services. It must match a User ID configured on the InnoMedia MTA 3328-8 for an analog telephone in Section 6, Step 15. Password: This must match the password associated with the corresponding User ID configured on the InnoMedia MTA 3328-8 for an analog telephone in Section 6, Step 15. Confirm Password: Re-enter the above Password. Host: Select from the drop-down menu the host name or IP address of the Avaya SIP Enablement Services server (in this example, 192.168.10.50). First Name, Last Name: Enter descriptive values. Add Media Server Extension: Check this box to add an OPS extension for the user (see Step 8). The completed form appears as follows. Click Add to submit the form. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 24 of 47 Innomedia_SIP.doc Step 7. 8. Description On the page that follows (see below), click Continue. The Add Media Server Extension page will appear as follows. Enter the following values: ƒ ƒ Extension: Enter the OPS extension corresponding to the station configured in Avaya Communication Manager. See Section 4.2, Step 6. Media Server: Select the Media Server added in Step 5 (in this example, S8500clan). The completed form appears as follows. Click Add to submit the form. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 25 of 47 Innomedia_SIP.doc Step Description 9. Repeat Steps 6-8 to add additional users to support the remaining analog/SIP telephones at the enterprises. 10. To view the configured users, select Users → List from the blue navigation pane. 11. To view the configured extensions, select Media Server Extensions → List from the blue navigation pane. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 26 of 47 Innomedia_SIP.doc Step Description 12. A Media Server Address Map must be administered to enable FAC and FNE entries to be routed to the appropriate Avaya Communication Manager. SIP call requests are made via an INVITE message, which includes as its destination a Uniform Resource Identifier (URI). Generally, the URI is of the form sip:@ where is either a domain name or an IP address. For the reference configuration, a SIP URI in an INVITE message specifying the user created in Step 6 would look like the following: sip: [email protected] Use the following steps to configure a Media Server Address Map: ƒ ƒ ƒ From the blue navigation pane, select Media Servers → List. The List Media Servers page appears. Select the Map link associated with the appropriate Media Server. The List Media Server Address Map page appears. Select the Add Map In New Group link. The Add Media Server Address Map page appears. Enter the following values: o Name: Enter a descriptive value (in this example, FAC8). o Pattern: Enter the regular expression to be used for pattern matching. In this example, pattern specification for station extensions is given: ^sip:8[0-9]{2}. This expression will match any URI that begins with the text string “sip:8” (the ^ matches the beginning of the line) and ending with any other combination of two digits. Any matching FACs or FNEs will then be routed to the Media Server associated with this Address Map (in this example, S8500clan). (See [4] for more details on address map syntax.) o Replace URI: Keep the default (√). The completed form appears as follows. Click Add to submit the form. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 27 of 47 Innomedia_SIP.doc Step DH; Reviewed: SPOC 9/27/06 Description Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 28 of 47 Innomedia_SIP.doc Step 13. Description After submitting the previous form, the List Media Server Address Map page appears as follows, showing an entry for the newly created Address Map. Notice that the list includes additional Address Maps. These were created to support the use of other commonly used dial strings (Abbreviated Dial Codes, etc). The procedures used to create them are similar to those shown in Step 12, but are not included here. In addition, a Media Server Contact is created automatically after the first Media Server Address Map is added. The contact specifies the IP address of the Avaya S8500 Media Server (in this example, 192.168.10.43) and the transport protocol used to send SIP signaling messages. The user in the original request URI is substituted for $(user). 6. Configure the InnoMedia MTA 3328-8 Gateway The InnoMedia MTA 3328-8 gateway provides both browser-based and command-line-based (Telnet or COM port access) administrative interfaces; however, since the full range of necessary configuration features is supported only via the command line interface (CLI), the steps in this section use only the CLI. In the CLI displays shown in this section, user-entered strings are shown in italics. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 29 of 47 Innomedia_SIP.doc Step 1. Description Connect to the InnoMedia MTA 3328-8 command line interface via either a Telnet interface or a terminal emulation program (e.g., HyperTerminal). The default IP address of the InnoMedia MTA 3328-8 is 192.168.99.1. Enter the Username (Admin) and default Password (see [8]). A list of available commands is displayed as follows. Enter Username:Admin Enter Password:******** C: Configuration: Operation Database Cd: Configuring VoIP DigitMap Ct: Configure FXS Setting Parameters Cs: Configuring SIP Settings Cu: Configuring User Account Database Cv: Configure VLAN Setting Cr: Enable/Disable Polarity Reversal C3: Enable/Disable Call Features C: Configuration: IP Information Cf: Display the Current IP Information Ci: Configure the IP Information Cw: Change Password E: Exiting and Logout G: Voice Volume Control Ga: Set Voice Volume for Each Channel H: Help Menu I: Information Id: Display Ig: Display Is: Display Ix: Display It: Display M: Miscellaneous Me: Configure DHCP parameters Mf: Configure Hook Flash Timer Mn: Selectable Configuration of IP Elements Mp: Configure Phone lines Mh: Show Syslog Mi: Configure SNTP server Mq: Configure Syslog server Mm: Configure Remote Services P: Provisioning Pv: Configure Provisioning setting Pr: Trigger Provisioning About this System VoIP DigitMap Voice Volume Level the State of All Ports/Lines network connection and UA registration status FXS Setting Parameters V: Version number R: Reset System DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 30 of 47 Innomedia_SIP.doc Step 2. Description Enter Ci to configure IP information. The following menu is displayed: Ci 1. 2. 3. 4. 5. 6. 9. 3. Configure Local IP Set DNS IP(s) SIP Proxy Server And SIP Domain Change IP Settings for All Configure other Local Host settings Configure Provisioning Server(obsolete) Configure MTA Web Server Port Enter 1 to modify the current IP address information. Respond to the prompts that follow with the appropriate values. The values shown here were used for one of the InnoMedia MTA 3328-8 gateways in the reference configuration. 1 Do you use DHCP to get dynamic IP address and IP mask? [y/n] n Please enter the Gateway FQDN : Input name is : Please enter your IP address... Example: 192.45.6.4 192.168.20.10 IP address entered: 192.168.20.10 Please enter your IP Mask... 255.255.255.0 IP Mask entered: 255.255.255.0 Please enter your Default Gateway IP addr... 192.168.20.1 Gateway IP address entered: 192.168.20.1 Do you want to store the changes permanently?[y/n] y Please wait for flash update... Please reboot the system DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 31 of 47 Innomedia_SIP.doc Step 4. Description After rebooting the system, reconnect as in Step 1, this time using the IP address configured in Step 3 (in this example, 192.168.20.10). Enter Ci, then 3 to specify the SIP Proxy Server configuration to be used. Respond to the prompts that follow with the appropriate values. The values shown here were used for one of the InnoMedia MTA 3328-8 gateways in the reference configuration. Ci 1. 2. 3. 4. 5. 6. 9. 3 Configure Local IP Set DNS IP(s) SIP Proxy Server And SIP Domain Change IP Settings for All Configure other Local Host settings Configure Provisioning Server(obsolete) Configure MTA Web Server Port Enable Outbound Proxy?[y/n] y Please enter either the FQDN or IP of SIP Outbound Proxy Servers... 192.168.10.50 SIP Proxy Server IP Address Entered: 192.168.10.50 [Optional] Do you want to configure SIP Domain(y/n)? Please enter SIP Domain (e.g.: InnoMedia.com)... y abcd.com SIP Domain Entered: abcd.com Do you want to store the changes permanently?[y/n] y Please wait for flash update... Please reboot the system DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 32 of 47 Innomedia_SIP.doc Step 5. Description After rebooting, reconnect as in Step 4. To specify the set of preferred codecs, enter Ci, then 5, then 1. Choose from the list of available codecs by entering, in order of preference, the corresponding numbers from the list provided, as shown below. These should match the codecs entered in Avaya Communication Manager in Section 4.1, Step 3. The values shown here were used for one of the InnoMedia MTA 3328-8 gateways in the reference configuration. Ci 1. 2. 3. 4. 5. 6. 9. Configure Local IP Set DNS IP(s) SIP Proxy Server And SIP Domain Change IP Settings for All Configure other Local Host settings Configure Provisioning Server(obsolete) Configure MTA Web Server Port 5 0. 1. 2. 3. 4. 5. 6. 7. 8. Set Fax Answer Tone Trigger Flag Select CODECs: Set Voice Frame Packetization Time Change Voice RTP port Set Silence Suppression Set DSCP(Differentiated Services Code Point) value Set Bullet interval Disable Pinging Gateway Change All the above settings 1 Num. of Available Codecs = 7 0. 1. 2. 3. 4. 5. 6. PCMU/8000 PCMA/8000 G729A/8000 G723/8000 G726-32/8000 G728/8000 G729/8000 (only if G729A is not selected) Num. of Selected Codecs = 3 active 0. 1. 2. G729A/8000 PCMU/8000 PCMA/8000 Please enter selections: (a,b,c,d....): 0,2 G729A is Selected!! ind_list[0]=0 ind_list[1]=2 Do you want to store the changes permanently?[y/n] y G729A is Selected!! ind_list[0]=2 ind_list[1]=0 ind_list[2]=1 INFO: read from NVS_PRIMARY (0x43) FS write: OK. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 33 of 47 Innomedia_SIP.doc Step 6. Description Enter C2 to configure the use of RFC 2833 to send DTMF tones. The InnoMedia MTA 3328-8 gateways in the reference configuration were administered as shown below. C2 RFC2833 (SDP and 2833 packets) is ALWAYS OFF! Please input your new choice(0:always off,1:always on, 2:negotiated) 2 INFO: read from NVS_PRIMARY (0x45) INFO: write to NVS_SECONDARY (0x46) INFO: write to NVS_PRIMARY (0x46) FS write: OK. RFC2833 (SDP and 2833 packets) is NEGOTIATED! 7. To configure additional SIP settings, enter Cs. The currently administered SIP parameters are displayed, as shown below. Cs Current SIP Proxy Servers = 192.168.10.50 Use Outbound Proxy = Yes Current Local SIP Port = 5060 Response Code for Retry Registration = Retry Registration Interval = 0 seconds Current SIP Domain = abcd.com Current Exponential Backoff = 500 ms Current Exponential Cap = 2000 ms Current Non-INVITE retry = 4 times Current INVITE msg retry = 4 times Current REGISTER expiration = 500 seconds Current Session Timer = 0 seconds Current Bullet Interval = 0 seconds Current Number of Codecs = 2 Current Codec List = G711(PCMU) G729A Digitmap Partial Match Timeout = 16 Digitmap Critical Timeout = 4 Cancel Call Waiting Invoke String = *72 Call Transfer Invoke String = *90 CID Block Invoke String = *67 CID Display Invoke String = *82 Call Park Invoke String = 316 Call Retrieve Invoke String = 317 Outside Line Access Number = Use User-Agent Header = Yes Set Jitter Buffer Adaptive = Yes Use SIP INFO for DTMF = No Re-registration Credential Enable = No Current SIP PING Interval = 0 seconds Current SIP PING Proxy Require Header = Current SIP External IP address = Use SIP INFO for Flash Event = No PRACK Support Enable = No c -- change SIP settings w -- write changes to Flash(changes is permanent) p -- print SIP settings q -- quit. h -- display the help menu SIP_Settings> DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 34 of 47 Innomedia_SIP.doc Step 8. Description To change the setting of a specific SIP parameter, enter c followed by the number of the item to change. In the example below, the SIP REGISTER Expiration (i.e., the length of time for which an endpoint’s registration is valid) is being set to 3600 seconds (one hour). Other parameters to be considered for configuration include: • • • SIP cmd Retry Exponential Backoff (starting value/ms): This is the starting time interval (in milliseconds) in which the InnoMedia MTA 3328-8 will re-send SIP messages in the case of no response from Avaya SIP Enablement Services. SIP cmd Retry Exponential Backoff (cap/ms): This is the cap on the exponentially increased interval (in milliseconds) for which the InnoMedia MTA 3328-8 will wait before re-sending unanswered SIP messages. SIP cmd (INVITE) Max Retry: This specifies the maximum number of times an INVITE message will be re-sent. The values presented in Step 7 were used for the InnoMedia MTA 3328-8 gateways in the reference configuration. After making all changes, enter w to write the changes to memory. SIP_Settings> c Select the item your want to change: ('Q' to quit) 1. SIP Proxy Server List 2. Outbound Proxy Enable/Disable 3. SIP Local Signaling Port 4. SIP Domain 5. SIP cmd Retry Exponential Backoff (starting value/ms) 6. SIP cmd Retry Exponential Backoff (cap/ms) 7. SIP cmd (Non-INVITE) Max Retry 8. SIP cmd (INVITE) Max Retry 9. SIP REGISTER Expiration (sec) 10. SIP Session Timeout(sec) 11. Bullet Interval (sec) 12. Select CODECs 13. Digitmap Partial (inter-digit) Timeout 14. Digitmap Critical Timeout 15. Configure Call Features & Invoke Strings 16. SIP User-Agent Header 17. Set Jitter Buffer Adaptive/Static 18. SIP INFO for DTMF 19. Set Response Code for Retry Registration 20. Retry Registration Interval 21. SIP PING Interval (sec) 22. SIP PING Proxy Require Header String 23. Header size limitation Option Enable/Disable 24. SIP External IP address 25. Use SIP INFO message to send flash event Enable/Disable 27. PRACK Support Enable/Disable 9 Please enter max expiration (seconds) for SIP REGISTER: SIP_Settings> w INFO: read from NVS_PRIMARY (0x46) INFO: write to NVS_SECONDARY (0x47) INFO: write to NVS_PRIMARY (0x47) FS write: OK. End of SIP Settings Configuring Shell. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 3600 35 of 47 Innomedia_SIP.doc Step 9. Description To enable and configure the ports on the InnoMedia MTA 3328-8 for T.38 fax transmission, enter D1 (to enable Debugging mode), then Th. At the Password: prompt, enter the appropriately authorized password for access to the InnoMedia MTA 3328-8’s debug-level commands. The following menu is displayed. D1 Debugging is enabled. Th Password: ********* 0: Setting EMTA Bootup delay not support now 1: Setting Project Variant not support now 2: Setting EMTA DQOS mode not support now 3: Setting Line Reverse mode not support now 9: Setting Virtual Device 10: Do HTTP provisioning now 11: Send SNMP trap 15: Reload the DSP 17: DSP play 1KHZ 0dbm0 test tone (both stream on slic side) 18: Setting Product Process Trace 19: Check the phy link status 21: Setting T38 Fax 22: Configure MTA Model Number 23. G726 PACKING order is lsn 27. Set Fax Frame Packetization Time 28. Set Fax Jitter Buffer Size 29. RTP control 30. G728 PACKING order is rfc 31. Configure Project Variant 32. Write a sequence of commands to DSP 33: Configure Prov 301 reDir Server DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 36 of 47 Innomedia_SIP.doc Step 10. Description Enter 21 (Setting T38 Fax). Enable the channels that are to be used for T.38 fax transmission as necessary. In this example, all channels are enabled. 21 Your T38 settings are: ch 1 T38 Fax is disabled ch 2 T38 Fax is disabled ch 3 T38 Fax is disabled ch 4 T38 Fax is disabled ch 5 T38 Fax is disabled ch 6 T38 Fax is disabled ch 7 T38 Fax is disabled ch 8 T38 Fax is disabled t38 jitter buffer is 160 ms t38 T2 is 240 ms t38 low speed redundancy is 3 t38 high speed redundancy is 0 t38 bit rate is 9600 t38 ECM is off t38 NSF is cleaned out t38 T38FaxMaxBuffer is 500 t38 FaxMaxDatagram is 421 Fax setting flag 0,port 10000 Fax is using voice port,it is 10000 t38 variant is Default ch 1 T38 Fax is disabled ch 2 T38 Fax is disabled ch 3 T38 Fax is disabled ch 4 T38 Fax is disabled ch 5 T38 Fax is disabled ch 6 T38 Fax is disabled ch 7 T38 Fax is disabled ch 8 T38 Fax is disabled Do you want to change?(y or n) y Do you want to disable/enable all channels?(y or n) y Please input 1:T38 enabled,0:T38 disabled 1 Current ch 0 T38 Fax is enabled Current ch 1 T38 Fax is enabled Current ch 2 T38 Fax is enabled Current ch 3 T38 Fax is enabled Current ch 4 T38 Fax is enabled Current ch 5 T38 Fax is enabled Current ch 6 T38 Fax is enabled Current ch 7 T38 Fax is enabled Current ch 8 T38 Fax is enabled DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 37 of 47 Innomedia_SIP.doc Step 11. Description The default values can be retained for all other parameters, with one exception: t38 variant must be set to Huawei mode (HW) to be compatible with Avaya Communication Manager. To configure this setting, enter 1 at the appropriate prompt (see below). After responding to all parameter prompts, enter y when prompted to store the settings in flash memory. t38 variant is Default Do you want to configure t38_variant (y or n) y Please input new t38_variant (<2) 1 Current t38_variant is HW Do you want to store them in flash memory (y or n) y INFO: read from NVS_PRIMARY (0x41) INFO: write to NVS_SECONDARY (0x42) INFO: write to NVS_PRIMARY (0x42) FS write: OK. End of T38 configuration DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 38 of 47 Innomedia_SIP.doc Step 12. Description Use the Cd command to change the digit map stored in the InnoMedia MTA 3328-8. This is a list of dialing patterns that will be recognized when entered from an analog endpoint. Once a match is found, the digits collected to that point are used for call establishment. The digit map can be a maximum of 2048 characters. In the listing shown below, the pattern 91xxxxxxxxxx (for PSTN calls) is being added to the list of entries used in the reference configuration. The remaining entries include 2xxxxxx (for dialing station extensions), 1xx (Abbreviated Dialing lists), 3xx (FNEs) and 8xx (FACs). After making all changes, enter w to write the changes to memory. Cd a -- add a new dialing pattern d# -- delete the n-th pattern in the DigitMap w -- write changes to Flash(permanent storage) e -- erase the entire DigitMap p -- print all patterns of the current Digitmap q -- quit. h -- display the help menu DigitMap> p No. DigitMap Pattern 1 2xxxxxx 2 1xx 3 3xx 4 8xx DigitMap> a Enter a new Digitmap pattern: 91xxxxxxxxxx DigitMap> p No. DigitMap Pattern 1 2xxxxxx 2 1xx 3 3xx 4 8xx 5 91xxxxxxxxxx DigitMap> w End of Configuring DigitMap. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 39 of 47 Innomedia_SIP.doc Step 13. Description To configure call features and invoke strings (equivalent to FACs or FNEs in Avaya Communication Manager), enter C3. At the CallFeatures> prompt, enter i and respond to the subsequent prompts as shown below. Specifically, the following values should be verified: • • • Call Park Invoke String: This must be the same as the Call Park FNE administered in Avaya Communication Manager in Section 4.2, Step 8. Call Retrieve Invoke String: This must match the Call Park Answer Back FNE administered in Avaya Communication Manager in Section 4.2, Step 8. Outside Line Access Number: This must be set to a null value (press Enter). Enter c and the CallFeatures> prompt to enable Call Waiting and Three-Way Call and Call Transfer on each channel to be used. In the example below, these features were enabled for Channel 1. C3 Configuring Set Call Features: c -- change a call feature setting i -- change a client call feature invoke string w -- write changes to Flash(changes is permanent) p -- print all records in the database on screen q -- quit. h -- display the help menu CallFeatures> i Do you want to change "Cancel Call Waiting Invoke String"?[y/n] n Do you want to change "Call Transfer Invoke String"?[y/n] n Do you want to change "Caller ID Block Invoke String"?[y/n] n Do you want to change "Caller ID Display Invoke String"?[y/n] n Do you want to change "Call Park Invoke String"?[y/n] y Please enter string: 316 Do you want to change "Call Retrieve Invoke String"?[y/n] y Please enter string: 317 Do you want to change "Outside Line Access Number"?[y/n] y Please enter string: CallFeatures>c Enter the Channel Number: (from 1 to 8 ) 1 Select the call feature your want to enable or disable: 1. Call Waiting 2. Three-Way Call and Call Transfer 3. Caller ID 4. Reject Anonymous calls 1 Enable this call feature? [y/n] y CallFeatures>c Enter the Channel Number: (from 1 to 8 ) 1 Select the call feature your want to enable or disable: 1. Call Waiting 2. Three-Way Call and Call Transfer 3. Caller ID 4. Reject Anonymous calls 2 Enable this call feature? [y/n] DH; Reviewed: SPOC 9/27/06 y Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 40 of 47 Innomedia_SIP.doc Step 14. Description Enter p at the CallFeatures> prompt to display the call features settings. The information for Channels 3-7 was deleted from the listing below for brevity. After making all changes, enter w to write the changes to memory. CallFeatures> p String to invoke cancel call waiting: *72 String to invoke call transfer: *90 String to invoke Caller ID Block: *67 String to invoke Caller ID Display: *82 String to invoke call park: 316 String to invoke call retrieve: 317 Outside Line Access Number: Ch 1: Call Waiting is enabled active Three-Way Call and Call Transfer are enabled Three-Way:active,B Tranx:active,C Tranx:active Caller ID is enabled active Reject Anonymous calls is disabled Ch 2: Call Waiting is enabled active Three-Way Call and Call Transfer are enabled Three-Way:active,B Tranx:active,C Tranx:active Caller ID is enabled active Reject Anonymous calls is disabled . . . Ch 8: Call Waiting is enabled active Three-Way Call and Call Transfer are enabled Three-Way:active,B Tranx:active,C Tranx:active Caller ID is enabled active Reject Anonymous calls is disabled CallFeatures> w INFO: read from NVS_PRIMARY (0x43) FS write: OK. End of Configuring Set Call Features. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 41 of 47 Innomedia_SIP.doc Step 15. Description To add user accounts and associate them with specific channels on the InnoMedia MTA 3328-8, enter Cu, then at the UserID> prompt, enter a. Enter the following values: • • • • Channel Number: Choose a port on the InnoMedia MTA 3328-8 that is not yet allocated to a user account (in this example, 3). User ID, Password: These are used to register with Avaya SIP Enablement Services, and must match one of the User ID/Password combinations administered in Section 5, Step 6. User Name: Enter a descriptive name to be used for Caller ID displays. Authentication: This is a second form of authentication that is not used by Avaya SIP Enablement Services, and so can be left blank (i.e., enter null). After entering user accounts, enter p to display all user account records. Enter w to write the changes to memory. Cu Configuring User Account Database: (each record consists of an User ID) a -- add a new record d# -- delete the n-th record in the database w -- write changes to Flash(changes is permanent) e -- erase all records from the database p -- print all records in the database on screen q -- quit. h -- display the help menu UserID> a Enter the Channel Number: (from 1 to 8 ) 3 Enter a new User ID: 2346247 Enter a new password: 2346247 Enter the user name: GW 2346247 Enter authentication (type 'null' for empty): Authentication content not changed. UserID> p No. UserID Passwd Name 0001 2346240 2346240 GW 2346240 0002 2346245 2346245 GW 2346245 0003 2346247 2346247 GW 2346247 0004 __ 0005 __ 0006 __ 0007 __ 0008 __ UserID> w INFO: read from NVS_PRIMARY (0x49) INFO: write to NVS_SECONDARY (0x4a) INFO: write to NVS_PRIMARY (0x4a) FS write: OK. End of Configuring User Account Database. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. AuthID 42 of 47 Innomedia_SIP.doc 7. Verification Steps The following steps can be used to verify that the configuration steps documented in these Application Notes have been done correctly. ƒ ƒ ƒ ƒ ƒ From Avaya Communication Manager’s SAT: o To verify that the SIP trunk group is in service, enter status trunk n (where n is the number of the trunk group to be verified). o To verify that the SIP signaling group is in-service, enter status signaling-group n (where n is the number of the signaling group to be verified). From Avaya SIP Enablement Services’ Administration Web Interface: o To verify that an analog telephone behind the InnoMedia MTA 3328-8 can register with Avaya SIP Enablement Services, select User → Registered Users. Verify that a call can be placed between two analog telephones behind the InnoMedia MTA 3328-8. Verify that a call can be placed between an analog telephone behind the InnoMedia MTA 3328-8 and a telephone in the PSTN. Verify that a call can be placed between an analog telephone behind the InnoMedia MTA 3328-8 and an Avaya 4600 Series H.323 IP telephone. 7.1. Avaya Communication Manager Feature Testing General testing of Avaya Communication Manager station features and capabilities was carried out against the reference configuration. Since the analog endpoints connected to the InnoMedia MTA 3328-8 are administered in Avaya Communication Manager as OPS extensions, they are able to use most Extended Access Features (e.g., call park, answer back, etc.), although in many cases such features must be activated using Feature Name Extensions (FNEs). The following table summarizes the results observed. Feature Abbreviated Dialing Announcements ANI Automatic Callback (auto redial) AWOH Bridged Call Appearance Busy Indication Call Coverage Call Forwarding – Unconditional (all) Call Forwarding – Busy/DA Call Forwarding Extended – Unconditional Call Park, Call Retrieve (Answer Back) 1 Innomedia MTA 3328-8 PASS PASS PASS fail PASS fail fail PASS PASS PASS PASS marginal1 Analog parking station does not hear confirmation tone. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 43 of 47 Innomedia_SIP.doc Feature Call Pickup-Group Call Pickup-Extended Group Call Pickup-Directed Call Waiting Termination Caller ID Conference (via Flash Button) Conference (Meet Me) Conference on Answer COR COS Data/Modem Call: G.711 Distinctive Ringing Displays DTMF: G.711 DTMF: G.729 Extension to Extension Calling FAX: G.711 FAX: T.38 Feature Access Codes/Feature Name Extensions Hold (Hard) 2 Hold (Consultation ) Hunt Groups Internal Auto Answer IP-IP Direct Audio (Shuffling) Last Number Dialed Leave Word Calling Manual Message Waiting Music on Hold Personalized Ringing Priority Calling PSTN DID Calling PSTN DOD Calling Send All Calls/DND Transfer Attended Transfer Unattended Transfer on Hangup Innomedia MTA 3328-8 PASS PASS PASS PASS PASS PASS PASS fail PASS PASS PASS fail PASS PASS PASS PASS PASS PASS PASS fail PASS PASS n/s3 PASS PASS n/s3 n/s3 PASS fail PASS4 PASS PASS PASS PASS PASS fail Call Park could be used to approximate hard hold functionality. n/s: The feature is not supported on analog phones, i.e. analog phones do not have the necessary buttons or displays to support the feature. 4 The feature can be invoked, but because Distinctive Ringing cannot be applied, the called station does not alert with priority ringing. 2 3 DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 44 of 47 Innomedia_SIP.doc Specifically, the following behaviors were noted: • Some features do not work exactly as expected: ™ Call Forward - Unconditional: No alert on the forwarded (analog) station. ™ Call Park: Analog parking station does not hear confirmation tone (although parked station does). ™ Hold (Consultation): The Innomedia MTA 3328-8 implements the return to the held party by using the conferencing feature: The holding station must flash twice after consult - first to create a conference, next to drop the 3rd party. ™ Send All Calls: No single-burst alert at the station where SAC is activated when an incoming call is redirected. ™ Transfer (Attended or Unattended): Transfer feature code must be entered over the media connection (attended) or over ringback (unattended). 7.2. Codec and Shuffling Testing During the testing, an effort was made to identify a configuration of codecs and IP network regions to achieve the following desirable characteristics: • • All calls have a direct IP-IP audio path (i.e. “shuffled”) The desired codec usage by call type is: • Intra-region calls: G.711 • Inter-region calls (PSTN to enterprise): G.729AB The configuration in Avaya Communication Manager that most closely achieves this goal was as follows: • Avaya Media Gateway G650 resources in Network Region 2. • Avaya Communication Manager/Avaya SIP Enablement Services trunk group with signaling group of Far End Network Region 1. • All analog SIP endpoints in Network Region 1 (by setting the IP-Network-Map of analog SIP IP addresses to Network Region 1) • Off-PBX-telephone station-mapping: All off PBX stations (the analog phones behind the SIP gateways) were mapped to one of two trunk groups – one whose signaling group was associated with Network Region 1, the other whose signaling group was associated with Network Region 2. • Intra-Network Region codec set: G.711 (1st preference), G.729AB (2nd preference • Inter-Network Region codec set: G.729AB (1st preference), G.711 (2nd preference) To support the above configuration, the InnoMedia MTA 3328-8 codec preferred order was set as follows: G.729AB (1st preference), G.711 (2nd preference). DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 45 of 47 Innomedia_SIP.doc With the configuration settings above, the following results were observed for InnoMedia MTA 3328-8 gateway: • For intra-site calls: o All calls are shuffled. o Analog-to-H.323 and H.323-only calls use G.711. o H.323-to analog and analog-only calls use G.729. • For inter-site calls (using WAN, including PSTN and VoIP resource connections): o Analog to PSTN use G.711. o All other combinations use G.729. 8. Support Technical support for the InnoMedia MTA 3328-8 can be obtained from InnoMedia. See the Support link at www.innomedia.com for contact information. 9. Conclusion The analog telephones, modems and fax machines behind InnoMedia MTA 3328-8 can successfully register to Avaya SIP Enablement Services and utilize telephony features of Avaya Communication Manager. 10. Additional References The following Avaya product documentation can be found at http://support.avaya.com. [1] Feature Description and Implementation For Avaya Communication Manager, Issue 4.0, February 2006, Document Number 555-245-205. [2] Administrator Guide for Avaya Communication Manager, Issue 2.1, May 2006, Document Number 03-300509. [3] Converged Communications Server R3.0 Installation and Administration Guide (SIP Enablement Services R3.0), July 2005, Issue 5.1, Document Number 555-245-705. [4] SIP Support in Release 3.1 of Avaya Communication Manager Running on the Avaya S8300, S8500, S8500B, S8700, and S8710 Media Server, February 2006, Issue 6, Document Number 555-245-206. [5] 4600 Series IP Telephone Release 2.4 LAN Administrator Guide, April 2006, Issue 2.3, Document Number 555-233-507. [6] Avaya Extension to Cellular User’s Guide, Issue 6, Document Number 210-100-700. [7] Avaya Extension to Cellular and OPS Installation and Administration Guide. Issue 8. Document Number 210-100-500. The following InnoMedia MTA 3328-8 product documentation is available from InnoMedia. Visit http://www.innomedia.com for company and product information. [8] InnoMedia SIP MTA 3328R Administrator’s Guide. DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 46 of 47 Innomedia_SIP.doc ©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. 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 e-mail 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 [email protected] DH; Reviewed: SPOC 9/27/06 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 47 of 47 Innomedia_SIP.doc