Professional Documents
Culture Documents
Accelerator Cisco UCM Express Integration Guide
Accelerator Cisco UCM Express Integration Guide
3
CISCO UNIFIED COMMUNICATION MANAGER
EXPRESS INTEGRATION GUIDE
April 2014
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.
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.
TABLE OF CONTENTS
INTRODUCTION ............................................................................................. 4
SUPPORTED VERSIONS ......................................................................................................... 5
PBX DEPENDENCIES – MOBILE UC........................................................................................... 5
ACRONYMS ................................................................................................. 26
Introduction
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.
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.
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.
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
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.
telnet <hostname>
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
ip source-route
7. Enter the domain for the CUCME PBX. The domain correlates to the PBX
domain provisioned on the Accelerator.
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....
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).
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.
Sample outgoing dial-peer for when the CUCME sees a simring alias number:
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):
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.
translate-outgoing called 1
voice-class codec 1
voice-class sip dtmf-relay force rtp-nte
session protocol sipv2
session target sip-server
incoming called-number ^467467....$
dtmf-relay rtp-nte
no vad
dial-peer voice 87200 voip
description **incoming pstn calls from abrazo-e**
translation-profile incoming SIP
translation-profile outgoing SIP
translate-outgoing calling 1
translate-outgoing called 1
voice-class codec 1
voice-class sip dtmf-relay force rtp-nte
session protocol sipv2
session target sip-server
incoming called-number ^767467....$
dtmf-relay rtp-nte
no vad
6. Configure the CUCME server to use dial-peers for inbound SIP trunk
selection:
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
number 5001 secondary 2685001
name RBAR 5001 line 1
mobility
snr 1684685001 delay 0 timeout 10
cti watch
!
!
ephone-dn 3
number 7684685000
!
!
ephone-dn 4
number 7684685001
!
!
ephone-dn 5
number 5555 secondary 2685555
!
!
ephone-dn 6
number 5556 secondary 2685556
!
!
ephone-dn 7
number 5002 secondary 2685002
name RBAR 5002 line 1
mobility
snr 1684685002 delay 0 timeout 10
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
vm-integration
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
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.
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.
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.
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.
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.
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
phone: + 1 469-229-6000
fax: + 1 469-467-9840
www.tango-networks.com