OPT 11 to Cisco don't have QSIG 1

[sarakodi]

Trying to set up PRI between Nortel Opt11 and Cisco
Set up is NI2 trunk type is DID can call back and forth but unable to call out from Cisco and Cisco can't recieve external call from Nortel, calls revert to operator
I don't have QSIG

Thanks in advance
Mike

TYPE adan dch 6

ADAN DCH 6
CTYP MSDL
CARD 03
PORT 1
DES CISCO
USR PRI
DCHL 3
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC NI2
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID **
RCAP COLP
MBGA NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7




TYPE RDB
CUST 00
DMOD
ROUT 9
DES CISCO
TKTP DID
SAT NO
RCLS EXT
DTRK YES
DGTP PRI
ISDN YES
MODE PRA
IFC NI2
CBCR NO
SBN NO
NCNA YES
NCRD YES
CHTY BCH
CPFXS YES
BCOT 0
INTC NO
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
RANX NO
SRCH RRB
TRMB YES
STEP
ACOD 4000
TCPP NO
PII NO
TARG 01
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
FLH 510
GRD 896
SFB 3
NBS 2048
NBL 4096
TFD 0
DRNG NO
CDR NO
MUS NO
MR NO
EQAR 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
TTBL 0
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0
AACR NO


TN 003 01
TYPE DID
CDEN SD
CUST 0
NCOS 0
RTMB 9 1
B-CHANNEL SIGNALING
NITE
STRI/STRO OWK OWK
NO
IAPG 0
CLS UNR DTN WTA LPR APN THFD HKD
P10 VNL
TKID
DATE 28 OCT 2011

 

[GHTROUT]

When the Cisco tries to call out, the system thinks TN 3-1 (for example) is originating the call. It is NCOS 0. That might be the problem. The TGAR 1 of the DID trunk might also be an issue if the TARG of your outgoing Route includes TARG 1. Depends on BARS ESN and how the Cisco user dials.

Quick examination would be to

>LD80

.TRAC 3 1 DEV



--
Nortel Resources at GHTROUT.com World Famous!
--

 

[sarakodi]

Changed it to TIE made call from 914-227-6815 to Nortel did 203-422-7846 that CDP's to Cisco ended up reception after hour’s menu.


DCH Message:

PRI228 DCH: 6 DATA: 00000000
DCH 6 OMSG RELEASE REF 00000003 CH 0 TOD 14:42:14
CAUSE :MANDATORY INFO IE MISSING
DCH 6 IMSG UNKNOWN REF 00000000 TOD 14:42:14
PROGRESS: INBAND INFO OR PATTERN IS AVAIL
DCH 6 IMSG NOTIFY REF 00000003 CH 3 3 TOD 14:42:14
CONNECT #:7846 NUM PLAN: NUM UNKNOWN
DCH 6 IMSG REL COMP REF 00000003 CH 3 3 TOD 14:42:14
DCH 6 OMSG SETUP REF 00000002 CH 3 2 TOD 14:42:16
CALLING #:9142276815 NUM PLAN: E164
CALLED #:7846 NUM PLAN: PRIVATE
PRI222 DCH: 6 DATA: 00000002
DCH 6 OMSG RELEASE REF 00000002 CH 0 TOD 14:42:16
CAUSE :INVALID IE CONTENTS
DCH 6 IMSG UNKNOWN REF 00000000 TOD 14:42:16
PRI228 DCH: 6 DATA: 00000000
DCH 6 OMSG RELEASE REF 00000002 CH 0 TOD 14:42:16
CAUSE :MANDATORY INFO IE MISSING
DCH 6 IMSG UNKNOWN REF 00000000 TOD 14:42:16
PROGRESS: INBAND INFO OR PATTERN IS AVAIL
DCH 6 IMSG NOTIFY REF 00000002 CH 3 2 TOD 14:42:16
CONNECT #:7846 NUM PLAN: NUM UNKNOWN
DCH 6 IMSG REL COMP REF 00000002 CH 3 2 TOD 14:42:16

Then I made the same call got the auto attendant tried to dial through to 7846 and got the following message.

