and 2, implemented With Cisco Unified Border Control Element (CUBE)

Transcription

1 XO SIP Service Customer Configuration Guide for Cisco Unified Communications Manager (CUCM) 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

2 SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE Control Element (CUBE) Contents and 2, implemented With Cisco Unified Border Control Element (CUBE) About This Document... 3 Known Issues... 3 Registration Method... 4 XO SIP Service Packages Supported... 4 CUCM Configuration for XO SIP... 7 CUBE Configuration Details XO COMMUNICATIONS CONFIDENTIAL 1

3 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) IP PBX, implemented with Cisco Unfied Border Control Element (CUBE), deployed with an XOprovided 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 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 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 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 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 Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 2 of 54

4 o 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 Border Control Element (CUBE) 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 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 XO COMMUNICATIONS CONFIDENTIAL 3

5 Registration Method Static registration is utilized between the CUCM 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 (see Known Issues above) 2 G.729a RFC2833 Fax was not tested on CUCM (see Known Issues above) 1.1. Testing of CUCM Software and Hardware Versions Tested 1. CUCM Server a. Hardware: Cisco MCS 7800 Series Product No MCS7825H3-K9- CMB2 b. Software Version: CUCM 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 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 CUCM and Cisco Unity Connection (CUC) PC GUI Access a. Microsoft Internet Explorer version xpsp_sp2_gdr Cisco Phones a. Cisco 7961 b. Software Version: SCCP S 6. Cisco FXS IAD a. Software Version: c2430-mz.xo 7. Cisco Catalyst 3560 PoE series P-24 a. Software Version: c3560-advipservicesk9-mz se2.bin Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 4 of 54

6 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 CUCM XO Lab Test Configuration Border Control Element (CUBE) XO VoIP Network T1, NxT1 or DS3 Serial Link XO Demarc Router CUCM Customer owned and maintained device CUBE 10/100 Ethernet Switch or 10/100 Power over Ethernet (PoE) Switch TN#1 IP Phone TN#2 IP Phone TN#3 IP Phone TN#4 IP Phone XO COMMUNICATIONS CONFIDENTIAL 5

7 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 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: st.html. For design guidance for CUCM and Cisco Unified Communications products based on CUCM, see the Solution Reference Network Design (SRND) guides: sign_guides_list.html 2 CUCM and CUBE Configuration 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 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. Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 6 of 54

8 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 CUCM Region Screen Capture for SP1 with CUBE Border Control Element (CUBE) XO COMMUNICATIONS CONFIDENTIAL 7

9 CUCM Device Pool Screen Capture for SP1 with CUBE Default Device Pool Screen Capture Part 1 Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 8 of 54

10 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 Default Device Pool Screen Capture Part 2 Border Control Element (CUBE) XO COMMUNICATIONS CONFIDENTIAL 9

11 Default Device Pool Screen Capture Part 3 Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 10 of 54

12 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 Default Device Pool Screen Capture Part 4 Border Control Element (CUBE) 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. XO COMMUNICATIONS CONFIDENTIAL 11

13 CUCM Region Screen Capture for SP2 with CUBE XO G.729 Region Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 12 of 54

14 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 CUCM Device Pool Screen Capture for SP2 with CUBE Border Control G.729 SIP Trunk Device Pool Screen Capture Part 1 Element (CUBE) XO COMMUNICATIONS CONFIDENTIAL 13

15 G.729 SIP Trunk Device Pool Screen Capture Part 2 Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 14 of 54

16 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 G.729 SIP Trunk Device Pool Screen Capture Part 3 Border Control Element (CUBE) XO COMMUNICATIONS CONFIDENTIAL 15

17 G.729 SIP Trunk Device Pool Screen Capture Part 4 Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 16 of 54

18 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 CUCM SIP Profile Screen Capture This section contains the SIP Profile used during service package 1 and Border 2 Control testing. Element (CUBE) SIP Profile Screen Capture Part 1 XO COMMUNICATIONS CONFIDENTIAL 17

19 SIP Profile Screen Capture Part 2 Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 18 of 54

20 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 SIP Profile Screen Capture Part 3 Border Control Element (CUBE) XO COMMUNICATIONS CONFIDENTIAL 19

21 CUCM SIP Trunk Security Profile This section contains the SIP Trunk Security Profile used during SP1 and SP2 testing. Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 20 of 54

22 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 CUCM SIP Trunk Screen Captures for SP1 This section contains the SIP trunk settings used during SP1 testing. Please Border Control note that the Media Termination Point Required box is not checked. This Element allows (CUBE) 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 XO COMMUNICATIONS CONFIDENTIAL 21

23 CUCM with CUBE SIP Trunk Screen Capture Part 2 Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 22 of 54

24 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 CUCM with CUBE SIP Trunk Screen Capture Part 3 Border Control Element (CUBE) XO COMMUNICATIONS CONFIDENTIAL 23

