Lucent Technologies 555-661-150 Manuale Utente
MERLIN LEGEND Communications System Release 6.1
Network Reference
Network Reference
555-661-150
Issue 1
August 1998
Network Management
Page 5-17
Non-Local Dial Plan Numbering
5
An extension number range may stipulate a single extension number. For
Release 6.1 and later systems, the single non-local extension member (called the
VMI conversion number) assigned to an integrated VMI calling group used to
route calls to a centralized VMS/AA must be the only extension assigned to an
extension range. This allows UDP routing to absorb all dialed digits and prepend
the extension number for the centralized VMS/AA calling group at the central site.
Release 6.1 and later systems, the single non-local extension member (called the
VMI conversion number) assigned to an integrated VMI calling group used to
route calls to a centralized VMS/AA must be the only extension assigned to an
extension range. This allows UDP routing to absorb all dialed digits and prepend
the extension number for the centralized VMS/AA calling group at the central site.
You can use inspect to review extension ranges. To see a report of existing non-
local extension ranges, select the
local extension ranges, select the
3ULQW
option on the System Programming
menu and then choose
1RQ/FO8'3
. Appendix B, “Network Reports,” includes a
sample.
On a single MERLIN LEGEND system, you can specify up to 50 ranges. Each
range has an associated pattern. On a single MERLIN LEGEND, you can specify
up to 20 patterns. A pattern can be used by more than one range. Each pattern
specifies as many as four routes. A route specifies a pool, FRL, number of digits
to absorb, digits to prepend, and voice/data call type. Consider DID and PRI dial-
plan routing when setting up these ranges. For more information, see
range has an associated pattern. On a single MERLIN LEGEND, you can specify
up to 20 patterns. A pattern can be used by more than one range. Each pattern
specifies as many as four routes. A route specifies a pool, FRL, number of digits
to absorb, digits to prepend, and voice/data call type. Consider DID and PRI dial-
plan routing when setting up these ranges. For more information, see
Dial Plan Routing” on page 25
.
When the numbering of a non-local system changes, the local system manager
should check the new non-local numbers and ascertain the impact on both the
local and non-local dial plans, then make changes manually for non-local
extension ranges.
should check the new non-local numbers and ascertain the impact on both the
local and non-local dial plans, then make changes manually for non-local
extension ranges.
NOTE:
Renumbering of non-local extensions on the local system does not
put those extensions in the forced-idle condition on the remote
system.
put those extensions in the forced-idle condition on the remote
system.
SECURITY
l
ALERT:
!
If barrier codes are not required, these calls receive default COR for non-tie
trunks. If the system uses tandem PRI trunks for ARS to route calls through
the system, then the calling restriction option of the default COR must be set
to unrestricted. This can lead to toll fraud.
trunks. If the system uses tandem PRI trunks for ARS to route calls through
the system, then the calling restriction option of the default COR must be set
to unrestricted. This can lead to toll fraud.
Valid Entries
New extension ranges: Starting and ending numbers for non-local extension
ranges; number of dialed digits for the extension (Release 6.0 V11 and later
systems), range 1-11
ranges; number of dialed digits for the extension (Release 6.0 V11 and later
systems), range 1-11
Deleting extension ranges: Starting numbers for non-local extension ranges to be
deleted
deleted