Lucent Technologies 555-661-150 Benutzerhandbuch
MERLIN LEGEND Communications System Release 6.1
Network Reference
Network Reference
555-661-150
Issue 1
August 1998
Call-Handling Scenarios
Page 2-4
Networking Guidelines
2
MERLIN LEGEND Communications System extension in a private
network. Although the MERLIN LEGEND Communications System can be
programmed to drop digit(s), it is recommended that in networks with
DEFINITY ECS or DEFINITY ProLogix Solutions use 4-digit dial plans. The
next topic provides additional details.
network. Although the MERLIN LEGEND Communications System can be
programmed to drop digit(s), it is recommended that in networks with
DEFINITY ECS or DEFINITY ProLogix Solutions use 4-digit dial plans. The
next topic provides additional details.
■
When planning non-local extension ranges, Primary Rate Interface (PRI)
dial-plan routing and Direct Inward Dialing (DID) numbers must be
considered. If calls are routed across the private network to these
numbers, they also must not conflict with extension ranges in other private
network systems. In addition, UDP routes must specify correct digit
manipulation (deleting or adding digits). When such calls are routed to
5-digit DEFINITY ECS or DEFINITY ProLogix Solutions systems, special
considerations apply. See the next topic for details.
dial-plan routing and Direct Inward Dialing (DID) numbers must be
considered. If calls are routed across the private network to these
numbers, they also must not conflict with extension ranges in other private
network systems. In addition, UDP routes must specify correct digit
manipulation (deleting or adding digits). When such calls are routed to
5-digit DEFINITY ECS or DEFINITY ProLogix Solutions systems, special
considerations apply. See the next topic for details.
■
A centralized VMS/AA is subject to the following configuration
requirements and constraints:
requirements and constraints:
— A DEFINITY ECS or DEFINITY Prologix
cannot share a centralized
VMS/AA with a MERLIN LEGEND system.
— The hub system and all remote systems sharing a centralized VMS/AA
must be MERLIN LEGEND Release 6.1 or later systems.
— Each MERLIN LEGEND system must be configured as Hybrid/PBX.
— Networked MERLIN LEGEND systems that are not directly connected to
the “hub” system (more than one span away) cannot share the
centralized VMS/AA.
centralized VMS/AA.
— More than one centralized VMS/AA can be configured in a single private
network. More than one centralized VMS/AA can be installed on a single
MERLIN LEGEND system.
MERLIN LEGEND system.
— Any MERLIN LEGEND system may also have a local VMS/AA system
that is not shared.
— Each extension in the system can have only one voice mailbox, no
matter how many VMS/AA systems are available.
— Only the following voice messaging systems are supported for
centralized VMS/AA:
■
MERLIN LEGEND Mail
■
Messaging 2000
■
Intuity AUDIX
■
IS-III AUDIX Voice Power (no longer orderable)
— A Uniform Dial Plan (UDP) must be established for the private network.
— All trunks within the private network should have unique trunk numbers.
This allows the centralized VMS/AA to provide different call handling
and/or greetings based on the trunk on which the call was received.
and/or greetings based on the trunk on which the call was received.