Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PRI Line not Working 2

Status
Not open for further replies.

Olisa

Technical User
Dec 10, 2009
30
DE
Hi,
I have IP412 with dual PRI card. We use one line only and have set it to network. It has been working well for one year then suddenly it went down and alarms went red. The TSP can and did something on his line and modem and lights went back to green. But calls cannot come in or go out. He says the problem is my PBX and my line is fine but channels are blocked. Have tried changing to use the second line but still the same.

Below is a trace from Monitor.

kindly advice? Is fault really mine or the TSP? What does Falc mean? and crc=1 ?


77660229mS ISDNL1Evt: v=1 peb=1,F2 F1
77660235mS ISDNL1Evt: v=1 peb=1,F1 F2
77660760mS H323Evt: Recv: RegistrationRequest c0a82818; Endpoints registered: 30; Endpoints in registration: 0
77661731mS ISDNL1Evt: v=1 peb=1,F2 F1
77661766mS ISDNL1Evt: v=1 peb=1,F1 F2
77664127mS ISDNL1Evt: v=1 peb=1,F2 F1
77664133mS ISDNL1Evt: v=1 peb=1,F1 F2
77664926mS ISDNL1Evt: v=1 peb=1,F2 F1
77664962mS ISDNL1Evt: v=1 peb=1,F1 F2
77665724mS ISDNL1Evt: v=1 peb=1,F2 F1
77665760mS ISDNL1Evt: v=1 peb=1,F1 F2
77666096mS ISDNL1Evt: v=1 peb=1,F2 F1
77666096mS ISDNL1Evt: v=1 peb=1,F1 F2
77666523mS ISDNL1Evt: v=1 peb=1,F2 F1
77666529mS ISDNL1Evt: v=1 peb=1,F1 F2
77669127mS ISDNL1Evt: v=1 peb=1,F3 F1
77669131mS PRN: Slot A, Falc 1: LOCK RAI crc=1 set=0 FMR1=4e FMR2=83
77669132mS ISDNL1Evt: v=1 peb=1,F1 F3
77669132mS PRN: Clock 1: excursion 6911
77672793mS ISDNL1Evt: v=1 peb=1,F2 F1
77672829mS ISDNL1Evt: v=1 peb=1,F1 F2
77673495mS ISDNL1Evt: v=1 peb=1,F2 F1
77673502mS ISDNL1Evt: v=1 peb=1,F1 F2
77674773mS ISDNL1Evt: v=1 peb=1,F2 F1
77674773mS ISDNL1Evt: v=1 peb=1,F1 F2
77678241mS PRN: Destroyed MH 18634ec parent unknown
77678277mS ISDNL1Evt: v=1 peb=1,F2 F1
77678312mS ISDNL1Evt: v=1 peb=1,F1 F2
77678979mS ISDNL1Evt: v=1 peb=1,F2 F1
77679014mS ISDNL1Evt: v=1 peb=1,F1 F2
77679584mS ISDNL1Evt: v=1 peb=1,F3 F1
77679589mS PRN: Slot A, Falc 1: LOCK RAI crc=1 set=0 FMR1=4e FMR2=83
77679589mS ISDNL1Evt: v=1 peb=1,F1 F3
77679589mS PRN: Clock 1: excursion 6912
77679777mS ISDNL1Evt: v=1 peb=1,F2 F1
77679813mS ISDNL1Evt: v=1 peb=1,F1 F2
 
PRI Line 1 (peb=1) has gone from the F1 state (normal Operational state) to the F2 state (Fault condition 1 state - receiving RAI or receiving CRC errors). Back and forth.
 
Thank you for your quick response.
So the problem is CRC errors? What is causing them? Should I uncheck the check CRC errors option? Will this make it work even with errors? Pls advice.
 
This depends on the Provider.

Some send a CRC (cyclic redundancy check)and some don't, if they do send it then you need to turn it on if they don't turn it off.

A CRC-enabled device calculates a short, fixed-length binary sequence, known as the CRC code or just CRC, for each block of data and sends or stores them both together. When a block is read or received the device repeats the calculation; if the new CRC does not match the one calculated earlier, then the block contains a data error and the device may take corrective action such as rereading or requesting the block be sent again

We always let the Provider turn on "CRC", here in the Netherlands we have the best experience if it's turned on.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________
 
Thanks Bas1234. Am in Somalia, and not sure what the provider has on his end but will try uncheck and see. But the device has been working well for over a year now till suddenly this came up. Could the STP have changed something on their end that they are not admitting? Thanks for your insight.
 
thank you all for your assistance and support. The problem is solved. It was on the TSP side. He had badly crimpped the cables coming to my side. He corrected it and am now fine. Asante!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top