SIP Trunking Configuration Guide For Cisco Unified C Ommunications Manager 10.5.1.10000-7 (CUCM) Version With Cisco Unified Border Element (CUBE)

SIP Trunking Configuration
Guide for Cisco Unified

Communications Manager
(CUCM) Version 10.5.1.10000-7
with Cisco Unified Border
Element (CUBE)
SIP Trunking Configuration Guide for Cisco Unified Communication
Manager with CUBE
Table of Contents
Introduction ....................................................................................................... …2
Executive Summary……………………………………………………………………..2
Equipment Hardware and Software Requirements ...............................................3
Test Configurations ...............................................................................................5
CUCM Configurations……………………………………………..……………………6
CUBE Configuration Details. ............................................................................... 41
Equipment Configuration Files and Information……………………………………47
© Copyright 12/16/2014. XO Communications, LLC. All rights reserved. XO, the XO design logo, and all related marks are
trademarks of XO Communications, LLC. All other trademarks are property of their respective owners. 1
Manager with CUBE
1. Introduction
This document contains the test results of the SIP Trunking evaluation performed on the
CUCM version 10.5.1.10000-7 connected to a Cisco 2821 Integrated Services Router
(ISR) running CUBE software version c2800nm-advipservicesk9-mz.151-4.M6.bin and a
Cisco 2432-24FXS Internet Access Device (IAD) acting as a router. The Cisco ATA187
was used to test FAX pass through and FAX Relay. The ATA187 was connected to the
Cisco 3560 PoE switch. The Cisco IAD was connected to the Juniper Networks ERX
1400 via a T1 configured for Point-to-Point Protocol (PPP). Cisco 7961 IP phones running
SCCP software downloaded from the CUCM were connected to the CUCM via a Cisco
3560 Power over Ethernet (PoE) switch. The Cisco 2821 ISR was also connected to the
Cisco 3560. The Cisco 3560 switch is up linked to the Cisco IAD via Fast Ethernet port
0/0. The customer LAN will connect directly to the Cisco IAD via a separate Ethernet port
and not the Cisco 3560 switch which is reserved only for Cisco IP phones.
Starting from version 10, all the components of CUCM is required to use virtualization. A
VMware (Virtual Machine Ware) ESXi was installed as native operating system after UCS
server was booted up. Two virtual machines CUCM and CUC were installed on the top
of ESXi. Each one of CUCM, CUC, and ESXi has its own IP address. For detail, please
see the Section 4 – Test configuration.
2. Executive Summary
This configuration guide provides the settings used during the lab evaluation for the
CUCM with CUBE with XO Communications SIP Trunking service. The following is a
summary of the issues addressed and the limitations found during the lab evaluation.
- SP2 fax pass-through in both directions fails with no work-around when SP1
fax pass-through works in both directions.
- CUCM doesn’t support in-band DTMF.
Manager with CUBE
SP1 and SP2 G.711 Pass-through and T.38 FAX Issues and Workarounds
Pkg Codec DTMF Fax

1 G.711 RFC 2833 (in-band DTMF is G.711
NOT supported) passthrough
and T.38
are
supported
2 G.729a/G.711 RFC 2833 (in-band DTMF is (G.711
NOT supported) passthrough is
NOT
supported.)
T.38 is
supported
Registration: Static
3. Equipment Hardware and Software Requirements for Testing
1. CUCM Server
a. Hardware: Cisco UCS server model No. UCSC-C220-M3S
b. Software Version: CUCM 10.5.1.10000-7
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-4.M6.bin”
3. Cisco Unity Connection (CUC) Voice Mail Server

a. Hardware: Cisco UCS server model No. UCSC-C220-M3S
b. Software Version: CUC 10.5.1.10000-7
4. CUCM and Cisco Unity Connection (CUC) PC GUI Access

a. Microsoft Internet Explorer version 8.0.7601.17514
5. Cisco Phones
a. Cisco 7961
Manager with CUBE
b. Software Version: SCCP41.9-3-1-1S
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
8. SIP Trunking PBXs Approved for Use

a. Cisco: 2811 CME, 2821 CME, Cisco UC520
b. Digium IP PBX
c. Avaya: IPO 406, IPO 500
9. VMware ESXi: version 5.1.0

