siemens realitis / gpt isdx using e1 dpnss to cisco...

© 2013 Cisco Systems, Inc. All rights reserved. Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com

of 29 EDCS# 1282915 Rev # Issue 1 08-13-2013

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 of 29

Network Topology

Figure 1. Basic Call Setup

IP IPIP

Cisco Unity Connection

Cisco Unified Communications Manager

Siemens DXR PBX 2

Siemens DXR PBX 1E1 DPNSS

DPNSS

E1 DPNSS

SIP

SIP

Applianx IP

Gateway

Applianx IP

Gateway

SIP

1251xx

143xxx

79xx

V

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



Software Requirements

The following software was installed:

Equipment Tested Software Revision(s)

Cisco Unified Communications Manager 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)



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

D A R D D D T M N R

MG TYPE CODE / OUT SRCH SEND PSD S T IN D T REG T S OG D L A PE

A T T T M T D

010 DPNS 1041 D HRS FXD A DDI N N 00 N I

Configuration of individual Trunk Channels showing X/Y setting (DIR) and Trunk Main Group number

?ltk p 0105-2

TK TYPE PAD MG TG DIR DSA OAD NSA SIG CCT PSP

1681 DPNS 010501-2 010 010 Y DDI Y DANS 038

1682 DPNS 010502-2 010 010 Y DDI Y DANS 038

1683 DPNS 010503-2 010 010 Y DDI Y DANS 038

1684 DPNS 010504-2 010 010 Y DDI Y DANS 038

1685 DPNS 010505-2 010 010 Y DDI Y DANS 038

1686 DPNS 010506-2 010 010 Y DDI Y DANS 038

1687 DPNS 010507-2 010 010 Y DDI Y DANS 038

1688 DPNS 010508-2 010 010 Y DDI Y DANS 038

1689 DPNS 010509-2 010 010 Y DDI Y DANS 038



1690 DPNS 010510-2 010 010 Y DDI Y DANS 038

1691 DPNS 010511-2 010 010 Y DDI Y DANS 038

1692 DPNS 010512-2 010 010 Y DDI Y DANS 038

1693 DPNS 010513-2 010 010 Y DDI Y DANS 038

1694 DPNS 010514-2 010 010 Y DDI Y DANS 038

1695 DPNS 010515-2 010 010 Y DDI Y DANS 038

1696 DPNS 010516-2 010 010 Y DDI Y DANS 038

1697 DPNS 010517-2 010 010 Y DDI Y DANS 038

1698 DPNS 010518-2 010 010 Y DDI Y DANS 038

1699 DPNS 010519-2 010 010 Y DDI Y DANS 038

1700 DPNS 010520-2 010 010 Y DDI Y DANS 038

1701 DPNS 010521-2 010 010 Y DDI Y DANS 038

1702 DPNS 010522-2 010 010 Y DDI Y DANS 038

1703 DPNS 010523-2 010 010 Y DDI Y DANS 038

1704 DPNS 010524-2 010 010 Y DDI Y DANS 038

1705 DPNS 010525-2 010 010 Y DDI Y DANS 038

1706 DPNS 010526-2 010 010 Y DDI Y DANS 038

1707 DPNS 010527-2 010 010 Y DDI Y DANS 038

1708 DPNS 010528-2 010 010 Y DDI Y DANS 038

1709 DPNS 010529-2 010 010 Y DDI Y DANS 038

1710 DPNS 010530-2 010 010 Y DDI Y DANS 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 VIRTUAL REAL LINK

010501-2 DPNSS C C B
































0105-2 MAINT U U

System Digit Translation Pattern, showing routing for 70, 71, 72 and 79 via Access Code 1041

ldtt 3 7

71 104171

72 1041

73 1042

74 1043

75 1048

76 1049

77 1050

78 1051

79 104179

70 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-- 0001 0010 0000 0000B

000000 00000. ---- 0000 0000 0000 0000B

?lssp

SYSTEM PARAMETER? :sprad

SPRAD 014612 06538. 1980 0001 1001 1000 1010B

040000 16384. 4--- 0100 0000 0000 0000B



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.



Create a new SIP Security profile setting the transport protocol as required.



Create a new SIP trunk with the default service type.



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.



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.



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:



Select Edit Configuration from Gateway Configuration section and a list of stored configurations is displayed.



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.



Next, edit the DPNSS protocol configuration as below.



Continued below…



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’.



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.



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.



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.



Select the ‘SIP’ tab, and set options as below.

Continued below…



Return to the ‘General’ tab and give the configuration a name and description.



‘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.



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.



QSIG Trunk Group settings.

The Routes section of the configuration should be configured as below.



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

http://www.cisco.com/en/US/solutions/collateral/ns340/ns414/ns728/ns784/963053_1.pdf



Acronyms

Acronym Definition

DPNSS Digital Private Network Signaling System as detailed in BTNR 188 and 189

NSI Non-Specified Information – vendor specific free-form PBX-to-PBX messaging

IPT IP Telephony

CUCM Cisco Unified Communications Manager

Q.931 ITU ISDN protocol at level 3

PBX Private Branch Exchange

MMI Man Machine Interface – specifically on iSDX/Realitis, a VT100 style console

COS Class Of Service – on an iSDX, the ability to activate features on a particular line

TAC Trunk Access Class – the ability for an extension to use a specific trunk

CLI Calling Line Identity

CLIP Calling Line Identity Presentation

CLIR Calling Line Identity Restriction

CNIP Calling Name Identity Presentation

COLP Connected Line Identity Presentation

COLR Connected Line Identity Restriction

CONP Connected Name Identity Presentation



Corporate

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

European

Headquarters

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

Americas

Headquarters

Cisco Systems, Inc.

170 West Tasman Drive

San Jose, CA 95134-1706

USA

www.cisco.com

Tel: 408 526-7660

Fax: 408 527-0883

Asia Pacific

Headquarters

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

http://www.cisco.com/go/offices



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.

siemens realitis / gpt isdx using e1 dpnss to cisco...

Documents