configure avaya communication manager and avaya sip ... ?· configuration of the sip trunks. ......

Download Configure Avaya Communication Manager and Avaya SIP ... ?· configuration of the SIP trunks. ... Incoming…

Post on 26-Aug-2018

212 views

Category:

Documents

0 download

Embed Size (px)

TRANSCRIPT

  • TLT; Reviewed: SPOC 2/12/2007

    Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.

    1 of 45 Cisco-SES.doc

    Avaya Solution & Interoperability Test Lab

    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.

  • TLT; Reviewed: SPOC 2/12/2007

    Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.

    2 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.

  • TLT; Reviewed: SPOC 2/12/2007

    Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.

    3 of 45 Cisco-SES.doc

    2. Equipment and Software Validated The following equipment and software were used for the sample configuration provided:

    Equipment Software

    Avaya S8700 Media Servers Avaya Communication Manager 3.1.2, R013x.01.2.632.1 Avaya G650 Media Gateway

    TN799DP C-LAN Circuit Pack TN2302AP IP Media Processor

    HW01 FW015 HW11 FW104

    Avaya SIP Enablement Services 3.1, SES03.1-03.1.018.0 Avaya 4610SW SIP Telephone 2.2.2 Avaya 4610SW H.323 Telephone 2.7 Avaya 6416D+ Digital Telephone NA Cisco Unified CallManager 5.0.4.2000-1 Cisco 7961 SIP Telephone POS3-07-4-00 Cisco 7941 SCCP H.323 Telephone Ver 7.0 (2.0)

  • TLT; Reviewed: SPOC 2/12/2007

    Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.

    4 of 45 Cisco-SES.doc

    3. Configure Avaya Communication Manager For successful interoperability with Cisco Unified CallManager, media shuffling has to be disabled. To maintain media shuffling amongst Avaya endpoints, and because calls to Cisco and Avaya SIP endpoints both require SIP trunks, separate SIP trunk groups along with separate signaling groups, network regions, and codec sets were created to provide the different treatments on media shuffling. In the test configuration, all Avaya endpoints (including the Avaya SIP endpoint) were configured to be in network region 1 with media shuffling enabled. Incoming SIP trunk calls from Avaya SIP endpoints will use network region 1 based on the IP network map configuration. Calls to Avaya SIP endpoints use network region 1 based on the Avaya SIP endpoints station mapping to a specific trunk group and signaling group. In the test configuration, network region 6 with media shuffling disabled was configured for Cisco endpoints. Incoming SIP trunk calls from Cisco endpoints will use network region 6 based on the signaling group configuration. Calls to Cisco endpoints will use network region 6 based on the AAR configuration, which selects a specific trunk group and signaling group. For this approach to enable shuffling among Avaya endpoints while preventing shuffling between Avaya and Cisco endpoints to be utilized, the signaling group whose far-end network region refers to the Cisco region must be a lower number than other signaling groups using the same near-end and far-end node names. When two SIP signaling groups use the same near-end and far-end node names, the lower numbered signaling group will be selected first by Avaya Communication Manager for incoming calls. It is also important to ensure sufficient trunks are allocated to the corresponding trunk group. Otherwise, in the case of insufficient trunks associated with the lower numbered signaling group, the higher numbered signaling group would be used. This could allow an incoming call from Cisco to be associated with the far-end region from the higher numbered signaling group that allows shuffling, resulting in no connected talk paths. If it is impractical to ensure that these conditions are met, then the same signaling group and trunk group can be used to reach both Avaya SIP and Cisco endpoints, with shuffling disabled on this signaling group. While not presented in these Application Notes, this simpler configuration where shuffling is disabled for all SIP calls has also been verified. The table below displays the configured network region, codec set, signaling group, trunk group associations and their purpose:

    Purpose Region Codec Signaling Trunk Intra-Region Inter-Region For Cisco Endpoints 6 6 140 140 Disabled Disabled

    For Avaya SIP Endpoints 1 1 141 141 Enabled Enabled

  • TLT; Reviewed: SPOC 2/12/2007

    Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.

    5 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

    3.1. Verify Avaya Communication Manager License Log into the System Access Terminal (SAT) to verify that the Avaya Communication Manager license has proper permissions for features illustrated in these Application Notes. Use the display system-parameters customer-options command and navigate to Page 2. Verify that there is sufficient remaining capacity for SIP trunks by comparing the Maximum Administered SIP Trunks field value with the corresponding value in the USED column. The difference between the two values needs to be greater than or equal to the desired number of simultaneous SIP trunk connections. When configuring the desired number of simultaneous SIP trunk connections, factor in the following: A call between an Avaya SIP endpoint and any Cisco endpoint uses two SIP trunks. A call between an Avaya non-SIP endpoint and any Cisco endpoint uses one SIP trunk.

    The license file installed on the system controls the maximum permitted. If there is insufficient capacity or a required feature is not enabled, contact an authorized Avaya sales representative to make the appropriate changes. display system-parameters customer-options Page 2 of 11 OPTIONAL FEATURES IP PORT CAPACITIES USED Maximum Administered H.323 Trunks: 5000 151 Maximum Concurrently Registered IP Stations: 5000 13 Maximum Administered Remote Office Trunks: 0 0 Maximum Concurrently Registered Remote Office Stations: 0 0 Maximum Concurrently Registered IP eCons: 0 0 Max Concur Registered Unauthenticated H.323 Stations: 10 0 Maximum Video Capable H.323 Stations: 0 0 Maximum Video Capable IP Softphones: 0 0 Maximum Administered SIP Trunks: 50 20

  • TLT; Reviewed: SPOC 2/12/2007

    Solution & Interoperability Test Lab Application Notes 2007 Avaya Inc. All Rights Reserved.

    6 of 45 Cisco-SES.doc

    3.2. Administer System Parameters Features Use the change system-parameters features command to allow for trunk-to-trunk transfers. Submit the change. This feature is needed to be able to transfer an incoming call from the Branch back out to the Branch (incoming trunk

Recommended

View more >