vSphere Client: version 5.1.0
Manager with CUBE
4. Test Configurations
4.1. Lab Configuration: CUCM with CUBE running on a Cisco 2821 ISR and the Cisco 2432-
24FXS IAD Acting as a Router
The diagram below shows the configuration used during lab testing. The CUCM
does not support fax directly. External devices such as a Cisco 2800 or 3800
series ISR running CUBE software, a Cisco 2900 or 3900 Series ISR G2 running
CUBE software, a Cisco ATA187, or a CUCM SIP trunk to a Right FAX server
can be used. The lab tested FAX pass through and T.38 FAX using a Cisco
ATA187.
Note: Above lab setup only shows main lab network elements.
Manager with CUBE
5. Test Bed Configuration Files: CUCM Configuration Details

5.1 CUCM Configuration Details
5.1.1 The following sections contain configuration information that is useful in configuring the
CUCM and CUBE.
5.2 CUCM Configuration Details
5.2.1 CUCM Region and Device Pool Configuration Description
5.3 The following sections contain a brief description of the CUCM region and device pool
configurations used during testing.
5.3.1 CUCM Region and Device Pool Configuration for SP1 with CUBE
5.4 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.
5.4.1 CUCM Region Screen Capture for SP1 with CUBE CUCM
Region Information Screen Capture for SP1 with CUBE
Manager with CUBE
5.5 CUCM Device Pool Screen Capture for SP1 with CUBE
Default Device Pool Configuration Screen Capture Part 1
Manager with CUBE
Manager with CUBE
5.6. 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.
Manager with CUBE
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.
5.6.1. CUCM Region Screen Capture for SP2 with CUBE
XO G.729 Region Information Screen Capture for SP2 with CUBE
5.7. CUCM Device Pool Screen Capture for SP2 with CUBE
G.729 SIP Trunk Device Pool Information Screen Capture Part 1
Manager with CUBE
G.729 SIP Trunk Device Pool Information Screen Capture Part 2
Manager with CUBE
G.729 SIP Trunk Device Pool Screen Capture Part 3
Manager with CUBE
5.8.1. CUCM SIP Profile and SIP Trunk Configuration Screen Captures
5.8.1.1. CUCM SIP Profile Configuration Screen Capture
This section contains the SIP Profile used during service package 1 and 2 testing.
Manager with CUBE
SIP Profile Configuration Screen Capture Part 1
Manager with CUBE
Manager with CUBE
Manager with CUBE
5.9. CUCM SIP Trunk Security Profile Configuration

5.9.1. This section contains the SIP Trunk Security Profile used during SP1 and
SP2 testing.
CUCM SIP Trunk Security Profile Screen Capture
Manager with CUBE
5.10. 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
Manager with CUBE
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 the Sonus Networks NBS signaling IP address.
CUCM with CUBE SIP Trunk Configuration Screen Capture Part 1
Manager with CUBE
Manager with CUBE
Manager with CUBE
5.11. 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
Manager with CUBE
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 the Sonus Networks NBS signaling IP address.
CUCM with CUBE CLID Blocked SIP Trunk Configuration Screen Capture Part 1
Manager with CUBE
Manager with CUBE
Manager with CUBE
5.12. 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
Manager with CUBE
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 the Sonus Networks NBS signaling IP address.
Manager with CUBE
Manager with CUBE
Manager with CUBE
5.13. CUCM SIP Trunk Screen Captures with CLID Blocked for SP2
Manager with CUBE
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 the Sonus Networks NBS signaling IP address.
Manager with CUBE
Manager with CUBE
Manager with CUBE
5.14. CUCM Phone Configuration Using a Four Digit Extension
CUCM Phone Screen Configuration Using a Four Digit Extension
Manager with CUBE
5.15. CUCM MoH Server Codec Selection
Manager with CUBE
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

Manager with CUBE
Manager with CUBE
5.16. 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.
Manager with CUBE
5.17. 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.
Manager with CUBE
5.18. 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.
6. CUBE Configuration Details
Manager with CUBE
6.1. 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.
6.1.1. Correcting the CUCM Diversion Header Problem With CUBE When Using
4 Digit CUCM Phone Extensions
6.1.2. 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:
6.1.3. voice class sip-profiles 1

6.1.4. request INVITE sip-header Diversion modify "<sip:(.*)@201.1.3.254>"
"<sip:469387\[email protected]>"
6.1.5. Please note that a customer CUCM environment may have several
NPANXXs 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.
6.1.6. CUBE SIP Profile Rules to Correct MoH Issue

