Citrix EasyCall Gateway Integrator Manual

Citrix EasyCall Gateway

Telephony System Integrator’s Guide

for Nortel Telephony Systems

Citrix® EasyCall Gateway™ 2.1Q

Copyright and Trademark Notice

Use of the product documented in this guide is subject to your prior acceptance of the End User License Agreement. A printable
copy of the End User License Agreement is included on your product USB-ROM and in the documentation download page of
the administration tool.

Information in this document is subject to change without notice. Companies, names, and data used in examples herein are
fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of Citrix Systems, Inc.

© 2006-2008 Citrix Systems, Inc. All rights reserved.
Citrix, is a registered trademark, and EasyCall,

Inc.

in the United States and other countries.

XenApp, and XenDesktop are trademarks of Citrix Systems,

RSA Encryption © 1996-1997 RSA Security Inc., All Rights Reserved.
This product includes software developed by The Apache Software Foundation (http://www.apache.org/)
Presentation Server (XenApp) Client: Portions of this software are based on code owned and copyrighted by O'Reilly Media,

Inc. 1998. (CJKV Information Processing, by Ken Lunde. ISBN: 1565922247.) All rights reserved.
Licensing: Portions of this documentation that relate to Globetrotter, Macrovision, and FLEXlm are copyright © 2005

Macrovision Corporation. All rights reserved.
This product includes open source Berkeley DB (BDB) software licensed from Oracle Corporation and PostgresSQL, released

under the BSD license.

Trad emark Acknowledgements

Adobe, Acrobat, and PostScript are trademarks or registered trademarks of Adobe Systems Incorporated in the U.S. and/or
other countries.

Asterisk is a registered trademark of Digium, Inc.
FreePBX is a registered trademark of Atengo, LLC.
Java, Sun, and SunOS are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

Solaris is a registered trademark of Sun Microsystems, Inc. Sun Microsystems, Inc has not tested or approved this product.
Portions of this software are based in part on the work of the Independent JPEG Group.
Microsoft, MS-DOS, Windows, W indo ws Media, Windows Server, W indows NT, Win32, Outloo k, ActiveX, Ac tive Directory,

and DirectShow are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other
countries.

trixbox (www.trixbox.com) is a registered trademark of Fonality, Inc.
UNIX is a registered trademark of The Open Group.
All other trademarks and registered trademarks are the property of their respective owners.
Document Code: August 12, 2008 (KP)

Contents

Chapter 1 Integration Overview

Call Detail Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2 Nortel SIP Trunk Integration

Configuring the IP Peer Network in Communication Server 1000. . . . . . . . . . . . . . . . 3

Enabling the SIP Trunk Gateway (SIP Virtual Trunk Application) . . . . . . . . . . . . . 4

Configuring the SIP Trunk Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Configuring Voice Codec for Nortel IP Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Restarting the Signaling Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Configuring the SIP Route and Trunks on the Call Server . . . . . . . . . . . . . . . . . . . . 11

Defining a Virtual Superloop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Creating a Virtual D-Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Defining ISDN Support for a Customer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Creating a Virtual Service Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Creating Virtual Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Verifying the Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

C

ONTENTS

Chapter 3 Nortel T1 QSIG Trunk Integration

Nortel Telephony System Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Line Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Configuring the T1 QSIG Route and Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Adding a PRI Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Adding a PRI D-Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Defining a PRI Customer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Defining a PRI Service Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Defining Service Channels and PRI Trunks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Defining System Timers and Clock Controller Parameters . . . . . . . . . . . . . . . . . 20

Enabling a TMDI or PRI MSDL Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Enabling the Clock Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Enabling a PRI Trunk Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Enabling the D-Channnel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Verifying the Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 4 Nortel E1 QSIG Trunk Integration

Nortel Telephony System Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Line Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

iv Telephony System Integrator’s Gui de

Configuring the E1 QSIG Route and Trunks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Adding a PRI Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Adding a PRI D-Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Defining a PRI Customer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Defining a PRI Service Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Defining Service Channels and PRI Trunks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Defining System Timers and Clock Controller Parameters . . . . . . . . . . . . . . . . . 30

Defining PRI Parameters and Threshholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Enabling a PRI2 MSDL Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Enabling the Clock Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Enabling a PRI2 Trunk Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Enabling the D-Channnel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Verifying the Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Integration Overview

The EasyCall Gateway has been certified for interoperability with Nortel
Communication Server 1000 version 5.0. The EasyCall Gateway supports SIP and
QSIG trunks.

To enable the EasyCall Gateway to work with the Nortel system, you must configure
the telephony system trunk between the EasyCall Gateway and the Nortel system.

C

HAPTER

1

EasyCall Gateway integrated with Nortel Communication Server

The integration described in this guide can be done in tandem with EasyCall Gateway
installation and configuration, which includes defining the properties of the telephony
system trunk and defining any changes the EasyCall Gateway makes to telephone
numbers before sending them to the telephony system for dialing. For information
about EasyCall Gateway configuration, refer to the EasyCall Gateway Administrator’s
Guide.

Those responsible for configuring the telephone system must take the specific
characteristics of a site into consideration to determine the appropriate settings.
Configuration of the Nortel telephone system for integration with the EasyCall Gateway
is similar to integration with a voicemail system.

The following topics describe how to configure trunks for the supported Nortel
systems.

“Nortel SIP Trunk Integration” on page 3
“Nortel T1 QSIG Trunk Integration” on page 15
“Nortel E1 QSIG Trunk Integration” on page 25

2 EasyCall Gateway Telephony System Integr ator ’s Guide

Call Detail Records

A Call Detail Record (CDR) is a file that contains information about calls placed
through the EasyCall Gateway. Information provided in the CDRs can be used for
billing calls to cost centers and for auditing potential abuse.

Nortel SIP T runk Integration

This chapter describes a sample configuration of Nortel telephony system for
integration with the EasyCall Gateway through a SIP trunk. The example
configurations are performed through the Nortel CS 1000 Element Manager and Nortel
overlays.

Please note the following regarding Nortel SIP trunk integration:

• When a call is made, there are two SIP virtual channels used on the CS 1000.
These are local loopback virtual channels.

• The EasyCall Gateway supports only the URI format number@IpAddress
(53380@47.248.100.179) and not the URI format [e-mail]
([e-mail]). This prevents the EasyCall Gateway from working
with a Nortel CS1000 SIP Gateway via Nortel SPS/NRS. Therefore, a direct SIP
connection should be set up between the CS1000 SIP GW and the EasyCall
Gateway without SPS involvement.

The following topics describe a sample configuration of Nortel SIP trunks:
“Configuring the IP Peer Network in Communication Server 1000” on page 3
“Configuring the SIP Route and Trunks on the Call Server” on page 11
“Verifying the Integration” on page 14

C

HAPTER

2

Configuring the IP Peer Network in Communication
Server 1000

The SIP Trunk Gateway runs only on the Signaling Server. You must configure both
the Signaling Server, using the CS 1000 Element Manager as described in this
section, and the Call Server, as described in “Configuring the SIP Route and Trunks on
the Call Server” on page 11.

The following topics describe how to use the Element Manager to configure the SIP
Trunk Gateway on the Signaling Server:

“Enabling the SIP Trunk Gateway (SIP Virtual Trunk Application)” on page 4
“Configuring the SIP Trunk Gateway” on page 8
“Configuring Voice Codec for Nortel IP Phones” on page 9
“Restarting the Signaling Server” on page 11

4 EasyCall Gateway Telephony System Integr ator ’s Guide

Enabling the SIP T runk Gateway (SIP Virtual T runk
Application)

1. Log in to the CS 1000 Element Manager.

2. From the EM Navigator, go to System > IP Network > Nodes: Servers, Media
Cards to open the Node Configuration page.

3. Click Edit.

Chapter 2 Nortel SIP Trunk Integration 5

4. Select Signaling Servers to display the list of signaling servers.

5. Select the appropriate Signaling Server 47.248.100.130 Prop erties to display
its properties.

6 EasyCall Gateway Telephony System Integr ator ’s Guide

6. From the Enable IP Peer Gateway (Virtual Trunk TPS) list, select a SIP option.
This field is used to enable SIP Trunk Gateway and Services.

7. Select the SIP Transport Protocol. This is the transport protocol used for SIP
message exchange between the Gateway and Redirect/Proxy Server. Defaults
to TCP, the recommended option for SIP traffic.

8. Verify the Local SIP Port. This is the port to which the gateway listens. Defaults
to 5060.

Note: The EasyCall Gateway always listens on port 5060. By default, the
EasyCall Gateway communicates with the SIP trunk over port 5060; that port is
configurable.

Chapter 2 Nortel SIP Trunk Integration 7

9. Enter the SIP Domain Name to identify the SIP Service Domain. This string is
used in building all SIP messages and appears in the phone context.

• The SIP Domain Name configured in the Signaling Server properties

must match the Service Domain name configured in the NRS.

• The string must be less than 128 characters in length.

• The valid characters are a-z, 0-9, period (.), hyphen (-), comma (,), and

underscore (_).

• This field must be specified if the SIP Trunk Gateway application is

enabled.

10. Click Save and Transfer.

8 EasyCall Gateway Telephony System Integr ator ’s Guide

Configuring the SIP T runk Gateway

1. From the EM Navigator, select System IP Network > Nodes: Servers, Media
Cards.

2. Click Edit.

3. Select SIP GW Settings to expand the section.

Chapter 2 Nortel SIP Trunk Integration 9

4. Complete the following for the Primary server:

• TLS Security: Select Security Disable from the list.

• Primary Proxy / Re-direct IP address: Enter the TLAN network interface

IP address of the Primary SIP Proxy Server / SIP Redirect Server.

• Primary Proxy / Re-direct IP Port: Leave the default port value as 5060

for the Primary SIP Proxy Server / SIP Redirect Server.

• Primary Proxy Supports Registration: This checkbox indicates to the

SIP Trunk Gateway whether the primary SIP Proxy Server / SIP Redirect
Server supports registration. If the checkbox is selected, then the SIP
Trunk Gateway must register with the primary SIP Proxy Server / SIP
Redirect Server. If the checkbox is not selected, then the SIP Trunk
Gateway will not register with the primary SIP Proxy Server / SIP Redirect
Server.

•The Primary CDS Proxy or Re-direct server flag is not used in this

release.

• Transport Protocol: Select UDP.

5. Click Save and Transfer.

Configuring Voice Codec for Nortel IP Phones

1. From the EM Navigator, select System IP Network > Nodes: Servers, Media
Cards.

2. Click Edit.

3. Click VGW and IP phone codec profile to expand the list.

10 EasyCall Gateway Telephony System Integr ator’s Guide

4. To configure a codec, select the Select check box to the right of the codec
name.

Note: The G.711 and T38 FAX codecs are automatically selected.

5. Click on the codec name to modify the Voice payload size (ms/frame), Voice

playout (jitter buffer) nominal delay, and Voice playout (jitter buffer)
maximum delay values of a codec. Use the lists to choose the values.

For detailed information about configuring codecs, refer to the Nortel
publications, Converging the Data Network with VoIP (NN43001-260) and IP
Line: Description, Installation, and Operation (NN43100-500).

6. Click Save and Transfer.

Chapter 2 Nortel SIP Trunk Integration 11

Restarting the Signaling Server

Some fields in the CS 1000 Element Manager can be changed at run-time: SIP
domain name, CDS proxy (yes or no), Gateway username and password, dialing
plans, and all “SIP Service” related fields except ACD DN. The rest of the fields require
a restart of the Signaling Server.

To perform a warm restart

1. From the EM Navigator, select System > IP Network > Maintenance and
Reports.

2. Select the node containing the Signaling Server to be restarted.

3. Click Reset for the Signaling Server.

To perform a cold restart

• Press the RST button on the front panel to cold restart the Signaling Server.

Configuring the SIP Route and Trunks on the Call Server

The following topics describe how to configure the SIP route and trunks on the Call
Server using Nortel LD Overlays:

LD 97: “Defining a Virtual Superloop” on page 11
LD 17: “Creating a Virtual D-Channel” on page 12
LD 16: “Defining ISDN Support for a Customer ” on page 12
LD 15: “Creating a Virtual Service Route” on page 12
LD 14: “Creating Virtual Trunks” on page 13

Defining a Virtual Superloop

The following example shows how to define a virtual superloop using LD 97. For all
other fields not listed in the example, press Enter to use default values.

Prompt Response Description

REQ CHG
TYPE SUPL
SUPL V100

Change existing data.
Superloop.
Create new virtual superloop 100.

12 EasyCall Gateway Telephony System Integr ator’s Guide

Creating a Virtual D-Channel

The following example shows how to create a virtual D-channel using LD 17. For all
other fields not listed in the example, press Enter to use default values.

Prompt Response Description

REQ CHG
TYPE ADAN
ADAN NEW DCH 12
CTYP DCIP
DES VTRK
USR ISLD

IFC SL1

RCAP ND2 MWI

Change existing data
Action Device And Number
Action Device And Number. Create new D-channel 12.
Card Type: D-channel is over IP (DCIP)
Designator
ISDN Mode of Operation. Mode: Integrated services

signaling link dedicated
Interface type for D-channel. Interface type is Meridian

1 – Meridian 1 (SL1)
Remote Capabilities. Allow Name display format 2

(ND2), Message Waiting Indicator (MWI)

Defining ISDN Support for a Customer

The following example shows how to define a custsomer with ISDN support using LD

15. For all other fields not listed in the example, press Enter to use default values.

Prompt Response Description

REQ CHG
TYPE CDB
CUST 0
ISDN YES

Change existing data
Customer data block
Customer number.
Customer is equipped with ISDN.

Creating a Virtual Service Route

The following example shows how to create a service route using LD 16. For all other
fields not listed in the example, press Enter to use default values.

Prompt Response Description

REQ NEW
TYPE RDB
CUST 0
ROUT 12
DES SIP

Create new data.
Route data block.
Customer number.
Route number.
Designator field for trunk.

Chapter 2 Nortel SIP Trunk Integration 13

Prompt Response Description

TKTP TIE
ICOG IAO
VTRK YES
ZONE 2

TIE trunk only, allowed between SL-1.
Incoming and outgoing.
Virtual trunk route.
Zone for codec selection and bandwidth

management.

NODE 510
PCID SIP
ISDN YES
MODE ISLD
DCH 12
PNI 1
IFC SL1
INAC YES

Node ID of signaling server of this route.
Protocol ID for this route is SIP.
ISDN option.
Route uses ISDN signaling link.
D-channel number used for this route.
Customer private network identifier.
Interface type: Meridian 1 to Meridian 1.
Insert ESN Access Code to an incoming private

network call.

NCNA YES
NCRD YES

Network calling name allowed.
Network call redirection.

Creating Virtual Trunks

The following example shows how to create virtual trunks using LD 14. For all other
fields not listed in the example, press Enter to use default values.

Prompt Response Description

REQ NEW 32
TYPE IPTI
TN 100 0 0 0
DES SIP
CUST 0
RTMB 12 1

STRI IMM
STRO IMM
CHID 1

Create 32 new trunks.
IP trunk.
Virtual card and channel number.
Designator field for trunk.
Customer number.
Route number 12, and trunk member numbers

started from 1.
Start arrangement incoming.
Start arrangement outgoing.
Channel ID for trunk.

14 EasyCall Gateway Telephony System Integr ator’s Guide

Verifying the Integration

To verify path replacement

1. To verify path replacement when the QSIG trunk integration is used please
check the number of B-channels used on the trunk between EasyCall Gateway
and the telephony system.

2. A few seconds after both call legs of the click-to-call have connected EasyCall
Gateway should be released from the call path and call should be bridged on the
telephony system.

3. To verify media bridging when the SIP trunk integration is used please capture
network traffic between EasyCall Gateway and telephony system. Make sure
that after the setup of the second call no RTP packets are flowing through the
EasyCall Gateway.

Nortel T1 QSIG T runk Integration

Please note the following regarding Nortel T1 QSIG trunk integration:

• Noise on the PRI link might indicate an incorrect PCMU configuration of PRI
trunks on the CS 1000. The PMCU should be set to Mu-Law for T1.

The following topics describe a sample configuration of Nortel Telephony (PBX)
system integration with the EasyCall Gateway through a T1 ISDN-PRI QSIG trunk.

“Nortel Telephony System Software Packages” on page 15
“Line Cards” on page 16
“Configuring the T1 QSIG Route and Trunks” on page 16
“Verifying the Integration” on page 23

C

HAPTER

3

Nortel Telephony System Software Packages

The Nortel telephony system used in this integration must have all supplemental
service packages installed for the QSIG protocol to operate properly and provide all
advanced supplemental services.

Required software packages:

Package Name Package Number

Network Alternate Route Selection (NARS), for Uniform
Dialing Plan

or
Coordinated Dialing Plan (CDP)

Integrated Services Digital Network (ISDN) 145

1.5 Mb Primary Rate Access (PRI)
or

2.0 Mb Primary Rate Access (PRI2)
Flexible Numbering Plan (FNP) 160
International Primary Rate Access (IPRA) 202
Multi-purpose Serial Data Link (MSDL) 222
Q-reference Signaling Point Interface Supplementary

Services (QSIG-SS)

58

59

146 (for T1)
154 (for E1)

263

16 EasyCall Gateway Telephony System Integr ator’s Guide

Package Name Package Number

QSIG Generic Functional Protocol Transport (QSIG-GF) 305
QSIG Supplementary Services (QSIG-SS) 316

Line Cards

A T1 Line Card must be available on the Nortel telephony system to connect to a T1
QSIG trunk.

Configuring the T1 QSIG Route and Trunks

The following topics describe how to configure the T1 QSIG route and trunks on the
Call Server using Nortel LD Overlays:

LD 17: “Adding a PRI Card” on page 17
LD 17: “Adding a PRI D-Channel” on page 17
LD 15: “Defining a PRI Customer” on page 18
LD 16: “Defining a PRI Service Route” on page 19
LD 14: “Defining Service Channels and PRI Trunks” on page 19
LD 73: “Defining System Timers and Clock Controller Parameters” on page 20
LD 48: “Enabling a TMDI or PRI MSDL Card” on page 21
LD 60: “Enabling the Clock Controller” on page 21
LD 60: “Enabling a PRI Trunk Loop” on page 21
LD 96: “Enabling the D-Channnel” on page 21

Chapter 3 Nortel T1 QSIG Trunk Integration 17

Adding a PRI Card

The following example shows how to add a PRI card using LD 17. For all other fields
not listed in the example, press Enter to use default values.

Prompt Response Description

REQ CHG
TYPE CFN
CEQU YES
DLOP 11
MG_CARD 4 0 2
MODE PRI
TMDI YES
TRSH 0

Change data.
Configuration data block.
Changes to common equipment.
Digital Trunk Interface Loop.
MG card assigned to superloop.
Mode of operation.
Card is TMDI card.
Threshold.

Adding a PRI D-Channel

The following example shows how to add a PRI D-channel using LD 17. For all other
fields not listed in the example, press Enter to use default values.

Prompt Response Description

REQ CHG
TYPE CFN
ADAN NEW DCH 11

CTYP TMDI

DES T1_QSIG
USR PRI

IFC ISGF

Change existing data.
Configuration data block.
Add a primary D-channel (any unused SDI port.)

xx =
1-9 for Option 11C main cabinet,
11-19 for IP expansion cabinet 1,
21-29 for IP expansion cabinet 2,
31-39 for IP expansion cabinet 3,
41-49 for IP expansion cabinet 4.

Xx = 11-14, 21-24, 31-34, 41-44 of the first, second,
third and fourth Media Gateway, respectively.

Card type where:
MSDL = The NTBK51BA Downloadable D-Channel

Daughterboard.
TMDI = TMDI (NTRB21) card.

Designator field.
D-channel is for ISDN PRI only.

2.0 Mb only supports PRI or SHA users.
Interface type.

18 EasyCall Gateway Telephony System Integr ator’s Guide

Prompt Response Description

DCHL 11

PRI card number carries the D-channel. Must match
entry made for the "CDNO" associated with the
"DCHI" prompt above.
xx =
1-9 for Option 11C main cabinet,
11-19 for IP expansion cabinet 1,
21-29 for IP expansion cabinet 2,
31-39 for IP expansion cabinet 3, and
41-49 for IP expansion cabinet 4.

xx = 11-14, 21-24, 31-34, 41-44 of the first, second,
third and fourth Media Gateway, respectively.

SIDE NET

NET = network, the controlling switch.
USR = slave to the controller.

RLS 5

Software release of far-end. This is the current
software release of the far-end. If the far-end has an
incompatible release of software, it prevents the
sending of application messages, for example,
“Network Ring Again.”

RCAP CCBI CCNI

PRI DV3I

CTI QMWI
PR_TRIGS
PR_TRIGS
PR_TRIGS
PR_TRIGS

DIV 2 1

CNG 2 1

CON 2 1

CTR2 2 1

Remote Capabilities.

Path Replacement Triggers.

Defining a PRI Customer

The following example shows how to define a PRI customer using LD 15. For all other
fields not listed in the example, press Enter to use default values.

Prompt Response Description

REQ CHG
TYPE CDB
CUST 0
ISDN YES

Change existing data.
Customer data block.
Customer number.
Customer is equipped with ISDN.

Chapter 3 Nortel T1 QSIG Trunk Integration 19

Defining a PRI Service Route

The following example shows how to add a PRI service route using LD 16. For all
other fields not listed in the example, press Enter to use default values.

Prompt Response Description

REQ NEW
TYPE RDB
CUST 0
ROUT 11
DES T1_QSIG
TKTP TIE
DTRK YES
ISDN YES
MODE PRI
PNI 1

IFC ISGF
ICOG IAO
ACOD 8011

Create new data.
Route data block.
Customer number.
Route number.
Designator field for trunk.
Trunk type.
Digital trunk route.
ISDN option.
Route used for PRI only.
Customer private network identifier. Is the same as

the CDB PNI at far-end.
Interface type.
Incoming and outgoing.
Trunk access code.

Defining Service Channels and PRI T runks

The following example shows how to create service channels and PRI trunks using LD

14. For all other fields not listed in the example, press Enter to use default values.

Prompt Response Description

REQ NEW 23
TYPE Tie
TN 11 1
PCML MU
DES T1_QSIG
CUST 0
RTMB 11 1
CLS UNR DTN

Create 23 new trunks.
Trunk type.
Loop (card) and channel number for digital trunks.
System PCM law.
Designator field for trunk.
Customer number.
Service route number and trunk member number.
Trunk Class Of Service.

20 EasyCall Gateway Telephony System Integr ator’s Guide

Defining System Timers and Clock Controller
Parameters

The following example shows how to define system timers and clock controller
parameters using LD 73. For all other fields not listed in the example, press Enter to
use default values.

Prompt Response Description

REQ CHG
TYPE DDB
MGCLK 4 0 2
PREF 2

SREF 2

Change data.
Digital Data Block.
Card slot number for Media Gateway 4 0.
Card number of PRI/DTI/SILC or DTI2/PRI2/SILC

containing the primary clock reference.
Card number of PRI/DTI/SILC or DTI2/PRI2/SILC

containing the primary clock reference.

Chapter 3 Nortel T1 QSIG Trunk Integration 21

Enabling a TMDI or PRI MSDL Card

The following example shows how to enable a TMDI card using LD 48.

>ld 48
LNK000
.enl tmdi 4 0 2

OK

Enabling the Clock Controller

The following example shows how to enable the clock controller using LD 60.

>ld 60
DTI000
.enl cc 4 0
.OK

Enabling a PRI T runk Loop

The following example shows how to enable a PRI loop using LD 60.

>ld 60
DTI000
.enll 11

OK

Enabling the D-Channnel

The D-Channel may not automatically come up. The following example shows how to
enable a PRI D-channel using LD 96.

>ld 96
DCH000
.enl dch 11
.
DCH: 11 EST CONFIRM TIME: 11:21:34 11/06/2008

DCH 11 UIPE_OMSG CC_RESTART_REQ REF 00000000 CH 0 TOD 11:21:34 CK
0086B935

TYPE: ALL CHANNEL

22 EasyCall Gateway Telephony System Integr ator’s Guide

DCH 11 UIPE_IMSG CC_RESTART_CONF REF 00008000 TOD 11:21:34 CK
0086B97B

TYPE: ALL CHANNEL

Verifying the Integration

To verify path replacement

1. To verify path replacement when the QSIG trunk integration is used please
check the number of B-channels used on the trunk between EasyCall Gateway
and the telephony system.

2. A few seconds after both call legs of the click-to-call have connected, EasyCall
Gateway should be released from the call path and call should be bridged on the
telephony system.

3. To verify media bridging when the SIP trunk integration is used, please capture
network traffic between EasyCall Gateway and telephony system. Make sure
that after the setup of the second call no RTP packets are flowing through the
EasyCall Gateway.

Chapter 3 Nortel T1 QSIG Trunk Integration 23

24 EasyCall Gateway Telephony System Integr ator’s Guide

Nortel E1 QSIG T runk Integration

Please note the following regarding Nortel E1 QSIG trunk integration:

• Noise on the PRI link might indicate an incorrect PCMU configuration of PRI
trunks on the CS 1000. The PMCU should be set to A-Law for E1.

• When there is an E1 link between CS1000 and the EasyCall Gateway, the end
user may experience that the E1 link is up and down continuously . This might be
caused to a mismatched multi-frame format configuration between CS1000 and
the EasyCall Gateway. The procedure in “Defining PRI Parameters and
Threshholds” on page 30 may help to resolve this issue.

The following topics describe a sample configuration of Nortel Telephony (PBX)
system integration with the EasyCall Gateway through an E1 ISDN-PRI QSIG trunk.

“Nortel Telephony System Software Packages” on page 26
“Line Cards” on page 26
“Configuring the E1 QSIG Route and Trunks” on page 26
“Verifying the Integration” on page 33

C

HAPTER

4

26 EasyCall Gateway Telephony System Integr ator’s Guide

Nortel Telephony System Software Packages

The Nortel telephony system used in this integration must have all supplemental
service packages installed for the QSIG protocol to operate properly and provide all
advanced supplemental services.

Required software packages:

Package Name Package Number

Network Alternate Route Selection (NARS), for Uniform
Dialing Plan

or
Coordinated Dialing Plan (CDP)

Integrated Services Digital Network (ISDN) 145

1.5 Mb Primary Rate Access (PRI)
or

2.0 Mb Primary Rate Access (PRI2)
Flexible Numbering Plan (FNP) 160
International Primary Rate Access (IPRA) 202
Multi-purpose Serial Data Link (MSDL) 222

58

59

146 (for T1)
154 (for E1)

Q-reference Signaling Point Interface Supplementary
Services (QSIG-SS)

QSIG Generic Functional Protocol Transport (QSIG-GF) 305
QSIG Supplementary Services (QSIG-SS) 316

Line Cards

An E1 Line Card must be available on the Nortel telephony system to connect to an E1
QSIG trunk.

Configuring the E1 QSIG Route and Trunks

The following topics describe how to configure the E1 QSIG route and trunks on the
Call Server using Nortel LD Overlays:

LD 17: “Adding a PRI Card” on page 27
LD 17: “Adding a PRI D-Channel” on page 27
LD 15: “Defining a PRI Customer” on page 28
LD 16: “Defining a PRI Service Route” on page 29
LD 14: “Defining Service Channels and PRI Trunks” on page 29
LD 73: “Defining System Timers and Clock Controller Parameters” on page 30

263

Chapter 4 Nortel E1 QSIG Trunk Integration 27

LD 73: “Defining PRI Parameters and Threshholds” on page 30
LD 48: “Enabling a PRI2 MSDL Card” on page 30
LD 60: “Enabling the Clock Controller” on page 31
LD 60: “Enabling a PRI2 Trunk Loop” on page 31
LD 96: “Enabling the D-Channnel” on page 31

Adding a PRI Card

The following example shows how to add a PRI card using LD 17. For all other fields
not listed in the example, press Enter to use default values.

Prompt Response Description

REQ CHG
TYPE CFN
CEQU YES
PRI2 10

Change data.
Configuration data block.
Changes to common equipment.
The PRI2 digital card number, where:

xx =
1-9 (Option 11C main cabinet),
11-19 (IP expansion cabinet 1),
21-29 (IP expansion cabinet 2),
31-39 (IP expansion cabinet 3),
41-49 (IP expansion cabinet 4.)

Xx = 11-14, 21-24, 31-34, 41-44 of the first, second,
third and fourth Media Gateway, respectively.

Adding a PRI D-Channel

The following example shows how to add a PRI D-channel using LD 17. For all other
fields not listed in the example, press Enter to use default values.

Prompt Response Description

REQ CHG
TYPE CFN
ADAN NEW DCH 10

CTYP MSDL

Change existing data
Configuration data block.
Add a primary D-channel (any unused SDI port).

xx =
1-9 for Option 11C main cabinet,
11-19 for IP expansion cabinet 1,
21-29 for IP expansion cabinet 2,
31-39 for IP expansion cabinet 3,
41-49 for IP expansion cabinet 4.

Xx = 11-14, 21-24, 31-34, 41-44 of the first, second,
third and fourth Media Gateway, respectively.

Card type where:
MSDL = The NTBK51BA Downloadable D-Channel
Daughterboard.
TMDI = TMDI (NTRB21) card.

28 EasyCall Gateway Telephony System Integr ator’s Guide

Prompt Response Description

DES E1_QSIG
USR PRI

Designator field.
D-channel is for ISDN PRI only.

2.0 Mb only supports PRI or SHA user

IFC ISGF
DCHL 10

Interface type.
PRI card number carries the D-channel. Must match

entry made for the "CDNO" associated with the
"DCHI" prompt above.

xx =
1-9 for Option 11C main cabinet,
11-19 for IP expansion cabinet 1,
21-29 for IP expansion cabinet 2,
31-39 for IP expansion cabinet 3,
41-49 for IP expansion cabinet 4.

Xx = 11-14, 21-24, 31-34, 41-44 of the first, second,
third and fourth Media Gateway, respectively.

SIDE NET

NET = network, the controlling switch.
USR = slave to the controller.

RLS 5

Software release of far-end. This is the current
software release of the far-end. If the far-end has an
incompatible release of software, it prevents the
sending of application messages, for example,
“Network Ring Again.”

RCAP CCBI CCNI

PRI DV3I

CTI QMWI
PR_TRIGS
PR_TRIGS
PR_TRIGS
PR_TRIGS

DIV 2 1

CNG 2 1

CON 2 1

CTR2 2 1

Remote Capabilities.

Path Replacement Triggers.

Defining a PRI Customer

The following example shows how to define a PRI customer using LD 15. For all other
fields not listed in the example, press Enter to use default values.

Prompt Response Description

REQ CHG
TYPE CDB
CUST 0
ISDN YES

Change existing data.
Customer data block.
Customer number.
Customer is equipped with ISDN.

Chapter 4 Nortel E1 QSIG Trunk Integration 29

Defining a PRI Service Route

The following example shows how to add a PRI service route using LD 16. For all
other fields not listed in the example, press Enter to use default values.

Prompt Response Description

REQ NEW
TYPE RDB
CUST 0
ROUT 10
DES E1_QSIG
TKTP TIE
DTRK YES
ISDN YES
MODE PRI
PNI 1

IFC ISGF
ICOG IAO
ACOD 8010

Create new data.
Route data block.
Customer number.
Route number.
Designator field for trunk.
Trunk type.
Digital trunk route.
ISDN option.
Route used for PRI only.
Customer private network identifier. Is the same as

the CDB PNI at far-end.
Interface type.
Incoming and outgoing.
Trunk access code.

Defining Service Channels and PRI T runks

The following example shows how to create service channels and PRI trunks using LD

14. For all other fields not listed in the example, press Enter to use default values.

Prompt Response Description

REQ NEW 30
TYPE Tie
TN 10 1
PCML A
DES E1_QSIG
CUST 0
RTMB 10 1
CLS UNR DTN

Create 30 new trunks.
Trunk type.
Loop (card) and channel number for digital trunks.
System PCM law.
Designator field for trunk.
Customer number.
Service route number and trunk member number.
Trunk Class Of Service.

30 EasyCall Gateway Telephony System Integr ator’s Guide

Defining System Timers and Clock Controller
Parameters

The following example shows how to define system timers and clock controller
parameters using LD 73. For all other fields not listed in the example, press Enter to
use default values.

Prompt Response Description

REQ CHG
TYPE PRI2
FEAT SYTI
MGCLK 4 0 1
PREF 1

SREF 1

Change data.

2.0 Mb PRI.
System timer.
Card slot number for Media Gateway 4 0.
Card number of PRI/DTI/SILC or DTI2/PRI2/SILC

containing the primary clock reference.
Card number of PRI/DTI/SILC or DTI2/PRI2/SILC

containing the primary clock reference.

Defining PRI Parameters and Threshholds

The following example shows how to define PRI parameters and thresholds using LD

73. For all other fields not listed in the example, press Enter to use default values.

Prompt Response Description

REQ CHG
TYPE PRI2
FEAT LPTI
MFF CRC
ACRC YES

Change data.

2.0 Mb PRI.
Loop timers.
Multiframe format.
Automatic reporting of CRC-4 error.

Enabling a PRI2 MSDL Card

The following example shows how to enable a PRI2 MSDL card using LD 48.

>ld 48
LNK000
.enl msdl 4 0 1

OK

Chapter 4 Nortel E1 QSIG Trunk Integration 31

Enabling the Clock Controller

The following example shows how to enable the clock controller using LD 60.

>ld 60
DTI000
.enl cc 4 0
.OK

Enabling a PRI2 Trunk Loop

The following example shows how to enable a PRI2 loop using LD 60.

>ld 60
DTI000
.enll 10

OK
.
DCH: 10 EST CONFIRM TIME: 11:18:22 11/06/2008

DCH 10 UIPE_OMSG CC_RESTART_REQ REF 00000000 CH 0 TOD 11:18:22 CK
0080E435

TYPE: ALL CHANNEL

DCH 10 UIPE_IMSG CC_RESTART_CONF REF 00008000 TOD 11:18:22 CK
0080E479

TYPE: ALL CHANNEL

Enabling the D-Channnel

The D-Channel may not automatically come up. The following example shows how to
enable the PRI2 D-channel using LD 96.

>ld 96
DCH000
.enl dch 10
.
DCH: 10 EST CONFIRM TIME: 11:21:34 11/06/2008

DCH 10 UIPE_OMSG CC_RESTART_REQ REF 00000000 CH 0 TOD 11:21:34 CK
0086B935

32 EasyCall Gateway Telephony System Integr ator’s Guide

TYPE: ALL CHANNEL

DCH 10 UIPE_IMSG CC_RESTART_CONF REF 00008000 TOD 11:21:34 CK
0086B97B

TYPE: ALL CHANNEL

Verifying the Integration

To verify path replacement

1. To verify path replacement when the QSIG trunk integration is used please
check the number of B-channels used on the trunk between EasyCall Gateway
and the telephony system.

2. A few seconds after both call legs of the click-to-call have connected, EasyCall
Gateway should be released from the call path and call should be bridged on the
telephony system.

3. To verify media bridging when the SIP trunk integration is used, please capture
network traffic between EasyCall Gateway and telephony system. Make sure
that after the setup of the second call no RTP packets are flowing through the
EasyCall Gateway.

Chapter 4 Nortel E1 QSIG Trunk Integration 33

34 EasyCall Gateway Telephony System Integr ator’s Guide