Accelerator Cisco UCM Express Integration Guide

ACCELERATOR 6.
3
CISCO UNIFIED COMMUNICATION MANAGER
EXPRESS INTEGRATION GUIDE
April 2014
Tango Networks, Inc. phone: +1 469-229-6000

3801 Parkwood Blvd, Suite 500 fax: +1 469-467-9840
Frisco, Texas 75034 USA www.tango-networks.com
Accelerator 6.3 Cisco Unified Communication Manager Express Integration Guide
© 2004 - 2014 Tango Networks, Inc..
This software is protected by copyright law and international treaties, and is the confidential and
proprietary information of Tango Networks, Inc. Unauthorized reproduction, use, or distribution of
this software, or any portion of it, may result in severe civil and criminal penalties, and will be
prosecuted to the maximum extent possible under the law. The software described in this
document is furnished under license agreement and may only be used in accordance with the
terms of the agreement. Tango Networks and Abrazo are trademarks of Tango Networks, Inc. All
other trademarks used herein are the property of their respective owners and are used for
identification purposes only.
© 2004 - 2014 Tango Networks, Inc..
Tango Networks, Abrazo and E=fmc2 are trademarks or registered trademarks of Tango
Networks, Inc. All other trademarks or service marks are the property of their respective owners.
Specifications and features are subject to change without notice.
April 2014 CONFIDENTIAL Page 2 of 28

TABLE OF CONTENTS
INTRODUCTION ............................................................................................. 4
SUPPORTED VERSIONS ......................................................................................................... 5
PBX DEPENDENCIES – MOBILE UC........................................................................................... 5
ACCELERATOR INTEGRATION PROCESSES ........................................................ 6

CISCO UNIFIED COMMUNICATIONS MANAGER EXPRESS PROVISIONING .................................................. 6
MOBILE UC AND PSTN ACCESS ENABLED ACCELERATOR .................................................................. 6
MOBILE UC ENABLED ACCELERATOR ......................................................................................... 6
CUCME Configuration ............................................................................................ 7
CSTA configuration for Call Move in CUCME 8.0 Only ...............................................13
PSTN ACCESS ENABLED ACCELERATOR .....................................................................................17
ACCELERATOR PROVISIONING ................................................................................................18
Mobile UC Enabled Accelerator ..............................................................................18
Voice Network: PBX/Trunk Dial Plan .............................................................18
Voice Network: Extension Ranges ................................................................19
Voice Network : Voice Mail ..........................................................................19
Subscriber Dial Plan/Subscriber ...................................................................19
PSTN Access Enabled Accelerator ..........................................................................20
Voice Network : PBX/Trunk Dial Plan ............................................................20
MOBILE UC FEATURE INTERACTIONS ............................................................. 21

ACCELERATOR PBX LEVEL 1 INTEGRATION .................................................................................21
ACRONYMS ................................................................................................. 26

Introduction
The Accelerator can potentially be provisioned in one of three ways based on

your Accelerator license key. Your license key dictates whether your
enterprise has the ability to enable Mobile UC and/or PSTN Access (SIP
Trunking) functionality.
During Accelerator provisioning, a Carrier(s) was created that enabled one or

both of these services. How you integrate your CUCME PBX with the
Accelerator depends on how your Carrier(s) is configured on the Accelerator.
 Mobile UC - The Mobile UC application extends PBX and Unified

Communications (UC) features to mobile devices. Examples include Single
Number, Single Voicemail, Abbreviated Dialing, and Presence Status.
For Mobile UC, the Accelerator uses a combination of SIP lines and trunks
to integrate with the CUCME PBX. SIP lines are used so that Accelerator-
controlled mobile devices appear as standard SIP phones and therefore
benefit from the common set of PBX services offered to such devices. SIP
trunks are used when the Accelerator must terminate a call via the Public
Switched Telephone Network (PSTN). CSTA (CUCME 8.0 only) must be
enabled to support Call Move service.
 PSTN Access (e.g. SIP Trunking Controller) – PSTN Access facilitates

interworking between enterprise and SIP entities such as PBXs and PSTN
carriers (i.e. SIP Trunking Service Providers) as well as between internal
enterprise SIP entities.
For PSTN Access, the Accelerator uses only SIP trunk(s) to integrate with
the CUCME PBX.
Important Note: Through out this document and other Tango

documents the term PSTN Access is used to describe the functions of
the SIP Trunking Controller product. These terms are interchangeable.
Whenever you see PSTN Access we are talking about the SIP Trunking
Controller.
Mobile UC and SIP Trunking combination – It is possible to have both

the Mobile UC functionality as well as the PSTN Access functionality enabled
on your Accelerator.

Supported Versions
This document addresses the way that the Accelerator integrates with Cisco
Unified Communications Manager Express 7.1 and 8.0. The document
will encompass any release of the Unified Communications Manager Express.
The screen captures on this document may vary depending on your release.
It is intended for users with a thorough understanding of the Cisco Unified
Communications Manager Express.
Note: This guide is meant to familiarize the reader with the minimum
provisioning steps required on the CUCME PBX for Accelerator
integration. It does not attempt to address all possible configurations
options or features that can be applied within the PBX. Please consult
your CUCME documentation for Cisco Unified Communication Manager
Express specific issues.
PBX Dependencies – Mobile UC
The following lists the Cisco Unified Communications Manager Express