6.1.7. These configuration commands are still required in the CUBE sip profile
section of the configuration for the remote party to hear MoH when the
call is placed on hold from a CUCM phone.
6.1.8. CUBE SIP Profile Rules for MoH to Work Properly:

6.1.9. voice class sip-profiles 1
6.1.10. request REINVITE sdp-header Audio-Attribute modify "inactive"
"sendrecv"
6.1.11. request ACK sdp-header Audio-Attribute modify "sendonly" "sendrecv"
6.1.12. response 200 sdp-header Audio-Attribute modify "sendonly" "sendrecv"
6.1.13. CUBE DSCP Bit Settings for Signaling and Media

6.1.14. 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
Manager with CUBE
voice #” at the CLI prompt for each voip dial peer where the # represents
the dial peer number.
6.1.15. Configuring the CUCM and Cisco ATA187 for FAX Pass Through or T.38
FAX Relay
6.2. This section provides CUCM and ATA187 configuration information for configuring
the CUCM and the Cisco ATA187 for FAX pass through and T.38 FAX relay.
6.2.1. Configuring the CUCM to Recognize the Cisco ATA187

6.3. Using the Cisco Unified CM Administration, under Device, Phone then click on the
Add New button. Under Phone Type* select ATA187 then click next. Enter the
MAC Address*, Description and Device Pool* information. In the Product Specific
Configuration Layout section, set the Fax Mode* field accordingly and save the
configuration.
Cisco ATA187 Device Information Configuration Screen Capture 1
Cisco ATA187 Device Information Configuration Screen Capture 2
Manager with CUBE
6.4. Configuring the Cisco ATA187

Using the Cisco provided instructions for the ATA187, configure the device such that
it shows up in the Cisco Unified CM Administration under Device, Phones as
registered with the CUCM as shown in the first line item entry under Device Name
Manager with CUBE
“ATAF02572784B29” in the screen capture below.
6.5. Configuring the Cisco ATA187 for FAX Pass Through

In the CUCM screen capture above, click on the ATA187 in question, then scroll
down to the Product Specific Configuration Layout section and set the Fax Mode*
option to Fax Pass-through as shown in the screen capture below and save. No
other settings were modified.
ATA187 Fax Pass Through Screen Capture

Manager with CUBE
6.6. Configuring the Cisco ATA187 for T.38 FAX Relay

In the CUCM screen capture above, click on the ATA187 in question, then scroll
down to the Product Specific Configuration Layout section and set the Fax Mode*
option to T.38 Fax Relay as shown in the screen capture below and save. No other
settings were modified.
ATA187 Fax Relay Screen Capture
Manager with CUBE
6.6.1. CUBE FAX Pass Through and T.38 FAX Relay Commands
This section contains the FAX specific commands that are required in the CUBE
configuration for FAX Pass Through and T.38 FAX Relay to work properly.
For FAX pass through, under the voice service voip section of the configuration,
add the command “fax protocol pass-through g711ulaw”. For FAX relay under
the voice service voip section of the configuration, add the command “fax
protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none”.
7. Equipment Configuration Files and Information
This section contains the Cisco 2821 ISR running CUBE, Cisco 3560 PoE, and
Cisco 2432-24FXS IAD and Juniper 1400 ERX configuration files used during
testing. It also contains a BroadSoft and Sonus Networks PSX screen capture
for settings that need to be checked for CUCM with CUBE to work properly in
production.
Manager with CUBE
7.1. Cisco 2821 ISR Running CUBE Software

The following sections contain the CUBE test configuration used during SP1 and
SP2 testing.
7.1.1. CUBE Configuration File for Service Package 1

CUBE's sip-server address must be set to the Sonus Networks NBS signaling IP
address.
C2821CUBE#wr t
Building configuration...
Current configuration : 2982 bytes

!
! Last configuration change at 18:42:51 UTC Mon Apr 8 2013 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
!
Manager with CUBE
!
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
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback passthrough
g711ulaw 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>"
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
!
Manager with CUBE
!
voice-card 0 dsp services
dspfarm
!
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
!
!
!
!
!
!
Manager with CUBE
!
control-plane
!
!
!
mgcp fax t38 ecm
!
mgcp profile default
!
!
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
Manager with CUBE
C2821CUBE#
7.1.2. CUBE Configuration File for Service Package 2

