xo sip packages 1 and 2, implemented with cisco unified … · · 2016-09-15a. hardware: cisco...

www.xo.com

XO SIP Service Customer Configuration Guide for Cisco Unified Communications Manager (CUCM) 8.0.3

XO SIP Packages 1 and 2, implemented With Cisco Unified

Border Control Element (CUBE)

1 PRODUCT TITLE 1.1 User Guide Title Optional line for more information

XO COMMUNICATIONS CONFIDENTIAL 1

SIP Configuration Guide for Cisco Unified

Communications Manager 8.0.3, Packages 1&2, with CUBE

Control Element (CUBE)

and 2, implemented With Cisco Unified


Contents

About This Document ............................................................................................... 3

Known Issues ............................................................................................................ 3

Registration Method .................................................................................................. 4

XO SIP Service Packages Supported ....................................................................... 4

CUCM 8.0.3 Configuration for XO SIP ...................................................................... 7

CUBE Configuration Details ................................................................................... 44

Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE

PAGE 2 of 54

1. Overview

About This Document

This document describes interoperability between XO SIP Package 1 (G.711) and 2 (G.729a) and the Cisco Unified Communications Manager (CUCM) 8.0.3 IP PBX , implemented with Cisco Unfied Border Control Element (CUBE), deployed with an XO-provided Cisco 2432 IAD as the router/demarcation device. This document assumes the audience has a general understanding of network provisioning and the connectivity requirements of XO Communications SIP service offering. A Cisco engineer should be consulted for assistance with CUBE specifications.

Known Issues

While XO certifies interoperability between XO SIP service and the IP PBX as outlined herein, the following known issues were identified during Interoperability testing. The customer should be aware that certain features and functions may not be fully supportable. In some cases, special configurations and/or PBX software patches may be available from the vendor.

Known Issues for XO SIP Services Packages 1 and 2 with CUBE:

CUBE “ip address trusted authenticate” Feature Command is Enabled - CUBE software version c2800nm-advipservicesk9-mz.151-2.T.bin provides an additional layer of security where the command “ip address trusted authenticate” is enabled by default. For inbound calls to the CUCM to work properly, the IP address of XO’s NBS signaling and media ports must be added to the CUBE configuration to the “voice service voip” section under the “ip address trusted list” command. On new customer installs XO recommends disabling “ip address trusted authenticate” command by entering “no ip address trusted authenticate” under the “voice service voip” section of the configuration to perform inbound test calls, and then re-enable the command at the customer’s request and add the trusted ip addresses under the “ip address trusted

list” under the “voice service voip” section. by Defau

CUCM Does Not Support SIP Refer for Outbound Calls O

Fax was not tested on CUCM version 8.0.3 as CUCM does not have FXS ports to

use for Fax testing (CUCM runs on a server hardware platform) Calls

*67 for Outgoing Calling Line ID Delivery Blocking Per Call is not supported. 1.1.1 Optional Workaround: Create a separate SIP Trunk where in the Outbound Calls

Section the Calling Line ID Presentation is set to Restricted. A route pattern is assigned to that SIP Trunk with a unique single digit access code to access that SIP Trunk which blocks the caller ID for all calls when requested by the user via the access code.

PSTN-to-PSTN call transfers using Call Forward Always (CFA), Call Forward On Busy (CFOB), and Call Forward No Answer (CFNA) when using 4-Digit CUCM extensions - in order for these call scenarios to function, the SIP profile in CUBE must be used to modify the diversion header to add the NPA-NXX to the 4 digit extension in the user portion of the diversion header. Please see section 2.2.4 for details.

CUBE hardware requirements – A Cisco Engineer should be consulted for CUBE hardware necessary to support transcoding, conferencing and call volume requirements.

Music on Hold Settings

o CUCM Music on Hold Server Codec Setting - when configuring the







customer for SP1 or SP2, the Music on Hold Server codec must be set accordingly to G.711ulaw for SP1 and G.729 for SP2 as discussed in detail in section 2.1.3.

o CUBE SIP Profile Rules - when using Music on Hold, some configuration commands are required in the CUBE sip profile section of the configuration for the remote party to hear Music on Hold when the call is placed on hold from a CUCM phone. This is discussed in detail in section 2.2.5.


PAGE 4 of 54

Registration Method

Static registration is utilized between the CUCM 8.0.3 IP PBX and the XO call agent.