components and license keys required for interoperating with the Accelerator:
 Cisco Unified Communications Manager
 Three incremental Device License Units (DLUs) per Accelerator Subscriber
o Each Accelerator-enabled mobile is configured as a Third Party Basic
SIP device. Each of these devices requires three DLUs each.

Accelerator Integration Processes
Cisco Unified Communications Manager Express Provisioning
The integration with the Accelerator can be setup in several ways. During
Accelerator provisioning, your enterprise selected Carrier types based on your
Accelerator enterprise license key. Your license key may be enabled for
Mobile UC functionality or it may be enabled for PSTN Access functionality, or
even both.
The sections and steps outlined below will guide your workflow to integrate
your Cisco Unified Communication Manager Express PBX with the Accelerator.
Mobile UC and PSTN Access Enabled Accelerator
For a Mobile UC and PSTN Access enabled Accelerator, execute both sets of
steps outlined below; Mobile UC Enabled Accelerator section and the PSTN
Access Enabled Accelerator section. It does not matter which set you execute
first, meaning it does not matter if you provision PSTN Access first or Mobile
UC first.
Mobile UC Enabled Accelerator
The Cisco Unified Communications Manager Express (CUCME) is provisioned

manually through a telnet session. The following section lists the
commands necessary to integrate the Accelerator with the CUCME.
The Accelerator integrates with the CUCME via SIP Trunk provisioning within
the Unified Communications Manager Express to provide full functionality.
The following steps are based under the understanding that SIP calls have
already been enabled along with having SIP Devices provisioned
appropriately.

CUCME Configuration
Note: The Unified Communications Manager Express server(s) must first

be configured appropriately with domain and host information as well as
SIP Calls and SIP devices enabled as per Unified Communications
Manager Express documentation.
After ensuring that the Unified Communications Manager Express server(s)

are configured appropriately with domain and host information, use the
following steps to establish a SIP connection between the Accelerator and the
Unified Communications Manager Express.
Ensure that the Accelerator has been provisioned with the appropriate CUCME
server information as shown in the section PSTN Access Enabled Accelerator
To make the Accelerator the ingress/egress point for off net calls between the
PBX and your SIP Trunk provider, modify your PBX’s routing tables to send
off-net calls over a SIP Trunk to the Accelerator on the SIP Trunking port
(default of 5080). This SIP Trunk should also allow incoming calls from the
Accelerator. Make sure any required Class of Service attributes are set
appropriately on the PBX. On-net calls between PBX’s can also be configured
to route via the Accelerator using a similar process. It is often desirable to
create a second SIP Trunk on the PBX in order to specify different Class of
Service attributes for on-net calls. Consult your PBX’s configuration guide for
specific details on SIP Trunk configuration.
Accelerator Provisioning on page 18 of this document.

1. Using a terminal, access the Unified Communications Manager Express
server by using the command telnet <hostname>, where
<hostname> is the hostname of the Unified Communications Manager
Express server or the IP Address. Log in with the appropriate credentials:
telnet <hostname>
2. Once inside the CUCME server, view the current configuration:
sh run
3. Copy the information displayed by the previous command into a text file
in case this configuration needs to be reset on the server.
4. Enter configuration mode by beginning the server’s configuration terminal
with the following command (where ‘t’ stands for terminal):
conf t
5. In order to unblock RTP packets, enter the following command:
ip source-route

6. Enable the CUCME server to allow two-way RTP traffic:
voice rtp send-recv
7. Enter the domain for the CUCME PBX. The domain correlates to the PBX
domain provisioned on the Accelerator.
ip domain name tango-networks.com
8. Configure DNs for SIP Phones:

 Provide a number for the DN (e.g. 2676007).
 Register the DN for SIP Message Waiting Indicator (MWI) service.
 Repeat for each SIP Phone Number needed.
voice register dn 7
number 2676007
mwi
voice register dn 8
number 2676008
mwi
voice register dn 9
number 2676009
mwi
9. This step is optional. For older phones (e.g. 7940/60 phones), setup a
dial plan to allow faster dialing from SIP phones so that the “Dial” key
does not need to be pressed or the user has to wait for an inter-digit
timeout for the CUCME to initiate a call:
 Select '7940-7960-others' for type
 Provide dial patterns for easier dialing (for example):
o Short desk numbers (4-digit dial)
o Full desk numbers (7-digit dial)
o Direct Inward Dialing (DID) numbers (10-digit dial)
o Pilot DN (10-digit dial)
voice register dialplan 1
type 7940-7960-others
pattern 1 6...
pattern 2 267....
pattern 3 267467....
pattern 4 667467....

1. Configure physical SIP phones so that each one is represented as a pool.

 Provide MAC address of device
 Assign a directory number for device
 Set DTMF relay mode to rtp-nte (allows 2833 events)
 Assign username/password to be used by client for authentication.