CUBE's sip-server address must be set to the Sonus Networks NBS signaling IP
address.
C2821CUBE#wr t

!
! Last configuration change at 23:07:17 UTC Mon Dec 15 2014
version 15.1
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
!
!
!
Manager with CUBE
!
!
!
!
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
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-throug
h g711ulaw
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>"
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
Manager with CUBE
!
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
!
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
!
!
!
!
!
!
Manager with CUBE
!
control-plane
!
!
!
mgcp fax t38 ecm
!
mgcp profile default
!
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..
modem passthrough nse codec g711ulaw
session protocol sipv2
session target ipv4:201.1.3.254
voice-class codec 1
voice-class sip dtmf-relay force rtp-nte
Manager with CUBE
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 ^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#
7.2. Cisco 3560 PoE Configuration File

This file contains the device configuration used during the evaluation.
CUCM3560#wr t

!
version 12.2 no
service pad
service timestamps log datetime msec no
service password-encryption
!
Manager with CUBE
hostname CUCM3560
!
boot-start-marker
boot-end-marker
!
enable secret 5 $1$T/F4$rIWfQ68OVzIO7yXqFxU0z1
!
no aaa new-model
system mtu routing 1998
vtp mode transparent ip
subnet-zero
!
!
!
crypto pki trustpoint TP-self-signed-3561089152
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-3561089152
revocation-check none rsakeypair TP-self-signed-
3561089152
!
!
crypto pki certificate chain TP-self-signed-3561089152
certificate self-signed 01
30820240 308201A9 A0030201 02020101 300D0609 2A864886 F70D0101
04050030
31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D
43657274
69666963 6174652D 33353631 30383931 3532301E 170D3933 30333031
30303030
35305A17 0D323030 31303130 30303030 305A3031 312F302D 06035504
03132649
4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D33
35363130
38393135 3230819F 300D0609 2A864886 F70D0101 01050003 818D0030
81890281
8100A233 FA77DC4C 79C0503F E8067FFD 629619E3 12F8CE94 ACBAB5B9
A7A6787F
DF892A30 8B0ADB48 869FF69D 14D3E262 FCC507AD 7FE382C1
0D1C3527 A1248C79
A0E58516 A8AA5928 7F66A66B B11C8C9B 50AE7253 CFFE55C3 58879021
9790C696
97C57B28 8C387F05 0EBBFF92 B630154D 516B9AAE 6127E87C 490C57B6
E294A5A2
Manager with CUBE
F6A70203 010001A3 68306630 0F060355 1D130101 FF040530 030101FF

30130603
551D1104 0C300A82 0843434D 33353630 2E301F06 03551D23 04183016
801405B2
76A81F94 38A596E0 20B6DCE5 9975EF1A 714B301D 0603551D 0E041604
1405B276
A81F9438 A596E020 B6DCE599 75EF1A71 4B300D06 092A8648 86F70D01
01040500
03818100 6E703269 5AC65206 E33DB499 5D0A7BC5 25331F18 DB839656
96D586DE
25BF6112 81585C1E 08A2331F AFE173E1 587BEE7C 4A726698 C3DA2709
C0E36E45
9F7881BE 8E707424 CB5EE28E 446402E2 0217A5FD F25D5D0D F0A045C0
AD8D8305
79B1C9E5 7DBF1E6B 4AA13B9A 75DF2E79 8A948C0C F8A65AEA
8E2E105C 961ABD0F FFB8A470
quit
!
!
!
!
!
spanning-tree mode pvst spanning-tree
extend system-id
!
vlan internal allocation policy ascending
!
vlan 10,99-101,200
!
!
!
!
interface FastEthernet0/1
description Connection to Cisco Unified Call Manager
switchport access vlan 10 switchport mode access
speed 100
duplex full
!
description Connection to Cisco Unity Connection Voice Mail
switchport access vlan 10 switchport mode access
speed 100
duplex full
Manager with CUBE
!
switchport access vlan 10
switchport mode access
!
!
!
!
!
!
!
!
!
!
!
!
Manager with CUBE
!
!
!
!
!
!
!
!
!
!
!
!
interface Vlan1
no ip address
shutdown
!
interface Vlan10 description CUCM3560
Telnet Connection ip address 201.1.3.249
255.255.255.0
!
ip classless ip http
server ip http
secure-server !
!
!
control-plane
!
banner login ^C
** Welcome to the CUCM 3560PoE **^C
!
Manager with CUBE
line con 0
line vty 0 4
password labbgp1
login line vty 5 15
password cisco
login
!
end
CUCM3560#

