MERLIN LEGEND Communications System Release 6.1 | Issue 1 |
Network Reference | August 1998 |
6 Troubleshooting |
|
No Message Waiting Light Update | Page |
|
|
■If the switch identifiers are correct and the problem persists, do one of the following:
—If the call is being routed over any tandem PRI facilities, go to Possible Cause 2.
—If the call is being routed over tandem tie trunks, the call information sent to the centralized VMS/AA for both inside calls and outside calls indicates an outside calls.
Possible Cause 2: System programming is not correct or tandem tie trunks are used to route the call.
What to Do: The action you takes depends on how frequently the problem occurs:
■If the problem occurs for all calls, verify that the outgoing VMI calling group is programmed as Integrated VMI.
■If the problem occurs only on tandem
■If the problem occurs only on tandem PRI trunks, Verify that switch identifier is not zero. See procedure earlier in this chapter.
■If the problem occurs only at certain times, check the time zone for Night Service and make adjustments to VMS recordings as needed.
No Message Waiting Light Update | 6 | |
|
|
|
The following are likely circumstances in which Message Waiting lights are not updated:
■The error log indicates that Message Waiting light update has been delayed more than one minute. Errors are 0C04 (Message Waiting light facility timeout) and 0C05 (Message Waiting light delivery delay).
■A selected tandem facility between the caller or called VMI extension is out of service. Check the error logs and if the error indicates an out of service condition, call the Lucent Technologies Helpline at 1 800
■No
■A technician may be performing maintenance on local tandem trunks or
■A power failure may have occurred at the destination system or at another networked system whose tandem trunks are included in routes for the call.