|
|
Joined: Aug 2005
Posts: 49
Member
|
Member
Joined: Aug 2005
Posts: 49 |
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:
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: May 2002
Posts: 17,742 Likes: 34
Member
|
Member
Joined: May 2002
Posts: 17,742 Likes: 34 |
Retired phone dude
|
|
|
|
Joined: Aug 2005
Posts: 49
Member
|
Member
Joined: Aug 2005
Posts: 49 |
|
|
|
|
Joined: May 2002
Posts: 17,742 Likes: 34
Member
|
Member
Joined: May 2002
Posts: 17,742 Likes: 34 |
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.
Retired phone dude
|
|
|
|
Joined: Aug 2005
Posts: 49
Member
|
Member
Joined: Aug 2005
Posts: 49 |
|
|
|
|
Joined: Aug 2005
Posts: 49
Member
|
Member
Joined: Aug 2005
Posts: 49 |
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?
|
|
|
|
Joined: May 2002
Posts: 17,742 Likes: 34
Member
|
Member
Joined: May 2002
Posts: 17,742 Likes: 34 |
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.
Retired phone dude
|
|
|
|
Joined: Sep 2005
Posts: 2,049
Member
|
Member
Joined: Sep 2005
Posts: 2,049 |
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 . 
Let It Be , I live in a Yellow Submarine . SCCE
|
|
|
|
Joined: Aug 2005
Posts: 49
Member
|
Member
Joined: Aug 2005
Posts: 49 |
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.
|
|
|
|
Joined: May 2002
Posts: 17,742 Likes: 34
Member
|
Member
Joined: May 2002
Posts: 17,742 Likes: 34 |
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.
Retired phone dude
|
|
|
Forums84
Topics94,513
Posts639,938
Members49,844
|
Most Online5,661 May 23rd, 2018
|
|
1 members (justbill),
320
guests, and
46
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|