SIP Trunking Configuration Guide For Cisco Unified C Ommunications Manager 10.5.1.10000-7 (CUCM) Version With Cisco Unified Border Element (CUBE)

Uploaded by

Copyright:

Available Formats

SIP Trunking Configuration Guide For Cisco Unified C Ommunications Manager 10.5.1.10000-7 (CUCM) Version With Cisco Unified Border Element (CUBE)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SIP Trunking Configuration Guide For Cisco Unified C Ommunications Manager 10.5.1.10000-7 (CUCM) Version With Cisco Unified Border Element (CUBE)

Uploaded by

Copyright:

Available Formats

What are the main components used in the SIP trunking configuration?

What are the main components used in the SIP trunking configuration?

What protocols and software versions are used?

What protocols and software versions are used?

SIP Trunking Configuration

Guide for Cisco Unified

Pkg Codec DTMF Fax

3. Equipment Hardware and Software Requirements for Testing

2. Cisco 2821 ISR running CUBE software

3. Cisco Unity Connection (CUC) Voice Mail Server

4. CUCM and Cisco Unity Connection (CUC) PC GUI Access

b. Software Version: SCCP41.9-3-1-1S

6. Cisco 2432-24FXS IAD

7. Cisco Catalyst 3560 PoE series P-24

8. SIP Trunking PBXs Approved for Use

9. VMware ESXi: version 5.1.0

5. Test Bed Configuration Files: CUCM Configuration Details

Default Device Pool Configuration Screen Capture Part 1

Default Device Pool Configuration Screen Capture Part 2

Default Device Pool Configuration Screen Capture Part 3

5.6.1. CUCM Region Screen Capture for SP2 with CUBE

XO G.729 Region Information Screen Capture for SP2 with CUBE

G.729 SIP Trunk Device Pool Information Screen Capture Part 1

G.729 SIP Trunk Device Pool Information Screen Capture Part 2

G.729 SIP Trunk Device Pool Screen Capture Part 3

SIP Profile Configuration Screen Capture Part 1

SIP Profile Configuration Screen Capture Part 2

SIP Profile Configuration Screen Capture Part 3

SIP Profile Configuration Screen Capture Part 4

5.9. CUCM SIP Trunk Security Profile Configuration

CUCM SIP Trunk Security Profile Screen Capture

5.10. CUCM SIP Trunk Screen Captures for SP1

CUCM with CUBE SIP Trunk Configuration Screen Capture Part 1

CUCM with CUBE SIP Trunk Configuration Screen Capture Part 2

CUCM with CUBE SIP Trunk Configuration Screen Capture Part 3

CUCM with CUBE SIP Trunk Configuration Screen Capture Part 4

5.12. CUCM SIP Trunk Screen Captures for SP2

CUCM with CUBE SIP Trunk Configuration Screen Capture Part 1

CUCM with CUBE SIP Trunk Configuration Screen Capture Part 2

CUCM with CUBE SIP Trunk Configuration Screen Capture Part 3

CUCM with CUBE SIP Trunk Configuration Screen Capture Part 4

5.14. CUCM Phone Configuration Using a Four Digit Extension

CUCM Phone Screen Configuration Using a Four Digit Extension

5.15. CUCM MoH Server Codec Selection

MoH Server Codec Screen Capture Part 1

MoH Server Codec Screen Capture Part 2

5.17. CUCM Conference Bridge Configuration for SP1

5.18. CUCM Conference Bridge Configuration for SP2

6. CUBE Configuration Details

6.1.3. voice class sip-profiles 1

6.1.6. CUBE SIP Profile Rules to Correct MoH Issue

6.1.8. CUBE SIP Profile Rules for MoH to Work Properly:

6.1.13. CUBE DSCP Bit Settings for Signaling and Media

6.2.1. Configuring the CUCM to Recognize the Cisco ATA187

Cisco ATA187 Device Information Configuration Screen Capture 1

Cisco ATA187 Device Information Configuration Screen Capture 2

6.4. Configuring the Cisco ATA187

“ATAF02572784B29” in the screen capture below.

6.5. Configuring the Cisco ATA187 for FAX Pass Through