Lucent Technologies 555-670-111 Benutzerhandbuch
MERLIN LEGEND Communications System Release 7.0
System Programming
System Programming
555-670-111
Issue 1
April 1999
Programming Procedures
3-104
Uniform Dial Plan Facilities
3
You can add a switch identifier to a block of trunks, and you can remove a switch
identifier from a block of trunks that use the same switch identifier.
identifier from a block of trunks that use the same switch identifier.
The correct switch identifier for a trunk or block of trunks is determined by the type
of switch to which the trunk is connected and whether or not that switch is a
satellite switch located within 200 miles of the local system. Identifying those
switches greater than 200 miles from the local system as satellite is important in
assuring transmission quality across the private network. The identifiers are
switch numbers that have the following meanings:
of switch to which the trunk is connected and whether or not that switch is a
satellite switch located within 200 miles of the local system. Identifying those
switches greater than 200 miles from the local system as satellite is important in
assuring transmission quality across the private network. The identifiers are
switch numbers that have the following meanings:
■
Unassigned (null) = trunk connected to central office
■
1–20 = trunk connected to a non-satellite MERLIN LEGEND
Communications System greater than 200 miles
Communications System greater than 200 miles
■
21–40 = trunk connected to a satellite MERLIN LEGEND Communications
System
System
■
41–50 = trunk connected to a non-satellite, non-LEGEND system (for
example, a DEFINITY Communications System) greater than 200 miles
example, a DEFINITY Communications System) greater than 200 miles
■
51–60 = trunk connected to a satellite, non-LEGEND system (for example,
a DEFINITY Communications System)
a DEFINITY Communications System)
NOTE:
The Enter Switch Number screens for the switch identifier procedures
include a Help option that supplies the information above.
include a Help option that supplies the information above.
Wherever possible, the same switch identifiers should be used for the same
switch across a private network. For example, LEGEND A is identified by switch
identifier 22 in LEGEND B and LEGEND C systems in a private network. This
helps avoid a situation where calls are directed in a loop through several systems.
However, a trunk may connect to a switch that is a satellite for one networked
system, but not a satellite for another networked system. In this case, a system
may have more than one switch identifier. For example, LEGEND D may be
located within 200 miles of LEGEND E, but more than 200 miles from LEGEND F
in the same private network. In this case, the switch identifier for LEGEND D (for
example, 21) as specified in LEGEND E is different from the identifier for
LEGEND D (for example, 1) as specified in LEGEND F.
switch across a private network. For example, LEGEND A is identified by switch
identifier 22 in LEGEND B and LEGEND C systems in a private network. This
helps avoid a situation where calls are directed in a loop through several systems.
However, a trunk may connect to a switch that is a satellite for one networked
system, but not a satellite for another networked system. In this case, a system
may have more than one switch identifier. For example, LEGEND D may be
located within 200 miles of LEGEND E, but more than 200 miles from LEGEND F
in the same private network. In this case, the switch identifier for LEGEND D (for
example, 21) as specified in LEGEND E is different from the identifier for
LEGEND D (for example, 1) as specified in LEGEND F.
This topic includes procedures for adding a switch identifier to a single trunk or to
a block of sequentially numbered trunks.
a block of sequentially numbered trunks.