Filter
Top Products
MERLIN LEGEND Communications System Release 6.1
Network Reference
555-661-150
Issue 1
August 1998
Troubleshooting
Page 6-9Call to Non-Local Extension: Silence or Fast Busy Tone
6
Possible Cause 6: There may be a numbering conflict in the switch identifiers for
the trunks that carry the call. Within a private network, switch identifiers should be
unique and unambiguous. If they are not, calls may terminate prematurely or
continue to route unexpectedly.
What to Do: The coordinating system manager must check system planning
Form Non-Local UDP Administration Form in the Installation Specification and
review the switch identifiers for all systems over which calls travel to reach the
destination extension(s). To review a report including the switch identifiers
programmed on your local system, select the
3ULQW option on the System
Programming menu and then choose
7UXQN,QIRand*HQHUDO.
■ If the switch identifiers are not correct, the coordinating system manager
must see that a change is made at one or more non-local systems where
the conflict exists. To change the current switch identifiers at your local
system, see “Switch Identifiers” on page 19
or “UDP Facilities” in Chapter 4
of
System Programming
.
■ 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 7.
— If the call is being routed over tandem tie trunks only, call the Lucent
Technologies Helpline at 1 800 628-2888; consultation charges may
apply.
Possible Cause 7: 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 a DEFINITY ECS or DEFINITY ProLogix Solutions system has its Interface field
set to Network, any MERLIN LEGEND Communications Systems connected to it
by tandem PRI trunks must specify LEGEND-Ntwk. If the Interface field specifies
User, the MERLIN LEGEND Communications System facilities must be
programmed with the LEGEND-PBX setting.
■ 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 report
including the switch type programmed for PRI facilities on your system,