DCH 6 OMSG SETUP REF 00000002 CH 3 2 TOD 14:50:50
CALLING #:9142276815 NUM PLAN: E164
CALLED #:7846 NUM PLAN: PRIVATE
PRI222 DCH: 6 DATA: 00000002
DCH 6 OMSG RELEASE REF 00000002 CH 0 TOD 14:50:50
CAUSE :INVALID IE CONTENTS
DCH 6 IMSG UNKNOWN REF 00000000 TOD 14:50:50
PRI228 DCH: 6 DATA: 00000000
DCH 6 OMSG RELEASE REF 00000002 CH 0 TOD 14:50:50
CAUSE :MANDATORY INFO IE MISSING
DCH 6 IMSG UNKNOWN REF 00000000 TOD 14:50:50
PROGRESS: INBAND INFO OR PATTERN IS AVAIL
DCH 6 IMSG NOTIFY REF 00000002 CH 3 2 TOD 14:50:50
CONNECT #:7846 NUM PLAN: NUM UNKNOWN
DCH 6 IMSG REL COMP REF 00000002 CH 3 2 TOD 14:50:50
DCH 6 OMSG SETUP REF 00000001 CH 3 1 TOD 14:50:52
CALLING #:9142276815 NUM PLAN: E164
CALLED #:7846 NUM PLAN: PRIVATE
PRI222 DCH: 6 DATA: 00000001
DCH 6 OMSG RELEASE REF 00000001 CH 0 TOD 14:50:52
CAUSE :INVALID IE CONTENTS
DCH 6 IMSG UNKNOWN REF 00000000 TOD 14:50:52
PRI228 DCH: 6 DATA: 00000000
DCH 6 OMSG RELEASE REF 00000001 CH 0 TOD 14:50:52
CAUSE :MANDATORY INFO IE MISSING
DCH 6 IMSG UNKNOWN REF 00000000 TOD 14:50:52
PROGRESS: INBAND INFO OR PATTERN IS AVAIL
DCH 6 IMSG NOTIFY REF 00000001 CH 3 1 TOD 14:50:52
CONNECT #:7846 NUM PLAN: NUM UNKNOWN
DCH 6 IMSG REL COMP REF 00000001 CH 3 1 TOD 14:50:52
DTC103
DCH 6 OMSG SETUP REF 00000005 CH 3 5 TOD 14:51:10
CALLING #:7777 NUM PLAN: PRIVATE
CALLED #:7846 NUM PLAN: PRIVATE
PRI222 DCH: 6 DATA: 00000005
DCH 6 OMSG RELEASE REF 00000005 CH 0 TOD 14:51:10
CAUSE :INVALID IE CONTENTS
DCH 6 IMSG UNKNOWN REF 00000000 TOD 14:51:10
PRI228 DCH: 6 DATA: 00000000
DCH 6 OMSG RELEASE REF 00000005 CH 0 TOD 14:51:10
CAUSE :MANDATORY INFO IE MISSING
DCH 6 IMSG UNKNOWN REF 00000000 TOD 14:51:10
PROGRESS: INBAND INFO OR PATTERN IS AVAIL
DCH 6 IMSG NOTIFY REF 00000005 CH 3 5 TOD 14:51:10
CONNECT #:7846 NUM PLAN: NUM UNKNOWN
DCH 6 IMSG REL COMP REF 00000005 CH 3 5 TOD 14:51:10

Got message I'm sorry extension 7846 not available then transferred back to night menu.

7777 is the voice mail system not Nortel not sure what it is.

 

[GHTROUT]

All of these PRI222 DCH: 6 DATA: 0000000x and PRI228 DCH: 6 DATA: 00000000

I'd be searching the forum for those.

--
Nortel Resources at GHTROUT.com World Famous!
--

 

[sarakodi]

Ok latest update seems that the call is making it to the Cisco phone it flashes and the phone rings for a brief audible signal and thats it. moment and thats it.
I get a busy signal on my end.

Any Ideas ???

 

[GHTROUT]

Yes, give us an update on what has been posted.

--
Nortel Resources at GHTROUT.com World Famous!
--

 

[m31690]

Try changing your STRI/STRO to IMM or WNK on TN 3-1

 

[janaya]

All I can say is NI2 doesn't play well with Nortel to Cisco. I have never gotten it to work well.

What software release do you have? You may have to do non-PRI circuit to get everything, except Caller ID to work.

 

[RickyPone]

I just set up four pri circuits to connect to a cisco call manager. The call manager can be configured as a d100 and I set the IFC as s100. That way I could be the net. Works fine. The cisco tech had to change a setting in the gateway because at first the interface was not functioning. My dchannel messaging looked a lot like yours. Oh yeah only nd2 should be in the rcap.

 

[sarakodi]

Rick
The four PRI's where they set as TIE or DID?
I'm having lots of luck with NI2 DID internal Cisco to Nortel are good and Nortel to Cisco are good, I just cant get an external call to the Cisco and can't Make external calls from Cisco out of the Nortel, calls end up @ reception phone.
What do you think?

 

[RickyPone]

TIE route for me. I know that they say ni2 interface will work and it probably will. I bet something in the gateway needs to be changed. I saved the email from the cisco tech that stated what he changed. I'll look for it.

 

[bhassell2000]

we use Tie for out 10 PRIs to our call manager

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[sarakodi]

RickyPone (TechnicalUser) 1 Nov 11 12:32
TIE route for me. I know that they say ni2 interface will work and it probably will. I bet something in the gateway needs to be changed. I saved the email from the cisco tech that stated what he changed. I'll look for it.

Rick any luck locating that e-mail from the cisco tech?

 

[RickyPone]

Yeah I found it but it didn't have what he changed on it. Don't know why either because I sure did read it.

ADAN DCH 24
CTYP MSDL
GRP 1
DNUM 15
PORT 2
DES cisco
USR PRI
DCHL 24
OTBF 128
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC S100
SIDE NET
CNEG 1
RLS ID 36
RCAP ND2
MBGA NO
OVLR NO
OVLS NO
T200 3
T203 10
N200 3
N201 260
K 7

This is how I built mine with the cisco ifc=d100. He wanted me to be the net and you can't if you use ni2.

 

[RickyPone]

no mgcp fax t38 inhibit

Didn't look back far enough.

 

[sarakodi]

Many Thanks Rick

 

[RickyPone]

Hope it helps.

 

[sarakodi]

Didn't help still can't call between Nortel & Cisco and it's getting old real quick because I seem to be making all the changes yet the problem still exsists and the vendor installing the Cisco side keeps saying he's set up correctly yet I don't know enough about the Cisco to say he's wrong.

 

[RickyPone]

I would make them tell me how they want the d-channel configured. The vendor I worked with tried the same thing when it didn't work at first. I just asked them nicely to tell me how they wanted it configured. If they can't tell you that then there is nothing you can do. He can't be setup correctly because it is not working.

 

[sarakodi]

Thats exactly what its going to come to.