PRI dropping frame and signal, but not connection. Monitor shows PRIU DSP 1: is dead

[YanceyWorks]

I have been chasing this for a bit.

Question is this:
1. Possible bad cross over cable between IPOffice 500v2 and Adtran 900e from provider?
2. Bad PRI Card?
3. Timing or other issue with provider?

Everything works great for a week or so and then (usually early AM) drops the frame and signal, but NOT the connection to the Adtran.

A simple reboot restores all services instantly.

Other details:

Box: IP office 500v2 with 8.1(56) with 4x TMC8 cards (to run Nortel T & M series phones) + 1 PRIS U in slot 1

Provider: Comcast PRI

Provider CPE: Adtran 900e with 4-wire RJ-48X PRI handoff

PRI settings:
Switch type: NI2
Provider: Local Telco
Framing: ESF
Zero Suppression: B8ZS
Clock Quality: Network
Line Signalling: CPE

Thanks in advance for your feedback.
Rich

 

[holdmusic34]

I've seen this before on the same type of service on a different system (NEC Electra Elite/ IPK). Customer would return to work every Monday morning and the lines were out. A reset of the PRI feed would not fix it.
Only a reset of the system would clear the lockup. The carrier ended up replacing the PRI output device.

If your PRI is faulty on your Avaya, i would expect it to be totally faulty.

 

[YanceyWorks]

That is great feedback. I had not tried resetting the PRI CPE, but I suspect my experience would be the same as yours.

I have ordered a manufactured RJ-48C crossover just in case the terminations on the custom one we did isn't perfect. Hard to imagine why a cable would be intermittent though.

So far it looks like having Comcast replace the Adtran is the most likely course of action.

I would be interested to see if anyone else has seen this with Comcast or any provider delivering on an Adtran 900 series.

Rich

 

[Westi]

we had a customer that had a setup similar to this, SIP over line of sight (yuck) to the Adtran and then into the IPO on PRI interface.
Nothing but trouble for 2 years and a lot of finger pointing from provider and us until the customer purchased a proper Internet over fiber but was so fed up with the system by that time that they replaced all phones with a hosted solution.
make sure that the connection to the Adtran is good and doesn't have any problems as that can also cause issues

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

Give a tech a solution and he will be back tomorrow to ask you the next question, teach a tech how to read the manual and he will be able to solve the problems for a life time.

 

[YanceyWorks]

Thanks Westi,

In this case we can see the connection is up from the dedicated data cable modem to the Adtran and oddly to the PBX from the Adtran. What we see dropping in the Adtran to PBX connection is the frame and signal.

I just cannot put my finger on what and why we might see that.

Rich

 

[YanceyWorks]

Just went down again this morning. This is what I was able to grab from Monitor set to monitor only the PRI.

Starts with T1DSP alive, then some ISDNL1Evt items and then DSP is dead.

Any input to help decipher what I am seeing here is immensely appreciated.

Rich

********** SysMonitor v10.1 (56) [connected to 192.168.1.5 (ADDLPS)] **********
217673877mS ISDNL1Rx: v=1 peb=1
0000 02 01 01 33 ...3
217673877mS ISDNL2Rx: v=1 peb=1
0000 02 01 01 33 ...3
217673877mS ISDNL2Tx: v=1 peb=1
0000 02 01 01 cb ....
217673877mS ISDNL1Tx: v=1 peb=1
0000 02 01 01 cb ....
217682357mS T1DSP: PRIU DSP 1: is alive
217683678mS ISDNL1Rx: v=1 peb=1
0000 02 01 01 33 ...3
217683678mS ISDNL2Rx: v=1 peb=1
0000 02 01 01 33 ...3
217683678mS ISDNL2Tx: v=1 peb=1
0000 02 01 01 cb ....
217683678mS ISDNL1Tx: v=1 peb=1
0000 02 01 01 cb ....
217693479mS ISDNL1Rx: v=1 peb=1
0000 02 01 01 33 ...3
217693479mS ISDNL2Rx: v=1 peb=1
0000 02 01 01 33 ...3
217693479mS ISDNL2Tx: v=1 peb=1
0000 02 01 01 cb ....
217693480mS ISDNL1Tx: v=1 peb=1
0000 02 01 01 cb ....
217703280mS ISDNL1Rx: v=1 peb=1
0000 02 01 01 33 ...3
217703280mS ISDNL2Rx: v=1 peb=1
0000 02 01 01 33 ...3
217703280mS ISDNL2Tx: v=1 peb=1
0000 02 01 01 cb ....
217703281mS ISDNL1Tx: v=1 peb=1
0000 02 01 01 cb ....
217713081mS ISDNL1Rx: v=1 peb=1
0000 02 01 01 33 ...3
217713081mS ISDNL2Rx: v=1 peb=1
0000 02 01 01 33 ...3
217713082mS ISDNL2Tx: v=1 peb=1
0000 02 01 01 cb ....
217713082mS ISDNL1Tx: v=1 peb=1
0000 02 01 01 cb ....
217722882mS ISDNL1Rx: v=1 peb=1
0000 02 01 01 33 ...3
217722883mS ISDNL2Rx: v=1 peb=1
0000 02 01 01 33 ...3
217722883mS ISDNL2Tx: v=1 peb=1
0000 02 01 01 cb ....
217722883mS ISDNL1Tx: v=1 peb=1
0000 02 01 01 cb ....