26 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 CUCM SIP Trunk Screen Captures with CLID Blocked for SP1 The screen captures in this section show the SIP trunk configuration settings Border Control where the caller ID is blocked by using a separate route pattern. In the CUCM Element (CUBE) 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 XO COMMUNICATIONS CONFIDENTIAL 25

27 CUCM with CUBE CLID Blocked SIP Trunk Screen Capture Part 2 Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 26 of 54

28 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 CUCM with CUBE CLID Blocked SIP Trunk Screen Capture Part 3 Border Control Element (CUBE) XO COMMUNICATIONS CONFIDENTIAL 27

30 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 CUCM SIP Trunk Screen Captures for SP2 This section contains the SIP trunk settings used during SP2 testing. Please Border Control note that the Media Termination Point Required box is not checked. This Element allows (CUBE) 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 XO COMMUNICATIONS CONFIDENTIAL 29

32 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 CUCM with CUBE SIP Trunk Screen Capture Part 3 Border Control Element (CUBE) XO COMMUNICATIONS CONFIDENTIAL 31

34 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 CUCM SIP Trunk Screen Captures with CLID Blocked for SP2 The screen captures in this section show the SIP trunk configuration settings Border Control where the caller ID is blocked by using a separate route pattern. This SIP Element trunk (CUBE) 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 XO COMMUNICATIONS CONFIDENTIAL 33

36 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 CUCM with CUBE CLID Blocked SIP Trunk Screen Capture Part 3 Border Control Element (CUBE) XO COMMUNICATIONS CONFIDENTIAL 35

38 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 CUCM Phone Configuration Using a Four Digit Extension Border Control Element (CUBE) CUCM Phone Screen Configuration Using a Four Digit Extension XO COMMUNICATIONS CONFIDENTIAL 37

39 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 Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 38 of 54

40 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 MoH Server Codec Screen Capture Part 2 Border Control Element (CUBE) XO COMMUNICATIONS CONFIDENTIAL 39

41 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. Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 40 of 54

42 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 CUCM Conference Bridge Configuration for SP1 The screen capture below shows the CUCM conference bridge resource Border Control parameters listed under CUCM Administration, Media Resources for the Element default (CUBE) 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. XO COMMUNICATIONS CONFIDENTIAL 41

43 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. Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 42 of 54

44 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 Border Control 2.2 CUBE Configuration Details Element (CUBE) 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 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 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 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 XO COMMUNICATIONS CONFIDENTIAL 43

45 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 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 ), 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:(.*)@ >" "<sip:469387\1@ >" 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. Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 44 of 54

46 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 CUBE SIP Profile Rules to Correct MoH Issue XO s BroadSoft servers modify the "a=send only" SDP attribute received Border in a re- Control INVITE to "a=inactive" which prevents MoH from being heard on the destination Element (CUBE) 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 sipprofiles 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" 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 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 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. XO COMMUNICATIONS CONFIDENTIAL 45

47 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 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 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 Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 46 of 54

48 SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE Control (CUBE) and 2, implemented With Cisco Unified Border no ip domain lookup no ipv6 cef multilink bundle-name authenticated voice service voip ip address trusted list ipv 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:(.*)@ >" "<sip:469387\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" voice translation-rule 1 rule 1 /^$...$$/ /469387\1/ voice translation-profile Sonus_NBS_Outgoing translate calling 1 voice-card 0 dsp services dspfarm Element Control Element (CUBE) XO COMMUNICATIONS CONFIDENTIAL 47

49 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 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 logging esm config control-plane mgcp fax t38 ecm Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 48 of 54

50 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 session protocol sipv2 session target ipv4: 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: 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 password labbgp1 login transport input all scheduler allocate end C2821CUBE# SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE Control (CUBE) and 2, implemented With Cisco Unified Border Element Control Element (CUBE) XO COMMUNICATIONS CONFIDENTIAL 49

51 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 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 ipv allow-connections sip to sip no supplementary-service sip moved-temporarily redirect ip2ip no fax-relay sg3-to-g3 sip header-passing Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 50 of 54

52 SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE Control (CUBE) and 2, implemented With Cisco Unified Border 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:(.*)@ >" "<sip:469387\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" 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 Element Control Element (CUBE) XO COMMUNICATIONS CONFIDENTIAL 51

53 interface GigabitEthernet0/0 description Connection to CUCM3560 port 23 ip address 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 logging esm config control-plane mgcp fax t38 ecm sccp local GigabitEthernet0/0 sccp ccm identifier 1 version 7.0 sccp sccp ccm group 1 bind interface GigabitEthernet0/0 associate ccm 1 priority 1 associate profile 3 register CFB A4CB0 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 Product SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE PAGE 52 of 54

54 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 session protocol sipv2 session target ipv4: 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: 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 password labbgp1 login transport input all scheduler allocate end C2821CUBE# SIP Configuration Guide for Cisco Unified Communications Manager 8.0.3, Packages 1&2, with CUBE Control (CUBE) and 2, implemented With Cisco Unified Border Element Control Element (CUBE) 3.3 Cisco 3560 PoE Configuration File XO COMMUNICATIONS CONFIDENTIAL 53