Cisco to Nortel Question

[gregdeike]

We have a Cisco Call Manager hooked to a Nortel 81C. The problem we are having is that about every three weeks the Call Manager will start to Lock Out the Loop on the Nortel side. Once we shut down the call manager and restart it, it works fine for the next three weeks. Is there a buffer on the Call Manager side that needs to be Changed? Thanks for any responses.

 

[talbotpat]

What ISDN protocol are you using here, and are you running Qsig as well? Usually, we see PRIMARY-NI2 used and the 81 set to network side and the CallManager gateway set to user side. Is CallManager seeing the gateway as a H.323 or MGCP gateway, and it would also help if you post a config from the CallManager gateway and provisioning info on the Nortel PRI.

Pat

 

[gregdeike]

Here is the information that I have from programming the Meridian Side. I do not control the Cisco part of it so I do not have that information. If you need any other information I will try to get it for the call manager. Thanks for any help.

(CONFIGURE COMMON EQUIPMENT)

>LD 22
PT2000

REQ PRT
TYPE CEQU

CEQU
MPED 8D
TERM
REMO
TERD
REMD
TERQ
REMQ
SUPL 004 020 028 036
044 052 060 N140
XCT 000 016 032 048
TDS * 000 * 016 * 032 * 048
CONF * 001 * 017 * 033 * 049
MFSD * 000 * 016 * 032 * 048

DLOP NUM DCH FRM LCMT YALM TRSH
PRI 002 00 ESF B8S FDL 00
003 12 ESF B8S FDL 00
010 24 ESF B8S FDL 00
011 12 ESF B8S FDL 00
026 00 ESF B8S FDL 00
027 12 ESF B8S FDL 00
034 12 ESF B8S FDL 00
035 24 ESF B8S FDL 00
050 24 ESF B8S FDL 00
EXT0 3PE
CNI 012 000 000
CNI 012 001 001
EXT1 3PE
CNI 012 000 000
CNI 012 001 001
MCFN S0B0 S0B1 S1B0 S1B1 S2B0 S2B1 S3B0 S3B1 FLSH TOTL
016 000 016 000 016 016 000 000 64 128





(CONFIGURE D-CHANNEL)

REQ END
>LD 22
PT2000

REQ PRT
TYPE ADAN DCH 50

ADAN DCH 50
CTYP MSDL
GRP 1
DNUM 13
PORT 3
DES CISCOVOIP
USR PRI
DCHL 50
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC D100
SIDE USR
CNEG 1
RLS ID **
RCAP ND2
T200 3
T203 10
N200 3
N201 260
K 7



(CONFIGURE ROUTE DATA BLOCK)

REQ END
>LD 21
PT1000

REQ: PRT
TYPE: RDB
CUST 0
ROUT 50

TYPE RDB
CUST 00
ROUT 50
DES CISCOVOIP
TKTP TIE
NPID_TBL_NUM 0
ESN NO
CNVT NO
SAT NO
RCLS EXT
DTRK YES
DGTP PRI
ISDN YES
MODE PRA
IFC D100
SBN NO
PNI 00000
NCNA YES
NCRD NO
CHTY BCH
CTYP UKWN
INAC NO
ISAR NO
CPUB OFF
DAPC NO
BCOT 0
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 7050
TCPP NO
PII NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0
NDNO 0 *
DEXT NO
DNAM NO
ANTK
SIGO STD
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
GRD 896
SFB 3
NBS 2048


PAGE 002

NBL 4096
TFD 0
DRNG NO
CDR NO
MUS NO
RACD NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
CBQ NO
AUTH NO
TTBL 0
PLEV 2
ALRM NO
ART 0
SGRP 0
AACR NO


(CONFIGURE TRUNK GROUP)

REQ: END
>LD 20

PT0000
REQ: PRT
TYPE: TNB
TN 50 1
SPWD
DATE
PAGE
DES

TN 050 01
TYPE TIE
CDEN SD
CUST 0
TRK PRI
PDCA 1
PCML MU
NCOS 0
RTMB 50 1
B-CHANNEL SIGNALING
TGAR 0
AST NO
IAPG 0
CLS UNR DTN CND WTA LPR APN THFD HKD
P10 VNL
TKID
DATE 2 OCT 2003


NACT
REQ: END
>


(CONFIGURE ROUTE LIST INDEX)

LD 86
ESN000

MEM AVAIL: (U/P): 6102981 USED U P: 1014699 337039 TOT: 7454719
DISK SPACE NEEDED: 570 KBYTES
2MB BACKUP DISKETTE(S) NEEDED: 1 (PROJECTED LD43 - BKO)
REQ PRT
CUST 0
FEAT RLB
RLI 11

RLI 11
ENTR 0
LTER NO
ROUT 50
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP NO
FRL 0
DMI 0
FCI 0
FSNI 0
SBOC NRR
OHQ NO
CBQ NO

ISET 0
NALT 5
MFRL 0