o The username/password does not need to be a DN. The
username/password is not tied to the DN being registered, Rather,
they are merely credentials for the SIP device from this MAC address.
If a SIP phone supports multiple lines, each line can be a different
number providing the same authentication credentials, since the
device is the same.
 Set the preferred voice codec for the phone (e.g., g711ulaw)
 Disable voice activity detection (no vad).
 Fr Cisco SIP phones set the proper device type (7940, 7941, etc.)
 Repeat above steps for each SIP device.
Below is an example of a 7940 phone configuration:
voice register pool 1
id mac 001A.A216.FFFF
type 7940
number 1 dn 1
dtmf-relay rtp-nte
username phone00 password 1234
codec g711ulaw
no vad

id mac 001A.A216.FB59
type 7940
number 1 dn 2
dtmf-relay rtp-nte
codec g711ulaw
no vad

id mac 001A.A29C.6BC9
type 7940
number 1 dn 3
dtmf-relay rtp-nte
codec g711ulaw
no vad

Below is an example of a third party SIP phone configuration:

voice register dn 14
number 4684686014

id mac 0018.8B85.1E8D
number 1 dn 14
dtmf-relay rtp-nte
username rbarxlite password 1234
codec g711ulaw
no vad
2. Set up parallel hunt groups to get simring to the Accelerator:
 Create a parallel hunt group.
 Assign the full DN and simring DNs to the list.
 Set the hunt group pilot to be the short DN.
 Repeat above steps for each SIP desk phone.
o Example: if 6007 is dialed, then CUCME rings both 467-6007 (the
desk) and 167-467-6007 (the Accelerator simring alias).
voice hunt-group 7 parallel
list 2676007,1674676007
timeout 20
pilot 6007
list 2676008,1674676008
timeout 20
pilot 6008
list 2676009,1674676009
timeout 20
pilot 6009
3. Create translations rules to convert long DNs into short code DNs. Long
DNs from the Accelerator will be converted to match the hunt-group Pilot
Numbers in order for simring to work in both directions:
 Add a rule to convert long DNs into short DNs.
 Add a rule to leave Accelerator Pilot DNs unmodified.
 Repeat for all necessary DNs.
voice translation-rule 1
rule 1 /^2676007$/ /6007/
rule 2 /^2676008$/ /6008/
rule 3 /^2676009$/ /6009/
rule 4 /^6675679500/ /6675679500/
4. Define a translation profile for SIP trunks. This assigns the rules to match
and translate for both the calling and called numbers:
 Add a translation rule for calling number
 Add a translation rule for called number
voice translation-profile SIP
translate calling 1
translate called 1

5. Define the SIP trunk dial-peers between CUCME and the Accelerator,
Conference server, etc. At a minimum, the following dial-peers should be
created:
 A dial-peer for the outgoing simring numbers to the Accelerator (alias
numbers).
 A dial-peer for the outgoing Accelerator Pilot DNs to the Accelerator
(PDNs).
 A dial-peer for the incoming desk calls from the Accelerator (long DNs not
short DNs).
Other dial-peers that may be needed:
 Outgoing and incoming calls to a conference server.

 Outgoing and incoming calls from PSTN/mobiles.
Dial-peers are searched from lowest dial-peer number to highest. The first
dial-peer that matches is used regardless of whether a better match exists
higher up the list. The dial-peer number is not a phone number; it is an
arbitrary identifier in the system.
For each dial-peer the following information should be set:
 For outbound peers: a destination-pattern should match the appropriate

digits. For inbound peers: an incoming called-number should match
the appropriate digits.
 Assign a codec for the dial-peer, or use a codec class to allow a set of
codecs to be used.
 If translations on the numbers should be performed, assign the
appropriate translation-profile and whether or not the outgoing side
should translate the calling/called digits.
 Set set-dtmf relay to be rtp-nte to make sure RFC 2833 events can be
negotiated.
 Set the session protocol to sipv2.
 Set the dial peer session target IP to be the IP address of the server
(remote or local).
 Disable voice activity detection (no vad).
Sample outgoing dial-peer for when the CUCME sees a simring alias number:
 The destination-pattern matches the simring alias-number format (i.e.,

the second number in the parallel hunt group lists). (e.g., 167467xxxx)
 The session target is the IP address of the Accelerator.
dial-peer voice 99000 voip
description **outgoing simring call to abrazo-e**
destination-pattern ^167467....$
voice-class codec 1
voice-class sip dtmf-relay force rtp-nte
session protocol sipv2
session target ipv4:192.168.82.151

dtmf-relay rtp-nte
no vad
Sample dial-peer for the outgoing Accelerator Pilot DNs:
 The destination-pattern matches Pilot DN number format on Accelerator

(e.g., 66756795xx).
 The session-target is the IP address of the Accelerator.
description **outgoing pdn to abrazo-e**
destination-pattern ^66756795..$
voice-class codec 1
session target ipv4:192.168.82.151
dtmf-relay rtp-nte
no vad
Sample dial-peer for incoming full desk numbers, which are called from the
Accelerator and used when the mobile subscriber creates new call legs to
desk sets via Accelerator feature activation codes (e.g., Consultative
Transfer):
 The incoming called-number is for full desk numbers (e.g., 267xxxx)

 CUCME converts a seven (7) digit desk number to four (4) digit desk
