Contents | Index | Previous | Next

Trunk Error Thresholds

Resident programs monitor all calls and note apparent errors. The errors are accumulated and, if they occur consistently (exceed a threshold) on any trunk, a diagnostic message which identifies the trunk is output to the TTY or printer. The trunk should be suspected of trouble and a manual test should be performed on the trunk.

A record is kept in memory for each threshold violation error message. At any time, all trunks which have been identified by such a message may be listed by entering the command LOVF for any trunk route. Once an identifying message has been printed, it will not be repeated for that trunk until the RSET command is entered for that trunk or an initialization has occurred.

Potentially, a trunk may fail by not detecting incoming calls. The Meridian 1/Meridian SL-1 threshold mechanism cannot be used to detect such failures so the Meridian 1/Meridian SL-1 maintains for each trunk a count of the number of days since an incoming call was received on each trunk.

Thus, customer reports that indicate incoming calls are not being processed can initiate a check for the trunk which has been without an incoming call for the longest interval via the LMAX command. This trunk should be tested first.

It is possible to determine for each trunk the number of days since an incoming call was processed via the LDIC command. Subsequent trunk tests should be performed on those trunks showing the highest counts until the trouble is located.