Avaya BCM50 to CS2K VoIP Reference Guide

Business Communication Manager 50 Call Server 2000

> Solution Reference Design Guide For BCM50 to CS2K VoIP

Enterprise Solution Engineering Document Date: November 4th, 2005 Document Version: 2.0

Technical Configuration Guide for: BCM50 to CS2K V2.0 November, 2005

All rights reserved. November 2005 The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Nortel Networks Inc.

The software described in this document is furnished under a lice nse agreement and may be used only in accordance with the terms of that license.

Trademarks

Nortel, the Nortel logo, the Globemark, Unified Networks, PASSPORT and BayStack are trademarks of Nortel Networks.

Adobe and Acrobat Reader are trademarks of Adobe Systems Incorporate. All other Trademarks are the property of their respective owners.

______________________________________________________________________________________________________

Nortel Networks External Distribution 1

Technical Configuration Guide for: BCM50 to CS2K V2.0 November, 2005

Abstract

The proliferation of VoIP technologies and the subsequent interconnect of Nortel’s Enterprise and Carrier networks, requires the dissemination of detailed concepts and configuration information.

This document describes the setup of a converged Carrier / Enterprise service consisting of PBX hosted subscribers that can leverage the wealth of services offered by the IP Telco Network.

Target Audience

This document is intended for an informed audience of Nortel Networks Sales Engineers, Deployment Primes, Installation personnel, and especially Customers.

Acknowledgements

This Configuration Guide is the product of numerous individuals and teams who have demonstrated the very best in teamwork, innovation, and integrity. The authors wish to extend their personal appreciation for their talented effort.

______________________________________________________________________________________________________

Nortel Networks External Distribution 2

Technical Configuration Guide for: BCM50 to CS2K V2.0 November, 2005

TABLE OF CONTENTS

INTRODUCTION ............................................................................................................................... 5

1.1

1.2

1.3

BCM50 A U

CS2K I

NTERCONNECTION VAILABILITY AND ORDERING SE CASE

...................................................................................................................................... 6

........................................................................................... 5

...................................................................................................... 6

2. CS2K SETUP.......................................................................................................................................7

2.1

OFTWARE OPTIONALITY CONTROL

2.2

RUNKING

2.2.1 TABLE: CLLI............................................................................................................................ 7

2.2.2 TABLE: TRKGRP..................................................................................................................... 8

2.2.3 TABLE TRKSGRP.................................................................................................................... 8

2.2.4 TABLE TRKMEM..................................................................................................................... 8

2.3

ALL PROCESSING (CALLP) TRANSLATIONS

2.3.1 TABLE XLAPLAN..................................................................................................................... 9

2.3.2 TABLE OFRT ........................................................................................................................... 9

2.3.3 TABLE HNPACONT................................................................................................................. 9

2.3.4 TABLE LTDEF......................................................................................................................... 9

2.3.5 TABLE LTDATA..................................................................................................................... 10

2.3.6 TABLE LTCALLS ...................................................................................................................10

2.3.7 TABLE LTMAP....................................................................................................................... 10

2.4

ACKETIZATION

2.5

ETSI PRI T

2.5.1 Problem Identification............................................................................................................ 11

2.5.2 Workaround............................................................................................................................ 12

3. BCM50................................................................................................................................................ 15

3.1

AVEATS

3.1.1 Centrex IP Call Manager (CICM) SN07 Testing ................................................................... 15

3.1.2 Called Party Number Display (CPND).................................................................................. 15

3.1.3 T.38 FAX................................................................................................................................. 16

3.2

EY CODES

3.3

IP N

3.4

IP T

3.5

ELEPHONES & LINES

3.6

IALING PLAN

3.7

H.323........................................................................................................................................... 23

..................................................................................................................................... 7

........................................................................................................................... 10

RUNKS & OVERLAP SIGNALING

..................................................................................................................................... 15

.................................................................................................................................. 16

ETWORKING

ELEPHONY RESOURCES

.......................................................................................................................... 17

......................................................................................................... 18

.................................................................................................................. 20

............................................................................................................................. 20

(SOC) ................................................................................... 7

................................................................................. 8

................................................................................. 11

4. GWC................................................................................................................................................... 26

4.1

DDING

GWC

CMT................................................................................................................ 26

4.2

SSOCIATING

4.3

ESERVING

4.4

ONFIGURING VOICE NETWORK SETTINGS

5. APPENDIX A: DMS READ FILES................................................................................................. 32

5.1.1 Translation Verification (Traver)........................................................................................... 32

6. APPENDIX B: DMS CLLIREF....................................................................................................... 37

