Cisco application note

Transcription

Application Note
Siemens Realitis / GPT iSDX using E1 DPNSS to Cisco
Unified Communications Manager 9.1 via Aculab ApplianX IP Gateway release 2.3.0
July16 2013 Initial Version
Table of Contents
Introduction .............................................................................................................................................................................................................. 1
Network Topology .................................................................................................................................................................................................... 2
Limitations ................................................................................................................................................................................................................ 2
System Components ................................................................................................................................................................................................. 2
Hardware Requirements ...................................................................................................................................................................................... 2
Software Requirements ....................................................................................................................................................................................... 3
Features .................................................................................................................................................................................................................... 3
Call Related Features Supported ......................................................................................................................................................................... 3
Management Related Features............................................................................................................................................................................. 3
Features Not Supported ....................................................................................................................................................................................... 4
Configuration ............................................................................................................................................................................................................ 4
Configuring the DXR PBX ................................................................................................................................................................................. 4
Configuring the Cisco Unified Communications Manager ................................................................................................................................. 7
Configuring the Aculab ApplianX IP Gateway ................................................................................................................................................. 12
Configuring the Aculab ApplianX IP Gateway as a DPNSS to QSIG gateway ...................................................................................................... 24
Acronyms ............................................................................................................................................................................................................... 27
Introduction
This application note provides configuration guidelines for interconnecting Cisco Unified Communications Manager with GPT iSDX, Siemens
Realitis or DXR PBXs using DPNSS to standard BTNR 188. As Cisco Unified Communications Manager does not natively support this
protocol, an Aculab ApplianX IP Gateway was tested to ascertain the level of compatibility possible. The gateway converts DPNSS to SIP,
mapping DPNSS features to their SIP equivalent, where possible.
Note that this document does not cover use of the ApplianX IP Gateway to perform DPNSS to QSIG conversion. However, there are a number
of known deployments where the ApplianX IP Gateway is running in that configuration.
Using configuration settings in this application note, supplementary service integration was verified using the test network described below.
This included basic call, call transfer, call conference, call forward, calling and connected names and numbers with some limitations on Caller
ID features during transfer, forward, and conference scenarios. MWI was also passed from Cisco Unified Communications Manager to PBX
phones.
© 2013 Cisco Systems, Inc. All rights reserved.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com
Page 1 of 29
EDCS# 1282915 Rev # Issue 1 08-13-2013
Network Topology
Figure 1.
Basic Call Setup
143xxx
79xx
IP
IP
Applianx IP
Gateway
IP
SIP
Cisco Unified Communications Manager
E1 DPNSS
Siemens DXR PBX 2
DPNSS
Applianx IP
Gateway
Siemens DXR PBX 1
SIP
SIP
E1 DPNSS
Cisco Unity Connection
V
1251xx
Q931
The test network was as shown in the diagram above. The Unity Connection system was used to provide voicemail for users on both the CUCM
and DXR PBX 1 and to direct incoming calls from the Q.931 link. The Q.931 link was attached to an Aurora DUET tester and used to simulate
the PSTN
Limitations
These are the known limitations, caveats, or integration issues:

SIP trunks cannot perform overlap dialing, therefore, the gateway is configured with an interdigit timer which performs a post dial delay

Names in DPNSS NIM messages are not mapped to the SIP call leg, therefore, there are no alerting names when calling from CUCM to
a PBX extension.
System Components
Hardware Requirements
The following hardware was required:

Cisco Unified Communications Manager Cluster

Cisco 2811 voice gateway+ NM-HDV2-2T1/E1

2 Aculab ApplianX IP Gateways

Cisco Unity Connection Voice Mail

