I have an Axxess 9.002 system with a PRI. I have been receiving complaints that callers can either get into the system and are being dropped or call and get dead air. I looked at the error logs and noticed a lot of PRI errors. I then changed the line build out from 7.5 to 0. For the next week all was fine then the errors reoccured.

Here is part of the error log:

-01:783- 13:36 04-19 *** PRI Card 6 state changed from Error to Working
-01:784- 13:36 04-19 *** Reason: STATE CHANGE - PORT [6.1.0]
-01:785- 13:36 04-19 M8002 SVR HW CP Red Alarm Condition Cleared on PRI Board [6.0.0]
-01:786- 13:36 04-19 A002 ALARM Network Alarm Automatically Cleared
-01:787- 14:35 04-19 M5086 WRN HW CP Daily Threshold For Out-of-Frame Adjustment Errors Exceeded on PRI Board [6.0.0]
-01:788- 14:36 04-19 M5086 WRN HW CP Hourly Threshold For Out-of-Frame Adjustment Errors Exceeded on PRI Board [6.0.0]
-01:789- 14:38 04-19 *** PRI Card 6 state changed from Working to Init Critical Error
-01:790- 14:38 04-19 *** Reason: STATE CHANGE - PORT [6.1.0]
-01:791- 14:38 04-19 *** PRI Card [6.1.0] clock mode: Slave Not Providing Sync
-01:792- 14:38 04-19 M8000 SVR HW CP Initial Trouble Condition Detected on PRI Board [6.0.0]
-01:793- 14:38 04-19 M8001 SVR HW CP PRI Board Problem: Receiver Loss of Signal from Network
-01:794- 14:38 04-19 M8000 SVR HW CP Initial Trouble Condition Detected on PRI Board [6.0.0]
-01:795- 14:38 04-19 M8001 SVR HW CP PRI Board Problem: T1 Signal Out-of-Frame
-01:796- 14:38 04-19 M8000 SVR HW CP Red Alarm Condition Detected on PRI Board [6.0.0]
-01:797- 14:38 04-19 M8001 SVR HW CP PRI Board Problem: Receiver Loss of Signal from Network
-01:798- 14:38 04-19 M2002 INF HW CP [6.1.1]: Off-Line From B-Channel Trunk Device
-01:799- 14:38 04-19 M2002 INF HW CP [6.1.2]: Off-Line From B-Channel Trunk Device
-01:800- 14:38 04-19 M2002 INF HW CP [6.1.3]: Off-Line From B-Channel Trunk Device
-01:801- 14:38 04-19 M2002 INF HW CP [6.1.4]: Off-Line From B-Channel Trunk Device
-01:802- 14:38 04-19 M2002 INF HW CP [6.1.5]: Off-Line From B-Channel Trunk Device
-01:803- 14:38 04-19 M2002 INF HW CP [6.1.6]: Off-Line From B-Channel Trunk Device
-01:804- 14:38 04-19 M2002 INF HW CP [6.1.7]: Off-Line From B-Channel Trunk Device
-01:805- 14:38 04-19 M2002 INF HW CP [6.1.8]: Off-Line From B-Channel Trunk Device
-01:806- 14:38 04-19 M2002 INF HW CP [6.1.9]: Off-Line From B-Channel Trunk Device
-01:807- 14:38 04-19 M2002 INF HW CP [6.1.10]: Off-Line From B-Channel Trunk Device
-01:808- 14:38 04-19 M2002 INF HW CP [6.1.11]: Off-Line From B-Channel Trunk Device
-01:809- 14:38 04-19 M2002 INF HW CP [6.1.12]: Off-Line From B-Channel Trunk Device
-01:810- 14:38 04-19 M2002 INF HW CP [6.1.13]: Off-Line From B-Channel Trunk Device
-01:811- 14:38 04-19 M2002 INF HW CP [6.1.14]: Off-Line From B-Channel Trunk Device
-01:812- 14:38 04-19 M2002 INF HW CP [6.1.15]: Off-Line From B-Channel Trunk Device
-01:813- 14:38 04-19 M2002 INF HW CP [6.1.16]: Off-Line From B-Channel Trunk Device
-01:814- 14:38 04-19 M2002 INF HW CP [6.1.17]: Off-Line From B-Channel Trunk Device
-01:815- 14:38 04-19 M2002 INF HW CP [6.1.18]: Off-Line From B-Channel Trunk Device
-01:816- 14:38 04-19 M2002 INF HW CP [6.1.19]: Off-Line From B-Channel Trunk Device
-01:817- 14:38 04-19 M2002 INF HW CP [6.1.20]: Off-Line From B-Channel Trunk Device
-01:818- 14:38 04-19 M2002 INF HW CP [6.1.21]: Off-Line From B-Channel Trunk Device
-01:819- 14:38 04-19 M2002 INF HW CP [6.1.22]: Off-Line From B-Channel Trunk Device
-01:820- 14:38 04-19 M2002 INF HW CP [6.1.23]: Off-Line From B-Channel Trunk Device
-01:821- 14:38 04-19 M8003 SVR HW CP All Calls on PRI Board [6.0.0] Have Been Dropped
-01:822- 14:38 04-19 A114 ALARM PRI Board 6 In Red Alarm
-01:823- 14:38 04-19 *** PRI Card 6 state changed from Init Critical Error to Critical Error
-01:824- 14:38 04-19 *** Reason: STATE CHANGE - PORT [6.1.0]
-01:825- 14:38 04-19 M8000 SVR HW CP Red Alarm Condition Detected on PRI Board [6.0.0]
-01:826- 14:38 04-19 M8001 SVR HW CP PRI Board Problem: T1 Signal Out-of-Frame
-01:827- 14:38 04-19 M5086 WRN HW CP Hourly Threshold For Controlled Slips Errors Exceeded on PRI Board [6.0.0]
-01:828- 14:38 04-19 M8000 SVR HW CP Initial Trouble Condition Detected on PRI Board [6.0.0]
-01:829- 14:38 04-19 M8001 SVR HW CP PRI Board Problem: Receiving Blue Alarm
-01:830- 14:38 04-19 M8000 SVR HW CP Red Alarm Condition Detected on PRI Board [6.0.0]
-01:831- 14:38 04-19 M8001 SVR HW CP PRI Board Problem: Receiving Blue Alarm
-01:832- 14:38 04-19 *** PRI Card 6 state changed from Critical Error to Error
-01:833- 14:38 04-19 *** Reason: STATE CHANGE - PORT [6.1.0]
-01:834- 14:38 04-19 *** PRI Card [6.1.0] clock mode: Slave Providing Sync
-01:835- 14:38 04-19 *** T1 [6.0.0] process_reference_clock_handshake - T1_REFERENCE_CLOCK_HANDSHAKE_DATA_ATTEMPTING
-01:836- 14:38 04-19 *** Reason: ATTEMPTING TO PROVIDE CLOCK SYNC - PORT [6.1.0]
-01:837- 14:38 04-19 *** T1 [6.0.0] process_reference_clock_handshake - T1_REFERENCE_CLOCK_HANDSHAKE_DATA_SUPPLYING
-01:838- 14:38 04-19 *** Reason: PROVIDING CLOCK SYNC - PORT [6.1.0]
-01:839- 14:38 04-19 M8000 SVR HW CP Initial Trouble Condition Detected on PRI Board [6.0.0]
-01:840- 14:38 04-19 M8001 SVR HW CP PRI Board Problem: Receiving Yellow Alarm
-01:841- 14:38 04-19 M8000 SVR HW CP Red Alarm Condition Detected on PRI Board [6.0.0]
-01:842- 14:38 04-19 M8001 SVR HW CP PRI Board Problem: Receiving Yellow Alarm
-01:843- 14:39 04-19 M2002 INF HW CP [6.1.1]: On-Line From B-Channel Trunk Device