number.
 The session target is the CUCME server where the just converted digits
(in the previous step) are sent back to the CUCME server.
description **incoming desk calls from abrazo-e**
translation-profile incoming SIP
translation-profile outgoing SIP
translate-outgoing calling 1
translate-outgoing called 1
voice-class codec 1
session target sip-server
incoming called-number ^267....$
dtmf-relay rtp-nte
no vad
Since both mobiles and PSTN numbers have been registered with the CUCME
server, dial-peers were created for these numbers. The following would not
be needed for Accelerator integration with the CUCME.

description **incoming mobile calls from abrazo-e**

voice-class codec 1
dtmf-relay rtp-nte
no vad
description **incoming pstn calls from abrazo-e**
voice-class codec 1
dtmf-relay rtp-nte
no vad
6. Configure the CUCME server to use dial-peers for inbound SIP trunk
selection:
dial-peer inbound selection sip-trunk
7. Define the CUCME as a server target. Wherever sip-server is found, the

CUCME server will replace it with the following IP and port:
sip-ua
sip-server ipv4:192.168.80.205:5060
CSTA configuration for Call Move in CUCME 8.0 Only

8. Configure VoIP for SIP and CTI CSTA
– Enable Global Call-ID (Gcid) for call control purposes.
– Suppress conversion or promotion of extension numbers of
associated endpoints in CTI messages.
– Enable CTI integration.
– Enable call monitoring messaging and functionality for processing
and reporting.
– Allow SIP to SIP calls.
– Bind signaling and media packets to the ethernet interface
– Enable "SIP Headers need to be passed to Applications"
– Enable local SIP registrar on CUCME (allows sip phones to register
with the CUCME). The Accelerator does not use the CUCME
registrar (just desks)
voice service voip
gcid

cti message device-id suppress-conversion

no cti shutdown
callmonitor
allow-connections sip to sip
fax protocol cisco
sip
bind control source-interface FastEthernet0/1
bind media source-interface FastEthernet0/1
header-passing
registrar server expires max 86400 min 600
9. Configure voice register global configuration.
– Mode CME (per cisco doc)
– Source address (SIP ip/port of the cucme)
– Set the maximum number of directory numbers (dns) supported.
This is the maximum number of defined SIP numbers
– Set the maximum number of pools supported. This is the
maximum number of physical SIP phones
– Provide firmware load name to be used for Cisco hardphones
– Enable authentication of registrations (The Accelerator doesn't
register, but without this, the CME is not secure?)
– Set the realm for authentication challenges.
– Provide location where firmware loads are located for Cisco
hardphones.
voice register global
mode cme
source-address 192.168.80.20 port 5060
no privacy
max-dn 42
max-pool 24
load 7960-7940 P0S3-08-12-00
authenticate register
authenticate realm tango-networks.com
tftp-path flash:
create profile sync 0000584505541132
10. Create a session manager for TANGO CSTA client application.
– Set the keepalive duration for registration in seconds. Range: 60
to 3600, default 300.
– Create TANGO_CSTA ID for explicitly identifying the Accelerator
CSTA application during REGISTER requests.
voice register session-server 1
keepalive 600
register-id TANGO_CSTA

11. The CTI CSTA interface is only available for SCCP phones.
– create account for CTI XML account (this must match the
user/password on the Accelerator provisioning for the CUCME CTI
peer.) [xml user admin ...]
telephony-service
protocol mode ipv4
no auto-reg-ephone
em logout 0:0 0:0 0:0
xml user admin password admin 15
max-ephones 30
max-dn 30
ip source-address 192.168.80.20 port 2000
system message Cisco Unified CME 8.0
load 7960-7940 P00308010200
time-zone 8
max-conferences 8 gain -6
transfer-system full-consult
create cnf-files
12. The Mobility feature and Single Number Reach (SNR) features are used to
provide forking to the Accelerator when an SCCP phone is the terminator.
– Enable 'mobility' feature
– Assign SNR number (the Accelerator alias number for the sub)
– Enable this number to be monitored and controlled by
– CSTA client application.
– Repeat above steps for each SCCP device with Accelerator service.
ephone-dn 1 dual-line
number 5000 secondary 2685000
name RBAR 5000 line 1
mobility
snr 1684685000 delay 0 timeout 10
cti watch
!
!
ephone-dn 2
mobility
cti watch
!
!
ephone-dn 3
number 7684685000
!
!
ephone-dn 4
number 7684685001
!
!
ephone-dn 5

!
!
ephone-dn 6
!
!
ephone-dn 7
mobility
cti watch
!
!
ephone-dn 10
number 8000
mwi on
!
!
ephone-dn 11
number 8001
mwi off
!
!
ephone 2
mac-address 001A.2FA6.CD03
type 7960
auto-line incoming
mwi-line 1
button 1:1 3:3 5:5
!
ephone 3
mac-address 001A.A216.FA63
type 7940
auto-line incoming
mwi-line 1
button 1:2 2:4
ephone 4
mac-address 001A.A216.FB59
type 7940
auto-line incoming
mwi-line 1
button 1:7 2:6
13. Enable voice mail integration with DTMF
vm-integration