XO SIP Service

Packages Supported

Pkg Codec DTMF Fax

1 G.711 RFC2833 (in-band RTP DTMF fall-back)

Fax was not tested on CUCM 8.0.3 (see Known Issues above)

2 G.729a RFC2833 Fax was not tested on CUCM 8.0.3 (see Known Issues above)

1.1. Testing of CUCM 8.0.3

1.1.1 Software and Hardware Versions Tested

1. CUCM Server a. Hardware: Cisco MCS 7800 Series Product No MCS7825H3-K9-

CMB2 b. Software Version: CUCM 8.0.3.10000-8

2. Cisco 2821 ISR running CUBE software

a. Hardware: Cisco 2821 ISR b. 1 PVDM2-32 and 2 PVDM2-48 DSP modules c. IOS software version“c2800nm-advipservicesk9-mz.151-2.T.bin”

3. Cisco Unity Connection (CUC) Voice Mail Server

a. Hardware: Cisco MCS 7800 Series Product No MCS7825H3-K9-CMB2

b. Software Version: CUC 7.0.1.11000-13-2

4. CUCM and Cisco Unity Connection (CUC) PC GUI Access a. Microsoft Internet Explorer version

6.0.2900.2180.xpsp_sp2_gdr.080814-1233

5. Cisco Phones a. Cisco 7961 b. Software Version: SCCP41.9-0-3S

6. Cisco 2432-24FXS IAD

a. Software Version: c2430-mz.xo

7. Cisco Catalyst 3560 PoE series P-24 a. Software Version: c3560-advipservicesk9-mz.122-44.SE2.bin







1.1.2 CUCM 8.0.3 XO Lab Test Configuration

T1, NxT1 or DS3

Serial Link

XO VoIP Network

CUCM

10/100 Ethernet Switch

or 10/100 Power over

Ethernet (PoE) Switch

XO Demarc

Router

TN#1IP Phone

TN#4IP Phone

TN#3IP Phone

TN#2IP Phone

CUBE

Customer owned and

maintained device


PAGE 6 of 54

CUCM and CUBE

Configuration

This section includes high level configuration captures of the CUCM and CUBE configuration screens relevant to configuring a SIP trunk. XO performed the minimum amount of configuration required to achieve successful completion of test calls over XO SIP. It is beyond the scope of this document and the testing efforts to show a complete CUCM 8.0.3 configuration, therefore screenshots of the GUI interface are provided only for the details of the SIP trunk configuration that are relevant to interfacing with XO’s SIP product.

Customers should refer to the CUCM administration guides for additional configuration options: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.

For design guidance for CUCM and Cisco Unified Communications products based on CUCM, see the Solution Reference Network Design (SRND) guides: http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guides_list.html

2 CUCM and CUBE Configuration

2.1.1 CUCM Region and Device Pool Configuration Description The following sections contain a brief description of the CUCM region and device pool configurations used during testing.

2.1.1.1 CUCM Region and Device Pool Configuration for SP1 with CUBE In this setup there is only one region called the default region and it is configured to use G.711 codec. The device pool used is the default device pool. All CUCM phones and the SIP trunk are assigned to the default device pool and use the G.711 codec to communicate over the default region and over the SIP trunk.

http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html

http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guides_list.html

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guides_list.html







CUCM Region Screen Capture for SP1 with CUBE


PAGE 8 of 54

CUCM Device Pool Screen Capture for SP1 with CUBE

Default Device Pool Screen Capture Part 1


PAGE 10 of 54









2.1.1.2 CUCM Region and Device Pool Configuration for SP2 with CUBE In this setup there are two regions where one is the default region and the other is named the XO g729 region. The default region is configured to use the G.729 codec. The XO g729 region is configured to use the G.729 codec. All CUCM phones are configured in the default device pool and the XO SIP trunk is configured in the XO SIP Trunk Device Pool. All phones communicate with each other over the default region using G.711 or G.722 the largest codecs available. When the phones establish an outbound call or receive an inbound call over the SIP trunk, these calls are processed over the XO g729 region configured for G.729 codec. On the CUCM a single SIP trunk can only support one codec. This means that all calls whether they are inbound or outbound over the SIP trunk will establish using only the G.729 codec.


PAGE 12 of 54

CUCM Region Screen Capture for SP2 with CUBE

XO G.729 Region







