Lucent Technologies 555-661-150 manual Hqhudo

MERLIN LEGEND Communications System Release 6.1	Issue 1
Network Reference 555-661-150	August 1998
6 Troubleshooting
No Message Waiting Light Update	Page 6-31

■Some of the problems described in this section can occur when a system manager makes a change in a networked system’s local dial plan, non-local dial plan, switch identifier, or DS1 Switch Type setting. Ensure that your private network system forms are kept up to date and that changes are cleared with the coordinating system manager.

NOTE:

If there is an alarm on the CPU board and Message Waiting light updates not delivered is the only obvious problem, check the possible causes in this section before calling the Lucent Technologies helpline.

Possible Cause 1: The UDP at the VMI hub system for voice messaging subscribers is programmed incorrectly.

What to Do: Check the programmed routing for the VMI conversion number:

■Verify the ranges for the non-local subscribers.

■Verify that the pattern for each range has routes assigned.

■Verify that each route has pools assigned with the same type of trunks in each pool.

Possible Cause 2: All programmed available routes for the call are busy.

What to do: Check that the pattern assigned to the VMI conversion number includes routes that include pools that have a sufficient number of trunks to handle the call volume.

■If you’re not sure of the pattern number being used to route calls in your local system, see “Reviewing the Non-Local Dial Plan and Routing” on page 3.

■To add different routes that can handle the call, consult the coordinating system manager and see “Uniform Dial Plan Routing” on page 25 or “Centralized Voice Message” in Chapter 4 of System Programming.

■If the routing is correct and enough routes are included in the pattern, but the problem persists, check if PRI lines are used. If they are, check the error log for D-channel inoperative and loss of signal alarms indicating lines are inoperative. If the D-channel inoperative alarm has occurred, check the CSU/DSU associated with the line for correct programming. If the loss of signal alarm has occurred, check for open cables, etc. If these conditions are not present, go to Possible Cause 4.

Possible Cause 3: Not enough trunks are assigned to the pools for UDP routes.

What to Do: Consult System Form 2c, System Numbering: Line/Trunk Jacks to determine the assignments. To see a report of pool assignments, select the 3ULQW option on the System Programming menu and then choose￿7UXQN￿,QIR￿and￿

*HQHUDO.