Lucent Technologies 555-661-150 User Manual
MERLIN LEGEND Communications System Release 6.1
Network Reference
Network Reference
555-661-150
Issue 1
August 1998
Troubleshooting
Page 6-29
Calls From a Remote System to Centralized Voice Messaging System Get the
6
instructions for determining the switch type programmed at your system
and changing it if necessary. “Switch Type” in the Chapter 4 “PRI Facilities”
section of
and changing it if necessary. “Switch Type” in the Chapter 4 “PRI Facilities”
section of
System Programming gives full details.
■
In Release 6.1 and later systems, the PRI Switch Type Test requests the
system at the other end to respond with information about the system
mode specification. Lucent Technologies technicians or authorized
representatives can run this test to determine the mode of the system at
the other end.
system at the other end to respond with information about the system
mode specification. Lucent Technologies technicians or authorized
representatives can run this test to determine the mode of the system at
the other end.
■
If the call is carried over other systems connected by tandem PRI facilities,
the coordinating system manger must ensure that the settings are correct,
as in this example of MERLIN LEGEND Communications Systems:
the coordinating system manger must ensure that the settings are correct,
as in this example of MERLIN LEGEND Communications Systems:
System A LEGEND-PBX
→
System B LEGEND-Ntwk
→
System C LEGEND-PBX
■
If the switch type settings are correct and problem persists, call the Lucent
Technologies Helpline at 1 800 628-2888; consultation charges may apply.
Technologies Helpline at 1 800 628-2888; consultation charges may apply.
Calls From a Remote System to
Centralized Voice Messaging System
Get the Wrong Message or Go To
Operator
Centralized Voice Messaging System
Get the Wrong Message or Go To
Operator
6
The following are likely circumstances in which calls reach the centralized voice
messaging system but receive the wrong message, for example, automated
attendant instead of voice mail, or no message, or go to operator:
messaging system but receive the wrong message, for example, automated
attendant instead of voice mail, or no message, or go to operator:
Possible Cause 1: 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.
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: Dial the local VMI group. If the problem still occurs, 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
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,QIR
and
*HQHUDO
.
■
If the switch identifiers are missing or 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
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
or “UDP Facilities”
in Chapter 4 of
System Programming.