Thank you very much :scratch:

What's the question?

What would cause this?

Your red alarm is loss of signal incoming Yellow is the far end telling you they lost signal, lots of out of frames too. Looks like you need to report this to your service provider.

Ok thanks I will

I did call the carrier and they stated that they tested the circuit and found no errors within the past 48 hours. The errors did appear in the logs for that same day, though. Could a bad T1 card be causing this?

Could be, but sounds like a circuit problem to me. Is this from a local LEC to your switch? If not is it a Long distance carrier? If you are seeing Red and Yellow alarms and they say they seen nothing I'd like to know what they're looking at. Depending on the carrier some may not show alarm history, but those alarms should show up as some oof's. If you don't mind who is the carrier? PM if you don't want to post.

justbill is correct , with the type of errors you are logging at the very least the CO should see oof errors . Ask them for a copy of the performance monitor they setup .

I am fine with posting the carrier. I haven't had good experience with them in the past anyways.
I wouldn't put it past them to goof the test up, anyways. The carrier is Bellsouth and it is local and long distance.

OK so that means they probably have no monitoring points on the T-1 so they are looking at the history in their switch. They should still see something. Do as OBTW suggest, ask for a performance monitor to be put on the circuit and when you see errors call them, especially if you see any alarms. If they are just taking it down to test and there are no errors at the time of test they won't see anything. They need to monitor the T-1 live.

