Technical Manual

ManualsBrandsCisco ManualsIP phonesCisco Bulk Administration Tool

Nortel Meridian PBX and Cisco CallManager

Integration

Document ID: 7207

Contents

Introduction

Prerequisites

Requirements

Configure

Configurations

Troubleshoot

Troubleshooting Commands

Related Information

Introduction

This configuration is taken from a Nortel Meridian 1 Option 81c private branch exchange (PBX), which runs

Release 2337. A T1 Primary Rate Interface (PRI) was defined to connect a DT24+ Voice over IP/Time

Division Multiplexing (VoIP/TDM) gateway.

A NT−6D80AB 4 port Multiple Serial Data Link (MSDL) was used to provide D−channel framing for the

PRI. There are three generations of PRI cards:

The oldest generation supports one PRI and requires one serial port on the MSDL for the D−channel.•

The next generation supports 2 PRIs and requires two serial ports on the MSDL for the D−channel.•

The newest generation supports one PRI and does not require an MSDL serial port for the D−channel.

(It has a high−level data link (HDLC) framer on the card.)

•

This PBX had the second generation PRI card; it required a physical cable to be run from the PRI card to a

port on the MSDL.

The DT24+ was set to the ISDN Network side with a switch type of 5E8 Custom. The PBX PRI trunk was set

to the ISDN User side with a switch type set to ESS5. This worked and is the configuration shown. We tried

to set the switch type on the PBX trunk to DMS100, but no matter what we did on DT24+, the PBX always

saw the trunk as in maintenance mode, and the calls were rejected.

For the D channel to become active, it does not matter which side (PBX or the VoIP gateway) is set to ISDN

USER or NETWORK. Set one device to ISDN USER and the other to NETWORK.

At this point, Layer 1 is active. For Layer 2 to initialize, each side sends Q.921 SABME frames. One side

responds with a Q.921 UA Unacknowledged message. After this, both sides begin to exchange Receiver

Ready (RR) messages. At this point, Layer 2 connectivity is established.

For further explanation of the PBX commands, refer to Nortel's "Administration Input/Output Guide for

Meridian 1" and Nortel's "1.5 mb DT1/PRI Administration and Maintenance Guide."

Prerequisites

Summary of content (8 pages)

PAGE 1
Nortel Meridian PBX and Cisco CallManager Integration Document ID: 7207 Contents Introduction Prerequisites Requirements Configure Configurations Troubleshoot Troubleshooting Commands Related Information Introduction This configuration is taken from a Nortel Meridian 1 Option 81c private branch exchange (PBX), which runs Release 2337. A T1 Primary Rate Interface (PRI) was defined to connect a DT24+ Voice over IP/Time Division Multiplexing (VoIP/TDM) gateway.
PAGE 2
Requirements There are no specific requirements for this document. Configure In this section, you are presented with the information to configure the features described in this document. This trunk was configured for a test scenario. The extension for the IP phone was x7373 and for the digital phone was x6925. When you called the IP phone from the digital phone, the access code 8815 was first dialed to choose the specific PRI trunk (see ACOD 8815 in LD21), and then the extension of the IP phone was dialed.
PAGE 3
PARM RS422 DTE DRAT 64KC CLOK EXT NASA NO IFC ESS5 SIDE USR CNEG 1 RLS ID 36 RCAP ND2 T200 3 T203 10 default − physical interface type default − physical interface rate default − physical interface clocking default − Network Attendant Service Allowed? Interface − aka "switch type" IDSN "side" − i.e.
PAGE 4
PAGE DES TN 115 01 configuration for TNB 115, B channel 1 TYPE TIE type of trunk − TIE, could be DID ..., see LD 14 CDEN SD default − card port density − single density CUST 0 Customer number − 0 get operator "x", 1 get "Y", ... NCOS 0 Network Class Of Service group − 0, change if trouble calling in or out RTMB 115 1 Route Number and Member Number − member 1, could be 2...
PAGE 5
OVL000 Call Routing Configuration >LD 21 load overlay module 21 to print a Route Data Block report PT1000 REQ PRT TYPE: RDB CUST 0 @ Request prompt, entered "PRT" to print @ Type prompt, entered "RDB" for Route Data Block Customer number − 0 get operator "x", 1 get "Y", ...
PAGE 6
NCNA YES NCRD NO CHTY BCH CTYP UKWN INAC NO default − Network Calling Name Allowed? − yes default − Network Call Redirection Allowed? − no Channel Type − BCH, could be ABCH default − Call Type for outgoing direct dialed TIE route− Unknown, could be INTL, NXX, ...
PAGE 7
ANTK default − ANI identifier number SIGO STD default − Signaling arrangement − std, could be ESN3, ...
PAGE 8
PLEV 2 default − Priority Level − 2, could be 0−7 for forcing override, camp−on, ... ALRM NO default − Malicious Call Trace Alarm is allowed for external calls? − no ART 0 SGRP 0 AACR NO default − Access Restriction Table − 0 default − Scheduled access Restriction Group − 0 default − Route Acquired by Application? − no Troubleshoot Refer to T1 PRI Troubleshooting for tips to debug PRI trunks.