CUCM Device Pool Screen Capture for SP2 with CUBE G.729 SIP Trunk Device Pool Screen Capture Part 1


PAGE 14 of 54

G.729 SIP Trunk Device Pool Screen Capture Part 2


PAGE 16 of 54








2.1.1.3 CUCM SIP Profile Screen Capture This section contains the SIP Profile used during service package 1 and 2 testing. SIP Profile Screen Capture Part 1


PAGE 18 of 54

SIP Profile Screen Capture Part 2







SIP Profile Screen Capture Part 3


PAGE 20 of 54

2.1.1.4 CUCM SIP Trunk Security Profile This section contains the SIP Trunk Security Profile used during SP1 and SP2 testing.







2.1.1.5 CUCM SIP Trunk Screen Captures for SP1 This section contains the SIP trunk settings used during SP1 testing. Please note that the Media Termination Point Required box is not checked. This allows CUBE to perform the Early Offer/Delayed Offer (EO/DO) conversion. The screen captures in this section use a 4 digit phone extension. Within the Call Routing Information, the Inbound Calls section has the Significant Digits* set to 4 and the option for Redirecting Diversion Header Delivery - Inbound is checked. Within the Outbound Calls section the Calling Party Selection* is set to Originator and the Caller ID DN is left blank because CUBE is configured to add the NPA-NXX via a SIP profile rule. The option for Redirecting Diversion Header Delivery - Outbound is checked. In the CUCM with CUBE SIP Trunk Screen Capture Part 3 under the SIP Information parameters the Destination Address must be set to CUBE's IP address. CUBE's sip-server address must be set to XO’s Sonus NBS signaling IP address. CUCM with CUBE SIP Trunk Screen Capture Part 1


PAGE 22 of 54

CUCM with CUBE SIP Trunk Screen Capture Part 2


PAGE 24 of 54








2.1.1.6 CUCM SIP Trunk Screen Captures with CLID Blocked for SP1 The screen captures in this section show the SIP trunk configuration settings where the caller ID is blocked by using a separate route pattern. In the CUCM with CUBE CLID Blocked SIP Trunk Screen Capture Part 3 under the Outbound Calls section, the Calling Line ID Presentation* and the Calling Name Presentation* fields are set to Restricted. This SIP trunk will block the caller ID for all outbound calls. In the same screen capture under the SIP Information parameters the Destination Address must be set to CUBE's IP address. CUBE's sip-server address must be set to XO’s Networks NBS signaling IP address. CUCM with CUBE CLID Blocked SIP Trunk Screen Capture Part 1


PAGE 26 of 54

CUCM with CUBE CLID Blocked SIP Trunk Screen Capture Part 2


PAGE 28 of 54








2.1.1.7 CUCM SIP Trunk Screen Captures for SP2 This section contains the SIP trunk settings used during SP2 testing. Please note that the Media Termination Point Required box is not checked. This allows CUBE to perform the Early Offer/Delayed Offer (EO/DO) conversion. The screen captures in this section use a 4 digit phone extension. Within the Call Routing Information, the Inbound Calls section has the Significant Digits* set to 4 and the option for Redirecting Diversion Header Delivery - Inbound is checked. Within the Outbound Calls section the Calling Party Selection* is set to Originator and the Caller ID DN is left blank because CUBE is configured to add the NPA-NXX via a SIP profile rule. The option for Redirecting Diversion Header Delivery - Outbound is checked. In the CUCM with CUBE SIP Trunk Screen Capture Part 3 under the SIP Information parameters the Destination Address must be set to CUBE's IP address. CUBE's sip-server address must be set XO’s Sonus NBS signaling IP address. CUCM with CUBE SIP Trunk Screen Capture Part 1


PAGE 30 of 54



PAGE 32 of 54








2.1.1.8 CUCM SIP Trunk Screen Captures with CLID Blocked for SP2 The screen captures in this section show the SIP trunk configuration settings where the caller ID is blocked by using a separate route pattern. This SIP trunk will block the caller ID for all outbound calls. In the CUCM with CUBE CLID Blocked SIP Trunk Screen Capture Part 3 under the Outbound Calls section, the Calling Line ID Presentation* and the Calling Name Presentation* fields are set to Restricted. In the same screen capture under the SIP Information parameters the Destination Address must be set to CUBE's IP address. CUBE's sip-server address must be set to XO Communications’ Sonus NBS signaling IP address. CUCM with CUBE CLID Blocked SIP Trunk Screen Capture Part 1