14. Terminate the CUCME configuration session:
exit
15. At this point, any test cases that are available for verifying the integration
between the CUCME server and the Accelerator can be run.
16. Execute and write to memory the configuration commands by typing:
wr mem
PSTN Access Enabled Accelerator
To make the Accelerator the ingress/egress point for off net calls between the
PBX and your SIP Trunk provider, modify your PBX’s routing tables to send
off-net calls over a SIP Trunk to the Accelerator on the SIP Trunking port
(default of 5080). This SIP Trunk should also allow incoming calls from the
Accelerator. Make sure any required Class of Service attributes are set
appropriately on the PBX. On-net calls between PBX’s can also be configured
to route via the Accelerator using a similar process. It is often desirable to
create a second SIP Trunk on the PBX in order to specify different Class of
Service attributes for on-net calls. Consult your PBX’s configuration guide for
specific details on SIP Trunk configuration.

Accelerator Provisioning
Note: This document assumes that the Accelerator has already been
provisioned with:
- Enterprise information
- Wireless carrier information. The Carrier should be enabled
for Mobile UC and/or PSTN Access.
Mobile UC Enabled Accelerator
The steps below describe the unique configuration areas needed to integrate
the CUCME PBX with the Accelerator. Refer to the Accelerator Provisioning
Guide for a comprehensive explanation of Accelerator provisioning.
Voice Network: PBX/Trunk Dial Plan

1. Add Trunk Dial Plan (required) –There are no unique configuration items
for Trunk Dial Plans and the CUCME PBX. Refer to the Accelerator
Provisioning Guide, Voice Networks, PBXs, Add Trunk Dial Plan section.
 Add PBX (required) –No unique configuration items for adding a PBX.
Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs, Add
New PBX section.
 Add Trunk Group/Trunk (required) –
o Port value must match the Inbound Port value that was provisioned
for the SIP Server within the CUCME integration.
o Trunk Group Request URI parameters are not used by the CUCME
PBX and therefore do not need to be provisioned.
o Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs
(Add/Modify), Add Trunk Groups/Trunk section.
 Add CTI interface for CUCME 8.0 (CSTA) (required) - Only one field is
unique to CUCME 8.0; the Session Register-ID field. This is the register-id
name used for CTI session registrations. This must match the provisioned
session server id on the CUCME. All other fields are not unique. Refer to
the Accelerator Provisioning Guide, Voice Networks, PBXs (Add/Modify)
section.
 Add Pilot Numbers (required if your enterprise intends to route Pilot DNs
through the CUCME PBX) - No unique configuration areas required for
provisioning Pilot Numbers to the Accelerator. Refer to the Accelerator
Provisioning Guide, Voice Networks, PBXs (Add/Modify) section.
 Add Call Service Pilot Number (required for Call Move service) - No
unique configuration items for Call Service Pilot Numbers. Refer to the
Accelerator Provisioning Guide, Voice Networks, PBXs (Add/Modify)
section.

 Add Least Cost Routing (optional) in the Accelerator for the CUCME
PBX. No unique configuration items for Least Cost Routing. Refer to the
Accelerator Provisioning Guide, Voice Networks, Least Cost Routes, Add
Least Cost Routes section.
Voice Network: Extension Ranges

2. Add Extension Ranges (required) – No unique configuration items for
adding an Extension Range. Refer to the Accelerator Provisioning Guide,
Voice Networks, Extension Ranges, Add New Extension Ranges section.
Voice Network : Voice Mail

17. Add Voice Mail (recommended) for the CUCME PBX in the Accelerator.
Select PBX as the Voice Mail Server Type. Refer to the Accelerator
Provisioning Guide, Voice Networks, Voice Mail Servers, Add Voice Mail
Server section.
Subscriber Dial Plan/Subscriber

18. Add Subscriber Dial Plan (required) - No unique configuration items for
adding Subscriber Dial Plans. Refer to the Accelerator Provisioning Guide,
Subscribers, Add Subscriber Dial Plan section.
19. Add Subscriber Dial Plan (required) - Several items to note when
provisioning subscribers:
 Home PBX – select the newly created Alcatel PBX as the subscriber’s
Home PBX.
 Enterprise Desk Number – The extension defined for the user’s SIP
station.
 SIP Address – The third party SIP device ID. Refer to SIP Line
Configuration of the Unified Communication Manager. The Accelerator will
use this address for registrations and other signaling.
 Home PBX Provides Orig Svcs – enable this setting. When checked,
the Accelerator always originates the call on behalf of the mobile user for
mobile originations into their home PBX within the enterprise.
 Desk phone is SIP – The following settings impact the Call Move service.
o If the user’s desk phone is SCCP or a non-SIP phone leave the option
unchecked
o If the user’s desk phone is SIP and NOT an SCCP phone, check the
option.

PSTN Access Enabled Accelerator
If your configuration is Mobile UC only, refer to section Mobile UC Enabled

Accelerator starting on page 18.
The steps below describe the unique configuration areas needed to integrate
the CUCME PBX with the Accelerator. Refer to the Accelerator Provisioning
Guide for a comprehensive explanation of Accelerator provisioning.
Voice Network : PBX/Trunk Dial Plan