MEM AVAIL: (U/P): 6102981 USED U P: 1014699 337039 TOT: 7454719
DISK SPACE NEEDED: 570 KBYTES
2MB BACKUP DISKETTE(S) NEEDED: 1 (PROJECTED LD43 - BKO)
REQ END


(COORDINATED DIALING PLAN)

>LD 87
ESN000

MEM AVAIL: (U/P): 6102981 USED U P: 1014699 337039 TOT: 7454719
DISK SPACE NEEDED: 570 KBYTES
2MB BACKUP DISKETTE(S) NEEDED: 1 (PROJECTED LD43 - BKO)
REQ PRT
CUST 0
FEAT CDP
TYPE DSC
DSC 53
DSC 53
FLEN 0
DSP LSC
RLI 11
NPA
NXX

 

[bythespy]

Technically you do not have the option 81 connected to the CCM, you have it connected to a T1 interface in a router or CAT switch. Please give me some details on the topo of your network.
I had this problem and I am pretty sure I can get you headed in the right direction.


More than likely it is a clocking problem, if you have the cisco side of the T1 configured in CCM with MGCP. There are a few check boxes that need to be changed and a few settings that need to be altered to make it work. I will compare your nortel config to mine later today......

Mspivey
CCNP

Have you been to

http://www.ciptug.org

?
The OFFICIAL Cisco IP Telephony User Group!

"convergence isn't coming...... it is here." mspivey 2003

 

[gregdeike]

The other problem I have is this is the message I got back from the guy that is controlling the Cisco.

Greg, I cannot send him the info. However, I can have a conversation with him, if that is OK.

They want me to fix it, but he does not want to share the information. That is the bigger part of my problem.

 

[talbotpat]

Greg...contact me offline at pat.talbot@sbc.com and I will talk to your Cisco admin if you like to verify the CallManager and CM gateway piece of the puzzle.

Pat

 

[xavtho]

HEllo everybody,

I think that our conversation is interessant for me because I try to connect CCM 4.0 in H323 and a Nortel Option 11 with an E1 connexion.
But I can't link Up the controller port in my gateway (Cisco 2651). Is anyone has a configuration example for the gateway.
PS : my gw is not registered with my CCM.

Thanks for your help

xavtho

 

[MG2005]

Hi all, I'm new here. looks like a great community-

First off I config my Nortel side different than you did-I know my way works because I have this in production for quite some time now, been doing it this way along time with no issues:

You have the Nortel set for D100 and USER side, My Nortel is set for S100 and NET side.

The Cisco T1 interface should then be DMS-100 USER side-

your way may work too but even Cisco documents the config I use on their website, and like I said I know it works without issues as I'm using it now-

Also you should have someone do a "show T1 controllers" on the Cisco side and ensure clocking is set to "LINE". If it is not I bet you'll see numerous frame errors and line voilations piling up and that is likley your issue. Also It should obviously be set to DMS-100 ESF B8ZS. Heres what you should see on the cisco side-

Applique type is Channelized T1
Cablelength is short 133
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20030807, FPGA: 11
Framing is ESF, FDL is ansi, Line Code is B8ZS, Clock Source is Line.
CRC Threshold is 320. Reported from firmware is 0.
Data in current interval (76 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 24 hours)
0 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs


good luck and let us know what happens....

 

[xavtho]

hello,

I will inform you that my problem with the controller down between the E1 connexion in a router 2651 and a nortel Option 11 is Ok.
THe problem is from th framing . so the correct configuration is :

Hdb3 / no crc4 and clock source line (for the Router)
(particulary for the no-crc4 command)

WIth MGCP we can have a lot a fo service like transfert and so one. (but H323 is very poor).

bye

 

[foleys]

Change the LIN in the RDB to RRB. We have had this several times when the pbx has released a call and the other side has not.

 

[STMorin]

Hi,
I have a PRI between a Nortel 61c and a Cisco VOIP phone system. It allows us to 4-digit dial between the two phone systems. The PRI terminates into a 6608 gateway blade in our 6509 chassis system on one end and a PRI card in the Nortel (loop2) on the other. Every couple of months, I would have to disable and re-enable Loop 2 because the b-channels get locked out. Finding out why the channels go LCKO was not a big issue at the time because it didn't happen any more often than the b-channels on two other PRI's.
We recently deployed 7 Cisco VOIP wireless phones in a manufacturing area with two Cisco access points and now I have to disable and re-enable Loop 2 every other day. I noticed on my Nortel terminal one morning an error referencing the loop and the channel and reason 44.
Does anyone know what causes b-channels to LCKO? Does anyone else have any experience with this type of problem??
Thanks in advance.
STMorin

 

[jyoderz]

Has anyone resolved this issue? I'm running into the same problem.

 

[jneiberger]

This brings up a related issue. Why are you running a converged network when you haven't converged your data and voice groups? That is a course fraught with much peril.

 

[rtfmdude]

jyoderz,

If you're having the same problem:

-setup a syslog server
-configure the IOS voice gateway to log to it
-enable a 'debug isdn q931' and make sure it's being logged.

And wait for the problem to occur. Zip the file and post a link to it here; I'd be more than happy to take a look.