Beruflich Dokumente
Kultur Dokumente
Configure Avaya Communication Manager and Avaya SIP Enablement Services for SIP Trunks with Cisco Unified CallManager Issue 1.0
Abstract
These Application Notes present a sample configuration for a network comprised of Avaya Communication Manager and Avaya SIP Enablement Services at the Main site, and Cisco Unified CallManager at the Branch site. SIP trunks are used to connect Avaya Communication Manager and Cisco Unified CallManager via Avaya SIP Enablement Services. All calls between the Main and Branch sites are carried over these SIP trunks. For the sample configuration, Avaya Communication Manager is running on the Avaya S8700 Media Servers with Avaya G650 Media Gateway. The results in these Application Notes should be applicable to other Avaya media servers and gateways.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
1 of 45 Cisco-SES.doc
1. Introduction
These Application Notes present a sample configuration for a network comprised of Avaya Communication Manager and Avaya SIP Enablement Services (SES) at the Main site, and Cisco Unified CallManager at the Branch site. The Avaya 4610SW SIP and H.323 Telephones at the Main site register locally to Avaya SES and Avaya Communication Manager respectively. The Cisco 7961 SIP and 7941 SCCP H.323 Telephones at the Branch site register locally to Cisco Unified Call Manager. SIP trunks are used to connect Avaya Communication Manager and Cisco Unified CallManager via Avaya SIP Enablement Services. All calls between the Main and Branch sites are carried over these SIP trunks. For the sample configuration, Avaya Communication Manager is running on the Avaya S8700 Media Servers with Avaya G650 Media Gateway. The results in these Application Notes should be applicable to other Avaya media servers and gateways.
A five digit Uniform Dial Plan (UDP) is used to facilitate dialing between the Main and Branch sites. Unique extension ranges are associated with Avaya Communication Manager at the Main site (33xxx), and Cisco Unified CallManager at the Branch site (56xxx). The detailed administration of the endpoint telephones is not the focus of these Application Notes and will not be described. For administration of endpoint telephones, refer to the appropriate documentation listed in Section 8. These Application Notes will focus on the configuration of the SIP trunks.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
2 of 45 Cisco-SES.doc
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
3 of 45 Cisco-SES.doc
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
4 of 45 Cisco-SES.doc
This section focuses on configuring the SIP trunks on Avaya Communication Manager to Avaya SES, which are used to reach the Avaya SIP endpoints and Cisco endpoints. In addition, this section highlights selected features that are required for the interoperability, and provides a sample routing using Automatic Alternate Routing (AAR). The configuration procedures include the following areas: Verify Avaya Communication Manager license Administer system parameters features Administer IP node names Administer IP interface and data module Administer IP codec sets and network regions Administer SIP trunk groups and signaling groups Administer SIP trunk group members and route patterns Administer location and public unknown numbering Administer uniform dial plan and AAR analysis Administer IP network map and station mapping
USED 151 13 0 0 0 0 0 0 20
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
5 of 45 Cisco-SES.doc
IP Address . . . . . .
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
6 of 45 Cisco-SES.doc
Type: Slot: Code/Suffix: Node Name: IP Address: Subnet Mask: Gateway Address: Enable Ethernet Port? Network Region: VLAN:
Target socket load and Warning level: 400 Receive Buffer TCP Window Size: 8320 ETHERNET OPTIONS Auto? y
Next, add a new data module using the add data-module n command, where n is an available extension. Enter the following values, and submit these changes. Name: Type: Port: Link: A descriptive name. ethernet Same slot number from the IP INTERFACES screen above and port 17. An available link number.
DATA MODULE Data Extension: Type: Port: Link: 24981 ethernet 02A0217 2 Name: CLAN 2A02 Data Module
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
7 of 45 Cisco-SES.doc
change ip-codec-set 6 IP Codec Set Codec Set: 6 Audio Codec 1: G.711MU 2: Silence Suppression n Frames Per Pkt 2 Packet Size(ms) 20
Page
1 of
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
8 of 45 Cisco-SES.doc
Administer two IP network regions, one to use for Avaya endpoints, and the other to use for Cisco endpoints. Use the change ip-network-region n command, where n is an existing network region number to be used for the interoperability.
yes yes y y y
Navigate to Page 3, and specify the appropriate codec set to use for calls between the Avaya network region 1 with the Cisco network region 6.
change ip-network-region 1 Inter Network Region Connection Management src rgn 1 1 1 1 1 1 1 dst codec direct Total rgn set WAN WAN-BW-limits 1 1 2 2 y :NoLimit 3 2 y :NoLimit 4 2 y :NoLimit 5 5 y :NoLimit 6 6 y :NoLimit 7 Video WAN-BW-limits :NoLimit :NoLimit :NoLimit :NoLimit :NoLimit Dyn CAC IGAR n n n n n Page 3 of 19
Intervening-regions
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
9 of 45 Cisco-SES.doc
no no n y y
Navigate to Page 3, and specify the appropriate codec set to use for calls between the Cisco network region 6 with the Avaya network region 1.
change ip-network-region 6 Inter Network Region Connection Management src rgn 6 6 dst codec direct Total rgn set WAN WAN-BW-limits 1 6 y :NoLimit 2 Video WAN-BW-limits :NoLimit Dyn CAC IGAR n Page 3 of 19
Intervening-regions
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
10 of 45 Cisco-SES.doc
3.6.1. SIP Trunk and Signaling Groups for Avaya SIP Endpoints
In the test configuration, trunk group 141 and signaling group 141 were used to reach the Avaya SIP endpoints. Use the add trunk-group n command, where n is an available trunk group number. Enter the following values for the specified fields, and retain the default values for the remaining fields. Group Type: Group Name: TAC: Service Type: sip A descriptive name. An available trunk access code. tie
Page TRUNK GROUP Group Number: Group Name: Direction: Dial Access? Queue Length: Service Type: 141 Group Type: SIP Trunk to Avaya COR: two-way Outgoing Display? n 0 tie Auth Code? sip 1 n CDR Reports: y TAC: 141 1 of 21
TN: 1
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
11 of 45 Cisco-SES.doc
Administer a SIP signaling group for the newly added trunk group to use for signaling. Use the add signaling-group n command, where n is an available signaling group number. Enter the following values for the specified fields, and retain the default values for all remaining fields. Submit these changes. Group Type: sip Transport Method: tls Near-end Node Name: C-LAN node name from Section 3.3. Far-end Node Name: SES server node name from Section 3.3. Near-end Listen Port: 5061 Far-end Listen Port: 5061 Far-end Network Region: Avaya network region number 1 from Section 3.5.1. Far-end Domain: SIP domain name of SES server from Section 4.1. DTMF over IP: rtp-payload
add signaling-group 141 SIGNALING GROUP Group Number: 141 Group Type: sip Transport Method: tls Far-end Node Name: MM-SES-server Far-end Listen Port: 5061 Far-end Network Region: 1 Bypass If IP Threshold Exceeded? n DTMF over IP: rtp-payload Session Establishment Timer(min): 120 Direct IP-IP Audio Connections? y IP Audio Hairpinning? Y Page 1 of 1
Near-end Node Name: clan2 Near-end Listen Port: 5061 Far-end Domain: mm.com
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
12 of 45 Cisco-SES.doc
TN: 1
Navigate to Page 2, and enter 900 for the Preferred Minimum Session Refresh Interval (sec) field. This field sets the session refresh timer value. Avaya Communication Manager sends a session refresh request as a Re-INVITE or UPDATE after every timer interval to maintain ongoing sessions. When this value is less than 900, then Cisco Unified CallManager returns a 402 Session Timer Too Small response and results in further timer negotiations. Set this field to 900 to reduce unnecessary SIP messages.
add trunk-group 140 Group Type: sip TRUNK PARAMETERS Unicode Name? y Redirect On OPTIM Failure: 5000 SCCAN? n Digital Loss Group: 18 Preferred Minimum Session Refresh Interval(sec): 900 Page 2 of 21
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
13 of 45 Cisco-SES.doc
Navigate to Page 3, and enter public for the Numbering Format field as shown below. Submit these changes.
display trunk-group 140 TRUNK FEATURES ACA Assignment? n Page Measured: none Maintenance Tests? y 3 of 21
Numbering Format: public Prepend '+' to Calling Number? n Replace Unavailable Numbers? n
Administer a SIP signaling group for the newly added trunk group to use for signaling. Use the add signaling-group n command, where n is an available signaling group number. Enter the following values for the specified fields, and retain the default values for all remaining fields. Submit these changes. Group Type: Transport Method: Near-end Node Name: Far-end Node Name: Near-end Listen Port: Far-end Listen Port: Far-end Network Region: Far-end Domain: DTMF over IP: sip tls C-LAN node name from Section 3.3. SES server node name from Section 3.3. 5061 5061 Cisco network region number 6 from Section 3.5.2. SIP domain name of SES server from Section 4.1. rtp-payload
Page SIGNALING GROUP Group Number: 140 Group Type: sip Transport Method: tls Far-end Node Name: MM-SES-server Far-end Listen Port: 5061 Far-end Network Region: 6 Bypass If IP Threshold Exceeded? n DTMF over IP: rtp-payload Session Establishment Timer(min): 120 Direct IP-IP Audio Connections? y IP Audio Hairpinning? Y 1 of 1
Near-end Node Name: clan2 Near-end Listen Port: 5061 Far-end Domain: mm.com
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
14 of 45 Cisco-SES.doc
change trunk-group 141 TRUNK GROUP Group Number: Group Name: Direction: Dial Access? Queue Length: Service Type: 140 Group Type: SIP Trunk to Avaya COR: two-way Outgoing Display? n 0 tie Auth Code? sip 1 n
Page
1 of
21
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
15 of 45 Cisco-SES.doc
Create two route patterns to use for the newly created SIP trunk groups. Use the change routepattern n command, where n is an available route pattern. Enter the following values for the specified fields, and retain the default values for the remaining fields. Submit these changes. Pattern Name: A descriptive name. Grp No: The trunk group number from above. FRL: Enter a level that allows access to this trunk, with 0 being least restrictive.
change route-pattern 140 Page Pattern Number: 140 Pattern Name: SES to Cisco SCCAN? n Secure SIP? n Grp FRL NPA Pfx Hop Toll No. Inserted No Mrk Lmt List Del Digits Dgts 1: 140 0 2: 3: 4: 5: 6: BCC VALUE TSC CA-TSC 0 1 2 3 4 W Request 1: y y y y y n n ITC BCIE Service/Feature PARM 1 of 3
IXC
rest
change route-pattern 141 Page Pattern Number: 140 Pattern Name: SES to Avaya SCCAN? n Secure SIP? n Grp FRL NPA Pfx Hop Toll No. Inserted No Mrk Lmt List Del Digits Dgts 1: 141 0 2: 3: 4: 5: 6: BCC VALUE TSC CA-TSC 0 1 2 3 4 W Request 1: y y y y y n n ITC BCIE Service/Feature PARM
IXC
rest
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
16 of 45 Cisco-SES.doc
change locations
Use the change public-unknown-numbering 0 command, to define the calling party number to be sent to Cisco Unified CallManager. Add an entry for the trunk group defined in Section 3.6.2 to reach Cisco endpoints. In the example shown below, all calls originating from a 5-digit extension beginning with 3 and routed to trunk group 140 will be sent as a 5-digit calling number. The calling party number will be sent to the far-end in the SIP From header. Submit these changes.
change public-unknown-numbering 0 NUMBERING - PUBLIC/UNKNOWN FORMAT Total Ext Ext Trk CPN CPN Ext Ext Trk Len Code Grp(s) Prefix Len Len Code Grp(s) 5 3 140 5 Page 1 of 2
CPN Prefix
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
17 of 45 Cisco-SES.doc
Percent Full: 0 Matching Insert Node Pattern Len Del Digits Net Conv Num 56 5 0 aar n Matching Insert Node Pattern Len Del Digits Net Conv Num n
Use the change aar analysis 0 command, and add an entry to specify how to route the calls to 56xxx. Enter the following values for the specified fields, and retain the default values for the remaining fields. Submit these changes. Dialed String: Total Min: Total Max: Route Pattern: Call Type: Dialed prefix digits to match on, in this case 56. Minimum number of digts. Maximum number of digits. The Cisco route pattern number from Section 3.7. aar
Page AAR DIGIT ANALYSIS TABLE Percent Full: Dialed String 56 Total Min Max 5 5 Route Pattern 140 Call Type aar Node Num ANI Reqd n 2 1 of 2
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
18 of 45 Cisco-SES.doc
Subnet or Mask)
Region 1
VLAN n n
Use the change off-pbx-telephone station-mapping n command, where n is the extension number of the Avaya SIP endpoint. In the Trunk Selection field, enter the trunk group defined in Section 3.6.1 to reach Avaya SIP endpoints. This will enable the Avaya network region to be used for this Avaya SIP endpoint for outgoing calls. Submit these changes. Repeat this procedure for every Avaya SIP endpoint.
change off-pbx-telephone station-mapping 33001 STATIONS WITH OFF-PBX TELEPHONE INTEGRATION Station Extension 33001 Application OPS Dial Phone Number Prefix - 33001 Trunk Selection 141 Page 1 of 2
Configuration Set 2
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
19 of 45 Cisco-SES.doc
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
20 of 45 Cisco-SES.doc
The Top screen is displayed, as shown below. If this is the initial setup of the SES server, then follow the Avaya SES documentation in Section 8 to administer the SIP domain and host. These Application Notes assume the SES server has already been configured with the proper domain and host information.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
21 of 45 Cisco-SES.doc
Select Server Configuration > System Properties from the left pane to display the Edit System Properties screen. Use the value in the SIP Domain field (in this case mm.com) for configuring the Authoritative Domain and Far-end Domain fields in Sections 3.5 and 3.6 respectively.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
22 of 45 Cisco-SES.doc
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
23 of 45 Cisco-SES.doc
In the List Host Address Map screen below, click on the Add Map In New Group link in the right pane.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
24 of 45 Cisco-SES.doc
The Add Host Address Map screen is displayed next. This screen is used to specify which calls are to be routed to Cisco Unified CallManager. For the Name field, enter a descriptive name to denote the routing. For the Pattern field, enter an appropriate syntax for address mapping. For the interoperability testing, a pattern of ^sip:56[0-9]{3} is used to match to any extensions in the range of 56000-56999 at the Branch site. Retain the check in Replace URI, and click Add.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
25 of 45 Cisco-SES.doc
In the Add Host Contact screen, enter the contact sip:$(user)@<destination-IP-address> :5060;transport=udp, where the <destination-IP-address> is the IP address of the Cisco Unified CallManager from Section 5.1. Avaya SES will substitute $(user) with the user portion of the request URI before sending the message. Click on the Add button.
After configuring the trusted host, the user must go back to the SES administration web interface, and click on the Update link in the bottom left pane for all changes in Section 4 to take effect.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
26 of 45 Cisco-SES.doc
Note that the default audio codec for all calls through Cisco Unified CallManager specifies G.711. Regions can be used to set up other audio codecs. Refer to the Cisco documentation in Section 8 for detailed procedures on how to configure regions.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
27 of 45 Cisco-SES.doc
The Find and List Media Resource Groups screen is displayed next. Click on Add New to add a new media resource group.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
28 of 45 Cisco-SES.doc
The Media Resource Group Configuration screen is displayed. Enter a descriptive Name and Description. Select the desired resources from the Available Media Resources section, and use the down arrow to move them to the Selected Media Resources section. For the interoperability testing, all available media resources were selected. Click Save.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
29 of 45 Cisco-SES.doc
The Find and List Media Resource Group Lists screen is displayed next. Click on Add New to add a new media resource group list.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
30 of 45 Cisco-SES.doc
The Media Resource Group List Configuration screen is displayed. Enter a descriptive Name. Select the media resource group created in Section 5.2 from the Available Media Resource Groups section, and use the down arrow to move to the Selected Media Resource Groups section. Click Save.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
31 of 45 Cisco-SES.doc
The Find and List SIP Trunk Security Profiles screen is displayed next. Click on Add New to add a new security profile for the SIP trunk to Avaya SES.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
32 of 45 Cisco-SES.doc
The SIP Trunk Security Profile Configuration screen is displayed. Enter a descriptive Name and Description. Select UDP from the Outgoing Transport Type field drop down list. Check the Accept Presence Subscription, Accept Out-of-Dialog REFER, Accept Unsolicited Notification, and Accept Replaces Header fields. Retain the default values in all remaining fields, and click Save.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
33 of 45 Cisco-SES.doc
The Find and List Trunks screen is displayed. Click on Add New to add a new SIP trunk to Avaya SES.
The Trunk Configuration screen is displayed next. Select SIP Trunk from the Trunk Type field drop down list, and the value for the Device Protocol field will automatically change to SIP. Click on Next to proceed.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
34 of 45 Cisco-SES.doc
The Trunk Configuration screen is updated. In the Device Information section, enter the following values for the specified fields, and retain the default values for the remaining fields. Check the Media Termination Point Required field, which is required for all SIP trunk calls. Device Name: Description: Device Pool: Media Resource Group List: Media Termination Point Required: A unique identifier. A descriptive text. Default The media resource group list from Section 5.3. Check the field.
Scroll down to the Call Routing Information section. Check the Redirecting Diversion Header Delivery Inbound and Redirecting Diversion Header Delivery Outbound fields, to support call redirection information in the incoming and outgoing INVITE messages.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
35 of 45 Cisco-SES.doc
Scroll down to the SIP Information section. Enter the following values for the specified fields, and retain the default values for the remaining fields. Click Save. Destination Address: SIP Trunk Security Profile: SIP Profile: DTMF Signaling Method: IP address of Avaya SES server from Section 4.1. The SIP trunk security profile from Section 5.4. Standard SIP Profile RFC 2833
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
36 of 45 Cisco-SES.doc
Next, the screen is updated with additional buttons appearing at the bottom of the screen. Click Reset.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
37 of 45 Cisco-SES.doc
The Find and List Route Patterns screen is displayed. Click on Add New to add a new route pattern for the SIP trunk to use.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
38 of 45 Cisco-SES.doc
The Route Pattern Configuration screen is displayed. Enter a route pattern for the Route Pattern field, in this case 33XXX to denote the 5-digit numbering plan for extensions at the Main site. Enter a descriptive text for the Description field, and select the SIP trunk from Section 5.3 for the Gateway/Route List field drop down list. Uncheck the Provide Outside Dial Tone field. Retain the default values in the remaining fields, and scroll down to the bottom of the screen to click Save (not shown).
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
39 of 45 Cisco-SES.doc
6. Verification Steps
This section provides the tests that can be performed on Avaya Communication Manager and Avaya SES, to verify proper configuration of Avaya Communication Manager, Avaya SES, and Cisco Unified CallManager.
0140/001 0140/002 0140/003 0140/004 0140/005 0140/006 0140/007 0140/008 0140/009 0140/010
T00351 T00352 T00353 T00354 T00355 T00366 T00367 T00368 T00369 T00370
in-service/idle in-service/idle in-service/idle in-service/idle in-service/idle in-service/idle in-service/idle in-service/idle in-service/idle in-service/idle
status trunk 141 TRUNK GROUP STATUS Member Port Service State Mtce Connected Ports Busy no no no no no no no no no no
0141/001 0141/002 0141/003 0141/004 0141/005 0141/006 0141/007 0141/008 0141/009 0141/010
T00356 T00357 T00358 T00359 T00360 T00361 T00362 T00363 T00364 T00365
in-service/idle in-service/idle in-service/idle in-service/idle in-service/idle in-service/idle in-service/idle in-service/idle in-service/idle in-service/idle
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
40 of 45 Cisco-SES.doc
Verify the status of the SIP signaling groups by using the status signaling-group n command, where n is the signaling group number administered in Section 3.6. Verify that the signaling group is in-service as indicated in the Group State field shown below.
status signaling-group 140 STATUS SIGNALING GROUP Group ID: Group Type: Signaling Type: Group State: 140 sip facility associated signaling in-service Active NCA-TSC Count: 0 Active CA-TSC Count: 0
status signaling-group 141 STATUS SIGNALING GROUP Group ID: Group Type: Signaling Type: Group State: 141 sip facility associated signaling in-service Active NCA-TSC Count: 0 Active CA-TSC Count: 0
Make a call within the Main site involving an Avaya SIP endpoint and an Avaya H.323 endpoint. Verify the status of connected SIP trunks by using the status trunk x/y, where x is the number of the SIP trunk group from Section 3.6.1 to reach Avaya SIP endpoints, and y is the member number of a connected trunk. Verify that the Service State is in-service/active, and that the IP addresses of the C-LAN and SES server are shown in the Signaling section. In addition, the Audio section shows the codec type and the IP addresses of the two Avaya endpoints. The Audio Connection Type displays ip-direct, indicating media shuffling.
status trunk 141/2 TRUNK STATUS Trunk Group/Member: 0141/002 Port: T00357 Signaling Group ID: Service State: in-service/active Maintenance Busy? no Page 1 of 2
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
41 of 45 Cisco-SES.doc
Make a call between the Main and the Branch site. Verify the status of connected SIP trunks by using the status trunk x/y, where x is the number of the SIP trunk group from Section 3.6.2 to reach Cisco endpoints, and y is the member number of a connected trunk. Verify that the Service State is in-service/active, and that the IP addresses of the C-LAN and SES server are shown in the Signaling section. In addition, the Audio section shows the codec type and the IP addresses of the Avaya IP Media Processor card and Cisco Unified CallManager. The Audio Connection Type displays ip-tdm, indicating no media shuffling.
status trunk 140/3 TRUNK STATUS Trunk Group/Member: 0140/003 Port: T00353 Signaling Group ID: Service State: in-service/active Maintenance Busy? no Page 1 of 3
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
42 of 45 Cisco-SES.doc
Proper display of only the calling party name information on all endpoints in both sites, when the Calling Number Block feature is activated from the sending site.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
43 of 45 Cisco-SES.doc
7. Conclusion
As illustrated in these Application Notes, Avaya Communication Manager can interoperate with Cisco Unified CallManager using SIP trunks via Avaya SES. The following is a list of interoperability items to note: Audio shuffling on Avaya Communication Manager, also referred to as direct IP-IP audio connection, must be disabled for calls between Avaya and Cisco endpoints. Media Termination Point on Cisco Unified CallManager must be checked, as it is required for all SIP trunk calls. The SIP session refresh interval on the Avaya SIP trunk group used to reach Cisco endpoints, can be set to 900 to avoid the 402 Session Timer Too Small response from Cisco Unified CallManager. The unattended trunk-to-trunk transfer scenario involving transfer of a Branch-Main call to another Branch-Main call in the alerting state does not always succeed. The workaround is to complete the transfer after the second Branch-Main call has been answered (i.e., attended transfer). The G.729B and G.729AB codecs are only interoperable for the basic endpoint-to-endpoint call scenarios, and not for more advanced scenarios such as transfers.
8. Additional References
This section references the product documentation relevant to these Application Notes. Administrator Guide for Avaya Communication Manager, Document 03-300509, Issue 2, February 2006, available at http://support.avaya.com. Installing and Administering SIP Enablement Services R3.1, Document ID 03-600768, Issue 1.4, February 2006, available at http://support.avaya.com. SIP Support in Release 3.1 of Avaya Communication Manager Running on the S8300, S8400, S8500 series, and S8700 series Media Server, Document 555-245-206, Issue 6, February 2006, available at http://support.avaya.com. Cisco Unified CallManager Administration Guide, Release 5.0(4), available at http://www.cisco.com.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
44 of 45 Cisco-SES.doc
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 interoplabnotes@list.avaya.com.
Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.
45 of 45 Cisco-SES.doc