ASM-CM-CUCMEASM-CM-CUCME, Avaya
[ Pobierz całość w formacie PDF ]
//-->Avaya Solution & Interoperability Test LabConfiguring SIP Trunks among Avaya Aura™ SessionManager, Avaya Aura™ Communication Manager, andCisco Unified Communications Manager Express – Issue 1.0AbstractThese Application Notes present a sample configuration for a network that uses Avaya Aura™Session Manager to connect Avaya Aura™ Communication Manager and Cisco UnifiedCommunications Manager Express using SIP trunks.For the sample configuration, Avaya Aura™ Session Manager runs on an Avaya S8510Server, Avaya Aura™ Communication Manager runs on an Avaya S8300 Server with AvayaG430 Media Gateway, and Cisco Unified Communications Manager Express runs on a Cisco3825 Integrated Services Router (ISR). The results in these Application Notes should beapplicable to other Avaya servers and media gateways that support Avaya Aura™Communication Manager.AM; Reviewed:SPOC 08/10/2009Solution & Interoperability Test Lab Application Notes©2009 Avaya Inc. All Rights Reserved.1 of 48ASM-CM-CUCME1 IntroductionThese Application Notes present a sample configuration for a network that uses Avaya Aura™Session Manager to connect Avaya Aura™ Communication Manager and Cisco UnifiedCommunications Manager Express (Cisco UCME) using SIP trunks.As shown inFigure 1,the Avaya 9630 IP Telephone (H.323) and 6408D+ Digital Telephone aresupported by Avaya Aura™ Communication Manager. The Cisco 7965G IP Telephone (SIP)and the Cisco 7975G IP Telephone (SCCP) are supported by the Cisco UCME. SIP trunks areused to connect these two systems to Avaya Aura™ Session Manager, using its SM-100(Security Module) network interface. All inter-system calls are carried over these SIP trunks.Avaya Aura™ Session Manager can support flexible inter-system call routing based on dialednumber, calling number and system location, and can also provide protocol adaptation to allowmulti-vendor systems to interoperate. It is managed by a separate Avaya Aura™ SystemManager, which can manage multiple Avaya Aura™ Session Managers by communicating withtheir management network interfaces. Configurations supporting SIP telephones still requireAvaya SIP Enablement Services, and are not addressed in these application notes.Figure 1 – Sample ConfigurationAM; Reviewed:SPOC 08/10/2009Solution & Interoperability Test Lab Application Notes©2009 Avaya Inc. All Rights Reserved.2 of 48ASM-CM-CUCMEFor the sample configuration, Avaya Aura™ Session Manager runs on an Avaya S8510 Server,Avaya Aura™ Communication Manager runs on an Avaya S8300 Server with Avaya G430Media Gateway, and Cisco Unified Communications Manager Express runs on Cisco 3825Integrated Services Router (ISR). The results in these Application Notes should be applicable toother Avaya Aura™ servers and Media Gateways.A five digit Uniform Dial Plan (UDP) is used for dialing between systems. Unique extensionranges are associated with Avaya Aura™ Communication Manager 5.2 (143xx) and CiscoUCME (777xx).These Application Notes will focus on the configuration of the SIP trunks and call routing.Detailed administration of the endpoint telephones will not be described (see the appropriatedocumentation listed inSection 8).AM; Reviewed:SPOC 08/10/2009Solution & Interoperability Test Lab Application Notes©2009 Avaya Inc. All Rights Reserved.3 of 48ASM-CM-CUCME2 Equipment and Software ValidatedThe following equipment and software were used for the sample configuration provided:DEVICE DESCRIPTIONAvaya Aura™ Communication Manager- Running on an Avaya S8300 Server with anAvaya G430 Media GatewayAvaya Aura™ System Manager- Running on an Avaya S8510 ServerAvaya Aura™ Session Manager- Running on an Avaya S8510 ServerAvaya 9630 IP Telephone (H.323)Avaya 6402D Digital TelephoneCisco Unified Communications Manager Express- Running on a Cisco 3825 ISRCisco 7965G Unified IP Phone (SIP)Cisco 7975G Unified IP Phone (SCCP)VERSION TESTEDCommunication Manager 5.2(R015x.02.0.947.3.) withSP1 (02.0.947.3-17294)1.01.1 with SP13.0-7.1IOS 12.4(24)T18.4.2S8.4.2S3 Configure Avaya Aura™ Communication ManagerThis section provides the procedures for configuring Avaya Aura™ Communication Manager.The procedures include the following areas:••••••••Verify Avaya Aura™ Communication Manager licenseAdminister system parameters featuresAdminister IP node namesAdminister IP codec set and network regionAdminister SIP trunk group and signaling groupAdminister SIP trunk group members and route patternsAdminister location and public unknown numberingAdminister uniform dial plan and AAR analysisSome administration screens have been abbreviated for clarity.AM; Reviewed:SPOC 08/10/2009Solution & Interoperability Test Lab Application Notes©2009 Avaya Inc. All Rights Reserved.4 of 48ASM-CM-CUCME3.1Verify Avaya Aura™ Communication Manager LicenseLog into the System Access Terminal (SAT) to verify that the Avaya Aura™ CommunicationManager license has proper permissions for features illustrated in these Application Notes. Usethe “display system-parameters customer-options” command. Navigate toPage 2,and verifythat there is sufficient remaining capacity for SIP trunks by comparing theMaximumAdministered SIP Trunksfield value with the corresponding value in theUSEDcolumn. Thedifference between the two values needs to be greater than or equal to the desired number ofsimultaneous SIP trunk connections.The license file installed on the system controls the maximum permitted. If there is insufficientcapacity or a required feature is not enabled, contact an authorized Avaya sales representative tomake the appropriate changes.display system-parameters customer-optionsOPTIONAL FEATURESIP PORT CAPACITIESPage2 of10USEDMaximum Administered H.323 Trunks: 800200Maximum Concurrently Registered IP Stations: 18000 2Maximum Administered Remote Office Trunks: 0Maximum Concurrently Registered Remote Office Stations: 0Maximum Concurrently Registered IP eCons: 0Max Concur Registered Unauthenticated H.323 Stations: 0Maximum Video Capable H.323 Stations: 0Maximum Video Capable IP Softphones: 0Maximum Administered SIP Trunks: 800473.2Configure System Parameters FeaturesUse 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/outgoing call from/to the remote switchback out to the same or another switch For simplicity, theTrunk-to-Trunk Transferfield wasset to “all” to enable all trunk-to-trunk transfers on a system wide basis. Note that this featureposes significant security risk, and must be used with caution. For alternatives, the trunk-to-trunk feature can be implemented using Class Of Restriction or Class Of Service levels. Refer tothe appropriate documentation inSection 8for more details.change system-parameters featuresPage1 ofFEATURE-RELATED SYSTEM PARAMETERSSelf Station Display Enabled? yTrunk-to-Trunk Transfer: allAutomatic Callback with Called Party Queuing? nAutomatic Callback - No Answer Timeout Interval (rings): 3Call Park Timeout Interval (minutes): 10Off-Premises Tone Detect Timeout Interval (seconds): 20DID/Tie/ISDN/SIP Intercept Treatment: attdInternal Auto-Answer of Attd-Extended/Transferred Calls: transferred18AM; Reviewed:SPOC 08/10/2009Solution & Interoperability Test Lab Application Notes©2009 Avaya Inc. All Rights Reserved.5 of 48ASM-CM-CUCME [ Pobierz całość w formacie PDF ] |
Podobne
|