Ok. Thank You. I will ask them. I appreciate all of your help.

Thanks for being our guest star Bill.



We don't get to see NEAR enough of you here in the Inter-Tel Forum! :thumb:

Thanks Trace. As you can see I didn't even try to answer any system questions. That's what you smart MOD's are for.

I liked the explanation justbill gave :toast:

I know this is an old post, but could someone tell me how to get these error logs. I have an Axxess 8.1 system and are having the same sort of issues.

You need to connect directly to the RS232 port on your T1 card.

The error logs the OP is referring to comes from downloading them from the Database Programming.

The easiest way to see that information is to enable message print in DB Studio and use Diagnostics Monitor

Also, setting the LBO to zero disables the onboard csu. Best to set it to auto and then see what the system determines is the best LBO, then you can set it to that if you so desire.

Hi ggirl4478,

I had a similar problem like yours. It turns out that the problem was the T1 circuit. At first, my ISP also told me that there is no problem with the circuit. A day later, my ISP found out that there was a problem at their C/O.

Did you ever find a solution to this? It sounds identical to a problem we are having with our PRI's and dropped calls. What we have had to do to solve this would amaze you.

What did you do that amaze you? Just curious.

thanks.

I do many things that amaze me. I'm just that sort of person!
For our PRI problem, however, we have been going around and around with this with our carrier since the PRI's went in the end of January, this year.
We have had explanations ranging from lightening strikes, to bad pairs, to bad cards, boxes, wiring, fried circuits.............you name it. I don't think there is a part of this PRI that has not been replaced to date or an excuse I haven't heard.
At this stage, we are running reports like crazy for our carrier while they are supposedly checking the lines from their end. We run SMDR's all day, have people track dropped calls and report them, and have had our vendor out here so often, he's practically a fixture in our office.
In the process, of four new servers (a CPU, VPU, CCS, and Gateway) our VPU, CCS, and CPU have all blown up within the first eight months.
What attracted me to ggirl's problem was when she said she called her carrier and they reported no errors found.
Boy! Am I familiar with that one! Our carrier was telling us we had no problem with our PRI's while upstairs, one of the cards was totally dead. Then I get a CBFM report.
Mostly what I've done that has amazed me is that in the course of all of this, I have yet to go to my carrier's CO, fall on the floor of the main office lobby, and have a tantrum that any three year old would stand up and applaud.