The last time the error that caused a particular alarm occurred.

How many times the alarm has occurred since the system restarted or you last cleared the alarm.

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

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)

If the trunk is not administered to be out of service but goes down, the following is displayed:

Trunk out of service.

When a T1/PRI trunk reports a red alarm, System Status displays Red Alarm. A red alarm indicates lost synchronization.

When a T1/PRI trunk reports a blue alarm, System Status displays Blue Alarm. A blue alarm indicates a signal failure.

When a T1/PRI trunk reports a yellow alarm, System Status displays Yellow Alarm. A yellow alarm indicates a transmission problem.

This alarm indicates loss of signal from a trunk.

For analog loop start trunks set to ICLID, this alarm indicates that the system did not receive any CLI.

This alarm indicates that the system did not detect loop current when trying to seize the trunk.

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