PAGE 34 of 54



PAGE 36 of 54








2.1.2 CUCM Phone Configuration Using a Four Digit Extension CUCM Phone Screen Configuration Using a Four Digit Extension


PAGE 38 of 54

2.1.3 CUCM MoH Server Codec Selection When configuring the customer for SP1 or SP2, the MoH Server Codec setting under CUCM administration, Service Parameters, Cisco IP Voice Media Streaming Application, Clusterwide Parameters, the codec selection displayed under Supported MoH Codecs must be set to G.711ulaw for SP1 and G.729 for SP2 accordingly. G.711ulaw is the system default. The codec must be selected and saved as shown in the screen captures below. The highlighted codec indicates the codec that is currently in use. MoH Server Codec Screen Capture Part 1







MoH Server Codec Screen Capture Part 2


PAGE 40 of 54

2.1.4 CUCM Enterprise Parameters: DSCP Bit Settings for Signaling and Media

The screen capture below shows the DSCP bit settings for the CUCM phones for signaling and media. The DSCP for Cisco CallManager to Device Interface* parameter is the signaling setting which is AF31 and the DSCP for Phone Configuration* parameter is the media setting which is EF. The CUCM server must be rebooted for these changes to take effect.







2.1.5 CUCM Conference Bridge Configuration for SP1 The screen capture below shows the CUCM conference bridge resource parameters listed under CUCM Administration, Media Resources for the default CUCM conference bridge. The CUCM software conference bridge was used to verify SP1 three and four way conference bridging test cases. This is a software resource that runs on the CUCM server itself versus the external conference bridge resource for SP2 which must run on CUBE due to the G.729 codec requirement discussed in the next section. This screen can also be used to verify that the CUCM conference bridge resource is registered by checking the registration state of the device.


PAGE 42 of 54

2.1.6 CUCM Conference Bridge Configuration for SP2 The screen capture below shows the Conference Bridge resource parameters listed under CUCM Administration, Media Resources. An external conference bridge resource is configured using CUBE which registers with the CUCM. This conference bridge resource was used in testing SP2 conference bridging for three and four way conference calls. When the CUCM is configured for SP1 which uses the G.711 codec, the CUCM uses its own software conference bridge. However when the CUCM is configured for SP2 which uses the G.729 codec, the conference bridge must be supported on an external device such as CUBE. This screen can also be used to verify that the CUBE conference bridge resource is registered with the CUCM by checking the registration state.







2.2 CUBE Configuration Details

The following sections provide a brief description regarding CUBE’s flow-through versus flow-around modes for media and which was used during lab testing. 2.2.1 CUBE Flow-Through Mode When the Media Termination Point (MTP) box is not checked on the CUCM SIP trunk, the CUCM is automatically configured to send Delayed Offer (DO) SIP INVITEs to initiate calls. This means the CUCM sends SIP INVITEs to the CUBE without the Session Description Protocol (SDP) portion. CUBE inserts the SDP portion into the INVITEs which converts the INVITEs to Early Offer (EO) INVITEs before they are forwarded to XO Communications’ Sonus NBS. When the DO/EO conversion capability of the CUCM with CUBE is used the media must be passed "through" the CUBE where it will insert its own IP address in the media packets for XO Communications’ Sonus NBS to send media to in place of the CUCM phone IP address. 2.2.2 CUBE Flow-Around Mode When the MTP box is checked on the CUCM SIP trunk, the CUCM uses MTPs to create Early Offer (EO) INVITEs. This means that the CUCM will insert the SDP portion into the INVITE before sending it to CUBE. When the CUCM is configured for SP1 which uses the G.711 codec, the MTP resource must be a software resource existing on the CUCM server or a CUCM media server within the cluster. If the CUCM is configured for SP2 which uses G.729 as the preferred codec, software MTPs must be configured on an external hardware device such as the Cisco 2800 or 3800 series ISR which can provide up to 500 MTPs per platform. When the CUCM is configured for SP2 the software MTPs must be handled externally because the CUCM does not support software MTPs for the G.729 codec. The external resources running on the ISR register transcoder, conference bridge and soft MTP resources with the CUCM media resource pools. These media resource types are processed with an IOS router or by using DSP resources that are installed on the external MTP device where the total MTPs resources are dependent on the quantity of DSP hardware installed such as PVDM2 modules. In flow-around mode the media passes through the CUBE unaltered. 2.2.3 Flow-Through versus Flow-Around Design Considerations Flow-around mode was researched on the CUBE to scale the number of SIP sessions that can be processed through the platform. However, the CUCM must either have MTPs or DO/EO conversions configured on the CUBE in order to interoperate with the XO SIP or ESIP service. This means that the customer will be limited based on the number of MTPs available or they will be limited based on the number of CUBE DO/EO sessions. This is because DO/EO on the CUBE


