Lucent Technologies MERLIN LEGEND Release 6.0 System Programming Manual page 553

MERLIN LEGEND Communications System Release 6.0
System Programming 555-660-111
4 Programming Procedures
Uniform Dial Plan Facilities
Wherever possible, the same switch identifiers should be used for the same
switch across a network. For example, LEGEND A is identified by switch identifier
22 in LEGEND B and LEGEND C systems in a 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 be more than 200 miles from LEGEND F in the same
private network. In this case, the switch identifier for LEGEND D (for example, 21)
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.
Summary: Switch Identifiers
Programmable by
Mode
Idle Condition
Planning Form
Factory Setting
Valid Entries
Inspect
Copy Option
Console Procedure To enter or remove an identifier for one trunk:
PC Procedure
System Manager
Hybrid/PBX
None
Form 2c, System Numbering: Line/Trunk Jacks
Form 3b, Incoming Trunks: DS1 Connectivity (100D Module)
Null (no value)
Null, 1–20, 21–40, 41–50, 51–60
No
No
More
Dial trunk no.
To enter or remove identifiers for a block of trunks:
More
trunk in block
Dial switch no.
Æ   Ã
To enter or remove an identifier for one trunk:

Type switch no.
Æ   Ä
To enter or remove identifiers for a block of trunks:

  Ç Ç Ç
Type ending trunk in block
or
4
Dial switch no.
Dial ending trunk in block
or
 Ç Ç Ç
Type trunk no.
or

Type starting trunk in block
Type switch no.
Issue 1
February 1998
Page 4-83
or
Dial starting