|
|
Joined: Jul 2009
Posts: 204
Member
|
OP
Member
Joined: Jul 2009
Posts: 204 |
Inter-tel 5000 system. We have a PRI card error Alarm 114. Phone system is still working normal however. Very odd.
Is there a way I can reset this so it stops beeping until we get someone out here to look at it?
|
|
|
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: Jun 2010
Posts: 797
Moderator-Inter-Tel
|
|
Moderator-Inter-Tel
Joined: Jun 2010
Posts: 797 |
Default feature code to clear the alarm is 9850. May have to hit the infinity key first and then 9850. Do it from the phone with the alarm as they have the admin features. Also, there should be a soft key on an Executive or 8560 endpoint that says CLEAR ALARM.
|
|
|
|
|
Joined: Jul 2009
Posts: 204
Member
|
|
OP
Member
Joined: Jul 2009
Posts: 204 |
I'm out of the office now but headed back now. I will take a look at that. Strange thing is the alarm was cleared on the phone earlier. The constant steady beep has not gone away. I'm wondering if it isn't the battery backup. I'm offsite and have obtained all info from the front desk staff member. Possible she is just confused.
Here is what i found in the error log:
-08:207- 13:03 05-06 M5040 WRN HW CP [1.0.0] (T1/E1/PRI Module): Ignored (DB Type = PRI Board)
-08:208- 13:03 05-06 *** PRI Card 1 Passed Self-Test
-08:209- 13:03 05-06 *** PRI Card 1 state changed from Dead to Self-Test
-08:210- 13:03 05-06 *** PRI Card [1.1.0] clock mode: Slave Not Providing Sync
-08:211- 13:03 05-06 *** PRI Card 1 state changed from Self-Test to Powerup-Wait
-08:212- 13:03 05-06 M2002 INF HW CP [1.0.0]: On-Line From PRI Board
-08:213- 13:03 05-06 M2002 INF HW CP [1.1.0]: On-Line From PRI Port T1/E1/PRI application version: 2.1.4
-08:214- 13:03 05-06 M3008 INF EG SS [1.0.0]: Print String Response From PRI Board : T1/E1/PRI application version: 2.1.4
T1/E1/PRI application build date/time: Fri Sep 29 2006 12:53:58 ˜-08:215- 13:03 05-06 M3008 INF EG SS [1.0.0]: Print String Response From PRI Board : T1/E1/PRI application build date/time: Fri Sep 29 2006 12:53:58
-08:216- 13:03 05-06 M8000 SVR HW CP Initial Trouble Condition Detected on PRI Board [1.0.0]
-08:217- 13:03 05-06 M8001 SVR HW CP PRI Board Problem: Receiving Yellow Alarm
-08:218- 13:03 05-06 M5086 WRN HW CP Hourly Threshold For Bipolar Violation Errors Exceeded on PRI Board [1.0.0]
-08:219- 13:03 05-06 M5086 WRN HW CP Hourly Threshold For Out-of-Frame Adjustment Errors Exceeded on PRI Board [1.0.0]
-08:220- 13:03 05-06 M5086 WRN HW CP Daily Threshold For Out-of-Frame Adjustment Errors Exceeded on PRI Board [1.0.0]
-08:221- 13:03 05-06 M2002 INF HW CP [1.1.1]: On-Line From B-Channel Trunk Device
-08:222- 13:03 05-06 M2002 INF HW CP [1.1.2]: On-Line From B-Channel Trunk Device
|
|
|
|
|
Joined: May 2009
Posts: 1,198
Member
|
|
Member
Joined: May 2009
Posts: 1,198 |
There are no audible alarms generated by the PBX; but a bad UPS sounds plausible.
Could have been a power issue that caused the PRI to hiccup, and the UPS didn’t recover.
|
|
|
|
|
Joined: Sep 2005
Posts: 840
Member
|
|
Member
Joined: Sep 2005
Posts: 840 |
Could also be that the termination device for the PRI is plugged into a bad UPS.
|
|
|
|
Forums84
Topics93,970
Posts637,430
Members49,704
| |
Most Online5,661
May 23rd, 2018
|
|
|
|
