PRI 208 ERRORS 1

[cscsupport]

Gettin pri 208 errors pretty consistent on option 81c release 3.0 does not appear to be service affecting to customer but annoying to look at what it reads is there is a protocol mismatch, below is the capture file that we, any suggestions.

Thanks.




recie DCH 8 OMSG CALLPROC REF 00008001 TN 00009804 CH 00000001 CK 4C55211A
% DCH 8 O 4C55211A
% 01 08 00 0B 08 02 80 01 02 18 04 E9 A0 83 01
%
% DCH 8 OMSG ALERT REF 00008001 TN 00009804 CH 00000001 CK 4C55251D
% DCH 8 O 4C55251D
% 01 08 00 05 08 02 80 01 01
%
% DCH 8 OMSG CONNECT REF 00008001 TN 00009804 CH 00000001 CK 4C55CAC2
% DCH 8 O 4C55CAC2
% 01 08 00 05 08 02 80 01 07
%
% DCH 8 IMSG CONN ACK REF 00008001 TN 00009804 CH 00000001 CK 4C55CAF6
% DCH 8 I 4C55CAF6
% 2F 08 00 05 08 02 00 01 06
%
% DCH 8 IMSG DISC REF 00008001 TN 00009804 CH 00000001 CK 4C56CAD5
% DCH 8 I 4C56CAD5
% 2F 08 00 09 08 02 00 01 07 02 02 81 90
%
% DCH 8 OMSG RELEASE REF 00008001 TN 00009804 CH 00000001 CK 4C56CAE1
% DCH 8 O 4C56CAE1
% 01 08 00 05 08 02 80 01 4D
%
% DCH 8 IMSG REL COMP REF 00008001 TN 00009804 CH 00000001 CK 4C56CB16
% DCH 8 I 4C56CB16
% 2F 08 00 05 08 02 00 01 0B
%
% PRI208 DCH: 8 DATA: 00000004ved on the dch debug for dch 8

 

[MagnaRGP]

Post your DCH.

 

[cscsupport]

Here is the Dchannel programming I believe this is what you were asking for.


REQ PRT
TYPE ADAN DCH 8

ADAN DCH 8
CTYP DCIP
DES VOIP
USR ISLD
ISLM 32
OTBF 32
NASA NO
IFC SL1
CNEG 1
RLS ID 25
RCAP ND2
MBGA NO
OVLR NO
OVLS NO
were asking for Magna.

 

[cscsupport]

Never got a reply on this can anyone tell me what the protocol mismatch is on this, or if anyone else has experienced this problem.

Thanks,
Happy New Year to everyone!

 

[x11tech]

Based on the print out of the DCH, it looks like an IP Peer Network Trunk. Do you have access to the remote side of the IP trunk?

You can collect more information on the DCH messaging (what you posted in the original post above) by using the following commands:


> LD 96
.SET MSGI 8 MON 2
.SET MSGO 8 MON 2
.ENL MSGI 8
.ENL MSGO 8


You can disable this using the reverse:


> LD 96
.DIS MSGI 8
.DIS MSGO 8
.SET MSGI 8 MON 0
.SET MSGO 8 MON 0


Much of this information will be meaningless to anyone who hasn't received training from Nortel GNTS (or someone who took training from them) on decoding the L3 DCH messaging.



PRI208 basically means that a L3 (layer 3) DCH (D channel) IE (information element) isn't as it is expected to be. Without knowing a little bit more, the answer isn't going to jump out at me. It might even be something as simple as firmware/loadware mismatch on your ITG/MC cards.


If you can post the DCH from the remote side, the LD 22 ISS from both systems, and a mode 2 DCH log I'll give it my best shot. Also please try to tell me what kind of IP hardware you're using (MC32, ITG, etc.)

You can find what kind of hardware you're using by (1) going to LD 60, (2) performing a STAT, (3) Find the Loop associated with the D channel, (4) go to LD 20, (5) print a channel (REQ: PRT, TYPE TRK) from the loop. (6) Look at the XTRK prompt in the print out. I'd expect to see either ITG, MC or a variation of that.

 

[cscsupport]

x11 thanks for the response I am working on getting all of the info for the remote sight as soon as I can collect it all, I will post it, started checking the trunks etc there could also be a mismatch on the trunk type could this also cause a problem or would it be directed more toward the dchannel itself. I guess we will find out more once I get you the info.

Thanks Again.