PAGE 44 of 54

and flow-around mode are mutually exclusive. Cisco Systems confirmed that using DO/EO requires flow-through mode. This limits the number of sessions based on the size of the CUBE platform used. The customer will either need to scale by increasing the number of MTPs available or increase the number of CUBE devices. Please note that when the CUCM was configured for DO/EO with the CUBE configured for flow-around mode, the XO lab experienced a one way media problem for all calls where there was no media in the PSTN to CUCM direction. For the XO lab configuration where the Sonus NBS performed the transcoding, CUBE was configured in flow-through mode with only a conference bridge resource using PVDM2s. Initial testing revealed that transcoding and software MTPs were not used on CUBE thus, these resource command lines were removed from the CUBE configuration. 2.2.4 Correcting the CUCM Diversion Header Problem With CUBE When

Using 4 Digit CUCM Phone Extensions During the XO lab’s evaluation of XO SIP/ESIP and CUCM without CUBE (with CUCM software version 8.0.3.10000-8), a diversion header problem was discovered where the NPA-NXX is not prefixed to the four digit extension number for the user portion of the diversion header. This problem affected PSTN-to-PSTN call transfers that use Call Forward Always (CFA), Call Forward On Busy (CFOB), and Call Forward No Answer (CFNA) where a four digit extension is used for the CUCM phones because the original caller ID is not delivered to the final PSTN destination. When the CUCM is configured to use CUBE running on a Cisco 2821 ISR, a SIP profile can be used to modify the diversion header to correct this problem. For the lab scenario a SIP profile was written for CUBE to modify the diversion header by adding the NPA-NXX to the 4 digit extension in the user portion of the diversion header. What follows is the sip profile rule used during lab testing: voice class sip-profiles 1 request INVITE sip-header Diversion modify "<sip:(.*)@201.1.3.254>" "<sip:469387\[email protected]>" Please note that a customer CUCM environment may have several NPA-NXXs or other phone extension digit configurations that will require different SIP profile rules and translation rules to be designed using CUBE that are unique to each customer environment.







2.2.5 CUBE SIP Profile Rules to Correct MoH Issue XO’s BroadSoft servers modify the "a=send only" SDP attribute received in a re-INVITE to "a=inactive" which prevents MoH from being heard on the destination phone when a call is placed on hold from the CUCM. To workaround this issue, the following sip profile rules need to be included in the CUBE “voice class sip-profiles” section of the configuration. These rules allow the MoH to be heard at the destination phone when the call is placed on hold from the CUCM phone. voice class sip-profiles 1 request REINVITE sdp-header Audio-Attribute modify "inactive" "sendrecv" request ACK sdp-header Audio-Attribute modify "sendonly" "sendrecv" response 200 sdp-header Audio-Attribute modify "sendonly" "sendrecv" 2.2.6 CUBE Conference Bridge Configuration for SP1 CUCM conference calls were observed to use the CUCM default conference bridge resource when configured for SP1. This is the reason a "dspfarm profile 3 conference" resource is not configured in CUBE. 2.2.7 CUBE Conference Bridge Configuration for SP2 CUCM conference calls were observed not to use the CUCM default conference bridge when configured for SP2. This is the reason a "dspfarm profile 3 conference" bridge is configured in CUBE. If the G.711 ulaw codec is listed in the conference profile along with the G.729 and G.729a codecs, the conference bridge will establish using the codec with the highest bandwidth which is G.711 ulaw. When configuring the customer for SP2, the G.711 ulaw codec must be removed from the profile list to save bandwidth over the SIP trunk. If the customer prefers the CUCM to use more bandwidth for the conference call then the G.711 ulaw codec needs to remain in the CUBE "dspfarm profile 3 conference" resource. 2.2.8 CUBE DSCP Bit Settings for Signaling and Media The CUBE voip dial peer default DSCP bit settings for signaling is AF31 and for media is EF. These settings do not appear in the configuration when a show configuration is executed at the CLI prompt. However, the settings can be displayed by executing the command “show dial-peer voice #” at the CLI prompt for each voip dial peer where the # represents the dial peer number.