1. Add Trunk Dial Plan (required) –There are no unique configuration items
for Trunk Dial Plans and the CUCME PBX. Refer to the Accelerator
Provisioning Guide, Voice Networks, PBXs, Add Trunk Dial Plan section.
 Add PBX (required) –No unique configuration items for adding a PBX.
Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs, Add
New PBX section.
 Add Trunk Group/Trunk (required) –
o Port value must match the Inbound Port value that was provisioned
for the SIP Server within the CUCME integration.
o Trunk Group Request URI parameters are not used by the CUCME
PBX and therefore do not need to be provisioned.
o Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs
(Add/Modify), Add Trunk Groups/Trunk section.
 Add Least Cost Routing (optional) in the Accelerator for the CUCME
PBX. No unique configuration items for Least Cost Routing. Refer to the
Accelerator Provisioning Guide, Voice Networks, Least Cost Routes, Add
Least Cost Routes section.

Mobile UC Feature Interactions
The intent of the Accelerator is to seamlessly extend existing PBX voice

features to mobile devices. The Accelerator is integrated with PBXs at three
levels of integration for Mobile UC. The Cisco Unified Communications
Manager Express is integrated at Level 2 (see below).
Accelerator PBX Level 1 Integration
Integration Level 1 provides the subscriber basic services that are commonly
used. The following features are considered Level 1:
 Abbreviated Dialing - Allows extension dialing or internal dialing from
the desktop phone. The Accelerator the user to dial these same
abbreviated numbers from the mobile phone.
 Ad Hoc Conferencing (Internal to PBX)- Allows an Accelerator
subscriber to initiate a reservation-less conference from a mobile phone
using the conference resources of the PBX.
 Ad Hoc Conferencing using (External to PBX) - Allows an Accelerator
subscriber to initiate a reservation-less conference from a mobile phone
using external media server located in the enterprise.
 Call Forward All (Desk) - Allows users to forward all calls to another
destination including those calls to the mobile number. This feature is
activated via the desk phone.
 Call Forward Activation on Mobile - - Allows users to forward all calls
to another destination. Users enter a feature access code on their mobile
phone to activate or deactivate call forwarding.
 Call Forward Busy (Desk) - Allows users to forward calls (including
those to their mobile number) to another destination when their device is
busy. Users activate or deactivate the Call Forward Busy capability with a
Call Forward Busy feature button from their desk phone
 Call Forward Busy Activation on the Mobile - Allows users to forward
calls to another destination when their device is busy. Users activate or
deactivate the Call Forward Busy capability with a feature access code
from their mobile phone.
 Call Forward No Answer (Desk) - Allows users to forward calls
(including calls to their mobile number) to another destination when their
device is not answered. Users activate or deactivate the Call Forward No
Answer capability with a Call Forward No Answer feature button from their
desk phone
 Call Forward No Answer Activation on Mobile - Allows users to
forward calls to another destination when their device is not answered.
Users activate or deactivate the Call Forward No Answer capability with a
feature access code from their mobile phone.

 Call Hold and Retrieve (Mobile) – Lets users temporarily disconnect

from a call, use the telephone for another call, and then return to the
original call. The Accelerator supports this capability in concert with the
wireless network.
 Call Line Identification (CLID) – Provides the user information about
the calling party. The Accelerator supports calling line identification when
it is the called party. The Accelerator also supports ensuring that the
enterprise identity of the caller is preserved when a call is initiated from
the mobile phone. In this case although the call is made from a mobile,
the calling line ID will be that of the user's desktop phone. The enterprise
main number may also optionally be used in place of a subscriber’s DID
for off-net calling.
 Call Transfer – Lets users move a currently established call from their
mobile phone to another destination. This is implemented by the user
entering a mid-call feature code followed by the transfer to number. There
are two types of call transfers that are supported by this functionality:
o Blind Call Transfer – Call is transferred without interaction between
the user who initiated the transfer and the transfer destination.
o Consultative Call Transfer - Call is transferred allowing interaction
between the user who initiated the transfer and the transfer
destination.
 Call Waiting and Retrieve - Provides users with an audible alert in the
voice stream that a new incoming call is waiting. The user can retrieve the
call from the desk phone. The Accelerator supports call waiting in concert
with the wireless network. Call Waiting tones are provided by the mobile
phone when an incoming call is waiting, and waiting calls can be retrieved
from the mobile phone.
 Direct Inward Dialing - Allows the desk phone to be directly accessed
from the PSTN. The Accelerator supports enterprise Direct Inward Dialing.
 Direct Outward Dialing - Allows users inside an enterprise to dial
directly to an external number. The Accelerator supports the mobile
device dialing directly to an external number.
 Directory Dial - Lets users select numbers to dial from a corporate or
personal directory. The Accelerator supports using a personal directory on
the phone and handles the translations of those digits into on-net network
numbers if appropriate. In addition, the Accelerator support a corporate
directory look up capability for access to the corporate address book.
 Flexible Dialing Support - The Accelerator has a flexible dialing plan
enabling PBX services to be provided to mobile users.
 Intelligent Call Delivery - Ensures that both the desk phone and mobile
