Filter
Top Products
MERLIN LEGEND Communications System Release 6.1
Network Reference
555-661-150
Issue 1
August 1998
Troubleshooting
Page 6-28Calls From a Remote System Do Not Reach the Centralized Voice Messaging
6
■ 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 at
signal alarm has occurred, check for open cables, etc. If these conditions
are not present, go to Possible Cause 4.
Possible Cause 4: Not enough trunks are assigned to the pools for UDP routes.
What to Do: Check the error log for no trunks in pool (such as 4c01, Pool empty).
If error is present, 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 choose7UXQN,QIR
and*HQHUDO.
■ If more trunks are available and need to be assigned, follow the procedure
in “Trunks to Pools Assignment” in Chapter 4 of
System Programming
to
assign more tandem trunks. All the tandem trunks in a pool must be of the
same type (tie or PRI).
■ If not enough trunks are available, consider adding more to your system.
■ If there are sufficient trunks assigned but the problem persists, go to
Possible Cause 5.
Possible Cause 5: No Touch-Tone Receivers (TTRs) available at remote system
when using tie trunks.
What to Do: This can be verified by checking for the 0C03 error on the error log
on the remote switches.
■ If this error persists, contact your local service representative.
Possible Cause 6: The Switch Type setting at both ends of a tandem PRI facility
may match.
What to Do: The coordinating system manager must check the programmed
Switch Type settings at networked systems. Calls are not routed properly unless
the Switch Type setting is correctly programmed at the systems on both ends of
any tandem PRI facilities on the call route. If only MERLIN LEGEND
Communications Systems are included in the routing, the switch types must not
match in a single private network link. For example, if System A is connected to
System B by tandem PRI trunks, System A can be set to a switch type LEGEND-
PBX and System B can be LEGEND-Ntwk. It does not matter which system is
assigned a given switch type as long as they are not the same.
■ If the call is routed over a tandem PRI facility connected to your system,
ensure that the system at the other end of the facility is programmed
correctly to work with your own setting. Consult system Non-Local UDP
Administration Form in the Installation Specification. To see a a report
including the switch type programmed for PRI facilities on your system,
select the
3ULQW option on the System Programming menu and then
choose
35,,QIR.“Tandem PRI Facilities” on page 22 provides summary