______________________________________________________________________________________________________

Nortel Networks External Distribution 3

H323 G

H323 C

ATEWAY TO

ARRIERS ON

GWC

H323 G

CMT....................................................................... 27

ATEWAY IN

................................................................................. 30

CMT.......................................................... 29

Technical Configuration Guide for: BCM50 to CS2K V2.0 November, 2005

List of Figures

Figure 1: Succession Network Reference Architecture................................................................... 5

Figure 2: Detailed Network Diagram ............................................................................................... 6

Figure 3: H.225 Setup Packet Trace............................................................................................. 11

Figure 4: BCM50 Key Codes......................................................................................................... 16

Figure 5: BCM50 IP Addressing.................................................................................................... 17

Figure 6: BCM50 DHCP, General Settings ................................................................................... 18

Figure 7: BCM50 Telephony Resources, IP Terminal Global Settings......................................... 19

Figure 8: BCM50 Telephony Resources, IP Terminal Details....................................................... 19

Figure 9: BCM50 Lines, Target Lines............................................................................................ 20

Figure 10: BCM50 Telephony, Active Sets ................................................................................... 20

Figure 11: BCM50 Dialing Plan, Public Network........................................................................... 21

Figure 12: BCM50 Dialing Plan, Private Networks........................................................................ 21

Figure 13: BCM50 Dial Plan - Routing, Routes............................................................................. 22

Figure 14: BCM50 Dial Plan - Routing, Destination Codes........................................................... 22

Figure 15: BCM50 Dialing Plan - Line Pools................................................................................. 23

Figure 16: BCM50 Port Ranges ....................................................................................................24

Figure 17: BCM50 Telephony Resources – IP Trunks, Local Gateway........................................ 24

Figure 18: BCM50 Telephony Resources, Media Parameters...................................................... 25

Figure 19: GWC – Add GWC ........................................................................................................26

Figure 20: GWC – Provisioning..................................................................................................... 27

Figure 21: GWC – Associate Media Gateway............................................................................... 28

Figure 22: GWC – Provisioning Gateway...................................................................................... 29

Figure 23: GWC – Add Carrier...................................................................................................... 29

Figure 24 GWC – Carriers............................................................................................................. 30

Figure 25: GWC Packet Level Main Screen.................................................................................. 31

Figure 26: Packetization Rate Selection ....................................................................................... 31

______________________________________________________________________________________________________

Nortel Networks External Distribution 4

Technical Configuration Guide for: BCM50 to CS2K V2.0 November, 2005

1. Introduction

The coupling of Nortel’ Succession Solution with the Business Communication Manager (BCM) has proven to be a significant step forward in the convergence of Enterprise and Carrier Networks.

It is fully anticipated that the addition of CS2K Gatekeeper functionality will result in a new specter of service offerings, and interconnect scenarios, to the Enterprise. This guide details the setup of a field deployable solution.

Figure 1: Succession Network Reference Architecture

1.1 BCM50 to CS2K Interconnection

The nuts and bolts of the architecture are the workings of the IP domain that binds the BCM to the CS2K (see Figure 2: Detailed Network Diagram). This new coupling of the traditional Carrier and Enterprise environments will require that SEs and Partners have a basic understanding of the components within this hybrid topology.

______________________________________________________________________________________________________

Nortel Networks External Distribution 5

Technical Configuration Guide for: BCM50 to CS2K V2.0 November, 2005

CS2K

ENET

LTC

LCME

Set C

TDM

Phone

613-234-4025

10.102.40.8

Interwork

SPM

GWC

(Gatekeeper)

10.102.40.60

10.102.40.13

BCM_M50

10.102.40.108 613-235-4353

10.102.40.110 613-236-4353

BCM2_M50

Figure 2: Detailed Network Diagram

Set A

i2004

10.102.40.109 Extension 353

Target Line 126

Set B

i2004

10.102.40.112 Extension 353

Target Line 127

From the Enterprise, Succession’s CS2K will appear as a Gatekeeper in the IP space; and as such will require minimum programming to interoperate correctly. However, the challenge for SEs will rest with the design, implementation, and understanding of the carrier portion of the network.

The CS2K will view the BCM as a call processing destination, defined in terms of Directory Numbers (DN), virtual trunks, and gateway endpoints. Detailed examples of these entities are available in the following chapters of this document

1.2 Availability and Ordering

This solution applies to the following Generally Available (GA) software streams:

• BCM50 Release 1

•

SN07, ISN07, SN08, and ISN08

1.3 Use Case

Within this document, a simple office-code translation plan will be used as a reference framework. From

Figure 2: Detailed Network Diagram