phone ring when the dialed number is an Accelerator subscriber.
 Least Cost Routing – For mobile originations and terminations, the
Accelerator ensures that the least cost route is used. This results in the
enterprise voice network being used to route the call as much as possible,
reducing PSTN interconnect costs, and other voice costs such as roaming.
 Meet-Me Conference - Allows users to set up a dial-in conference of up
to six parties. The mobile user can participate in the meet-me conference
by dialing the conference bridge.

 Multiple Calls per Line – Allows multiple calls to be delivered to a single

number and have the incoming call information displayed to the user. The
Accelerator supports this feature on the mobile phone based on the ability
to support call waiting for mobile phone devices. Mobile devices typically
show a maximum of two lines per mobile phone.
 PBX Do Not Disturb (Desk) – Allows users to activate or deactivate the
Do Not Disturb capability by pressing a button or a softkey from their desk
phone. When active, Do Not Disturb will not ring the mobile or desk
phone.
 PBX Do Not Disturb (Mobile) - Allows users to activate or deactivate
the Do Not Disturb capability by entering a feature access code from their
mobile phone. When active, Do Not Disturb will not ring the mobile phone
however the desk phone will continue to ring.
 Single Number Services - A single phone number that a subscriber
publishes to communicate with others. When this single number is dialed,
the subscriber’s enterprise desktop phone as well as mobile phone will
ring.
 Voice Mail Waiting Indication - Provides a visible indication on the
mobile phone that there is a message waiting in the voice mail system.
The Accelerator supports supplying a Message Waiting indication on the
mobile phone that indicates that there are voice mail messages in the
enterprise voice mail system.
Table 1 Accelerator PBX Level 1 Integration

Feature Support Comments
Abbreviated Dialing Yes
Uses an external IP Media 2000
conference server. Refer to the
Ad Hoc Conferencing (Internal to PBX) No
Accelerator Provisioning Guide, Voice
Networks, Conference Servers section.
Ad Hoc Conferencing (External to PBX) Yes
Call Forward All (Desk) Yes
Call Forward All Activation from Mobile Yes
Call Forward Busy (Desk) Yes
Call Forward Busy Activation from Mobile Yes
Call Forward No Answer (Desk) Yes
Call Forward No Answer Activation from
Yes
Mobile
Call Hold and Retrieve (Mobile) Yes
Call Line Identification (CLID) Yes
Call Transfer – Blind Yes
Call Transfer – Consultative Yes
Call Waiting and Retrieve Yes
Direct Inward Dialing Yes
Direct Outward Dialing Yes
Directory Dial Yes
Flexible Dialing Support Yes
Intelligent Call Delivery Yes
Least Cost Routing Yes
Meet-Me Conference Yes
Multiple Calls per Line Yes
PBX Do Not Disturb (Desk) Yes
PBX Do Not Disturb (Mobile) Yes
Single Number Services Yes
Voice Mail Message Waiting Indication Yes

Integration Level 2 provides the subscriber more advanced features than

more commonly used basic features. The following features are considered
Level 2 integration targets:
o Call Accounting Codes - To support the mobile office environment,
client billing must be supported when the user is away from his/her
desktop phone and using a mobile phone. For example, law offices,
accounting firms, consulting firms and other organizations benefit from
tracking the length of a call for a client. Client billing is achieved by
having the user enter a code to specify that the call relates to a
specific client matter or account. The code, which is often referred to
as a client matter code (CMC) or call accounting code, can be assigned
to customers, students, or other populations for call accounting and
billing purposes. Call accounting codes are used by enterprise to
manage call accounting.
o Call Coverage/Hunt Groups - Allows a group of extensions to be set
up to handle multiple calls to a single telephone number. For each call
to the number, the PBX hunts for an available extension in the hunt
group and connects the call to that extension. The Accelerator can be
defined as one of the extensions.
o Call Line Identification Restriction (CLIR) (Mobile) - Allows the
user to restrict their calling line information from being displayed to
the called number. The Accelerator supports restriction of calling line
identification from mobile phones. Enterprise identity will be replaced;
however restriction code will be preserved.
o Call Pull (Desk->Mobile Call Move)- Allows a subscriber to move a
phone call between the desk phone and the mobile phone. Feature is
invoked from the mobile phone.
o Call Push (Mobile->Desk Call Move)- Allows a subscriber to move a
phone call between the desk phone and the mobile phone. Feature is
be invoked from the mobile phone.
o Class of Restriction (COR) (PBX) - Defines the restrictions that
apply when a user places or receives a call. The Accelerator supports
COR for mobile originated calls.
o Class of Service (COS) (PBX) - Allows or denies user access to
some system features. The Accelerator supports COS for mobile
originated calls over SIP lines.
Table 2 Accelerator PBX Level 2 Integration
Feature Support Comments

Call Accounting Codes No
Call Coverage/Hunt Groups Yes
Call Line Identification Restriction (CLIR) (Mobile) Yes
For CUCME 7.1, not supported
Call Pull (Desk->Mobile Call Move) No/Yes
For CUCME 8.0, support via CTI/CSTA
Call Push (Mobile->Desk Call Move) Yes
Class of Restriction (COR) (PBX) Yes
Class of Service (COS) (PBX) Yes

