CS1000E - CISCO Call Manager PRI E1 Interfacing 2

[encryptedangel]

Hi,

I am a newbie to Nortel and working on integrating Nortel PRI E1 with Cisco Call Manager. I have different protocols but got RLS: Wrong Mode error. Only ESGF working fine to an extent that I can receive the call from CISCO with CLI, hear the voice from that side, however, they can not hear my voice. Neither can I call any of CISCO ext... What might be the problem?

If someone has configurations of such scenario, please let me know as I am stuck on site.

Thanks.

 

[telebub]

You have a loopback in the circuit pointed towards the Nortel. Remove the loop and you should be fine. I agree with your setup, QSIG is the way to go.

 

[encryptedangel]

How can I remove this loop back, can you please tell me a little more? I shall be very thankful as I am almost stuck in this last step....

 

[Avaya911PLM]

What telebub is saying is that error is common if you have a loop back on the circuit.

If there is no physical loop back plug, then you and the far end are both set to the same side. If your interface is set as USR, then change to NET, of you are set to NET, then change your side to USR.

The error message you are getting says you are the same side as the far end. This is what you will see with a loop back plug towards you, but you will also see it if you are not the opposite side of the far end.



--
Fletch
Avaya E9-1-1 Product Manager

 

[encryptedangel]

Thanks, but what might be the reason of one way speech? When I call to Cisco, they receive my called and calling number in their debug however they receive some bad bearer problem and cant make the call through. When they call my side, I can hear them however, they are unable to hear me. In such case, protocol is ESGF.

Please help..

 

[Avaya911PLM]

Now I am confused. If the DCH is not up, no calls should be able to be made at all. The RLS WRONG MODE error is what I was talking about.

The one way speech may be a packetization size error.

--
Fletch
Avaya E9-1-1 Product Manager

 

[encryptedangel]

Ok, let me elaborate it a little. Cisco provide me a document in which they asked me to set ISGF as protocol. When I do this, I get that Wrong Mode error. However when I tried ESGF, D-Channel went up with result of this one way speech and other details I told you. Can you analyze it now?

 

[telebub]

I would go back to ISGF protocol and on the d-channel prompt SIDE, set it to NET. Enable and test. Below is my QSIG d-channel programming from an Option 81c to a Cisco Call Manager:

ADAN DCH 10
CTYP MSDL
GRP 2
DNUM 12
PORT 2
DES CISCO
USR PRI
DCHL 34
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC ISGF
PINX_CUST 0
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE NET
CNEG 1
RLS ID 26
RCAP COLP NDI CCBI CCNI PRI DV3I CTI QMWI
PR_TRIGS DIV 2 3
CNG 2 3
PR_RTN NO
MBGA NO
OVLR NO
OVLS NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7

 

[Avaya911PLM]

I agree . . . go to ISGF. You have to look at this logically.

First get the LINK up (signal on both sides - I think you are here now)
Next get the DCH to establish (You are close - CHG the SIDE NET/USR)
Last is to get calls to pass - you may have to play with anything from Dialplan to CBD to ADAN Configuration here, but no sense in doing any of this before the 1st 2 steps are done.

You reported your first error as RLS WRONG MODE. That is a sure indicator of the SIDE being wrong. NET has to see USR and USR has to see NET. You may be pretty close to where you need to be.

--
Fletch
Avaya E9-1-1 Product Manager

 

[encryptedangel]

Thankyou very much for your kind support. I just confirmed from Cisco officials, they are using Slave, so I think I will have to be Net, right?

Thank you very much again. I will implement these changes by day thursday and will report you guys back. Thanks.

 

[telebub]

Right.

 

[encryptedangel]

Thanks telebulb....

 

[Avaya911PLM]

Right. Cisco calls it SLAVE, Nortel/Avaya calls it USR.

I know Cisco likes to be the Master or NET sideby default. You can change it, but from what I have seen, it's a simpler change on the CS 1K side.

--
Fletch
Avaya E9-1-1 Product Manager

 

[encryptedangel]

Came back from the site today. When I went there, I was having Yellow Alarm, continuously. The configuration at that time was this:


>ld 21
PT1000

REQ: prt
TYPE: rdb
CUST 0
ROUT 21

TYPE RDB
CUST 00
ROUT 21
DES CISCO PRI2
TKTP TIE
NPID_TBL_NUM 0
ESN YES
RPA NO
CNVT NO
SAT NO
RCLS EXT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI2
ISDN YES
MODE PRA
IFC ISGF
SBN NO
PNI 00000
NCNA NO
NCRD NO
CTYP UKWN
INAC NO
ISAR NO
CPFXS YES
DAPC NO
INTC NO
MBXR NO
DSEL VOD
PTYP DTT
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 774
TCPP NO
TARG 01
CLEN 1
BILN NO
OABS
INST
ANTK
SIGO STD
MFC NO
ICIS YES
OGIS YES
PTUT 0
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
GTO 896
GTI 896
SFB 3
NBS 2048


PAGE 002

NBL 4096

IENB 5
TFD 0
VSS 0
VGD 6
DTD NO
SCDT NO
2 DT NO
DRNG NO
CDR YES
INC YES
LAST YES
QREC YES
OAL YES
AIA NO
OAN YES
OPD NO
NDP EXC 0
CDRX NO
NATL YES
SSL
CFWR NO
IDOP NO
VRAT NO
MUS NO
PANS YES
FRL 0 0
FRL 1 1
FRL 2 2
FRL 3 3
FRL 4 4
FRL 5 5
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
CBQ NO
AUTH NO
TDET NO
TTBL 0
ATAN NO
PLEV 2
OPR NO
ALRM NO
ART 0
PECL NO
DCTI 0
TIDY 774 21
SGRP 0
ARDN NO
AACR NO

