Alarms

Last Updated : Nov 12, 2020 |
Prolog information
Metadata
Keywords:
Path: TrunksLinesLineAlarms
Information Displayed
Description
Last Date of Error
The last time the error that caused a particular alarm occurred.
Occurrences
How many times the alarm has occurred since the system restarted or you last cleared the alarm.

Error Description

The table below details a description of the error that caused the alarm
Error
Description
Insufficient DID Digits
A user can administer routes based on DID digits by using the MSN routing form. On this form, the user administers how many digits are expected (the Presentation Digits field). If a call is received and the number of digits received do not match the number in the Presentation Digits field, the following is displayed:
  • There was a mismatch in the number of DID digits
  • Expected number of digits: XX
  • Digits Received: YYYYY
Incoming Call on Outgoing Trunk
On T1/PRI and analog lines, the direction for each channel can be administered to be incoming, outgoing or both. If the channel is outgoing and an incoming call arrives on the channel, the following is displayed:
  • An incoming call arrived on the channel configured for Outgoing calls only.
  • Channel Number: XX (for digital lines)
  • Port Number: XX (for analog lines)
Trunk Went Out of Service
If the trunk is not administered to be out of service but goes down, the following is displayed:
Trunk out of service.
Red Alarm Active on Trunk
When a T1/PRI trunk reports a red alarm, System Status displays Red Alarm. A red alarm indicates lost synchronization.
Blue Alarm Active on Trunk
When a T1/PRI trunk reports a blue alarm, System Status displays Blue Alarm. A blue alarm indicates a signal failure.
Yellow Alarm Active on Trunk
When a T1/PRI trunk reports a yellow alarm, System Status displays Yellow Alarm. A yellow alarm indicates a transmission problem.
Loss of Signal on Trunk
This alarm indicates loss of signal from a trunk.
Caller ID not received
For analog loop start trunks set to ICLID, this alarm indicates that the system did not receive any CLI.
Seize Failure
This alarm indicates that the system did not detect loop current when trying to seize the trunk.
Response Failure
The system generates this alarm when it sends a TCP Sync to the remote end of an H.323 trunk and does not receive an acknowledgement and when it sends an INVITE over a SIP trunk which times out.
  • No response to IP trunk call request.
  • IP Trunk Line Number: xxx
  • Remote end IP address: yyy.yyy.yyy.yyy

Buttons

The following buttons can appear on this screen:
Buttons
Description
Clear Alarm History
Clear the historical alarms displayed.
Clear All
Clears all listed historical alarms that are no longer active. Note that any alarms still active (red) remain but with the occurrences count reset to 1.
Print...
Prints all information available in the current screen (including any information currently scrolled off).
Save As...
Saves the information shown on the screen to a text file (TXT or CSV). You can only save trace screens as CSV text files.
Related links
Alarms