2 Siemens DXR PBXs with analogue and digital extensions
Page 2 of 29
Software Requirements
The following software was installed:
Equipment
Tested Software Revision(s)
9.1.0
Cisco 2811 voice gateway
c2800nm-adventerprisek9-mz.151-3.T1.bin
Aculab ApplianX IP Gateways
R2.30
Cisco Unity Connection Voice Mail
7.1.2
Siemens DXR PBX
DXR 8.0.001
Siemens DXR PBX
DXR 8.0.31
Features
This section lists supported and unsupported features.
Call Related Features Supported
Basic Call (Enbloc and Overlap dialing)
Calling/Connected Number Display and Update
Calling/Connected Name Display and Update (see limitations)
Call Transfer: Supervised Local Transfer
Call Transfer: Supervised Network/External Transfer
Call Conference: Local
Call Conference: Network/External
Call Forward: Local
Call Forward: Network/External
Message Waiting Indication
Route Optimization / Path Replacement
Transit Count / Loop Avoidance
Management Related Features
Protocol tracing
Diagnostic logging
Remote logging (Syslog)
SIP Ping (Options)
Page 3 of 29
Call Logging
Features Not Supported
Call Back When Free
Call Back Next Used
Configuration
Configuring the DXR PBX
The configuration below is taken from one of the DXR PBXs and displays the configuration of the trunk to the Aculab ApplianX IP Gateway.
This section is provided primarily as an example of how to ascertain the necessary information for the correct configuration of the gateway.
Ensure Trunk Group has correct Trunk Access
?ltga
GROUP:10
ZONE:0
TAC
0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
MG010
Z 00 N
Configuration of Trunk Main Group – note Trunk Access code (CODE) of 1041
?ltmg 10
MG
D
/
A
1041 D
TYPE CODE
010 DPNS
OUT SRCH
HRS
SEND PSD
FXD
A
S
A
R
T IN
DDI
D
D
T
D
T
T
D T
REG T S OG
T
N N 00
M
D
M
N
N
L
T
R
A
D
I
Configuration of individual Trunk Channels showing X/Y setting (DIR) and Trunk Main Group number
?ltk p 0105-2
TK TYPE PAD
1681 DPNS 010501-2
1682 DPNS 010502-2
1683 DPNS 010503-2
1684 DPNS 010504-2
1685 DPNS 010505-2
1686 DPNS 010506-2
1687 DPNS 010507-2
1688 DPNS 010508-2
1689 DPNS 010509-2
MG
010
010
010
010
010
010
010
010
010
TG
010
010
010
010
010
010
010
010
010
DIR
Y
Y
Y
Y
Y
Y
Y
Y
Y
DSA
DDI
DDI
DDI
DDI
DDI
DDI
DDI
DDI
DDI
OAD
Y
Y
Y
Y
Y
Y
Y
Y
Y
NSA SIG
DANS
DANS
DANS
DANS
DANS
DANS
DANS
DANS
DANS
CCT
PSP
038
038
038
038
038
038
038
038
038
Page 4 of 29
PE
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
DPNS
DPNS
DPNS
DPNS
DPNS
DPNS
DPNS
DPNS
DPNS
DPNS
DPNS
DPNS
DPNS
DPNS
DPNS
DPNS
DPNS
DPNS
DPNS
DPNS
DPNS
010510-2
010511-2
010512-2
010513-2
010514-2
010515-2
010516-2
010517-2
010518-2
010519-2
010520-2
010521-2
010522-2
010523-2
010524-2
010525-2
010526-2
010527-2
010528-2
010529-2
010530-2
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
010
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
DDI
DDI
DDI
DDI
DDI
DDI
DDI
DDI
DDI
DDI
DDI
DDI
DDI
DDI
DDI
DDI
DDI
DDI
DDI
DDI
DDI
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
DANS
DANS
DANS
DANS
DANS
DANS
DANS
DANS
DANS
DANS
DANS
DANS
DANS
DANS
DANS
DANS
DANS
DANS
DANS
DANS
DANS
038
038
038
038
038
038
038
038
038
038
038
038
038
038
038
038
038
038
038
038
038
Display of DLI configuration, showing DPNSS A/B Side Setting (LINK) and the Real and virtual channels configured.
?ldlc
XXYY/LINK:0105-2
CHANNEL:a
TRUNK
TYPE
010501-2 DPNSS
010502-2 DPNSS
010503-2 DPNSS
010504-2 DPNSS
010505-2 DPNSS
010506-2 DPNSS
010507-2 DPNSS
010508-2 DPNSS
010509-2 DPNSS
010510-2 DPNSS
010511-2 DPNSS
010512-2 DPNSS
010513-2 DPNSS
010514-2 DPNSS
010515-2 DPNSS
010516-2 DPNSS
010517-2 DPNSS
010518-2 DPNSS
010519-2 DPNSS
010520-2 DPNSS
010521-2 DPNSS
010522-2 DPNSS
010523-2 DPNSS
010524-2 DPNSS
VIRTUAL
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
REAL
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
LINK
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
Page 5 of 29
010525-2
010526-2
010527-2
010528-2
010529-2
010530-2
0105-2
DPNSS
DPNSS
DPNSS
DPNSS
DPNSS
DPNSS
MAINT
C
C
C
C
C
C
U
C
C
C
C
C
C
U
B
B
B
B
B
B
System Digit Translation Pattern, showing routing for 70, 71, 72 and 79 via Access Code 1041
ldtt 3 7
71
72
73
74
75
76
77
78
79
70
104171
1041
1042
1043
1048
1049
1050
1051
104179
104170
Display the exchange identity (speid) and (sprad). Cisco Unified Communications Manager should route 12<extension range> and
19804<everything> back to the PBX. Note the parameters required may vary with the configuration of the DPNSS network.
?lssp
SYSTEM PARAMETER? :speid
SPEID 011000
04608.
12-000000
00000.
----
0001 0010 0000 0000B
0000 0000 0000 0000B
?lssp
SYSTEM PARAMETER? :sprad
SPRAD 014612
06538.
1980
040000
16384.
4---
0001 1001 1000 1010B
0100 0000 0000 0000B
Page 6 of 29
Configuring the Cisco Unified Communications Manager
The only significant part of the CUCM configuration with respect to the Aculab ApplianX IP Gateway is the SIP trunk configuration. Create a
new SIP profile under Device -> Device Settings -> SIP profile. Under the Trunk Specific Configuration section check:
‘Early Offer support for voice and video calls (insert MTP if needed)’
‘Send send-receive SDP in mid-call INVITE’
Enable SIP Options ping.
Page 7 of 29
Create a new SIP Security profile setting the transport protocol as required.
Page 8 of 29
Create a new SIP trunk with the default service type.
Page 9 of 29
Add a name and description of the trunk and check ‘Media Termination Point Required.
Check ‘Remote Party ID’ and ‘Asserted Identity’ check boxes and direct incoming calls to the appropriate CSS.
Page 10 of 29
Ensure outbound CLID and name presentation are allowed.
Under the SIP information section enter the IP address of the gateway media/signaling port and select the SIP Trunk Security Profile and the SIP
Profile that were configured earlier.
Page 11 of 29
Configuring the Aculab ApplianX IP Gateway
Initial preparation consists of IP address configuration and setting the administration username and password. These steps are detailed in the
Quick Start Guide shipped with the unit. It should be noted for planning purposes that the gateway requires two IP addresses, one for
management, and one for signaling and media.
The basic management principle is to edit a configuration off line, then apply it to the gateway. It is not possible to edit a running configuration.
The following are screen shots of the ApplianX IP Gateway configuration pages: Global Config followed by Gateway configuration pages.
All other pages (network configuration, etc.), whilst important to an individual installation in a network, are not relevant to interoperation with
CUCM and not presented.
Global Configuration:
Configuration pages
After initial configuration and login the main menu is presented as below:
Page 12 of 29
Select Edit Configuration from Gateway Configuration section and a list of stored configurations is displayed.
Page 13 of 29
To proceed, copy either the running configuration or one of the available configurations and the edit the copy. The following screen shot shows
the explicit configuration used in the test network.
Select the ‘Trunks’ tab then ‘Edit’ next to the first TDM trunk.
.
At the bottom of the page click the ‘Change’ button and select DPNSS from the protocol choices. Configure the general settings as below. Note
that the trunk must be configured with an inter-digit timer since the SIP trunks cannot support overlap dialing. In lab testing a value of 1500
milliseconds was found to be optimum, but this value may need to be changed according to prevailing network conditions.
Page 14 of 29
Next, edit the DPNSS protocol configuration as below.
Page 15 of 29
Continued below…
Page 16 of 29
Note the settings for CLC generation are changed from the defaults. The MWI custom NSI strings include the OLI string for the voicemail pilot
number (7300 in the test network). The strings are not complete – the gateway inserts the leading ‘*58’ and the trailing ‘#’. It is also not possible
to send both custom NSI and callback messaging.
Apply changes at both the protocol and trunk levels. Repeat the procedure for further trunks if required.
Before a new SIP endpoint is added, a new Group, in which the endpoint is to reside, should be created. Open the ‘Groups’ tab and select ‘Add’
then give the new group a name and description. Click ‘Apply’.
Page 17 of 29
From the top level select the ‘Endpoint’ tab and add a new endpoint as shown below. Add the endpoint into the newly created CUCM group.
On the ‘Routes’ pages, only routes for ‘ToSIP’ and ‘ToDPNSS’ are set up. Others are left at default. The TDM trunks group routing can be left
at the default settings, which will route all incoming calls to the CUCM group.
Page 18 of 29
The CUCM group settings require specific entries to ensure that calls which are diverted on the PBX back to CUCM are correctly handled. In
the test network this required the CUCM extension range 79xx, the voicemail pilot 7300 and the PSTN steering digit 9 all to be specifically sent
to the CUCM as below. Note that the order is significant. The default rule, which sends all incoming SIP calls to the TDM group, must be the
last one in the table.
Page 19 of 29
Select the ‘Clocking’ tab and select the TDM trunk(s) you wish to use as the clock source.
Select the ‘Codec’ tab and then select and order (Move Up/Down), the codecs to be used.
Page 20 of 29
Select the ‘SIP’ tab, and set options as below.
Continued below…
Page 21 of 29
Return to the ‘General’ tab and give the configuration a name and description.
Page 22 of 29
‘Save’ the configuration and the page will return to the top level ‘edit configurations’ page. Apply the configuration by clicking the ‘Use’ button
beside the required configuration.
The gateway will ask for confirmation of the selection and then load the configuration. The gateway will go off line for approximately 30
seconds while the configuration is applied.
Page 23 of 29
Configuring the Aculab ApplianX IP Gateway as a DPNSS to QSIG gateway
As noted, this document does not cover full configuration of the ApplianX IP Gateway to perform DPNSS to QSIG conversion. However, there
are a number of known deployments where the ApplianX IP Gateway is running in that configuration.
For setup as a DPNSS to QSIG gateway, use the setup wizard within the ApplianX IP Gateway to create a default configuration. Use the default
values provided for the QSIG trunk, and the settings within the configuration above for the DPNSS trunk.
The ‘Groups’ section of the configuration should be configured as below.
DPNSS Trunk Group settings.
Page 24 of 29
QSIG Trunk Group settings.
The Routes section of the configuration should be configured as below.
Page 25 of 29
In the configuration above, all inbound calls on the DPNSS trunks will be routed out over the QSIG trunks, and vice versa.
For details on how to configure the QSIG link on Cisco Unified Communications Manager, please see the following document:
http://www.cisco.com/en/US/solutions/collateral/ns340/ns414/ns728/ns784/963053_1.pdf
Page 26 of 29
Acronyms
Acronym
DPNSS
NSI
IPT
CUCM
Q.931
PBX
MMI
COS
TAC
CLI
CLIP
CLIR
CNIP
COLP
COLR
CONP
Definition
Digital Private Network Signaling System as detailed in BTNR 188 and 189
Non-Specified Information – vendor specific free-form PBX-to-PBX messaging
IP Telephony
ITU ISDN protocol at level 3
Private Branch Exchange
Man Machine Interface – specifically on iSDX/Realitis, a VT100 style console
Class Of Service – on an iSDX, the ability to activate features on a particular line
Trunk Access Class – the ability for an extension to use a specific trunk
Calling Line Identity
Calling Line Identity Presentation
Calling Line Identity Restriction
Calling Name Identity Presentation
Connected Line Identity Presentation
Connected Line Identity Restriction
Connected Name Identity Presentation
Page 27 of 29
Corporate
Headquarters
European
Headquarters
Americas
Headquarters
Asia Pacific
Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 526-4100
Cisco Systems International
BV
Haarlerbergpark
Haarlerbergweg 13-19
1101 CH Amsterdam
The Netherlands
www-europe.cisco.com
Tel: 31 0 20 357 1000
Fax: 31 0 20 357 1100
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
www.cisco.com
Tel: 408 526-7660
Fax: 408 527-0883
Cisco Systems, Inc.
Capital Tower
168 Robinson Road
#22-01 to #29-01
Singapore 068912
www.cisco.com
Tel: +65 317 7777
Fax: +65 317 7799
Cisco Systems has more than 200 offices in the following countries and regions. Addresses, phone numbers, and fax numbers are listed on
the Cisco Web site at www.cisco.com/go/offices.
Argentina • Australia • Austria • Belgium • Brazil • Bulgaria • Canada • Chile • China PRC • Colombia • Costa Rica • Croatia • Czech
Republic • Denmark • Dubai, UAE • Finland • France • Germany • Greece • Hong Kong SAR • Hungary • India • Indonesia • Ireland •
Israel • Italy • Japan • Korea • Luxembourg • Malaysia • Mexico • The Netherlands • New Zealand • Norway • Peru • Philippines •
Poland • Portugal • Puerto Rico • Romania • Russia • Saudi Arabia • Scotland • Singapore • Slovakia • Slovenia • South Africa • Spain •
Sweden • Switzerland • Taiwan • Thailand • Turkey Ukraine • United Kingdom • United States • Venezuela • Vietnam • Zimbabwe
CCENT, Cisco Lumin, Cisco Nexus, Cisco TelePresence, the Cisco logo and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Ciso
Store and Changing the Way We Work, Live, Play, and Learn are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst,
CCDA, CCDP, CCVP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems,
Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive,
HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace,
MeetingPlace Chime Sound, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The
Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States
and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a
partnership relationship between Cisco and any other company. (0705R)
Printed in the USA
Page 28 of 29
Important Information
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE
WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE
ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL
RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR
INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT
OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
Page 29 of 29

Cisco application note

Transcription

Similar documents

Cisco Recruitment Session* When

crescent village - Prime Commercial, Inc.

Cisco.com AEM Integration and Migration

Read More - FusionStorm

Virtual Lock for Corporate IP Telephony v 3.0

Single pane of glass: Myth or reality?

5.3.4.2 Lab - Hard Drive Maintenance in Windows 7

Cisco Chooses to Be Smart in Songdo

Cisco SA 500 Series - Pyramid Technology Services