550; a VoIP Trunk access code of 9 will be used on the BCMs. From the above diagram, here are a few examples of dialing sequences:

• A (BCM_M50) calls B (BCM2_M50) via the CS2K, A dials: 9-550-236-4353

• B (BCM2_M50) call A (BCM_M50) via the CS2K, B dials: 9-550-235-4353

• A calls C (CS2K analogue line), A dials: 9-234-4025

•

C calls B (BCM2_M50), C dials: 550-235-4353

, the BCM50s are accessed via an area code of

______________________________________________________________________________________________________

Nortel Networks External Distribution 6

Technical Configuration Guide for: BCM50 to CS2K V2.0 November, 2005

2. CS2K Setup

It should be clearly understood by the reader that the design and implementation of translations is customer specific. What is contained herein is one way of accomplishing the objective; there are other methods which are equally effective.

To simplify the vulgarization of the concepts within, a North American ISDN PRI context was selected. This does not limit this solution to that signaling context; it does work with other PRI variants.

2.1 Software Optionality Control (SOC)

It is critical that the CS2K have the H.323 Gatekeeper functionality activated. For further information on the SOC, please consult NTP 297-8991-901 (www.nortel.com); customers may purchase software activation codes from authorized Nortel Sales Representatives.

For the H.323 Gatekeeper, please ensure that CS2B0004 is enabled. Firstly, you need to unlock the SOC by assigning a limit; this will also set the right to use flag:

• assign limit 100 <license key #1> to CS2B0004

Secondly, activation is accomplished by setting the state. This requires a second license key:

• assign state on <license key #2> to CS2B0004

When completed, the CS2B004 option should appear as follows: >soc

SOC: OPTION NAME RTU STATE USAGE LIMIT UNITS LAST_CHG CS2B0004 H323 Gatekeeper Y ON 8 100 1VC 05/01/20

2.2 Trunking

The CS2K needs to have unique addressable connection paths on which it may route calls to each BCM. These are referred to as trunk members within a group. They are defined in the following order through the tables.

2.2.1 TABLE: CLLI

The Common Language Location Identifier, or CLLI, is the route of the trunk group datafill. In this example, the CLLI BCM_M50 is associated to an administrator.

CLLI ADNUM TRKGRSIZ ADMININF

---------------------------BCM_M50 411 50 PIERRE_FOURNIER

______________________________________________________________________________________________________

Nortel Networks External Distribution 7

Technical Configuration Guide for: BCM50 to CS2K V2.0 November, 2005

2.2.2 TABLE: TRKGRP

The trunk group is characterized with PRA to indicate that it will appear to call processing as ISDN PRI signaling and ISDN translations.

GRPKEY GRPTYP TRAFSNO PADGRP NCCLS GRPINFO

-----------------------------------------BCM_M50 PRA 0 NPDGP NCRT MIDL N (ISDN 550) $ $

2.2.3 TABLE TRKSGRP

Detailed signaling setup (DS1, Q.931) and physical location (GWC card & port) are defined here.

SGRPKEY CARDCODE SGRPVAR SGRPVAR

-------------------------------BCM_M50 0 DS1SIG ISDN 20 20 87Q931 2 N STAND NETWORK PT_PT USER N UNEQ 160 N DEFAULT GWC 9 114 1 64K HDLC $ $

2.2.4 TABLE TRKMEM

CLLI EXTRKNM SGRP MEMVAR

-----------------------BCM_M50 1 0 GWC 9 114 2 BCM_M50 2 0 GWC 9 114 3 BCM_M50 3 0 GWC 9 114 4 BCM_M50 4 0 GWC 9 114 5

2.3 Call Processing (CallP) Translations

Designing CallP translations requires training and experience. The text of this section provides enough information to permit qualified personnel to complete the task. It is not a replacement for adequate training; please do not attempt unless properly qualified to do so.

The trunk group has been defined as an ISDN PRI, so the next step is to define a set of rudimentary translations to be able to route the calls to and from the BCM. For this,

• a “type” of translation is defined in XLAPLAN

• an office route in table OFRT

• association between the dialed digits and the office routes in HNPACONT and its sub

tables

• and finally, the ISDN specifics in “LT” family (ISDN Logical Terminal) of tables

______________________________________________________________________________________________________

Nortel Networks External Distribution 8

Technical Configuration Guide for: BCM50 to CS2K V2.0 November, 2005

2.3.1 TABLE XLAPLAN

XLAPIDX SCRNCL HSTS PRTNM ZEROMPOS RESINF OPTIONS ADMINI NF