PAGE 46 of 54

3 Equipment Configuration Files and Additional Information This section contains the configuration files used during XO lab testing for the Cisco 2821 ISR running CUBE. It also contains details on XO network settings that need to be checked for CUCM with CUBE to work properly with XO SIP and ESIP.

3.1 Additional Information for CFA, CFOB, and CFNA Call Transfer Scenarios Using a Four digit Phone Extension

Although CUBE allows the CUCM diversion header to be corrected through the use of a SIP profile, XO must make some setting changes in Broadsoft and in XO’s Sonus PSX, which your XO representatives will configure at time of install.

3.2 Cisco 2821 ISR Running CUBE Software

The following sections contain the CUBE test configurations used during the XO lab’s SP1 and SP2 testing and are provided as a reference. 3.2.1 CUBE Configuration File for Service Package 1 CUBE's sip-server address must be set to XO’s Sonus NBS signaling IP address. C2821CUBE#more cube-sp1.cfg ! ! Last configuration change at 18:49:47 UTC Wed Sep 22 2010 ! version 15.1 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname C2821CUBE ! boot-start-marker boot-end-marker ! ! no logging buffered enable secret 5 $1$dgKR$TQ5lvonJvCjRAWx7.cyIX0 ! no aaa new-model ! ! dot11 syslog ip source-route ! ! ip cef !







! ! no ip domain lookup no ipv6 cef ! multilink bundle-name authenticated ! ! ! ! ! ! ! voice service voip ip address trusted list ipv4 205.158.163.0 255.255.255.0 allow-connections sip to sip no supplementary-service sip moved-temporarily redirect ip2ip no fax-relay sg3-to-g3 sip header-passing error-passthru early-offer forced midcall-signaling passthru sip-profiles 1 ! voice class media 1 ! voice class codec 1 codec preference 1 g711ulaw ! voice class sip-profiles 1 request INVITE sip-header Diversion modify "<sip:(.*)@201.1.3.254>" "<sip:469387\[email protected]>" request REINVITE sdp-header Audio-Attribute modify "inactive" "sendrecv" request ACK sdp-header Audio-Attribute modify "sendonly" "sendrecv" response 200 sdp-header Audio-Attribute modify "sendonly" "sendrecv" ! ! ! ! voice translation-rule 1 rule 1 /^$....$$/ /469387\1/ ! ! voice translation-profile Sonus_NBS_Outgoing translate calling 1 ! ! voice-card 0 dsp services dspfarm !


PAGE 48 of 54

crypto pki token default removal timeout 0 ! ! ! ! license udi pid CISCO2821 sn FHK1023F1J8 archive log config hidekeys ! redundancy ! ! ! ! ! ! ! ! ! ! interface GigabitEthernet0/0 description Connection to CUCM3560 port 23 ip address 201.1.3.252 255.255.255.0 duplex auto speed auto ! interface GigabitEthernet0/1 no ip address shutdown duplex auto speed auto ! no ip forward-protocol nd no ip http server no ip http secure-server ! ! ip route 0.0.0.0 0.0.0.0 201.1.3.1 ! logging esm config ! ! ! ! ! ! control-plane ! ! ! mgcp fax t38 ecm !







! dial-peer voice 10 voip description Outgoing dial-peer to Sonus NBS translation-profile outgoing Sonus_NBS_Outgoing destination-pattern .T session protocol sipv2 session target sip-server voice-class codec 1 voice-class sip dtmf-relay force rtp-nte voice-class sip early-offer forced voice-class sip profiles 1 dtmf-relay rtp-nte no vad ! dial-peer voice 11 voip description Outgoing dial-peer to CUCM destination-pattern 46938739.. session protocol sipv2 session target ipv4:201.1.3.254 voice-class codec 1 voice-class sip dtmf-relay force rtp-nte voice-class sip early-offer forced dtmf-relay rtp-nte no vad ! ! sip-ua sip-server ipv4:205.158.163.138 ! ! banner login ^C ** Welcome to the Cisco2821 running CUBE **^C ! line con 0 session-timeout 120 exec-timeout 60 0 absolute-timeout 180 flowcontrol hardware line aux 0 line vty 0 4 exec-timeout 3600 0 password labbgp1 login transport input all ! scheduler allocate 20000 1000 end C2821CUBE#