********** SysMonitor v10.1 (56) [connected to 192.168.1.5 (ADDLPS)] **********
217732684mS ISDNL1Rx: v=1 peb=1
0000 02 01 01 33 ...3
217732684mS ISDNL2Rx: v=1 peb=1
0000 02 01 01 33 ...3
217732684mS ISDNL2Tx: v=1 peb=1
0000 02 01 01 cb ....
217732684mS ISDNL1Tx: v=1 peb=1
0000 02 01 01 cb ....
217742357mS T1DSP: PRIU DSP 1: is alive
217742485mS ISDNL1Rx: v=1 peb=1
0000 02 01 01 33 ...3
217742485mS ISDNL2Rx: v=1 peb=1
0000 02 01 01 33 ...3
217742485mS ISDNL2Tx: v=1 peb=1
0000 02 01 01 cb ....
217742485mS ISDNL1Tx: v=1 peb=1
0000 02 01 01 cb ....
217747438mS ISDNL1Evt: v=1 peb=1,F3 F1
217747438mS ISDNL1Evt: v=1 peb=1,F4 F3
217747445mS ISDNL1Evt: v=1 peb=1,UnLocked
217747938mS ISDNL1Evt: v=1 peb=1,PHDI
217752938mS ISDNL3Evt: v=1 p1=1,p2=1001,p3=4,p4=127,s1=
217752940mS ISDNL3Evt: v=1 p1=1,p2=1001,p3=5,p4=0,s1=
217752945mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217752948mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217754095mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217754098mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217755245mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217755248mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217756395mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217756398mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217757545mS ISDNL3Evt: v=1 p1=1,p2=1001,p3=5,p4=0,s1=
217787545mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217787548mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217788695mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217788698mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217789845mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217789848mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217790995mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217790998mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...

********** SysMonitor v10.1 (56) [connected to 192.168.1.5 (ADDLPS)] **********
217792145mS ISDNL3Evt: v=1 p1=1,p2=1001,p3=5,p4=0,s1=
217802357mS T1DSP: PRIU DSP 1: is dead
217802360mS T1DSP: PRIU DSP 1: loading image
217822145mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217822148mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217823295mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217823298mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217824445mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217824448mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217825595mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217825598mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217826745mS ISDNL3Evt: v=1 p1=1,p2=1001,p3=5,p4=0,s1=

********** SysMonitor v10.1 (56) [connected to 192.168.1.5 (ADDLPS)] **********
217856745mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217856748mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217857895mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217857898mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217859045mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217859048mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217860195mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217860198mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217861345mS ISDNL3Evt: v=1 p1=1,p2=1001,p3=5,p4=0,s1=
217862357mS T1DSP: PRIU DSP 1: is dead
217862360mS T1DSP: PRIU DSP 1: loading image
217891345mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217891348mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217892495mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217892498mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217893645mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217893648mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217894795mS ISDNL2Tx: v=1 peb=1
0000 00 01 7f ...
217894798mS ISDNL1Tx: v=1 peb=1
0000 00 01 7f ...
217895945mS ISDNL3Evt: v=1 p1=1,p2=1001,p3=5,p4=0,s1=

 

[tlpeter]

217747938mS ISDNL1Evt: v=1 peb=1,[b]PHDI[/b]

PHDI means physical line down.
Not your problem


BAZINGA!

I'm not insane, my mother had me tested!

 

[YanceyWorks]

@tlpeter, thanks, I would expect your recommendation would be to just have ISP replace the Adtran, correct? I'm sure I would be seeing more issues if a bad PRI card, etc.

ISP does see it down, but so far has not seen it as an issue on their end (yes, it is not like they would). IPO is brand new as is the Adtran.

Thanks,
Rich

 

[tlpeter]

I would kick some provider ass in this case.


BAZINGA!

I'm not insane, my mother had me tested!