Pri when bring span up

[edkender]

I'm getting this error when I bring this pri up.

DCH054 DCH: 19 EST CONFIRM TIME: 15:02:04 23/02/2009

PRI264 DCH: 19 DATA: 00000002

PRI264 DCH: 19 DATA: 00000002

PRI264 DCH: 19 DATA: 00000002
!
PRI264 DCH: 19 DATA: 00000002

>
PRI264 DCH: 19 DATA: 00000002

PRI264 DCH: 19 DATA: 00000002


PRI0264
Protocol Error: Received an invalid call reference from far-end switch.
Output data: DCH: x DATA: y. Where: x = D-channel number and y =
Message type.
Report problem if condition persists.
Severity: Critical


What does the data: 00000002 mean?

Also eventually the span goes out of service because of slipr's and reached it's out of service limit.

 

[phonz1]

sounds like a protocol mis match, you need to match the CO with SLI, ESS5, ESS4 or NI2 protocol.

 

[mwpage2001]

First verify what kind of switch is on the other end of the PRI. Match the DCH and RDB programming to that. In my experience it has always been easier to change the PBX to match the CO. If other end is NI1, you may need to set IFC to D100.

 

[johnpoole]

and because your getting slips (layer 2) check your clocking as well

john poole
bellsouth business
columbia,sc

 

[edkender]

Here's what I have. I have a point to point pri between the nortel and a third party server. We need to utilize pri because they do routing based on caller id. I only have 4 protocol's to choose from on the third party server. d100, ni2, 5ess, or 4ess. They need to clock off of me so my only option is ni2. Problem is I have to set it up as a did trunk. When I do that if they send me a 7 or 10 digit number it strips it down to only 4 digits based on the ld0 prompt in ld 15. Does anyone have a work around to get an external call to tandem through the nortel with the ni2 protocol. It will not allow me to build it as tie because I do not have any isa routes built.