MERLIN LEGEND Communications System Release 6.0
System Programming
555-660-111 Issue 1
February 1998
Programming Procedures
Page4-83Uniform Dial Plan Facilities
4
Wherever possible, the same switch identifiers should be used for the same
switch across a network. For example, LEGEND A is identified by switch id entifier
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 4
Programmable by System Manager
Mode Hybrid/PBX
Idle Condition None
Planning Form Form 2c, System Numbering: Line/Trunk Jacks
Form 3b, Incoming Trunks: DS1 Connectivity (100D Module)
Factory Setting Null (no value)
Valid Entries Null, 1–20, 21–40, 41–50, 51–60
Inspect No
Copy Option No
Console Procedure To enter or remove an identifier f or one trunk:
→More→ → ���
Dial trunk no.→ →Dial switch no.→ or →
→ →
To enter or remove identifiers for a block of trunks:
→More→ → →Dial starting
trunk in block→ →Dial ending trunk in block→
→Dial switch no.→ or →
→ →
PC Procedure To enter or remove an identifier f or one trunk:
→ → → →Type trunk no.→ →
Type switch no.→ or →→ →
To enter or remove identifiers for a block of trunks:
→ → → →Type starting trunk in block→
→Type ending trunk in block→ →Type switch no.→
or →→→