REQ:
REQ PRT
TYPE: nend
SCH0099 NEND?
TYPE: end
SCH0099 END?
TYPE: l****
>
OVL000
>;d
OVL013

>
OVL000
>ld 22
PT2000

REQ prt
TYPE adan

ADAN HIST
SIZE 25000
USER MTC BUG
ADAN TTY 0
CTYP MGC
IPMG 4 0
DNUM 0
PORT 0
DES
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC
XSM NO
TTYLOG 0
BANR YES
ADAN TTY 1
CTYP MGC
IPMG 4 0
DNUM 1
PORT 1
DES
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER CTY
XSM NO
ADAN TTY 2
CTYP MGC
IPMG 4 0
DNUM 2
PORT 2
DES
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC SCH BUG
XSM NO
TTYLOG 0
BANR YES
ADAN TTY 4
CTYP CPSI
DNUM 4
PORT 0
DES
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC TRF SCH BUG OSN
XSM NO
TTYLOG 0
BANR YES



PAGE 001

ADAN TTY 5
CTYP CPSI
DNUM 5
PORT 1
DES
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC TRF SCH BUG OSN
XSM NO
TTYLOG 0
BANR YES
ADAN TTY 6
CTYP PTY
DNUM 6
PORT 1
DES otm
FLOW NO
USER MTC SCH CTY
XSM NO
TTYLOG 66
BANR NO
ADAN TTY 7
CTYP PTY
DNUM 7
PORT 0
DES otm2
FLOW NO
USER MTC SCH CTY
XSM NO
TTYLOG 66
BANR NO
ADAN DCH 18
CTYP MSDL
MG_CARD 004 0 03
PORT 1
DES pri_ghq
USR PRI
DCHL 18
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC ESGF
PINX_CUST 0
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID **
QCHID YES
RCAP COLP
MBGA NO
OVLR YES
DIDD 0
OVLS YES
OVLT 0
T310 120



PAGE 002

T200 3
T203 10
N200 3
N201 260
K 7
ADAN DCH 19
CTYP MSDL
MG_CARD 004 0 04
PORT 1
DES ghq2
USR PRI
DCHL 19
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC ESGF
PINX_CUST 0
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID **
QCHID YES
RCAP COLP
MBGA NO
OVLR YES
DIDD 0
OVLS YES
OVLT 0
T310 120
T200 3
T203 10
N200 3
N201 260
K 7
ADAN DCH 21
CTYP MSDL
MG_CARD 004 1 01
PORT 1
DES
USR PRI
DCHL 21
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC ISGF
PINX_CUST 0
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE NET
CNEG 1
RLS ID **
QCHID YES
RCAP COLP
MBGA NO
OVLR YES
DIDD 0



PAGE 003

OVLS YES
OVLT 0
T310 120
T200 3
T203 10
N200 3
N201 260
K 7

REQ logi adm

SCH0101

REQ
N 121 00 A018021 3114 03/11 12:27:29 00:02:10.0

&80112611XXXXXXXX 00
0 000
& 000 09 0

TIM000 12:30 11/3/2010 CPU 0

N 122 00 2053 A018037 03/11 12:29:51 00:00:16.0 A770872517

& 00
0 000
& 000

ERR225 0 7
in1

SCH0101

REQ
N 123 00 A018021 3136 03/11 12:30:12 00:00:24.0

&85125607XXXXXXXX 00
0 000
& 000 09 0
0000

SCH0101

REQ end
>



***********************************************************

I then tried to change protocols, but no solution. Then I changed LD 73 > PRI2 > LPTI > MFF to CRC... The Yellow alarm disappeared, D-Channel got up and I got this:


DTA300 21

DTA300 21

DTA300 21

DTA300 21

DTA300 21

DTA300 21

DTA300 21

************************************************************


I tried to use ACOD to seize the tone, got the tone and when dialed, received this:


DCH 21 UIPE_OMSG CC_SETUP_REQ REF 0000000A CH 21 30 TOD 14:00:54 CK 004EB354
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:2000 NUM PLAN: PRIVATE TON: ESN CDP
CALLED #:4101 NUM PLAN: PRIVATE TON: ESN CDP

DCH 21 UIPE_IMSG CC_REJECT_IND REF 0000000A CH 21 30 TOD 14:00:54 CK 004EB3F9
CAUSE: #58 - BC NOTAVAIL


************************************************************

Same thing was observed when call was dialed directly to 4101 using CDP.

After 2/3 minutes, PRI was getting Out of Service (most probably due to exceeded DTA300 Alarms). I tried everything, from changing protocols to changing PRI Cards.

I just need to confirm now, if it is still a problem from my side. I dont want to put everything on Cisco config, but I am like stuck right here.

 

[encryptedangel]

One more thing to mention. I am running two more PRIs with Erricson MD 1XX (110 or 100 I think). Its working perfectly fine as well.

Looking forward for kind support as before.


Regards,
Maaz Bin Mahmood

 

[Avaya911PLM]

A Yellow alarm is what we call a recieved alarm. It means that the far end does not see your signal so it could be their recieve or your transmit that is out.

The DCH error you got means that the call attempt made it to the net point but was rejected for some reason. CHeck the logs on that side.

--
Fletch
Avaya E9-1-1 Product Manager