---------------------------------------------------------BCM_PRI_TRAF NSCR 550 PRI_TRAF NONE N $ PRI_TRAFFIC

2.3.2 TABLE OFRT

RTE RTELIST OPTIONS

------------------550 (N D BCM_M50 0 N N) $ $

2.3.3 TABLE HNPACONT

STS SNPA NORTREFS NOAMBIGC RTEREF HNPACODE ATTRIB RTEMAP OPTIONS

---------------------------------------------------------------613 Y 1023 0 (237) (1) (0) (0) $

2.3.3.1 SUB RTEREF

RTE RTELIST

----------55 (T OFRT 550) $

RET 613 Y 1023 0 (237) (1) (0) (0) $

2.3.3.2 SUB HNPACODE

FROMDIGS TODIGS CDRRTMT

----------------------235 235 LRTE 55

RET 613 Y 1023 0 (237) (1) (0) (0) $

2.3.4 TABLE LTDEF

Is the Logical Terminal (LT) definition table; it defines logical terminals and access privileges. It also specifies an LTID and access privileges for the PRI trunk group.

LTKEY LTAP CLASSREF

-------------------

______________________________________________________________________________________________________

Nortel Networks External Distribution 9

Technical Configuration Guide for: BCM50 to CS2K V2.0 November, 2005

ISDN 550 B PRA 47 NTNAPRI V1 NIL (NOPMD ) $

2.3.5 TABLE LTDATA

The logical terminal data table stores service-related data associated with the logical terminal identifier (LTID), field LTDKEY, which is the key to this table.

LTDKEY LTDRSLT

-------------ISDN 550 SERV SERV Y Y ALWAYS ALWAYS (PRI_IP_PROT H323) $

2.3.6 TABLE LTCALLS

Logical terminal calls table. It specifies the types of calls that can route over each PRI trunk group. This table defines the first translations for each trunk group and call type.

LTID XLARTSEL OPTIONS

--------------------ISDN 550 PUB XLALEC 0 BCM_PRI_TRAF NLCA_NILLA_0 $

2.3.7 TABLE LTMAP

The logical terminal map table associates the logical terminal identifier (LTID) to a trunk group (identified by CLLI).

LTKEY MAPPING OPTION

-------------------ISDN 550 CLLI BCM_M50 (TEI 0) $

2.4 Packetization

Succession CS2K Solution supports both 10 and 20 millisecond (ms) rates; what is critical is that all components bet set to the same value. Care must be taken to ensure that the IW-SPM and the GWC are set to the same rate as the CS2K and the BCM.

The IW-SPM, required for interwork with locally hosted legacy lines, is set as follows for 20 ms: TABLE MNIPPARM

TOP MNKEY DFCODEC PRFCODEC PKTRATE INGRESS EGRESS JITMIN JITMAX JITTARG ECAN VOICE CMFNOISE T38 RFC2833 RTCP TONESET LOGINT CRCERROR USIZEPKT OSIZEPKT FRAGMENT JABBER DROPEVNT BRDCAST JITTER LATENCY VPKTLOST MINLOG OMPARMS

------------------------------------------------------------------------IWSPM G711ULAW G729 20 0 0 0 100 0 DISABLE OFF DISABLE DISABLE DISABLE N NORTHAMERICA 5 20 10 20 10 20 10 20 10 20 10 20 10 20 10 20 10 20 10 20 10 1000 50 1000 1000

______________________________________________________________________________________________________

Nortel Networks External Distribution 10

Technical Configuration Guide for: BCM50 to CS2K V2.0 November, 2005

Please see 4.4

Configuring Voice Network Settings

for information on the GWC packetization

setup.

2.5 ETSI PRI Trunks & Overlap Signaling

There are two types of signaling associated with ISDN PRI: ENBLOC and OVERLAP. Both pertain to the method in which digits are forwarded, first refers to the method when all digits are sent at one time and the latter where they are forwarded in multiple messages. Unused in North America, overlap is quite common in the remainder of the world.

There are a few key points that should be highlighted to ensure simple operation of a BCM connected to an overlap aware network:

• In general BCMs, who do not support overlap signaling, can interoperate with PRI overlap signaling provided all digits are contained within the H.323 setup message.

• Future CS2K releases intend to incorporate PRI variant checking to ensure that H.323 trunk groups destined to BCMs will not support overlap signaling.

2.5.1 Problem Identification

The BCM will reject H.225 setup messages that contain the “canOverlapSend” flag set to “True”, see highlight box inError! Reference source not found.

Figure 3: H.225 Setup Packet Trace

______________________________________________________________________________________________________

Nortel Networks External Distribution 11

+ 28 hidden pages