Integration Level 3 provides features that are specific to the PBX or specific to
vertical markets.
The Accelerator does not currently support any level 3 features on the Cisco
Unified Communications Manager Express PBX.

Acronyms
Table 3 Acronyms
Term Definition
Accelerator Tango Enterprise
CA Certificate Authority
CDR Call Detail Record
CFA Call Forward All Calls
CFB Call Forward Busy
CFNA Call Forward Not Answered
CLI Command Line Interface
CLID Calling Line Identification
CLIR Calling Line Identification Restriction
COR Class of Restriction
COS Class of Service
CTI Computer Telephony Integration
DID Direct Inward Dial
DN Directory Number
DTMF Dual-Tone Multi-Frequency
IPDR Internet Protocol Data Record
Mobilizer Tango Carrier
MWI Message Waiting Indication
NAT Network Address Translation
PBX Private Branch Exchange
PDN Pilot Directory Number
PSTN Public Switched Telephone Network
SIM Ring Simultaneous Ring
SIP Session Initiation Protocol
SMDI Simplified Message Desk Interface
SOAP Simple Object Access Protocol
TDM Time Division Multiplex
TLDN Temporary Location Directory Number
TLS Transport Layer Security

Cisco Unified Communication Manager Express Integration Guide
Tango Networks, Inc.

3801 Parkwood Blvd, Suite 500
Frisco, Texas 75034 USA
phone: + 1 469-229-6000
fax: + 1 469-467-9840
www.tango-networks.com
September 2009 CONFIDENTIAL Page 28 of 28

Accelerator Cisco UCM Express Integration Guide

Uploaded by

Document Information

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

Accelerator Cisco UCM Express Integration Guide

Uploaded by

Copyright:

Available Formats

ACCELERATOR 6.

Tango Networks, Inc. phone: +1 469-229-6000

© 2004 - 2014 Tango Networks, Inc..

© 2004 - 2014 Tango Networks, Inc..

April 2014 CONFIDENTIAL Page 2 of 28

ACCELERATOR INTEGRATION PROCESSES ........................................................ 6

MOBILE UC FEATURE INTERACTIONS ............................................................. 21

April 2014 CONFIDENTIAL Page 3 of 28

The Accelerator can potentially be provisioned in one of three ways based on

During Accelerator provisioning, a Carrier(s) was created that enabled one or

 Mobile UC - The Mobile UC application extends PBX and Unified

 PSTN Access (e.g. SIP Trunking Controller) – PSTN Access facilitates

Important Note: Through out this document and other Tango

Mobile UC and SIP Trunking combination – It is possible to have both

April 2014 CONFIDENTIAL Page 4 of 28

PBX Dependencies – Mobile UC

The following lists the Cisco Unified Communications Manager Express

April 2014 CONFIDENTIAL Page 5 of 28

Accelerator Integration Processes

Cisco Unified Communications Manager Express Provisioning

Mobile UC and PSTN Access Enabled Accelerator

Mobile UC Enabled Accelerator

The Cisco Unified Communications Manager Express (CUCME) is provisioned

April 2014 CONFIDENTIAL Page 6 of 28

Note: The Unified Communications Manager Express server(s) must first

After ensuring that the Unified Communications Manager Express server(s)

Accelerator Provisioning on page 18 of this document.

2. Once inside the CUCME server, view the current configuration:

5. In order to unblock RTP packets, enter the following command:

April 2014 CONFIDENTIAL Page 7 of 28

6. Enable the CUCME server to allow two-way RTP traffic:

voice rtp send-recv

ip domain name tango-networks.com

8. Configure DNs for SIP Phones:

April 2014 CONFIDENTIAL Page 8 of 28

1. Configure physical SIP phones so that each one is represented as a pool.

voice register pool 2

voice register pool 3

April 2014 CONFIDENTIAL Page 9 of 28

Below is an example of a third party SIP phone configuration:

voice register pool 5

April 2014 CONFIDENTIAL Page 10 of 28

Other dial-peers that may be needed:

 Outgoing and incoming calls to a conference server.

For each dial-peer the following information should be set:

 For outbound peers: a destination-pattern should match the appropriate

 The destination-pattern matches the simring alias-number format (i.e.,

April 2014 CONFIDENTIAL Page 11 of 28

Sample dial-peer for the outgoing Accelerator Pilot DNs:

 The destination-pattern matches Pilot DN number format on Accelerator

 The incoming called-number is for full desk numbers (e.g., 267xxxx)

dial-peer voice 87100 voip

April 2014 CONFIDENTIAL Page 12 of 28

dial-peer inbound selection sip-trunk

7. Define the CUCME as a server target. Wherever sip-server is found, the

CSTA configuration for Call Move in CUCME 8.0 Only

April 2014 CONFIDENTIAL Page 13 of 28

cti message device-id suppress-conversion

April 2014 CONFIDENTIAL Page 14 of 28

April 2014 CONFIDENTIAL Page 15 of 28

13. Enable voice mail integration with DTMF

April 2014 CONFIDENTIAL Page 16 of 28

14. Terminate the CUCME configuration session:

PSTN Access Enabled Accelerator