PAGE 50 of 54

3.2.2 CUBE Configuration File for Service Package 2 CUBE's sip-server address must be set to XO’s Sonus NBS signaling IP address. C2821CUBE#more cube-sp2.cfg ! ! Last configuration change at 15:57:55 UTC Wed Sep 22 2010 ! version 15.1 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname C2821CUBE ! boot-start-marker boot-end-marker ! ! enable secret 5 $1$dgKR$TQ5lvonJvCjRAWx7.cyIX0 ! no aaa new-model ! ! dot11 syslog ip source-route ! ! ip cef ! ! ! no ip domain lookup no ipv6 cef ! multilink bundle-name authenticated ! ! ! ! ! ! ! voice service voip ip address trusted list ipv4 205.158.163.0 255.255.255.0 allow-connections sip to sip no supplementary-service sip moved-temporarily redirect ip2ip no fax-relay sg3-to-g3 sip header-passing







error-passthru early-offer forced midcall-signaling passthru sip-profiles 1 ! voice class media 1 ! voice class codec 1 codec preference 1 g729r8 codec preference 2 g711ulaw ! voice class sip-profiles 1 request INVITE sip-header Diversion modify "<sip:(.*)@201.1.3.254>" "<sip:469387\[email protected]>" request REINVITE sdp-header Audio-Attribute modify "inactive" "sendrecv" request ACK sdp-header Audio-Attribute modify "sendonly" "sendrecv" response 200 sdp-header Audio-Attribute modify "sendonly" "sendrecv" ! ! ! ! voice translation-rule 1 rule 1 /^$....$$/ /469387\1/ ! ! voice translation-profile Sonus_NBS_Outgoing translate calling 1 ! ! voice-card 0 dsp services dspfarm ! crypto pki token default removal timeout 0 ! ! ! ! license udi pid CISCO2821 sn FHK1023F1J8 archive log config hidekeys ! redundancy ! ! ! ! ! ! ! ! ! !


PAGE 52 of 54

interface GigabitEthernet0/0 description Connection to CUCM3560 port 23 ip address 201.1.3.252 255.255.255.0 duplex auto speed auto ! interface GigabitEthernet0/1 no ip address shutdown duplex auto speed auto ! no ip forward-protocol nd no ip http server no ip http secure-server ! ! ip route 0.0.0.0 0.0.0.0 201.1.3.1 ! logging esm config ! ! ! ! ! ! control-plane ! ! ! mgcp fax t38 ecm ! sccp local GigabitEthernet0/0 sccp ccm 201.1.3.254 identifier 1 version 7.0 sccp ! sccp ccm group 1 bind interface GigabitEthernet0/0 associate ccm 1 priority 1 associate profile 3 register CFB0018191A4CB0 ! dspfarm profile 3 conference codec g711ulaw codec g729r8 codec g729ar8 maximum sessions 8 associate application SCCP ! dial-peer voice 10 voip description Outgoing dial-peer to Sonus NBS translation-profile outgoing Sonus_NBS_Outgoing destination-pattern .T session protocol sipv2







session target sip-server voice-class codec 1 voice-class sip dtmf-relay force rtp-nte voice-class sip early-offer forced voice-class sip profiles 1 dtmf-relay rtp-nte no vad ! dial-peer voice 11 voip description Outgoing dial-peer to CUCM destination-pattern 46938739.. session protocol sipv2 session target ipv4:201.1.3.254 voice-class codec 1 voice-class sip dtmf-relay force rtp-nte voice-class sip g729 annexb-all voice-class sip early-offer forced dtmf-relay rtp-nte no vad ! ! sip-ua sip-server ipv4:205.158.163.138 ! ! banner login ^CC ** Welcome to the Cisco2821 running CUBE **^C ! line con 0 session-timeout 120 exec-timeout 60 0 absolute-timeout 180 flowcontrol hardware line aux 0 line vty 0 4 exec-timeout 3600 0 password labbgp1 login transport input all ! scheduler allocate 20000 1000 end C2821CUBE#

3.3 Cisco 3560 PoE Configuration File

xo sip packages 1 and 2, implemented with cisco unified … · · 2016-09-15a. hardware: cisco...

Documents