|
|
Joined: May 2005
Posts: 90
Member
|
Member
Joined: May 2005
Posts: 90 |
We're having issues with our InterTel Axxess 5.349 System...
Here's a portion of the error report from today... is this looking like a bad PRI PAL chip or possibly a bad T1 card? I really have no idea what would cause this. The phone system has rebooted itself 4 times today. Help!!!
-01:015- 11:46 11-17 M3000 INF EG CP MAJOR RESET: Power-Up -01:016- 11:46 11-17 M3007 INF EG CP Call Processing Version: 5.349 -01:017- 11:46 11-17 A000 ALARM Alarm Automatically Cleared -01:018- 11:46 11-17 M2028 INF HW CP [8.0.0]: Initializing Board's Companding Mode To Mu-Law.
-01:036- 11:46 11-17 *** PRI Card 5 Passed Self-Test -01:037- 11:46 11-17 *** PRI Card 5 does not have an Optional Daughter Card installed -01:038- 11:46 11-17 *** PRI Card [5.1.0] clock mode: Slave Not Providing Sync -01:125- 11:46 11-17 M8000 SVR HW CP Initial Trouble Condition Detected on PRI Board [5.0.0] -01:126- 11:46 11-17 M8001 SVR HW CP PRI Board Problem: Receiving Yellow Alarm -01:127- 11:46 11-17 M5086 WRN HW CP Hourly Threshold For Out-of-Frame Adjustment Errors Exceeded on PRI Board [5.0.0] -01:128- 11:46 11-17 M2007 INF HW CP [1.1.1]: Power-Up From DSS 1 (Version = 0) -01:129- 11:46 11-17 M8000 SVR HW CP Red Alarm Condition Detected on PRI Board [5.0.0] -01:130- 11:46 11-17 M8001 SVR HW CP PRI Board Problem: Receiving Yellow Alarm -01:131- 11:46 11-17 M5086 WRN HW CP Daily Threshold For Out-of-Frame Adjustment Errors Exceeded on PRI Board [5.0.0] -01:132- 11:46 11-17 M2005 INF HW CP [1.1.1]: Off-Line From DSS 1 -01:133- 11:46 11-17 M2007 INF HW CP [1.1.1]: Power-Up From DSS 1 (Version = 0) -01:134- 11:46 11-17 *** PRI Card [5.1.0] clock mode: Slave Providing Sync -01:135- 11:46 11-17 A114 ALARM PRI Board 5 In Red Alarm
-01:143- 11:46 11-17 M8002 SVR HW CP Red Alarm Condition Cleared on PRI Board [5.0.0] -01:144- 11:46 11-17 A002 ALARM Network Alarm Automatically Cleared
-01:015- 12:23 11-17 M3000 INF EG CP MAJOR RESET: Power-Up -01:016- 12:23 11-17 M3007 INF EG CP Call Processing Version: 5.349 -01:017- 12:23 11-17 A000 ALARM Alarm Automatically Cleared --01:036- 12:23 11-17 *** PRI Card 5 Passed Self-Test -01:037- 12:23 11-17 *** PRI Card 5 does not have an Optional Daughter Card installed -01:038- 12:23 11-17 *** PRI Card [5.1.0] clock mode: Slave Not Providing Sync
Trouble Condition Detected on PRI Board [5.0.0] -01:112- 12:23 11-17 M8001 SVR HW CP PRI Board Problem: T1 Signal Out-of-Frame -01:113- 12:23 11-17 M5086 WRN HW CP Daily Threshold For Out-of-Frame Adjustment Errors Exceeded on PRI Board [5.0.0] -01:126- 12:23 11-17 M8000 SVR HW CP Initial Trouble Condition Detected on PRI Board [5.0.0] -01:127- 12:23 11-17 M8001 SVR HW CP PRI Board Problem: Receiving Yellow Alarm -01:128- 12:23 11-17 M5086 WRN HW CP Hourly Threshold For Out-of-Frame Adjustment Errors Exceeded on PRI Board [5.0.0] -01:129- 12:23 11-17 M8000 SVR HW CP Red Alarm Condition Detected on PRI Board [5.0.0] -01:130- 12:23 11-17 M8001 SVR HW CP PRI Board Problem: Receiving Yellow Alarm -01:131- 12:23 11-17 M2007 INF HW CP [1.1.1]: Power-Up From DSS 1 (Version = 0) -01:132- 12:23 11-17 M2005 INF HW CP [1.1.1]: Off-Line From DSS 1 -01:133- 12:23 11-17 M2007 INF HW CP [1.1.1]: Power-Up From DSS 1 (Version = 0) -01:134- 12:23 11-17 *** PRI Card [5.1.0] clock mode: Slave Providing Sync -01:135- 12:23 11-17 A114 ALARM PRI Board 5 In Red Alarm --01:143- 12:23 11-17 M8002 SVR HW CP Red Alarm Condition Cleared on PRI Board [5.0.0] -01:144- 12:23 11-17 A002 ALARM Network Alarm Automatically Cleared
|
|
|
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: Nov 2008
Posts: 4
Member
|
Member
Joined: Nov 2008
Posts: 4 |
first off - the t-1 cards are fairly reliable - either the are working good or just plain shot usually - is this a t1c or a t1/e1 card and what kind of circuit is installed ? can you hook up to the rs232 port with an adapter and look directly into real time errors ? also what is the cpu - if it is 64 /128 than you have to have a clock card on the backplane.
|
|
|
|
Joined: Nov 2006
Posts: 241
Member
|
Member
Joined: Nov 2006
Posts: 241 |
Every time the system resets you're going to get the errors above (plus the stuff you cut out). Not having a clock card won't cause resets, just a cruddy span if you can get it to come up at all.
If the system is resetting this often there is a bigger issue looming. Power source, power supply and CPU are suspects to me. You could look at the reset log for clues as well.
60% of the time it works every time
|
|
|
|
Joined: May 2005
Posts: 90
Member
|
Member
Joined: May 2005
Posts: 90 |
Thanks for the replies. At this point I'm fairly certain that the issue was caused by network issues on the service provider's end. In this case, Cbeyond. Here was their response (2 days later)... "Dear Customer: We saw evidence that your service was bouncing especially on the 17th of November. You appear to be running clean now. To ensure that Cbeyond doesn't have an issue, I have reset/reloaded and cleared buffers in your router. Your phones should be stable now. If they are still having issues, please check with your phone vendor to ensure that there are no failures on that side. Thank you Cbeyond"
I suspected as much... but since Internet access was stable, I couldn't be sure. We'd also just had some database corruption issues on the PBX just a week prior... so, it seemed to me at the time that there may have been a larger problem. Now it seems like it was just a strange coincidence. The phone system has been stable for the last few days, so I think we're in the clear.
Thanks again for the responses.
|
|
|
|
Joined: Nov 2006
Posts: 241
Member
|
Member
Joined: Nov 2006
Posts: 241 |
But the evidence of the "service bouncing" was because the Axxess reset. Of course they saw errors!
Cross your fingers on that corruption issue. What did you do to correct it?
60% of the time it works every time
|
|
|
|
Joined: May 2005
Posts: 90
Member
|
Member
Joined: May 2005
Posts: 90 |
We were getting weekly and then daily System Alarm #104 notifications. A few weeks later the phones went blank and the software showed no database. I restored the database from backup and all was well... until the random system resets on Monday.
I interpreted Cbeyond's message differentlty, but I see your point.
When Cbeyond did their router thing, I saw the same erors in the log. So, I do think it's them doing this somehow...
Here's what it did tonight just a few minutes before their tech emailed me... mind you, there were no errors on the 18th. On the 19th they reset the router and then I start to see the same type of errors... so, either their router is screwed up or they're sending some funky stuff through it.
01:146- 20:28 11-19 *** PRI Card [5.1.0] clock mode: Slave Not Providing Sync -01:147- 20:28 11-19 M8000 SVR HW CP Initial Trouble Condition Detected on PRI Board [5.0.0] -01:148- 20:28 11-19 M8001 SVR HW CP PRI Board Problem: Receiver Loss of Signal from Network -01:149- 20:28 11-19 M8000 SVR HW CP Initial Trouble Condition Detected on PRI Board [5.0.0] -01:150- 20:28 11-19 M8001 SVR HW CP PRI Board Problem: T1 Signal Out-of-Frame -01:151- 20:28 11-19 M8000 SVR HW CP Red Alarm Condition Detected on PRI Board [5.0.0] -01:152- 20:28 11-19 M8001 SVR HW CP PRI Board Problem: Receiver Loss of Signal from Network -01:153- 20:28 11-19 M2002 INF HW CP [5.1.1]: Off-Line From B-Channel Trunk Device -01:154- 20:28 11-19 M2002 INF HW CP [5.1.2]: Off-Line From B-Channel Trunk Device -01:155- 20:28 11-19 M2002 INF HW CP [5.1.3]: Off-Line From B-Channel Trunk Device -01:156- 20:28 11-19 M2002 INF HW CP [5.1.4]: Off-Line From B-Channel Trunk Device -01:157- 20:28 11-19 M2002 INF HW CP [5.1.5]: Off-Line From B-Channel Trunk Device -01:158- 20:28 11-19 M2002 INF HW CP [5.1.6]: Off-Line From B-Channel Trunk Device -01:159- 20:28 11-19 M2002 INF HW CP [5.1.7]: Off-Line From B-Channel Trunk Device -01:160- 20:28 11-19 M8003 SVR HW CP All Calls on PRI Board [5.0.0] Have Been Dropped -01:161- 20:28 11-19 A114 ALARM PRI Board 5 In Red Alarm -01:162- 20:28 11-19 M8000 SVR HW CP Red Alarm Condition Detected on PRI Board [5.0.0] -01:163- 20:28 11-19 M8001 SVR HW CP PRI Board Problem: T1 Signal Out-of-Frame -01:164- 20:28 11-19 M5086 WRN HW CP Hourly Threshold For Controlled Slips Errors Exceeded on PRI Board [5.0.0] -01:165- 20:29 11-19 M5086 WRN HW CP Daily Threshold For Controlled Slips Errors Exceeded on PRI Board [5.0.0] -01:166- 20:30 11-19 *** PRI Card [5.1.0] clock mode: Slave Providing Sync -01:167- 20:30 11-19 M8002 SVR HW CP Red Alarm Condition Cleared on PRI Board [5.0.0] -01:168- 20:30 11-19 A002 ALARM Network Alarm Automatically Cleared -01:169- 20:30 11-19 M2002 INF HW CP [5.1.1]: On-Line From B-Channel Trunk Device -01:170- 20:30 11-19 M2002 INF HW CP [5.1.2]: On-Line From B-Channel Trunk Device -01:171- 20:30 11-19 M2002 INF HW CP [5.1.3]: On-Line From B-Channel Trunk Device -01:172- 20:30 11-19 M2002 INF HW CP [5.1.4]: On-Line From B-Channel Trunk Device -01:173- 20:30 11-19 M2002 INF HW CP [5.1.5]: On-Line From B-Channel Trunk Device -01:174- 20:30 11-19 M2002 INF HW CP [5.1.6]: On-Line From B-Channel Trunk Device -01:175- 20:30 11-19 M2002 INF HW CP [5.1.7]: On-Line From B-Channel Trunk Device -01:176- 23:08 11-19 M2004 INF HW CP On-Line From ASAI Device On Logical Port 0x03 -01:177- 23:09 11-19 M3001 INF EG CP System History Of Node 1 Has Been Frozen From Node 1 -01:178- 23:11 11-19 M3009 INF EG CP Retrieving System History Information
|
|
|
Forums84
Topics94,520
Posts639,990
Members49,850
|
Most Online5,661 May 23rd, 2018
|
|
2 members (justbill, C5Z),
230
guests, and
44
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|