Guide Business Talk IP Cisco
Guide Business Talk IP Cisco
connection to Business Talk IP service : it shall not be used for other goals or in another context.
Document Version
Version of 06/10/2017
Table of contents
The aim of this document is to list technical requirements to ensure the interoperability between Cisco
CUCM IPBX with Business Talk IP SIP, hereafter so-called “service”.
2 Architecture overview
2.1 CUCM without CUBE
CUCM
SBC
Nominal
Business Talk
CE
SBC
Backup
signalization
media
All SIP trunks attached directly to CUCM
CUCM
SBC
Nominal
Business Talk
CE
SBC
Backup
signalization
media
All SIP trunks attached to the CUBE. Signaling and media flows cross the CUBE.
SBC
Backup
signalization
All SIP trunks attached to the CUBE. Signaling flows cross the CUBE, but media flows go
directly towards endpoints.
Cisco IPBX
Equipment validation IPBX
Equipment status
Version Version
R10.5 / R10.6 Load 10.5.2.12901-1 min
CUCM
R11 Load 11.0.1.10000-10 min
CBE5000/6000 R11.5 Load 11.5.1.11900-26 min
Cisco ecosystems
Equipment validation IPBX
Equipment Comment
Version status Version
10.5.2.10-15 R10.5
Attendant
Console
CUxAC 11.0.1.3058 R11.0 Standard and Advanced editions
11.5.x R11.5
10.5.2.10000-15 R10.5
Unity Connection 11.0.1.20000-2 R11.0
Voice Mail 11.5.x R11.5
Unity Express
11.0.x R11.0
11.5.x R11.5
CUPS
10.5.2.10000-9 R10.5
As a component of CUPC only
not supported R11.x
Unified
Communica- not supported R10.5
tions
Meeting place 11.0.x R11.0
11.5.x R11.5
10.6.1.10000-39 R10.5
Contact
center
UCCX 11.0.1.10000-75 R11.0
11.5.x R11.5
R10.x
Cisco VoIP GW R11.x
VOIP
OneAccess VoIP GW R10.x
(Business Livebox) R11.x
Cisco Unified
10.5.2.12901-1 R10.5
Communication
Manager Assistant
11.0.1.10000-10 R11.0
(IPMA)
11.5.1.11900-26 R11.5
All Cisco SCCP R10.x
phones (skinny) R11.x
R10.x
All Cisco SIP phones R11.x
Phones
IPCommunicator R10.x
SCCP R11.x
Jabber
10.5.2 R10.5
11.5.0 R11.x
CUCILync
9.7.4 R10.5
R11.x
Cisco CUBE
Equipment validation IPBX
Equipment Comment
Version status Version
R10.5 CUBE authorized on demand with
Cisco Unified Border Element on demand versions CUCM 10.5 and 11.0
R11.0
(CUBE) - “flow thru” mode
15.5(3)S4a R11.5 IOS 15.6 authorized on demand
Cisco Unified Border Element R10.5
on demand
(CUBE) - “flow around” mode R11.x
Media Resources
Transcoder configuration : Warning! Hardware MTP resources on IOS Gateway and software MTP
resource on CUCM are NOT SUPPORTED. Software MTPs on
IOS Gateway are SUPPORTED in BT/BTIP SIP Trunking.
Menu Value
Media Resources > Transcoder > Add new
Transcoder Type Cisco IOS Enhanced Media Termination Point
Device Name Use the name configured in sccp ccm group in the IOS
Device Pool Use the appropriate Device Pool
Trusted Rely Point Unchecked
Media Resources
Conference Bridge configuration
Media Resources > Conference Bridge > Add new
Conference Bridge Type Cisco IOS Enhanced Media Termination Point
Device Name Use the name configured in sccp ccm group in the IOS
Device Pool Use the appropriate Device Pool
Device Security Mode Non Secure Conference Bridge
Media Resources
Multicast Music on Hold
CUCM configuration - Region
System > Region Information > Region > Add new
New Region Please refer to chapter on Region configuration for
additional information.
With this configuration, all devices in “MoH Multicast”
region will use G.711 as codec for sending RTP packets
to devices to all other regions and also for the “WAN”
region where codec G.711 will be used.
Media Resources
Multicast Music on Hold
CUCM configuration – Device Pool
System > Device Pool > Add new
New Device Pool Choose a name and associate the Region “MoH
Multicast” to this new Device Pool.
Media Resources
Multicast Music on Hold
CUCM configuration - Audio Source Configuration
Media Resources > Music On Hold Audio Source > Add new
Play continuously (repeat) Checked
Allow Multicasting Checked
Media Resources
Multicast Music on Hold
CUCM configuration - Multicast MoH server configuration
Menu Value
Media Resources > Music On Hold Server
Device Pool Checked
Enable Multi-cast Audio Sources on this MoH Server Checked
Base Multi-cast IP Address 239.1.1.1 (example)
Base Multi-cast IP Port 16384 (example)
Increment Multi-cast on IP Address
Max Hops (per Audio Source in Selected Audio 1
Sources configuration area)
Media Resources
Multicast Music on Hold
CUCM configuration - Multicast MoH server configuration
Media Resources > Media Resource Group
Appropriate Media Resource Group Check the Use Multicast for MoH Audio checkbox to
allow multicast with this resource group.
Media Resources
Multicast Music on Hold
Router configuration – Audio file
Frequency 9kHz
Coded with 8bit
Audio mode Mono
Codec type CCITT u-law
Media Resources
Multicast Music on Hold
Router configuration – IOS Commands
Commands ccm-manager music-on-hold
call-manager-fallback
max-conferences 4
ip source-address 10.108.105.254 port 2000
max-ephones 24
max-dn 48
moh TheJourneyAndTheWind.alaw.wav
multicast moh 239.1.1.1 port 16384 route 210.72.240.13 10.108.105.254
Media Resources
Multicast Music on Hold
Media Resource Group Lists configuration
Media resources Warning! Media Resources, which are not associated with any MRG are
available to every device in the cluster by default.
Name DIV-HEADER-PT
Off-net calling via BT/BTIP
Diversion Header manipulation
Called Party Transformation Pattern
Call Routing -> Transformation -> Transformation Pattern -> Called PartyTransformation Pattern ->
Add New
Pattern XXXX
Prefix digits Site Prefix
Off-net calling via BT/BTIP
Diversion Header manipulation
Calling Search Space
Call Routing -> Class of Control -> Calling Search Space -> Add New
Name DIV-HEADER-CSS
Selected Partitions DIV-HEADER-PT
Off-net calling via BT/BTIP
Basic Configuration
Sip Trunk Security Profile
System > Security > SIP Trunk Security Profile, select “Non Secure SIP Trunk Profile” from SIP Trunk
Security Profile List
Incoming Transport Type TCP + UDP
Outgoing Transport Type UDP
Off-net calling via BT/BTIP
Basic Configuration
SIP Profile
Device > Device Settings > SIP Profile
User-Agent and Server header information Send Unified CM Version Information as User-Agent
Header
Version in User Agent and Server Header Full Build
SIP Rel1XX Options Send PRACK for 1xx Messages
Early Offer support for voice and video Mandatory (insert MTP if needed)
Send send-receive SDP in mid-call INVITE Checked
Ping Interval for In-service and Partially In-service 300
Trunks (seconds)
Ping Interval for Out-of-service Trunks (seconds) 5
Version in User Agent and Sever Header Full build
Session Refresh Method INVITE or UPDATE
Version in User Agent and Sever Header - inject info about full version of CUCM
Session Refresh Method - since CUCM 10.0 there is additional method – “UPDATE”. “INVITE” should be
used by default.
if reason
then
msg:removeHeader("Reason")
end
end
return M
SME Architecture
Off-net calling via BT/BTIP
SIP Trunk Security Profile (at CUCM SME and CUCM)
Device > Device Settings > SIP Profile
User-Agent and Server header information Send Unified CM Version Information as User-Agent
Header
Version in User Agent and Server Header Full Build
SIP Rel1XX Options Send PRACK for 1xx Messages
Early Offer support for voice and video calls (insert Checked
MTP if needed)
Send send-receive SDP in mid-call INVITE Checked
Ping Interval for In-service and Partially In-service 300
Trunks (seconds)
Ping Interval for Out-of-service Trunks (seconds) 5
SME Architecture
Off-net calling via BT/BTIP
SIP Normalization Script (at CUCM SME)
Device > Device Settings > SIP normalization script > Add new
SIP Normalization Script is applied to SIP trunk at CUCM SME and is required to adapt the SIP
signaling to the form expected by BT/BTIP infrastructure. Create the script.
The content of the script is given below:
then
msg:modifyHeader("Reason", "Q.850; cause=27")
else
msg:addHeader("Reason", "Q.850; cause=27")
end
end
pai = msg:getHeader("P-Asserted-Identity")
--check if Pai header is not present
if pai==nil
then
-- add Pai header filled with From URI value
local uri = string.match(from, "(<.+>)")
msg:addHeader("P-Asserted-Identity", uri)
end
end
end
return M
SME Architecture
Off-net calling via BT/BTIP
SIP Trunk Configuration to offnet (at CUCM SME)
Menu Value
Device > Trunk > Add new
Device Pool Choose Device Pool which include Region and Location
value
Media Resource Group List None
Redirecting Diversion Header Delivery - Inbound Checked
Destination Address SBC IP Address
SIP Trunk Security Profile SIP Trunk Secure Profile name
SIP Profile Standard SIP Profile with PRACKs, EO and Send-recv
Normalization Script SIP Normalization Script name
Enable Trace Unchecked
SME Architecture
Off-net calling via BT/BTIP
Route group (at CUCM SME)
Call Routing > Route/Hunt > Route group > Add new
Distribution algorithm Top Down
Selected devices both SIP trunks to ACMEs
SME Architecture
Off-net calling via BT/BTIP
Route list (at CUCM SME)
Call Routing > Route/Hunt > Route list > Add new
Selected Groups Route Group with SIP trunks to BT/BTIP
SME Architecture
Off-net calling via BT/BTIP
Route pattern (at CUCM SME)
Call Routing > Route/Hunt > Route Pattern > Add new
Route Pattern Specific Route Pattern
Gateway/Route List Route List name
Call Classification OffNet
Discard Digits PreDot Trailing#
SME Architecture
On-net calling
The configuration of such intercluster SIP Trunk is the same as the one described for off-net calls
except for:
Media Resource Group List – should be set to the group containing following resources:
conference, transcoder, annuciator (Subscribers), MOH Server (Subscribers), software MTP
SIP Normalization Script should not be added to this trunk
SIP Trunks should be between CUCM of independent site and CUCM SME (there is no direct
SIP Trunks between independent sites in SME Architecture – all on-net calls are managed by
CUCM SME).
CSS_LINE associated to the line deals with general call right except emergency numbers.
CSS_PHONE associated to the phone deals with emergency calls. This CSS should be unique for
each site.
Device > Phone > Calling Search Space
Associate the calling search spaces for emergency numbers with particular phones (deivces), and
calling search spaces for non-emergency numbers with lines.
Device > Phone -> find a phone ->Calling select the proper CSS
Search Space field
Device > Phone -> find a phone ->select the line select the proper CSS
on the left menu -> Calling Search Space field
Survivable Remote Site Telephony configuration
SRST mode is not supported with BT/BTIP infrastructure but with local PSTN gateway configured on
CE router
CUCM Administration > User management > End Create UCCX administrative user in CUCM
users
UCCX administration > Tools > User Management select this user as administrator
> Administrator capability view
Tools > Plugin > Desktop suite > Client Run the Unified CCX Desktop Client Configuration
Configuration Tool Tool
Applications > Application Management Add a new Cisco script application
From the Application Type drop-down menu, choose Cisco Script Application and select your script or
the standard ICD script SSCRIPT[ics.aef].
Set the value for CSQ variable: check the checkbox next to it and enter “mycsq” (will be created later)
into the text area. (quotation marks are required)
Configure a new trigger for this application (Add new trigger), this is the CTI route point, which will
route calls to this application
Testing your System and the Unified CCX Script
Use one of your IP phones to call the Unified CM Telephony trigger.
If you get the welcome prompt, then the icd.aef script is working
Provisioning UCCX - Configuring IP Phone Agent service
User Management > End User In the Controlled Devices list box below the
Device Information section, select the agent’s
phone device.
Phone > Subscribe services dropbox Subscribe all agents’ phones to this newly
created service
Create an application user named “telecaster” with “telecaster” as the password (or whatever BIPPA
user ID and password was specified in the CAD Configuration Setup utility).
Assign the telecaster application user to all the IP agent phones
Provisioning UCCX - Provisioning Call Control Group
Subsystems > Unified CM Telephony > Call Provision Unified CM Telephony call control
Control Group groups
Synchronize Cisco JTAPI Client and Unified CM Telephony Data (this creates all necessary CTI devices
on CUCM using AXL interface)
Provisioning UCCX - Configuring Customer Service Queues
Subsystems > RmCm > RmCm Provider Provision the RmCm Provider to allow the RmCm
Subsystem to be in service.
Subsystems > RmCm > Skills Create skills..
Subsystems > RmCm > Resources Assigning skills to agents
Subsystems > RmCm > Contact Service Queues Creating Contact Service Queues
Subsystems > RmCm > Teams Creating teams and assigning agents to teams
Menu Value
UCCX administration > System > System G711
Parameters > Media Parameters > Codec
DTMF support An MTP or transcoder is needed to translate the
DTMFs sent through a SIP trunk.
Menu Value
Engineering > CUCM connectivity CUCM parameters, if blank, enter CUCM IP address in
name field, port number (443), and user name and
password of application user.
Engineering > Database Management Parameters for the SQL server, if blank enter IP address
of machine where SQL server is installed, specify user
name, and password of application user
System Configuration > System Device Menagment
CT Gateway Devices> From 6301 (example)
CT Gateway Devices> To 6302 (example)
Service Devices> From 6401 (example)
Service Devices>To 6402 (example)
Park Devices>From 6501 (example)
Park Devices>To 6502 (example)
System Configuration > System Device Menagment Synchronize with CUCM (Devices will be added
automatically to CUCM)
User Configuration > General Properties
Minimum internal device digit length 1
Maximum internal device digit length 7
External access number 8
Note! Such configuration is necessary to perform successful delayed transfer. Although etting external access
number makes it impossible to perform onnet connections to numbers beginning with 8 (i.e LO BLB) as even
though they are seven digits numbers, they are traeted as external numbers. Refer to mantis ticket 2462.
User Configuration > Queue Management
Team Dev1
DDI 6100 (example)
Synchronize with CUCM Will be automatically added to CUCM as CTI port
User Configuration > Operator Management
Login Name OPERATOR1 (example)
Password Set password
Confirm Password Confirm password
Associated Queues Associate queue created in previous step
CISCO UNIFIED ATTENDAND CONSOLE
Menu Value
Installation When asked enter the IP address of Cisco
Unified Attendant Server
Select the language for application
Follow on screen instruction until installation I
completed
Login Login with credentials created in previous step
CISCO UNIFIED COMMUNICATION MANAGER
User Management > Application User > CUDAC
Controlled Devices Associate devices added by CUDAC Admin
Device > CTI route point > Route point created by CUDAC Admin
Media Resource Group List MRGL_MTP_XCODE
network interface
Note : for two SIP trunks two IP addresses must be configured.
interface GigabitEthernet0/0
description CUBE Voice Interface
no ip address
duplex auto
speed auto
!
interface GigabitEthernet0/0.<INTERFACE>
description *** CUBE ***
encapsulation dot1Q <INTERFACE>
ip address <IP_ADDR> <Mask>
SNMP Server
Global settings
Codecs
For customers using G.711 alaw codec:
sip-ua
retry invite 1
retry response 2
retry bye 2
retry cancel 2
reason-header override
connection-reuse
g729-annexb override
timers options 1000
To enable the translation to PAID privacy headers in the outgoing header on a specific dial peer, use
the voice-class sip asserted-id pai command in dial peer voice configuration mode:
CUBE needs to be configured with physical interface will be configured with a secondary IP
address.
CUCM will be configured with a Route List composed of (at least) 4 Route Groups. Each route
group will include SIP trunk to one of CUBE IP Address (Primary or Secondary). On each route
group parameters, a specific prefix should be defined (one prefix for each RG). This way the
CUBE will be able to route the outgoing calls to the right SBC, depending on this prefix value:
answer-address <INTERFACE>....
destination-pattern <INTERFACE>....
voice-class codec 1
dtmf-relay rtp-nte
no vad
preference 1
answer-address <INTERFACE>....
destination-pattern <INTERFACE>....
voice-class codec 1
dtmf-relay rtp-nte
no vad
huntstop
destination-pattern 113T
voice-class codec 1
dtmf-relay rtp-nte
no vad
huntstop
destination-pattern 114T
voice-class codec 1
dtmf-relay rtp-nte
no vad
answer-address +.T
voice-class codec 1
dtmf-relay rtp-nte
no vad
The prefix should be stripped using voice translation rules before sending the call to the
infrastructure.
CUBE needs to be configured with physical interface will be configured with a secondary IP
address.
CUCM will be configured with a Route List composed of (at least) 2 Route Groups. Each route
group will include one of the SIP trunk configured. On each route group parameters, a specific
prefix should be defined. This way the CUBE will be able to route the outgoing calls to the right
SBC, depending on this prefix value:
description **CUCMBE**
answer-address 227....
destination-pattern 227....
[…]
answer-address 227....
destination-pattern 11T
session-target <SBC1_IP>
[…]
answer-address 227....
destination-pattern 12T
session-target <SBC2_IP>
[…]
answer-address +.T
voice-class codec 1
dtmf-relay rtp-nte
no vad
CUBE needs to be configured with physical interface will be configured with a secondary IP
address.
CUCM will be configured with a Route List composed of (at least) 2 Route Groups. Each route
group will include one of the SIP trunk configured. On each route group parameters, a specific
prefix should be defined. This way the CUBE will be able to route the outgoing calls to the right
SBC, depending on this prefix value:
preference 1
answer-address 227....
destination-pattern 227....
voice-class codec 1
[…]
preference 2
answer-address 227....
destination-pattern 227....
voice-class codec 1
[…]
preference 1
answer-address 227....
destination-pattern 11T
session-target <SBC1_IP>
[…]
preference 2
answer-address 227....
destination-pattern 12T
session-target <SBC2_IP>
[…]
answer-address +.T
voice-class codec 1
dtmf-relay rtp-nte
no vad