Lucent Technologies Marine Radio 6 1 Users Manual

Merlin Legend R6-1 System Planning Merlin Legend R6-1 System Planning

6.1 to the manual df41c244-1c74-4824-b11a-dc6412c5d77e

: Lucent-Technologies Lucent-Technologies-Lucent-Technologies-Marine-Radio-6-1-Users-Manual-436297 lucent-technologies-lucent-technologies-marine-radio-6-1-users-manual-436297 lucent-technologies pdf

Open the PDF directly: View PDF .
Page Count: 588

Download
Open PDF In Browser	View PDF

MERLIN LEGEND®
Communications System
Release 6.1
System Planning

555-661-112
Comcode 108289489
Issue 1
August 1998

Copyright © 1998, Lucent TechnologiesDocument 555-661-110
All Rights ReservedComcode 108289000
Printed in USAAugust 1998
Notice
Every effort was made to ensure that the information in this book was complete and accurate at the time of printing. However, information is
subject to change. See Appendix A, “Customer Support Information,” for important information.
Your Responsibility for Your System’s Security
Toll fraud is the unauthorized use of your telecommunications system by an unauthorized party, for example, persons other than your company’s
employees, agents, subcontractors, or persons working on your company’s behalf. Note that there may be a risk of toll fraud associated with your
telecommunications system, and if toll fraud occurs, it can result in substantial additional charges for your telecommunications services.
You and your System Manager are responsible for the security of your system, such as programming and configuring your equipment to prevent
unauthorized use. The System Manager is also responsible for reading all installation, instruction, and system programming documents provided
with this product in order to fully understand the features that can introduce risk of toll fraud and the steps that can be taken to reduce that risk.
Lucent Technologies does not warrant that this product is immune from or will prevent unauthorized use of common-carrier telecommunication
services or facilities accessed through or connected to it. Lucent Technologies will not be responsible for any charges that result from such unauthorized use. For important information regarding your system and toll fraud, see Appendix A, “Customer Support Information.”
Federal Communications Commission Statement
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits
are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may
cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in
which case the user will be required to correct the interference at his own expense. For further FCC information, see Appendix A, “Customer
Support Information.”
Canadian Department of Communications (DOC) Interference Information
This digital apparatus does not exceed the Class A limits for radio noise emissions set out in the radio interference regulations of the Canadian
Department of Communications.
Le Présent Appareil Numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la classe A
préscrites dans le règlement sur le brouillage radioélectrique édicté par le ministère des Communications du Canada.
Trademarks
5ESS, AUDIX, DEFINITY, HackerTracker, CONVERSANT, Lucent Technologies Attendant, Fax Attendant System, MERLIN, MERLIN
LEGEND, MERLIN MAIL, MERLIN PFC, MLX-10, MLX-10D, MLX-10DP, MLX-16DP, MLX-20L, MLX-28D, PassageWay, PARTNER,
and Voice Power are registered trademarks and 4ESS, Intuity, Lucent Technologies, MLX-5, MLX-5D, and ExpressRoute 1000 are trademarks
of Lucent Technologies in the US and other countries. NetPROTECT is a service mark of Lucent Technologies in the US and other countries.
Supra, StarSet, and Mirage are registered trademarks of Plantronics, Inc.
MEGACOM, ACCUNET, AT&T, Magic on Hold, and MultiQuest are registered trademarks of AT&T.
Pipeline is a trademark of Ascend Communications, Inc.
Intel and Pentium are registered trademarks of Intel Corporation.
PagePac is a registered trademark and PagePal a trademark of DRACON, a division of Harris Corporation.
UNIX is a registered trademark of UNIX System Laboratories, Inc
NORTEL is a registered trademark and DMS a trademark of Northern Telecom.
MCI, Prism, and Vnet are registered trademarks of MCI Communications Corp.
Apple and Macintosh are registered trademarks of Apple Computer, Inc.
Microsoft and Windows are registered trademarks of Microsoft Corporation.
Ordering Information
Call:
BCS Publications Center
Voice 1 800 457-1235 International Voice 317-322-6791
Fax 1 800 457-1764 International Fax 317-322-6699
Write:
BCS Publications Center
2855 North Franklin Road
Indianapolis, IN 46219-1385
Order:
Document No. 555-661-110
Comcode: 108289000
Issue 1, August 1998
For more information about Lucent Technologies documents, refer to the section entitled ‘‘Related Documents’’ on page xlix.
Support Telephone Number
In the continental US, Lucent Technologies provides a toll-free customer helpline 24 hours a day. Call the Lucent Technologies Helpline at
1 800 628-2888 or your Lucent Technologies authorized dealer if you need assistance when installing, programming, or using your system.
Consultation charges may apply. Outside the continental US, contact your local Lucent Technologies authorized representative.
Lucent Technologies Fraud Intervention
If you suspect you are being victimized by toll fraud and you need technical support or assistance, call BCS National Service Assistance Center at
1 800 628-2888.
Year 2000 Compliance
The MERLIN LEGEND Communications System is certified to be Year 2000 compliant. Additional information on this certification, and other
issues regarding Year 2000 compliance, is available online at http://www.lucent.com/enterprise/sig/yr2000.
Warranty
Lucent Technologies provides a limited warranty on this product. Refer to “Limited Warranty and Limitation of Liability” in Appendix A,
“Customer Support Information.”

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Contents

Page iii

Contents

New Features and Enhancements
■

Release 6.1 Enhancements (August, 1998)

Prior Releases: Features and Enhancements

xiii

xvii

■

Release 6.0 Enhancements (February, 1998)

xvii

■

Release 5.0 Enhancements (June, 1997)

xxii

■

Release 4.2 Enhancements (June, 1997)

xxvii

■

Release 4.1 Enhancements (June, 1997)

xxx

■

Release 4.0 Enhancements (March, 1996)

xxxii

■

Release 3.1 Enhancements (March, 1996)

xxxv

About This Book

1

xiii

xxxvii

■

Intended Audience

xxxvii

■

How to Use This Book

xxxvii

■

Terms and Conventions Used

xxxix

■

Security

xli

■

Related Documents

xlii

■

How to Comment on This Book

xliii

Before You Begin

1–1

■

Reviewing System Components

1–1

■

Confirming the Location of the Control Unit

1–2

■

Requirements for Supporting CTI Applications

1–6

■

Obtaining Telephone Company Information

1–10

■

Obtaining User Information

1–11

■

Obtaining a Floor Plan

1–13

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Contents

Page iv

2

3

4

5

Control Unit Configuration

2–1

■

Planning Module Placement

2–2

■

Recording System Operating Conditions

2–7

■

Numbering the System

Lines/Trunks

2–13

3–1

■

Identifying Line/Trunk Jacks

3–2

■

Selecting Line/Trunk Options

3–11

■

Assigning Lines/Trunks

3–50

■

Assigning Telephone Buttons

3–52

Features

4–1

■

Telephone and Extension Features

■

Operator Features

4–18

■

Group-Assigned Features

4–26

■

System Features

4–41

Data Communications

4–2

5–1

■

Terminology

5–3

■

About Data and Video Communications

5–5

■

Planning Overview

5–19

■

Assigning Extension Jacks

5–21

■

Assigning Lines/Trunks to Data and Video Stations

5–27

■

Assigning Features to Data Stations

5–35

■

Creating Data Hunt Groups

5–40

■

Digital Data/Video Stations

5–42

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Contents

Page v

6

7

A

Modifications

6–1

■

Preparation

6–2

■

Adding to the System

6–2

Upgrading

7–1

■

Upgrading to Release 6.1

7–2

■

Release 6.1 Forms

7–5

Customer Support Information

A–1

■

Support Telephone Number

A–1

■

Federal Communications Commission (FCC)
Electromagnetic Interference Information

A–1

Canadian Department of Communications (DOC)
Interference Information

A–2

■

FCC Notification and Repair Information

A–2

■

Installation and Operational Procedures

A–4

■

DOC Notification and Repair Information

A–5

■

Renseignements sur la notification du ministère des
Communications du Canada et la réparation

A–6

■

Security of Your System: Preventing Toll Fraud

A–9

■

Toll Fraud Prevention

A–10

■

Other Security Hints

A–16

■

Limited Warranty and Limitation of Liability

A–20

■

Remote Administration and Maintenance

A–21

■

B

System Forms

B–1

C

Data Forms

C–1

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Contents

Page vi

D

T1/PRI Planner

D–1

E

DS1 Connectivity Ordering

E–1

F

Unit Load Calculation

F–1

■

Unit Load Rules

F–2

■

Calculating Unit Loads

F–2

■

Unit Load Worksheet

F–3

G

NI-1 BRI Review

G–1

H

NI-1 BRI Provisioning

H–1

■

Lucent Technologies 5ESS Switch Translations

H–2

■

Northern Telecom DMS-100 Switch Translations

H–19

■

Siemens SSC EWSD Switch Translations

H–30

I

Network Engineering Forms

I–1

GL

Glossary

GL–1

IN

Index

IN–1

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Figures

Page vii

0

Figures

1

2

3

4

Before You Begin
1–1

System Configuration for Support of CTI Applications

1–2

Sample Floor Plan

1–7
1–14

Control Unit Configuration
2–1

Sample Control Unit Diagram

2–6

2–2

Extension Numbers for 2-Digit Numbering Plan

2–34

2–3

Extension Numbers for 3-Digit Numbering Plan

2–35

2–4

Extension Numbers for Set Up Space Numbering Plan 2–35

Lines/Trunks
3–1

Partially Completed System Form 2c

3–2

Factory-Set Assignment, MLX Telephones
(Hybrid/PBX Mode)

3–8
3–53

3–3

Factory-Set Assignment, Analog Multiline Telephones
(Hybrid/PBX Mode)
3–54

3–4

Factory-Set Assignment, MLX Telephones
(Key and Behind Switch Modes)

3–58

3–5

Factory-Set Assignment, Analog Multiline Telephones
(Key and Behind Switch Modes)
3–59

3–6

MLX Direct-Line Console

3–62

3–7

Analog Direct-Line Console

3–63

Features
4–1
4–2

Completed ARS Worksheet Automatic Route
Selection Tables

4–62

Example 1: Form 3f, 6-Digit Table

4–65

4–3

Example 2: Form 3f, Area Code Table

4–66

4–4

Subpattern Example

4–68

4–5

Other Digits Example

4–69

4–6

Digit Absorption Example

4–71

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Figures

Page viii

5

D

Data Communications
5–1

Analog Voice and Modem Data

5–8

5–2

Modem Data-Only

5–9

5–3

MLX Voice and Modem Data

5–10

5–4

MLX Voice and ISDN Terminal Adapter Data

5–12

5–5

ISDN Terminal Adapter Data-Only

5–13

T1/PRI Planner
D–1

Sample DS1 Planning Map

D–4

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Tables

Page ix

0

Tables

1

2

3

4

Before You Begin
1–1

Environmental Requirements

1–2

1–2

Control Unit Space Requirements

1–3

1–3

Employee Communications Survey: Description of
Questions

1–12

Control Unit Configuration
2–1

Application Ports

2–15

2–2

Modules with Touch-Tone Receivers

2–17

2–3

Touch-Tone Receivers Required by Voice
Messaging Systems

2–17

2–4

System Requirements for Touch-Tone Receivers

2–18

2–5

TTRs Required for Primary Delay Announcement Devices

2–19

2–6

TTRs Required for Secondary Delay Announcement
Devices

2–19

2–7

Maximum Number of Operator Positions

2–22

2–8

Application Ports

2–31

Lines/Trunks
3–1

Line/Trunk Jack Types

3–3

3–2

Codes for Line/Trunk Jacks

3–5

3–3

Line Compensation Settings

3–26

3–4

Line Compensation Settings

3–32

3–5

NI-1 BRI Timers

3–48

3–6

Total Number of TTRs Required

3–49

Features
4–1

Features That Can Be Copied

4–11

4–2

Disallowed List 7 Factory Set Entries

4–52

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Tables

Page x

5

6

7

B

Data Communications
5–1

Data Station Configurations

5–14

5–2

Data Forms

5–19

5–3

System Forms

5–20

5–4

Extension Jack Types

5–21

Modifications
6–1

Required Line/Trunk and/or Extension Modules

6–3

6–2

Adding New Trunks

6–5

6–3

Adding Auxiliary Equipment

6–6

6–4

Adding New Extensions

6–6

Upgrading
7–1

Programming Compatibility

7–3

7–2

Planning Forms

7–5

System Forms
B–1

C

Data Forms

C–1

DS1 Connectivity Ordering
E–1

I

B–1

Data Forms
C–1

E

System Forms

Guide to DS1 Connectivity Ordering

E–1

Network Engineering Forms
I–1

Network Forms

I–1

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998
Page xi

IMPORTANT SAFETY INSTRUCTIONS

0

The exclamation point in an equilateral triangle is
intended to alert the user to the presence of
important operating and maintenance (servicing)
instructions in the literature accompanying the
product.

When installing telephone equipment, always follow basic safety precautions to
reduce the risk of fire, electrical shock, and injury to persons, including:
■

Read and understand all instructions.

■

Follow all warnings and instructions marked on or packed with the product.

■

Never install telephone wiring during a lightning storm.

■

Never install a telephone jack in a wet location unless the jack is
specifically designed for wet locations.

■

Never touch uninsulated telephone wires or terminals unless the telephone
wiring has been disconnected at the network interface.

■

Use caution when installing or modifying telephone lines.

■

Use only Lucent Technologies-manufactured MERLIN LEGEND
Communications System circuit modules, carrier assemblies, and power
units in the MERLIN LEGEND Communications System control unit.

■

Use only Lucent Technologies-recommended/approved MERLIN LEGEND
Communications System accessories.

■

If equipment connected to the analog extension modules (008, 408,
408 GS/LS) or to the MLX telephone modules (008 MLX, 408 GS/LS-MLX)
is to be used for in-range out-of-building (IROB) applications, IROB
protectors are required.

■

Do not install this product near water, for example, in a wet basement
location.

■

Do not overload wall outlets, as this can result in the risk of fire or electrical
shock.

■

The MERLIN LEGEND Communications System is equipped with a 3-wire
grounding-type plug with a third (grounding) pin. This plug will fit only into a
grounding-type power outlet. This is a safety feature. If you are unable to
insert the plug into the outlet, contact an electrician to replace the obsolete
outlet. Do not defeat the safety purpose of the grounding plug.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998
Page xii

■

The MERLIN LEGEND Communications System requires a supplementary
ground.

■

Do not attach the power supply cord to building surfaces. Do not allow
anything to rest on the power cord. Do not locate this product where the
cord will be abused by persons walking on it.

■

Slots and openings in the module housings are provided for ventilation. To
protect this equipment from overheating, do not block these openings.

■

Never push objects of any kind into this product through module openings
or expansion slots, as they may touch dangerous voltage points or short
out parts, which could result in a risk of fire or electrical shock. Never spill
liquid of any kind on this product.

■

Unplug the product from the wall outlet before cleaning. Use a damp cloth
for cleaning. Do not use cleaners or aerosol cleaners.

■

Auxiliary equipment includes answering machines, alerts, modems, and
fax machines. To connect one of these devices, you must first have a
Multi-Function Module (MFM).

■

Do not operate telephones if chemical gas leakage is suspected in the
area. Use telephones located in some other safe area to report the trouble.

!

WARNING:
■

For your personal safety, DO NOT install an MFM yourself.

■

ONLY an authorized technician or dealer representative shall install, set
options on, or repair an MFM.

■

To eliminate the risk of personal injury due to electrical shock, DO NOT
attempt to install or remove an MFM from your MLX telephone. Opening
or removing the module cover of your telephone may expose you to
dangerous voltages.

SAVE THESE INSTRUCTIONS

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
New Features and Enhancements
Release 6.1 Enhancements (August, 1998)

Page xiii

New Features and Enhancements

Release 6.1 Enhancements
(August, 1998)

0

Release 6.1 includes all Release 6.0 functionality, plus the enhancements listed
below.

Private Networking

0

Release 6.1 enhances the functioning of the networked MERLIN LEGEND
Communications System in a number of ways:
■

Centralized Voice Messaging

■

Group Calling Enhancements

■

Transfer Redirect

■

Direct Station Selector

■

Call Forwarding

■

SMDR

■

Decrease in Call Set-Up Time

■

PRI Switch Type Test

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
New Features and Enhancements
Release 6.1 Enhancements (August, 1998)

Centralized Voice Messaging

Page xiv

0

One or more MERLIN LEGEND systems (Release 6.1 or later) can share the
voice messaging system (VMS) of another MERLIN LEGEND system, provided
the systems are directly connected to the system with the VMS. In this
configuration, the system containing the VMS is known as the hub. This sharing of
the VMS is called “Centralized Voice Messaging.” Centralized Voice Messaging
includes the functions of voice mail, Automated Attendant, and fax messaging.
See the Network Reference for detailed information about Centralized Voice
Messaging.
Centralized Voice Messaging offers the following benefits:
■

Private-networked MERLIN LEGEND systems do not need a local VMS.
Having systems use a centralized VMS instead of separate VMS’s is more
economical.

■

Users that travel between sites can dial the same digits anywhere in the
private network to access the voice messaging system. For example, a
salesperson headquartered in Cincinnati can dial the same four digits at
the company’s Los Angeles office to retrieve voice messages.

■

Productivity is enhanced because messages can be forwarded and
broadcasted to all personnel within the private network.

■

Calling groups on networked systems can send overflow coverage to a
shared VMS, so that an incoming caller can leave a message instead of
waiting in a queue.

■

The VMS can light the Message Waiting lights on multiple MERLIN
LEGEND systems in a private network. This greater efficiency saves time
because a user only has to look at his or her telephone to determine if he or
she has a message.

Group Calling Enhancements

0

A calling group can have a single non-local member that is defined by the Uniform
Dial Plan and exists on another MERLIN LEGEND Communications System
connected by a tandem trunk to the local system. If a calling group contains a
non-local member, the non-local member must be the only member in the calling
group. See the Network Reference for details.
A calling group containing a single non-local member can be used for the same
purposes as a calling group containing local extensions, including:
■

Night Service. Night Service coverage can be provided across a private
network to a centralized Automated Attendant, a non-local calling group, a
QCC queue, a DLC, or any individual extension on the remote system,
such as a night bell.

■

Group Coverage. Group Coverage can be provided across a private
network to a VMS, a non-local calling group, a QCC queue, a DLC, or any
individual extension on the remote system.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
New Features and Enhancements
Release 6.1 Enhancements (August, 1998)

Page xv

■

Calling group overflow coverage. Calling group overflow coverage can
be provided by a centralized VMS, a non-local calling group, a QCC queue,
a DLC, or any individual extension on the remote system.

■

Calls directed to another system. Lines connected to remote systems
can be answered by any extension programmed to answer the call, such
as a centralized Automated Attendant or a system operator (QCC or DLC).

Transfer Redirect

0

When an Automated Attendant transfers a call to a non-local extension, the
transferring MERLIN LEGEND system monitors the call to ensure that it is
answered. If the non-local extension is not available or the call is not answered
within the transfer redirect timeout period (fixed at 32 seconds), the call stops
ringing at the non-local destination and is redirected to the extension on the same
system as the Automated Attendant that is programmed to receive redirected
calls. This redirect extension can be a QCC queue, a calling group, or an
individual extension.

Direct Station Selector

0

Now users can press a Direct Station Selector (DSS) button for a non-local
extension to make or transfer calls to that extension. However, no busy indication
is displayed by the DSS for non-local extensions.

Call Forwarding

0

The Forward feature now can be used to send calls to non-local extensions
across the private network.

0

SMDR

In addition to SMDR options for non-network calls placed to and from the local
system, system managers now can program SMDR to log incoming and outgoing
UDP calls, or they can choose to log no UDP calls. The factory setting is to record
all UDP calls.
Customers who use a call accounting system may not want to fill the database
with calls coming and going across the private network. These customers may
choose not to log UDP calls.

Decrease in Call Set-Up Time

0

The set-up time for a call across a private network has been reduced by
programming the number of UDP digits expected.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
New Features and Enhancements
Release 6.1 Enhancements (August, 1998)

PRI Switch Type Test

Page xvi

0

A new maintenance test, the PRI Switch Type Test, has been created to allow
Lucent Technologies technicians or authorized dealers to automatically determine
if each end of the PRI tandem trunks has been programmed correctly.

Service Observing

0

Service Observing allows one extension to listen in on (observe) a call at another
extension. A typical application of this feature is that of a Customer Service
supervisor observing how a Customer Service representative handles calls.
The Service Observing group can consist of from one extension to all extensions
in the system, including other Service Observers. Up to 16 Service Observing
groups can be programmed. The Service Observer and the observed extension
must be on the same system.
The observer activates Service Observing either by pressing a Service Observing
button and then dialing an extension number or by pressing a DSS or Auto
Intercom button. The Service Observer must use an MLX telephone to observe an
extension; the telephone at the observed extension can be of any type.
A warning tone that alerts the observer, the observed extension, and the caller
that Service Observing is occurring can be set to On or Off through System
Programming. The factory setting is On.

Win SPM

0

The System Programming and Maintenance (SPM) software is now available in a
Windows format called Win SPM. For Release 6.1 and later systems, Win SPM
provides a graphical user interface (GUI) for those tasks must commonly
performed by the system manager. Pictorial representations of system
components, such as modules and their vintages and the creation of MLX
telephone button labels, appear on Win SPM. Win SPM also provides a
DOS-emulator mode to program tasks not currently supported by the GUI and
to program a MERLIN LEGEND system of Release 6.0 or earlier. Win SPM is
available on CD-ROM and is supported in Windows 95, Windows NT, and
Windows 98.

Windows NT Driver

0

Now available is the MERLIN LEGEND Windows NT PBX driver. When coupled
with the CentreVu Telephony Services application, the driver provides true
server-based Computer Telephony Integration (CTI). The new driver requires a
MERLIN LEGEND system of Release 5.0 or later and servers and PCs that
support the applications.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 6.0 Enhancements (February, 1998)

Page xvii

Prior Releases: Features and
Enhancements

Release 6.0 Enhancements
(February, 1998)

0

Release 6.0 includes all Release 5.0 functionality, plus the enhancements listed
below.

Private Networks

0

In Hybrid/PBX mode systems only, MERLIN LEGEND Communications Systems
can be networked with one another or with DEFINITY® Enterprise
Communications Server (ECS) and ProLogix™ Communications Systems in
private networks. In previous releases, this functionality is available using tie lines,
but users handle calls between networked switches as outside calls. In this
release, dialing the pool access code is not necessary for a call going from one
networked switch to another. Also, delay-start tie trunks or T1 trunks administered
as PRI can act as tandem trunks to connect networked systems.
Available for Hybrid/PBX mode systems, the private network features of the
MERLIN LEGEND Communications System Release 6.0 provide the following
advantages for geographically dispersed organizational sites:
■

Intersystem Calling. In a private network, users on one local system can
call extensions on other systems in the network. Release 6.0 can support
2-, 3-, 4-, or 5-digit dial plans. They dial these extensions as inside calls. To
implement this function, the system manager programs the extension
ranges of remote networked switches to create a non-local dial plan. This
programming does not actually affect numbering on the remote system. To
correctly set up systems for transparent calling among non-local dial plan
extensions, the system manager assigns networking tie and/or PRI tandem
trunks to pools. Then he or she programs as many as 20 patterns,

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 6.0 Enhancements (February, 1998)

Issue 1
August 1998
Page xviii

associates with routes, Facility Restriction Levels (FRLs), digit absorption,
and digit prepending. This allows ARS-like routing of non-local dial plan
calls. In addition, system managers can control whether calling name,
calling number, or both are shown at MLX display telephone for incoming
calls across PRI tandem trunks.
■

Toll Savings. Private networked trunks may allow you to realize significant
cost savings on long-distance and toll calls by performing tandem switching
in the following two ways:
— Callers on a local system, or individuals dialing in to remote access
at a local system, can reach the public switched telephone network
(PSTN) via outside trunks connected to other systems in a private
network, avoiding toll charges or decreasing the cost of toll calls. No
special dialing is required. For example, an organization might have
a main office in Boston and a subsidiary office in New Jersey,
connected by networked private tandem trunks between two
systems. A user in the New Jersey office who wishes to make an
outside call to the 617 area code (Boston) can do so through a
line/trunk connected to the system in Boston. For example, he or
she might dial, . The local ARS tables would route this
call over the private network trunks and use the ARS tables of the
remote system in Boston to route this call. The system managers at
each end of a private network set up ARS and Remote Access
features to implement this functionality.
— In addition, local organizations or incoming DID calls use private
networked trunks to make intersystem calls between networked
systems, which may be geographically distant from one another,
also resulting in toll savings.

■

Service Cost Savings. In addition to toll call saving, there are two ways
that organizations can save on service costs incurred from
telecommunications providers that provide public switched telephone
network access:
— You order a point to point T1 facility from a service provider, then
use system programming to set it up for PRI signalling. As
necessary, a service provider can provide amplification on the T1
facility, but does not supply switching services.
— You can tailor your use of PRI B-channels with drop-and-insert
equipment that allows fractional use of B-channels for dedicated
data/video communications between systems at speeds greater
than 64kbps per channel or 128 kbps for 2B data, while keeping the
remaining B-channels for PRI voice traffic. The PRI D-channel must
remain active.
— You can tailor use of T1 channels to support both T1-emulated
tandem tie service and T1 Switched 56 service for data
communications at 56 kbps per channel, allowing 2B data transfers
at 112 kbps. You can also use drop-and-insert equipment to provide
fractional T1 use.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 6.0 Enhancements (February, 1998)
■

Page xix

Voice Mail and Auto Attendant. Networked systems should have their
own local voice mail and/or auto attendant applications as well as their own
external alerts and Music On Hold sources. However, a single auto
attendant can transfer calls throughout the network. It can answer only
those calls that arrive on the PSTN facilities of the system where it is
connected.

Although many features are available using tie trunks for network connectivity,
PRI tandem trunks provide greatly enhanced features and faster call setup. For
this reason, PRI is recommended over tie functionality in private networks.

Group Calling Enhancements

0

Release 6.0 and later systems include Group Calling features that enhance group
calling operations.

0

Queue Control

The system manager can control the maximum number of calls allowed in the
primary calling group queue for calls that arrive on certain facilities often assigned
to calling groups. When the number of the calls in queue reaches the
programmed maximum, subsequent callers receive a busy signal.
Queue control applies to calls received on the following types of facilities:
■

DID (Direct Inward Dialing)

■

PRI facilities programmed for dial-plan routing

■

All calls transferred from a VMI (voice messaging interface) port

■

Dial-in Tie

Queue control also applies to internal calls to a DGC group and calls to a calling
group through the QCC.
Internal calls that dial  or  and are directed to a calling group
administered as Position-Busy Backup are eligible for queue control. Calls that
come in on a trunk assigned to the Queued Call Console (QCC) are not eligible
for queue control if the call is directed to a calling group designated as
Position-Busy Backup.
Remote-access calls to a calling group, coverage calls directed to a calling group,
calls directed to calling group through QCC Position-Busy backup, and all other
outside calls are not eligible for queue control.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 6.0 Enhancements (February, 1998)

Prompt-Based Overflow

Page xx

0

System managers can activate the Prompt-Based Overflow option. This option
allows callers waiting in queue and listening to a delay announcement to press the
# key in order to reach the overflow receiver for the group, which may be the QCC
queue or another calling group (including a calling group assigned for a voice mail
system).
All three overflow distribution options—based on the number of calls, the time a
caller has waited, and according to the caller’s prompt—may be used at one time.
In this case, time-based and number-of-calls based options take precedence over
overflow distribution based on the caller’s prompt.
When prompt-based overflow distribution is used, an extra TTR must be provided
for each delay announcement device assigned to the associated calling group.
The delay announcement informs the caller of the # key option to exit the queue
and leave rather than waiting for an agent. If no TTR is available when a calling
group call arrives, the call is not sent to a delay announcement extension.

Centrex Transfer via Remote Call Forwarding

0

Centrex Transfer via Remote Call Forwarding can be used in all system modes of
operation to send outside calls to a remote telephone number or another Centrex
station. In this context, the term outside calls refers to calls from outside the
communications system, which may originate at extensions in the Centrex system
but not connected to the local MERLIN LEGEND Communications System.
An outside call that uses this feature is defined as a call that arrives on an analog
Centrex loop-start line at the MERLIN LEGEND Communications System. It may
arrive directly or be transferred without consultation or without transfer supervision
(in the case of an automated attendant). The forwarding call to the outside
number is made on the same line/trunk on which the call arrived, conserving
system facilities. The following considerations and rules apply:
■

Only outside Centrex calls are forwarded using this feature.

■

The system must be equipped with analog loop-start Centrex lines and all
loop-start lines in the system must be Centrex facilities. Loop-start lines do
not have to provide reliable disconnect for use by the Centrex Transfer via
Remote Call Forwarding feature.

■

To transfer calls outside the Centrex system, the organization must
subscribe to a Centrex trunk-to-trunk transfer feature.

Activating Centrex Transfer via Remote Call Forwarding is just like activating
regular Remote Call Forwarding and requires that Remote Call Forwarding be
enabled for the extension. However, the user dials 
 instead of a dial-out code,
and a Pause character may be required after the 
. The Centrex service provider
determines whether the Pause is needed.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 6.0 Enhancements (February, 1998)

Page xxi

Pause cannot be originated from a single-line telephone or a remote access user.
A multiline telephone user in the local system must enter an authorization code to
activate the feature.
A remote access user may activate the feature without using an authorization
code. Barrier code requirements do apply, however.

Authorization Codes and
Remote Call Forwarding

0

In Release 6.0 and later Key or Hybrid/PBX mode systems, forwarding features,
including Centrex Transfer via Remote Call Forwarding, but excluding Follow Me,
can be activated or deactivated at a multiline telephone by entering the
authorization code for the extension from which calls are to be forwarded. The
user enters the authorization code, then activates or deactivates the forwarding
feature in the normal fashion. This is especially useful for a single-line telephone
user who must include a Pause character in a Centrex Transfer via Remote Call
Forwarding dialing sequence, because the character cannot be dialed at a
single-line telephone. It is also useful when activating Call Forwarding or Remote
Call Forwarding at phantom stations, or via remote access (e.g. from another
switch in the network). No other features can be used by entering an authorization
code in this fashion.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 5.0 Enhancements (June, 1997)

Page xxii

Release 5.0 Enhancements (June, 1997) 0
Release 5.0 includes all Release 4.2 functionality, plus the enhancements listed
below.

Computer Telephony Integration (CTI)

0

Beginning with Release 5.0, a PassageWay® Telephony Services CTI link from
the MERLIN LEGEND Communications System to a LAN server running Novell®
NetWare® software allows Lucent Technologies-certified telephony applications to
control and monitor MLX and analog multiline telephone (BIS only) operations.
The physical connection for the CTI link is an MLX port on a 008 MLX or 408 MLX
module on the MERLIN LEGEND Communications System control unit and an
ISDN link interface card plugged into the customer’s server. The feature is
available for Hybrid/PBX mode systems only.
NOTE:
The NetWare server software version must be 3.12, 4.1 or 4.11.
The 008 MLX and 408 MLX modules must have firmware vintage other
than 29. If the module has firmware 29, programming a CTI link on the
module is prevented. An earlier or later vintage firmware is supported.

0

Basic Call Control

A CTI link application on a user’s computer can assume basic call control of the
user’s analog multiline or MLX telephone’s SA buttons. Basic call control includes:
■

Answering calls arriving on an SA button

■

Making calls from an SA button

■

Hanging up calls

■

Hold and retrieving a call on hold at the user’s extension
NOTE:
Transfer and three-way conference, when handled through a CTI link
application, provide the original caller’s calling number information or
other information to the transfer receiver or new conference
participant, if the user has screen-pop capability.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 5.0 Enhancements (June, 1997)

Page xxiii

0

Screen Pop

Screen pop occurs when the calling number, called number, or other user-defined
identifier (such as account code that a voice-response unit prompts the caller to
dial) is used to display a screen associated with the far-end party. For example,
Caller ID services can be used to support screen pop on a system that includes a
CTI link; using the calling party number as a database key code, information
about a caller automatically appears on the user’s computer screen when the call
arrives at the extension. Depending on the application, screen pop may be
available for calls that arrive on line buttons other than SA buttons and/or calls
that are answered manually at the telephone rather than by the application.
Screen pop can occur on incoming calls from the following sources:
■

Calling group distribution

■

ISDN PRI Routing by Dial Plan

■

An extension on the MERLIN LEGEND Communications System

■

Remote access
NOTE:
In the case of remote access calls, the only information that the
application can collect about the caller is the remote telephone
number.

■

A transfer of a call that was answered by a voice response unit

■

A transfer, redirection, or conference of a call that was answered at a DLC
or at a QCC
NOTES:
1. DLCs (Direct-Line Consoles) may use CTI applications. If they do, they
perform the same way as other extensions. A DLC assigned to use a
CTI link application is a monitored DLC. When a DLC is used as a
regular operator console and not using a CTI link extension, it is
non-monitored.
2. Calls to a QCC or non-monitored DLC do not initiate screen pop at the
operator position, but when an operator directs a call to an extension
using a CTI application, caller information does initiate screen pop. If
the DLC is non-monitored, screen pops can occur after the DLC
releases the call.
3. Calls transferred from Cover buttons on non-monitored DLCs do not
initiate screen pop at the destination extension.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 5.0 Enhancements (June, 1997)

HotLine Feature

Page xxiv

0

The Release 5.0 HotLine feature is designed for retail sales, catalogue sales, and
other types of businesses and organizations and is available in all three modes of
system operation. It allows a system manager to program a single-line telephone
extension connected to an 008 OPT, 012, or 016 module as a HotLine. When a
user lifts the handset at the HotLine extension, the telephone automatically dials
the inside extension or outside telephone number programmed as the first
Personal Speed Dial number (code #01) for the extension. The system does not
permit calls to be transferred, put on hold, or conferenced. (A user can press the
telephone’s Hold button, if it has one, to put a call on local hold, but the call
cannot be redirected in any way. Switchhook flashes are ignored.)
Personal Speed Dial codes can be programmed from the extension prior to
HotLine assignment (a system programming function). Alternatively, a Personal
Speed Dial code can be programmed from the single-line telephone after HotLine
operation is assigned. However, because of security considerations, this is a
one-time opportunity. Once the Personal Speed Dial number is programmed, any
changes to it or any other extension programming must be performed using
centralized telephone programming.
Any type of inside or outside line that is normally available to a single-line
telephone can be assigned to a HotLine extension. Generally, the HotLine
telephone does not receive calls, and its lines should be set to No Ring.

!

SECURITYlALERT:
If a HotLine extension accesses a loop-start line, that line should provide
reliable disconnect and be programmed for reliable disconnect. Otherwise,
a user at the extension may be able to stay on the line after a call is
completed and then make a toll call.

Group Calling Enhancements

0

Release 5.0 and later systems include Group Calling features that enhance group
calling operations.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 5.0 Enhancements (June, 1997)

Most Idle Hunt Type

Page xxv

0

In addition to the Circular (factory setting) and Linear hunt types supported in
earlier releases, a third hunt type distributes calling group calls in an order based
on which agent has waited the longest since transferring or hanging up on an
incoming calling group call. For some applications, this hunt type is more efficient
than the circular type because it takes into account the varying duration of calls.
The system distributes calls based on when an agent last completed a call, not on
when he or she last received one. This hunting method ignores non-calling group
calls. For example, if an agent transfers a call that arrived on a line not assigned
to the calling group, the calling group member’s most-idle status is unaffected.

Delay Announcement Devices

0

The system manager can designate as many as ten primary delay announcement
devices per group rather than the single device for each group that is available in
Release 4.2 and earlier systems. Furthermore, an additional secondary delay
announcement device can be specified, for a total of ten primary device
extensions and one secondary device extension per group.
A primary delay announcement device operates in the same fashion as a single
delay announcement device, playing once, as soon as it is available, for the caller
who has waited the longest for a calling group agent and has not heard a primary
delay announcement. If a secondary announcement device is used, it can use the
factory setting, which plays the announcement once, or it can be set to repeat the
announcement after a certain amount of time. The system manager programs the
time (0–900 seconds) between announcements. This setting controls both the
interval between primary and secondary announcements and the interval
between repetitions of the secondary announcement if it is set to repeat. (See
Group Calling Options in Chapter 4 for guidelines on setting the delay.)
The primary and secondary announcement options, when used together, allow an
initial message to play for callers, followed by a repeating announcement that, for
example, urges callers to stay on the line and wait for a calling group member.
Two or more groups may share an announcement device.
A primary delay announcement device can be administered as a secondary delay
announcement device.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 5.0 Enhancements (June, 1997)

Enhanced Calls-in-Queue Alarm Thresholds

Page xxvi

0

Three Calls-in-Queue Alarm thresholds can be set to more clearly indicate the
real-time status of the calls waiting in the queue according to the behavior of
programmed Calls-in-Queue Alarm buttons. In earlier releases, only one
Calls-in-Queue Alarm Threshold setting is available to activate the LEDs at
programmed Calls-in-Queue Alarm buttons for a calling group.
Using all three levels, the system manager sets Threshold 3 to the highest value,
Threshold 2 to a middle value, and Threshold 1 to the lowest value. A
Calls-in-Queue Alarm button indicates the severity of the alarm conditions in the
following ways:
■

If the number of waiting calls is less than the value programmed for
Threshold 1 or drops below that level, the LED is unlit.

■

If the number of waiting calls is greater than or equal to the Threshold 1
value but less than the Threshold 2 value, the LED flashes.

■

If the number of waiting calls is greater than or equal to the Threshold 2
value but less than the value for Threshold 3, the LED winks.

■

If the number of waiting calls is greater than or equal to the highest value,
Threshold 3, the LED lights steadily.
NOTE:
A DSS (Direct Station Selector) button that is used as a
Calls-in-Queue Alarm button can only indicate two threshold levels,
either by flashing or by lighting steadily. If a calling group must use
this type of Calls-in-Queue Alarm button, only two threshold levels
should be programmed.

If all three thresholds are set to the same value, the result is one threshold only
with LED state either off or on (steady). If two values are the same, then the result
is two alarm levels (flash, steady). The factory setting is one call for all three
thresholds with LED states of off and steady.
An external alert only signals when the number of calls in the queue meets or
exceeds the programmed Threshold 3 value.

MLX-5 and MLX-5D Telephones

0

The MLX-5 nondisplay and MLX-5D display telephones are compatible with all
system releases. The display telephone includes a 2-line by 24-character display,
and both telephones come with 5 line buttons. In systems prior to Release 5.0, the
MLX-5 and MLX-5D telephones are treated as MLX-10 and MLX-10D telephones
respectively. As of Release 5.0, the system recognizes the MLX-5 and MLX-5D
telephones as 5-button telephones.
If these telephones are connected to communications system releases prior to
5.0, they are recognized by the communications system as 10 button telephones.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 4.2 Enhancements (June, 1997)

Issue 1
August 1998
Page xxvii

Release 4.2 Enhancements (June, 1997) 0
Release 4.2 includes all Release 4.1 functionality, plus the enhancements listed
below. There are no hardware changes for Release 4.2.

Additional Network Switch and Services Options
for ISDN Primary Rate Interface (PRI)
0
Release 4.2 of the system supports connectivity to MCI® or local exchange carrier
(LEC) PRI services and to the following central office switch types (in addition to
the 4ESS™ and 5ESS® switch types that carry for AT&T Switched Network
services):
■

NORTEL® DMS™-100 BCS 36 for local exchange carrier services

■

NORTEL DMS-250 generic MCI07 serving the MCI network

■

Digital Switch Corporation DEX600E generic 500-39.30 serving the MCI
network

Beginning with Release 4.2, the following MCI PRI and PRI local exchange carrier
(LEC) services (along with AT&T Switched Network Services) can be provided to
users of the MERLIN LEGEND Communications System:
■

MCI Toll Services for DMS-250 or DEX600E switch type:
— MCI Prism® service for domestic outgoing long-distance and
international voice calls; for domestic outgoing 56-kbps restricted,
64-kbps unrestricted, and 64-kbps restricted circuit-switched data calls
— MCI VNet® service for incoming and outgoing domestic and voice calls;
for 56-kbps restricted, 64-kbps restricted, and 64-kbps unrestricted
circuit-switched data calls
— MCI 800 for domestic, toll-free, incoming voice calls
— MCI 900 service numbers

■

LEC services for DMS-100 switch types:
— DMS Virtual Private Network service for calls between the MERLIN
LEGEND Communications System and another communications
system (such as another MERLIN LEGEND Communications System)
— DMS INWATS (Inward Wide Area Telephone Service) for domestic
toll-free incoming voice calls
— DMS OUTWATS (Outward Wide Area Telephone Service) for domestic
outgoing long-distance voice calls
— DMS FX (foreign exchange) to provide local call rating for calls from the
local exchange to the area serviced by the foreign exchange.
— DMS tie trunk service to provide private exchange call rating for calls
placed on a dedicated central office facility between the MERLIN
LEGEND Communications System and another communications
system (such as another MERLIN LEGEND Communications System)

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 4.2 Enhancements (June, 1997)

Improvements to Station Message Detail
Recording (SMDR) and Support for MERLIN
LEGEND Reporter Application

Page xxviii

0

The SMDR feature is enhanced to provide more details about calling group agent
activities and to help system managers assess the effectiveness of call centers in
terms of both agent performance and the adequacy of facilities to handle inbound
calls. These improvements apply to calling groups that are programmed as Auto
Login or Auto Logout type. The SMDR and MERLIN LEGEND Reporter features
listed are administrable:
■

TALK Field. For Auto Login and Auto Logout calling groups, the TALK field
records the amount of time a calling group agent spends on a call.

■

DUR. (DURATION) Field. For Auto Login and Auto Logout calling groups,
call timing begins when a call arrives at MERLIN LEGEND
Communications System and not after a preset number of seconds. Call
timing ends when the call is disconnected; either the caller or the agent
hangs up. This allows the system manager to determine how long a caller
waited for an agent’s attention.

■

Coding of Calls on Reports. An asterisk (*) appears in the call record
when:
a.

A call is not answered by an Auto Login or Auto Logout calling group
agent and is abandoned while waiting for an agent.

b.

The call is answered by someone not a member of an Auto Login or
Auto Logout calling group.

An exclamation point (!) signals that an Auto Login or Auto Logout agent
handled a call that was answered by someone who was not a member of
that Auto Login or Auto Logout with Overflow group. An ampersand (&) in
the call record indicates that the group’s overflow receiver answered the
call.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 4.2 Enhancements (June, 1997)

MERLIN LEGEND Reporter

Page xxix

0

MERLIN LEGEND Reporter provides basic call accounting system reports for all
incoming calls to Auto Login or Auto Logout type calling groups. MERLIN
LEGEND Reporter assists in determining the effectiveness of calling group
agents, assessing the level of service provided to callers, and ascertaining
whether adequate incoming phone lines and agents are available to handle
peak-call load. The SMDR Talk Time option sets up special call records used by
MERLIN LEGEND Reporter. The default is Off, in which case the Release 4.0
SMDR reports are available. If the option is set to On, the following new reports
are provided:
■

Organization Detail Report

■

Organization Summary and Trends Report

■

Selection Detail Report

■

Account Code Report

■

Traffic Report

■

Extension Summary Report

■

Data Report

■

Talk and Queue Time Distribution Report

■

Time of Day Report

■

ICLID Call Distribution Report

■

Facility Grade of Service Report

Maintenance Enhancements

0

Change to Permanent Error Alarm

0

Beginning with Release 4.2, the most recent permanent error alarm is not shown
on the System Error Log menu screen but is available as an option from that
screen. For details, refer to the Maintenance section of the technician guide,
Installation, Programming, and Maintenance.

Enhanced Extension Information Report

0

Beginning with Release 4.2, the Extension Information Report includes the
Extension Status (ESS) and supervisory mode of each extension.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 4.1 Enhancements (June, 1997)

Page xxx

Release 4.1 Enhancements (June, 1997) 0
Release 4.1 includes all Release 4.0 functionality, plus the enhancements listed
below. There are no hardware changes in Release 4.1.

Coverage Timers Programmed for
Individual Extensions

0

Beginning with Release 4.1, coverage timers, which control the duration of the
delay before calls are sent to each level of coverage, are changed as follows:
■

The Group Coverage Ring Delay (1–9 rings) is programmed on individual
extensions and replaces the Coverage Delay Interval programmed
systemwide in previous releases.

■

The Primary Cover Ring Delay (1–6 rings) and Secondary Cover Ring
Delay (1–6 rings), programmed on individual extensions, replace the Delay
Ring Interval programmed systemwide in previous releases.

These enhancements allow the system manager to customize coverage call
delivery to match individual extensions’ call-handling requirements.

Night Service with Coverage Control

0

Beginning with Release 4.1, a system manager can enable the Night Service
Coverage Control option to automatically control the status of telephones
programmed with Coverage VMS (voice messaging system) Off buttons,
according to Night Service status.
When Coverage Control is enabled and the MERLIN LEGEND Communications
System is put into Night Service, all programmed Coverage VMS Off buttons are
automatically turned off (LED is unlit) and all eligible outside calls are sent to the
assigned voice messaging system calling group with normal ringing delay. When
Night Service is deactivated during the day, all programmed Coverage VMS Off
buttons are automatically turned on (LED is lit) and voice mail coverage is
disabled for outside calls.
Users can override the Coverage VMS Off button status at any time by pressing
the programmed Coverage VMS Off button to turn the LED on or off.

Night Service Group Line Assignment

0

Beginning with Release 4.1, a system manager can assign lines to Night Service
groups to control handling of after-hours calls received on individual lines. This
capability replaces the automatic assignment to Night Service groups of only
those lines that ring on the Night Service operator console. An outside line must
be assigned to a Night Service group to receive Night Service treatment.
With this enhancement, Night Service can be activated and deactivated on lines
that do not appear on operator consoles (for example, personal lines), and lines
appearing at operator positions can be excluded from Night Service.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 4.1 Enhancements (June, 1997)

Forward on Busy

Page xxxi

0

Beginning with Release 4.1, the Forward, Follow Me, and Remote Call Forward
features are enhanced to remove the requirement that a call be ringing at an
extension before it can be forwarded. With the Forward on Busy enhancement, a
call to an extension with no available SA (System Access) or ICOM (Intercom)
buttons is forwarded immediately to the programmed destination, preventing the
caller from hearing a busy signal from the intended call recipient’s extension.

Maintenance Testing for BRI Facilities that Are
Part of Multiline Hunt Groups (MLHGs)

0

Beginning with Release 4.1, the NI-1 BRI (National Integrated Services Digital
Network-1 Basic Rate Interface) Provisioning Test Tool is enhanced to include
testing for BRI facilities that are part of Multiline Hunt Groups (MLHGs).
The NI-1 BRI Provisioning Test Tool is used by Lucent Technologies maintenance
personnel on MERLIN LEGEND Communications Systems that include an
800 NI-BRI module. Technicians use the tool during system installation and
maintenance to test the functionality of the BRI lines and to report analyzed
results.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 4.0 Enhancements (March, 1996)

Release 4.0 Enhancements
(March, 1996)

Page xxxii

0

Release 4.0 includes all Release 3.1 functionality, plus the enhancements listed
below.

Support for Up to 200 Extensions

0

An expanded dial plan supports up to 200 tip/ring devices.

Support for National ISDN BRI Service

0

This service (Hybrid/PBX and Key modes) provides an alternative to loop-start
and ground-start lines/trunks for voice and digital data connectivity to the central
office. Each of the two B-channels (bearer channels) on a BRI line can carry one
voice and one data call at any given time. The data speeds on a B-channel are up
to 28.8 kbps for analog data and up to 64 kbps for digital data, which is necessary
for videoconferencing and other high-speed applications. Release 4.0 supports
the IOC Package “S” (basic call handling) service configuration and Multiline Hunt
service configuration on designated CO switches.

New Control Unit Modules

0

Release 4.0 supports a new NI-BRI line/trunk module and a higher-capacity
tip/ring module.

800 NI-BRI Module

0

This new module connects NI-BRI trunks to the MERLIN LEGEND system for
voice, high-speed data, and video transmission.

016 Tip/Ring Module

0

This new module supports a 200-extension dial plan by providing 16 ports for
tip/ring devices. Applications that use a tip/ring interface can connect to this
board. All 16 ports can ring simultaneously. Four touch-tone receivers (TTRs) are
included on the module as well. The module’s ringing frequency (default 20 Hz)
can be changed through programming to 25 Hz for those locations that require it.

Downloadable Firmware for the
016 T/R and NI-BRI Modules

0

The Personal Computer Memory Card International Association (PCMCIA)
technology introduced in Release 3.0 continues to support these two boards for
installation and upgrade in Release 4.0. A Release 3.0 or later processor is
required for PCMCIA technology.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 4.0 Enhancements (March, 1996)

Support for 2B Data Applications

Page xxxiii

0

A Lucent Technologies-certified group and desktop video application can use two
B-channels to make video/data calls when connected to a single MLX extension
jack programmed for 2B data. The 2B data devices must be equipped with
ISDN-BRI interfaces. NI-1 BRI, PRI, or T1 Switched 56 facilities support 2B data
communications at 112 kbps (using two 56-kbps channels) or 128 kbps (using two
64-kbps B-channels). This feature is available for Hybrid/PBX and Key modes
only.

Support for T1 Switched 56
Digital Data Transmission

0

For Hybrid/PBX and Key mode systems, Release 4.0 expands support of T1
functionality by providing access to digital data over the public switched 56-kbps
network, as well as to digital data tie-trunk services. Users who have T1 facilities
for voice services can now use them for video or data calls at rates of 56 kbps per
channel (112 kbps for video calls using 2B data). The Release 4.0 offering also
includes point-to-point connectivity over T1 tie trunks, allowing customers to
connect two MERLIN LEGEND Communications Systems or a MERLIN LEGEND
Communications System with a Lucent Technologies DEFINITY® G1.1
Communications System or DEFINITY Enterprise Communications Server. The
two communications systems can be co-located or at different sites.

Forwarding Delay Option

0

Each user can program a Forwarding Delay setting for the Forward, Remote Call
Forwarding, or Follow Me features. The forwarding delay is the number of times
that a call rings at the forwarding extension before the call is sent to the receiver.
The delay period gives the original call recipient time to answer or to screen calls
by checking the displayed calling number (if available). The delay can be set at
0-9 rings. The factory setting for the forwarding delay is 0 rings (no delay).

Voice Announce on Queued Call Console

0

The system manager can enable the fifth Call button on a QCC console
(Hybrid/PBX mode only) to announce a call on another user’s speakerphone
(providing the destination telephone has a voice announce-capable SA button
available). A QCC cannot receive voice-announced calls; they are received as
ringing calls. The factory-set status for the fifth Call button is voice
announce-disabled.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 4.0 Enhancements (March, 1996)

Time-Based Option for
Overflow on Calling Group

Page xxxiv

0

Release 4.0 has added a time limit for calls in queue in addition to the previous
number of calls limit. If the Overflow Threshold Time option is set to a valid
number between 1 and 900 seconds, calls that remain in the calling group queue
for the set time are sent to the overflow receiver. If the overflow threshold time is
set to 0, overflow by time is turned off. The factory-set time limit is 0 seconds (off).

Single-Line Telephone Enhancements

0

The following changes enhance the performance of single-line telephones:
■

Disable Transfer. Through centralized telephone programming, the
system manager can disable transfer by removing all but one SA or ICOM
button from the extension.

■

No Transfer Return. When a handset bounces in its cradle, the system
interprets this as a switchhook flash and attempts to transfer a call. When
the transfer attempt period expires, the user’s telephone rings. Release 4.0
eliminates this unintended ringing by disconnecting the call in situations
where a switchhook flash is followed by an on-hook state and a dial tone is
present.

■

Forward Disconnect. All ports on 008 OPT, 012, and 016 modules now
send forward disconnect to all devices connected to them when forward
disconnect is received from the CO. This enhancement prevents the
trunk/line from being kept active when one end disconnects from the call. If
an answering machine is connected to the port, it does not record silence,
busy tones, or other useless messages. This operation is not
programmable.

Seven-Digit Password for SPM

0

Release 4.0 has increased system security by requiring a 7-digit password for
system managers or technicians who use System Programming and Maintenance
(SPM) to perform programming or the Trunk Test procedure. This password is for
use in addition to a remote access barrier code.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 3.1 Enhancements (March, 1996)

Release 3.1 Enhancements
(March, 1996)

Page xxxv

0

Release 3.1 includes all Release 3.0 functionality, plus the enhancements listed
below.

Call Restriction Checking for Star Codes

0

Beginning with Release 3.1, a system manager can add star (*) codes to Allowed
and Disallowed Lists to help prevent toll fraud. Star codes, typically dialed before
an outgoing call, enable telephone users to obtain special services provided by
the central office (CO). For example, in many areas, a telephone user can dial

 before a telephone number to disable central office-supplied caller
identification at the receiving party’s telephone. You must contract with your
telephone service provider to have these codes activated.
When users dial star codes, the system’s calling restrictions determine whether
the codes are allowed. If they are allowed, the system’s calling restrictions are
reset and the remaining digits that the users dial are checked against the calling
restrictions.

Trunk-to-Trunk Transfer Set for Each Extension

0

This enhancement to the Transfer feature enables the system manager to allow or
disallow trunk-to-trunk transfer on a per-extension basis. In Release 3.1 and later
systems, the default setting for all extensions is restricted.

Programmable Second Dial Tone Timer

0

The system manager can assign a second dial tone timer to lines/trunks, in order
to help prevent toll fraud (for example, when star codes are used). After receiving
certain digits dialed by a user, the CO may provide a second dial tone, prompting
the user to enter more digits. If this second dial tone is delayed, and the user dials
digits before the CO provides the second dial tone, there is a risk of toll fraud or
misrouting the call. The second dial tone timer enables the system manager to
make sure that the CO is ready to receive more digits from the caller.

Security Enhancements

0

The sections below outline security measures that are implemented in
Release 3.1 and later systems.

Disallowed List Including Numbers Often
Associated with Toll Fraud

0

A factory-set Disallowed List 7 contains default entries, which are numbers
frequently associated with toll fraud. By default, Disallowed List 7 is automatically
assigned to both generic and integrated VMI (voice messaging interface) ports
used by voice messaging systems. The system manager can manually assign this
list to other extensions.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Prior Releases: Features and Enhancements
Release 3.1 Enhancements (March, 1996)

Default Pool Dial-Out Code
Restriction for All Extensions

Page xxxvi

0

The default setting for the pool dial-out code restriction (Hybrid/PBX mode only) is
restricted. No extension or remote access user with a barrier code has access to
pools until the restriction is removed by the system manager.

Default Outward Restrictions for VMI Ports

0

Ports assigned for use by voice messaging systems (generic or integrated VMI
ports) are now assigned outward restrictions by default. If a voice messaging
system must be allowed to call out (for example, to send calls to a user’s home
office), the system manager must remove these restrictions.

!

SECURITYlALERT:
Before removing restrictions, it is strongly recommended that you read
Appendix A, “Customer Support Information.”

Default Facility Restriction
Level (FRL) for VMI Ports

0

The default Automatic Route Selection (ARS) FRL for VMI ports is 0, restricting all
outcalling.

Default for the Default Local Table

0

The default Automatic Route Selection (Hybrid/PBX mode only) FRL has changed
to 2 for the Default Local table. System managers can easily change an extension
default of 3 to 2 or lower in order to restrict calling. No adjustment to the route FRL
is required.

New Maintenance Procedure for
Testing Outgoing Trunks

0

Technicians must enter a password in order to perform trunk tests.

!

SECURITYlALERT:
The enhancements in Release 3.1 help increase the security of the MERLIN
LEGEND System. To fully utilize these security enhancements, be sure to
read and understand the information in the upgrade notes and in the
relevant system guides.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
About This Book
Intended Audience

Page xxxvii

About This Book

The MERLIN LEGEND® Communications System is an advanced digital
switching system that integrates voice and data communications features. Voice
features include traditional telephone features, such as Transfer and Hold, and
advanced features, such as Group Coverage and Park. Data features allow both
voice and data to be transmitted over the same system wiring.

Intended Audience

0

This book provides detailed information about system planning. It is intended for
use by anyone who works with customers to plan, coordinate, and implement a
system, including support personnel, sales representatives, and account
executives. It is also intended for technicians who are responsible for system
installation, maintenance, and troubleshooting.

How to Use This Book

0

This book has been designed to provide optimal assistance to you in completing
the planning forms, for example:
1.

Since some chapters and/or sections apply to one or another of the
configurations (Key or Behind Switch, Hybrid/PBX, or data
communications), these sections are clearly marked, for example,
“Hybrid/PBX only.” Also, you are alerted to proceed or skip chapters or
sections that do not apply to your particular system. Proceed through this
book as appropriate.

2.

A list of forms or information that will be needed for particular procedures
appears at the beginning of each chapter and section.

3.

Where appropriate, examples of completed forms are included so you can
confirm what you have done.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
About This Book
How to Use This Book

Issue 1
August 1998
Page xxxviii

Since this book assumes that you are familiar with the system, detailed
information about equipment, features, and programming are not included. Refer
to the following documentation for additional information:
■

System Programming gives procedural instructions for programming
system features.

■

User’s guides and operator’s guides give procedural instructions for
programming and using telephone features.

‘‘Related Documents’’ on page -xlii provides a complete list of system
documentation together with ordering information.
In the USA only, Lucent Technologies provides a toll-free customer Helpline
24 hours a day. Call the Helpline at 1 800 628-2888 (consultation charges may
apply), or call your Lucent Technologies representative if you need assistance
when installing, programming, or using your system.
Outside the USA, if you need assistance when installing, programming, or using
your system, contact your Lucent Technologies authorized representative.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
About This Book
Terms and Conventions Used

Page xxxix

0

Terms and Conventions Used

The terms described here are used in preference to other, equally acceptable
terms for describing communications systems.

0

Lines, Trunks, and Facilities
Facility is a general term that designates a communications path between a
telephone system and the telephone company central office. Technically, a trunk
connects a switch to a switch, for example, the MERLIN LEGEND
Communications System to the central office. Technically, a line is a loop-start
facility or a communications path that does not connect switches, for example, an
intercom line or a Centrex line.
However, in actual usage, the terms line and trunk are often applied
interchangeably. In this guide, we use lines/trunks and line/trunk to refer to
facilities in general. Specifically, we refer to digital facilities. We also use specific
terms such as personal line, ground-start trunk, DID trunk, and so on. When you
talk to personnel at your local telephone company central office, ask about the
terms they use for the specific facilities they connect to your system.
Some older terms have been replaced with newer terms. The following list shows
the old term and the new term.
Old

New

trunk module
trunk jack
station
station jack
analog data station
7500B data station
analog voice and data station

line/trunk module
line/trunk jack
extension
extension jack
modem data workstation
ISDN terminal adapter data workstation
analog voice and modem data
workstation
MLX voice and modem data workstation
modem data-only workstation
ISDN terminal adapter data-only
workstation
MLX voice and ISDN terminal adapter
data workstation

digital voice and analog data station
analog data-only station
7500B data-only station
MLX voice and 7500B data station

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
About This Book
Terms and Conventions Used

Typographical Conventions

Page xl

0

Certain type fonts and styles act as visual cues to help you rapidly understand the
information presented:
Example

Purpose

It is very important that you follow these Italics indicate emphasis.
steps. You must attach the wristband
before touching the connection.
Italics also set off special terms.
The part of the headset that fits over
one or both ears is called a headpiece.
If you press the Feature button on an
MLX display telephone, the display lists
telephone features you can select. A
programmed Auto Dial button gives
you instant access to an inside or
outside number.

The names of fixed-feature, factory-imprinted buttons appear in bold.
The names of programmed buttons are
printed as regular text.

Choose ([W3URJfrom the display
screen.

Plain constant-width type indicates text
that appears on the telephone display
or PC screen.

To activate Call Waiting, dial 


Constant-width type in italics indicates
characters you dial at the telephone or
type at the PC.

Product Safety Advisories

0

Throughout these documents, hazardous situations are indicated by an
exclamation point inside a triangle and the word CAUTION or WARNING.

!

WARNING:
Warning indicates the presence of a hazard that could cause death or
severe personal injury if the hazard is not avoided.

!

CAUTION:
Caution indicates the presence of a hazard that could cause minor personal
injury or property damage if the hazard is not avoided.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
About This Book
Security

Page xli

0

Security

Certain features of the system can be protected by passwords to prevent
unauthorized users from abusing the system. You should assign passwords
wherever you can and limit knowledge of such passwords to three or fewer
people.
Nondisplaying authorization codes and telephone numbers provide another layer
of security. For more information, see Appendix A, “Customer Support
Information.”
Throughout this document, toll fraud security hazards are indicated by an
exclamation point inside a triangle and the words SECURITY ALERT.

!

SECURITYlALERT:
Security Alert indicates the presence of toll fraud security hazard. Toll fraud
is the unauthorized use of your telecommunications system, or use by an
unauthorized party (e.g., persons other than your company’s employees,
agents, subcontractors, or persons working on your company’s behalf). Be
sure to read “Your Responsibility for Your System’s Security” on the inside
front cover of this book and “Security of Your System: Preventing Toll Fraud”
in Appendix A, “Customer Support Information.”

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
About This Book
Related Documents

Related Documents

Page xlii

0

The documents listed below are part of the MERLIN LEGEND documentation set.
Within the continental United States, these can be ordered from the Lucent
Technologies Customer Information Center by calling 1 800 457-1235.
Document No. Title
System Documents
Customer Documentation Package1
555-661-100
555-661-110
Feature Reference
555-661-111
System Programming
555-661-112
System Planning
555-661-113
System Planning Forms
555-661-116
Pocket Reference
555-661-118
System Manager’s Guide
555-661-150
Network Reference
555-661-800
Customer Reference CD-ROM2
Telephone User Support
Analog Multiline Telephones User’s Guide
555-660-120
555-660-122
MLX Display Telephones User’s Guide
555-660-124
MLX-5® and MLX-10® Nondisplay Telephones User’s Guide
555-660-126
Single-Line Telephones User’s Guide
555-660-138
MDC and MDW Telephones User’s Guide
555-630-150
MLX-10D Display Telephone Tray Cards (5 cards)
555-630-155
MLX-16DP Display Telephone Tray Cards (5 cards)
555-630-152
MLX-28D and MLX-20L Telephone Tray Cards (5 cards)
555-630-151
MLX-10 and MLX-5 Nondisplay Telephone Tray Cards (6 cards)
System Operator Support
Analog Direct-Line Consoles Operator’s Guide
555-660-132
555-660-134
MLX Direct-Line Consoles Operator’s Guide
555-660-136
MLX Queued Call Console Operator’s Guide
Miscellaneous User Support
Calling Group Supervisor and Service Observer User Guide
555-661-130
555-640-105
Data/Video Reference
555-025-600
BCS Products Security Handbook
Documentation for Qualified Technicians
Installation, Programming, & Maintenance (IP&M) Binder
555-661-140
Includes: Installation, System Programming & Maintenance
(SPM), and Maintenance & Troubleshooting
1. The Customer Documentation Package consists of the paper versions of the System
Manager’s Guide, Feature Reference, and System Programming.
2. The Customer Reference CD-ROM contains the System Manager’s Guide, Feature
Reference, System Programming, and Network Reference.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
About This Book
How to Comment on This Book

How to Comment on This Book

Page xliii

0

We welcome your comments, both positive and negative. Please use the
feedback form on the next page to let us know how we can continue to serve you.
If the feedback form is missing, write directly to:
Documentation Manager
Lucent Technologies
211 Mount Airy Road, Room 2W226
Basking Ridge, NJ 07920

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
About This Book
How to Comment on This Book

Issue 1
August 1998
Page xliv

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

1

1

Before You Begin
Reviewing System Components

Page 1-1

Before You Begin

1

You should perform several tasks before you begin filling out the planning forms
for the system:
1.

Review the system’s hardware, features, and operation as defined at the
time of purchase.

2.

Confirm the location of the control unit.

3.

Obtain the required information from the local telephone company.

4.

Obtain information about telephone users and their needs.

5.

Obtain or develop a floor plan of the customers site.

Each of these preplanning tasks is described in this chapter.

Reviewing System Components

1

To tailor the system to the customer’s business, you must know the number and
types of telephones, outside lines/trunks, and adjuncts that were ordered. You
also need to know how the equipment will be used, for example, which type of
telephone is assigned to each employee, which consoles operators will be using,
and where adjuncts will be located.
Review the list of equipment ordered. If you did not participate in the ordering
process, you may want to confer with the customer representative who did. You
also may want to conduct a premises check to determine whether any additional
equipment is required.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

1

Before You Begin
Confirming the Location of the Control Unit

Confirming the Location of
the Control Unit

Page 1-2

1

Before installation, a room, closet, or other area must be designated where the
system control unit can be mounted on the wall. The area must meet the
environmental requirements in Table 1–1.
Table 1–1.

Environmental Requirements

Conditions

Requirements

Distances

Within 25 cable feet (7.6 m) of the network interface
(cannot be installed outdoors)
Within 1000 cable feet (304.8 m) of telephones
Within 5 cable feet (1.5 m) of a dedicated AC power outlet
(one outlet for every carrier)

Heat
Dissipation

Fully loaded basic carrier: 500 Btu/hr (35 cal/sec)
Fully loaded 2-carrier:
1000 Btu/hr (70 cal/sec)
Fully loaded 3-carrier:
1500 Btu/hr (105 cal/sec)

Power

Basic carrier: 117 VAC 60 Hz ± 5% 160 W
5.4 amps
2-carrier:
117 VAC 60 Hz ± 5% 320 W
10.8 amps
3-carrier:
117 VAC 60 Hz ± 5% 480 W
16.2 amps
one properly grounded outlet needed for each carrier
Additional outlets may be needed if installing printers and PCs.

Temperature

40° through 104°F; 4° through 40°C
(optimal temperature 60°F; 16°C)

Humidity

20% through 80% relative humidity

Ventilation

Allow at least 1 in. (2.5 cm) of space on the right and left sides of
the control unit and 12 in. (30.5 cm) above and below the
control unit to prevent overheating.

!

CAUTION:
The AC outlet for the control unit should not be switch-controlled.
Plugging the control unit into an outlet that can be turned on and off
by a switch can cause accidental disconnection of the system.
The AC outlet must be properly grounded by using an AC receptacle
for a 3-prong plug.
Do not install the control unit outdoors.
Do not place the control unit near extreme heat (furnaces, heaters,
attics, or direct sunlight).
Do not expose the control unit to devices that generate electrical
interference (such as arc welders or motors).

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

1

Issue 1
August 1998

Before You Begin
Confirming the Location of the Control Unit

Page 1-3

Do not expose the control unit to moisture, corrosive gases, dust,
chemicals, spray paint, or similar material.
Do not place anything on top of the carriers.
Do not install under any device that may drip fluid, such as an air
conditioner.
In addition, a backboard is needed to mount the system on the wall. One can be
made locally from 0.75-in. (1.9-cm) plywood. The dimensions depend on the
number of carriers, as shown in Table 1–2. A newly designed pre-drilled,
light-weight plastic backboard may be ordered (COMCODE 847007523). In some
areas, fire or electrical codes require a flame-retardant backboard. Check with the
appropriate authorities to ensure that the proper material is provided. A template
is available (COMCODE 847009206). It shows the layout for mounting equipment.
It also comes with safety, electrical, environmental, and space requirements for
the communications system.
Table 1–2.

Control Unit Space Requirements

Carrier

Requirements

Basic carrier

14" w by 23" h by 12" d
(35.6 cm by 58.4 cm by 30.5 cm)

Basic carrier + 1 expansion carrier

25" w by 23" h by 12" d
(63.5 cm by 58.4 cm by 30.5 cm)

Basic carrier + 2 expansion carriers

37" w by 23" h by 12" d
(94 cm by 58.4 cm by 30.5 cm)

Backboard
Without Systimax

6’ w by 3’ h by 0.75" d
(182.9 cm by 91.4 cm by 1.9 cm)

With Systimax

7’ w by 4’ h by 0.75" d
(213.4 cm by 121.9 cm by 1.9 cm)

It is important that the location selected for the control unit meets all of these
specifications and that the backboard is in place before installation. If the location
has already been selected and changes are needed, arrange for these changes
before installation.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

1

Before You Begin
Confirming the Location of the Control Unit

Page 1-4

1

Grounding Requirements

Proper grounding of the installation site is essential for correct and safe
functioning of the system. Grounding protects the system against:
■

Lightning

■

Power surges

■

Power crosses on outside lines/trunks

■

Electrostatic discharge (ESD)

The telephone company is responsible for providing protection of outside
lines/trunks at the entrance to the site. The protection should consist of:
■

Carbon blocks or gas-discharge tubes connected to an approved ground

■

Adequate bonding of the outside line/trunk protector ground and the
power-company ground

!

CAUTION:
Improper ground can result in equipment failures and service
outages. Verify that the AC power uses an approved ground for its
primary ground and that all voltage-limiting devices are attached to
an approved ground. Approved grounds are as follows:
■

The metal frame of the building

■

A metal water pipe connected to an underground water pipe
that is in direct contact with earth

■

An electrode encased by at least 2 inches (5 cm) of concrete
and located within and near the bottom of a concrete
foundation or footing in direct contact with earth

■

A copper ring that encircles a building and is in direct contact
with earth

For most surge occurrences, the following standard grounding requirements
provide adequate lightning and power surge protection:
■

Properly wired, grounded, and bonded outside line protectors

■

Properly wired and grounded AC outlet

■

Properly grounded single-point ground bar

■

Properly wired connection between single-point ground and power supply

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

1

Before You Begin
Confirming the Location of the Control Unit

Electrical Noise/Radio-Frequency Interference

Page 1-5

1

In most cases, electrical noise is introduced to the system through lines/trunks or
telephone cables. However, electromagnetic fields near the control unit may also
induce noise in the system. Therefore, the control unit and cable runs should not
be placed in areas where a high electromagnetic field strength exists. Radio
transmitters (AM and FM), television stations, induction heaters, motors (with
commutators) of 0.25 horsepower (200 watts) or greater, and similar equipment
are leading causes of interference. Small tools with universal motors do not
generally cause a problem when operated on separate power lines. Motors
without commutators generally do not cause interference.
Field strengths below 1.0 volt per meter are unlikely to cause interference.
Estimate the field strength produced by radio transmitters by dividing the square
root of the emitted power (in kilowatts) by the distance from the antenna in
kilometers.
This yields the approximate field strength in volts per meter and is relatively
accurate for distances greater than about half a wavelength (492 feet, or 150 m,
for a frequency of 1000 Hz).
To comply with FCC Part 15 requirements, each power supply on a newly
installed system must have a ferrite core installed around the AC power cord and
ground wire. Beginning with Release 2.1 this ferrite core is packaged with the
power supply module at the factory. Ferrite cores are also compatible with earlier
releases.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

1

Before You Begin
Requirements for Supporting CTI Applications

Requirements for Supporting CTI
Applications

Page 1-6

1

If your site will take advantage of the Computer Telephony Integration (CTI)
capabilities of the MERLIN LEGEND Communications System (Release 5.0 or
later), each Client Desktop must have one extension associated with a computer
that is networked to a Telephony server which in turn is connected to the MERLIN
LEGEND Communications System through a CTI link. Figure 1–1 on page -7
shows the system configuration for support of CTI applications.
Use the following resources and procedures to implement a CTI application.
1.

2.

Complete the appropriate MERLIN LEGEND/Telephony Services
Preliminary Survey for the application being sold.
■

The Preliminary Survey is available from the SDSC Techni-Fax
(1 888 297-4700 select the appropriate prompts), or from
IntraWorks at http://www.bcs.lucent.com/tech_info/sdsc/forms.

■

The survey is completed by the A. E. and Customer.

Contact the Sales and Design Support Center (SDSC) for CTI pre-sale
support.
■

3.

The A.E. should contact the SDSC (1 888 297-4700 select the
appropriate prompts to reach the MERLIN LEGEND split) to discuss
customer requirements and potential solutions. If the CTI solution is
deemed appropriate, then the A.E. must obtain the appropriate
MERLIN LEGEND/Telephony Services Preliminary Survey.

Return the completed Survey after the sale is made.
■

The A.E. will coordinate and monitor the relationship between the
OEM and the customer.

■

The A.E. will put the DOSS Order Number on the completed survey.

■

For Phonetastic:
— Fax the completed survey to the Phonetastic™ Outsource
Partner Desk (1 801 984-1120, Attention Phonetastic
Outsource Coordinator).

■

The OEM will assign an Outsource Partner.

■

The OEM will establish an implementation date with the customer.

■

The OEM Outsource Partner will complete the Statement of Work
(SOW) for the customer.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

1

Before You Begin
Requirements for Supporting CTI Applications

4.

5.

Page 1-7

Statement of Work (SOW)
■

Defines all duties performed by the OEM Outsource Partner.

■

Defines customer expectations.

■

Defines customer responsibilities.

■

Once the customer and the Outsource Partner have signed the
SOW, it will be sent back to the A.E. to be included in the customer
contract package.

Implementation Considerations for OEM Outsource Partners
■

Application installation requires a six-week interval. Early
coordination will be required to enable a smooth implementation.

Incoming/Outgoing
Calls
LAN
Client Desktop

MERLIN LEGEND
Release 5.0 or later
Telephony Server
CTI Link

Public
Network

Figure 1–1.

System Configuration for Support of CTI Applications

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

1

Issue 1
August 1998

Before You Begin
Requirements for Supporting CTI Applications

Page 1-8

For this configuration you must have the following equipment and software:
■

An Intel i386, Intel i486, or Pentium Class computer with at least
16 megabytes of RAM. Additional memory may be needed if additional
applications will be running on the server machine. Refer to the MERLIN
LEGEND Network Manager’s Guide form more information.

■

One of the following configurations:
— Novell NetWare® Version 3.12, 4.1 or 4.11
■

MERLIN LEGEND PassageWay Driver Version 1.1 or later
installed

■

Telephony Services for NetWare software, Release 2.2.1 or
later installed

■

An Eicon SCOM ISDN BRI card for the CTI link

■

A free 8- or 16-bit ISA slot for the ISDN BRI card

■

5 megabytes of disk space on the SYS (system) volume

■

Either Interrupt 2 or Interrupt 3 available

— Microsoft Windows NT® 4.0 Server or Windows NT 4.0 Workstation
■

■

MERLIN LEGEND NT PBX Driver Version 1.0 or later
installed
CentreVu® Computer-Telephony Release 3.1 or later
installed

■

An Eicon DIVA Version 2.0 ISDN BRI card for the CTI link

■

5 megabytes of disk space available

■

A free 16-bit ISA slot for the ISDN BRI card

■

System software Release 5.0 or later installed on the MERLIN LEGEND
Communications System

■

The MERLIN LEGEND Communications System configured in Hybrid/PBX
mode

■

An MLX port board (using firmware version 28 or later, except Version 29)
installed in the MERLIN LEGEND Communications System
NOTE:
If you have Version 29, replace the board with an appropriate
version, or for a replacement card, call the TSO at: 1 800 628-2888.

■

If the MERLIN LEGEND Communications System has only one MLX port
board, you will also need System Programming and Maintenance (SPM)
software, Version 5.15 or later to program your CTI link.

■

One port on an MLX port board is used for the link. Select from ports 2, 3,
4, 6, 7, or 8 . The CTI link port cannot be the potential operator port or the
console programming port.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

1

Before You Begin
Requirements for Supporting CTI Applications
■

Page 1-9

For a NetWare 3.12 installation, ensure that NWSNUT.NLM, Version 4.11
or later, and TUI.NLM, Version 1.04 or later, is obtained from Novell and
installed in the SYS:\SYSTEM directory.
NOTE:
To obtain these NLMs from Novell, access either the Novell web site
(http:\\www.novell.com) or the Novell FTP site (ftp.novell.com). First
download IPXRT4.EXE and follow the directions in the associated
readme file. Then, download NWSNUT.NLM and TUI.NLM.

■

For a Windows NT installation, the required .DLLs and drivers will be
provided on a CD-ROM.

For more information on setting up the system see the MERLIN LEGEND
Communications System Network Manager’s Guide.

Environmental Specifications

1

If the Telephony Server platform and the MERLIN LEGEND Communications
System are to share an equipment room, the room’s environment (temperature,
humidity, contaminants, EMI, AC power and grounding) must meet the more
demanding set of environmental specifications for the two units. Refer to the
specifications for each hardware platform for details.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

1

Before You Begin
Obtaining Telephone Company Information

Obtaining Telephone Company
Information

Page 1-10

1

To fill out many of the forms, especially forms involving incoming lines/trunks, you
need to obtain information from the local telephone company. Before you speak
with the local telephone company, make sure you understand your customer’s
company requirements regarding the communications system. Some of the
information you will need to know includes:
■

Which incoming line/trunk connects to each channel on each 100D
module, and the order in which the lines/trunks are assigned

■

The Service Profile Identifier (SPID) and Directory Number (DN)
associated with each channel on each 800 NI-BRI module

■

Whether the disconnect signals for loop-start lines/trunks are reliable or
unreliable, and the length of the Hold disconnect interval

Information the local telephone company can provide includes:
■

Detailed T1 parameters

■

Detailed NI-1 BRI parameters

■

The number of digits sent on DID trunks

■

Which lines/trunks, if any, require a toll-call prefix

■

The telephone number for each incoming line/trunk

■

The type(s) of incoming lines/trunks (loop-start, ground-start, and so on)

■

Which lines/trunks, if any, are rotary-dial lines/trunks

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

1

Before You Begin
Obtaining User Information

Obtaining User Information

Page 1-11

1

The features and calling privileges you assign to each employee’s telephone
ensure that employees get the most benefit from the system. If you were not
involved in the planning and equipment-ordering for the system, you should
discuss the system’s design with the customer representative who took part.
To determine calling privileges, answer the following questions:
■

Does management want to allow both local and toll calls to be made from
every telephone?

■

If any telephones are restricted, are there any numbers the users should be
allowed to call?

■

Are there any specific numbers (such as 900) that you want to restrict
users from calling?

■

Who, if anyone, will be given personal lines?

■

Will access to central office lines/trunks (outside lines) be restricted to
certain employees?

■

Do any departments (such as sales and service) receive frequent special
calls that should come to them directly, bypassing a system operator?

■

Do any departments or extensions need to screen incoming calls?

You may want to use the Employee Communication Survey form to determine
each employee’s telecommunications needs. A copy of this form is in Appendix B
and is included in the forms package. Since a survey form should be completed
for each user, make as many copies of the form as you need.
If it is not feasible for each employee fill out a form, get the information you need
from a knowledgeable person in each department, section, or work group. This
person should have sufficient information and authority to make decisions about
calling features and coverage assignments for others in the department.
Use the information in Table 1–3 to interpret and analyze the results of the
Employee Communication Survey. Numbers for items in the Required Information
column correspond to question numbers on the survey.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

1

Before You Begin
Obtaining User Information

Table 1–3.

Issue 1
August 1998
Page 1-12

Employee Communications Survey: Description of Questions

Required Information

Description

1. Types of lines/trunks
(outside lines) used

Indicates toll-calling habits. In most cases, assigning a
button for each line/trunk is not necessary; the use of
Automatic Route Selection (Hybrid/PBX mode only)
ensures that the preferred line/trunk is selected.

2. Calls covered by someone
else (sender)

Suggests that this employee should be assigned as a
sender in either an Individual or a Group Coverage
arrangement, particularly if calls are covered by someone
other than the operator.

3. Shares lines/telephone
numbers

Identifies Shared System Access buttons and/or common
personal line appearances.

4. Covers someone else’s
calls (receiver)

Suggests assignment as a receiver in someone else’s
Individual or Group Coverage arrangements.

5. Shares incoming calls

Identifies calling group needs.

6. Frequency of use

Identifies heavy and light telephone users. Heavy users
may benefit from additional System Access buttons
and/or an additional System Access Originate Only
button.

7. Data needs

Identifies existing and potential data terminal and
personal computer users.

8. Use of account codes

Identifies current account codes used for charge-back of
calls if there is a programmed Account Code button on the
telephone and if the system includes Call Accounting
System (CAS).

9. Frequently dialed numbers

Identifies useful numbers for the System Speed Dial list.

10. Picks up calls

Identifies need for a Pickup group.

11. View incoming caller
information

Identifies which telephone users need call screening
capabilities. This service may be part of the local
telephone company’s services, if available, and must be
subscribed to.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

1

Before You Begin
Obtaining a Floor Plan

Obtaining a Floor Plan

Page 1-13

1

You may want to use a floor plan to make planning more manageable and to
ensure that the correct telephone equipment is assigned to each employee. If the
customer does not already have a floor plan showing the location of system
equipment, you should create one. Use the symbols shown in Figure 1–2 and the
following instructions:
1.

Use a large sheet of paper and sketch the office layout. The location of
office walls and other partitions is important when features are assigned to
telephones that must be within hearing range of each other. For example,
pickup group members must be able to hear each others’ telephones
ringing.

2.

Indicate the location of each employee’s telephone, other locations that will
have a telephone (such as a conference room), and the locations of data
terminals, PCs, and host computers.

3.

Indicate the type of telephone at each location, using an abbreviation that
includes the number of programmable buttons. For example, write MLX-10
at 10-button MLX telephones, MLX-20L at 20-button MLX display
telephones, BIS-34 at 34-button analog multiline telephones, and so on.

4.

Indicate the type of adjunct at each location. For example, write FAX,
ana. modem (analog modem), headset, or other type of adjunct beneath
the symbol.

5.

Indicate any additional equipment, such as a Station Message Detail
Recording (SMDR) printer, Call Accounting System device, equipment
required for off-site telephones, and so on.

6.

Indicate the locations where AC power is available and/or required, for
example, for a Multi-Function Module (MFM), a console with two Direct
Station Selectors (DSSs), or an Integrated Services Digital Network (ISDN)
terminal adapter (such as the Ascend Pipeline™ 25 or 50).

The floor plan does not need to be elaborate or to scale. Keep the floor plan on
hand. Refer to it during planning and complete it (by filling in extension numbers)
when you get to Numbering the System in Chapter 2.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

1

Before You Begin
Obtaining a Floor Plan

Page 1-14

HORN
PRESIDENT'S
OFFICE

PLANT AREA

PLANT MANAGER'S
OFFICE

VICE
PRESIDENT'S
SECRETARY

PRESIDENT'S
SECRETARY

FAX
ANS. MACH.
VICE
PRESIDENT'S
OFFICE

SALES
DEPARTMENT
FAX
WAREHOUSE
ANS. MACH.

RECEPTION
DRAFTING
DEPARTMENT
CONFERENCE
ROOM

DSS
ACCOUNTING
DEPARTMENT

SUPPLY
ROOM
SHIPPING & RECEIVING

FAX

Figure 1–2.

MLX
Telephone

Single-line
Telephone

Computer
or Data
Terminal

Analog
Multiline
Telephone

Operator
Position

Adjunct

Sample Floor Plan

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration

Page 2-1

2

Control Unit Configuration

2

After you have completed the preplanning tasks described in Chapter 1, “Before
You Begin”, you can plan the control unit configuration. Planning the control unit
configuration consists of the following tasks:
1.

Planning Module Placement. Calculate the system’s line/trunk and
extension capacity according to the number of module types; then map out
the placement of the modules on the Control Unit Diagram.

2.

Recording System Operating Conditions. Note the system’s type of
programming equipment, it’s mode and language choice, and whether the
Automatic Maintenance Busy feature is to be enabled or disabled.

3.

Numbering the System. Decide the order in which to connect the
telephones and other equipment to the control unit based on the
customer’s needs and applications. Determine whether the
system-assigned extension numbers are appropriate for the customer’s
business or if they need to be renumbered.

This chapter contains instructions for completing each of these tasks.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Planning Module Placement

Planning Module Placement

Page 2-2

2

In addition to the processor module and power supply module, the system
supports several types of line/trunk and extension modules. Deciding how to
place the modules in the carriers consists of the following tasks:
1.

Calculating the system’s line/trunk capacity according to module types

2.

Calculating the system’s extension capacity according to module types

3.

Mapping out module placement on the Control Unit Diagram, according to
specific guidelines

This section contains instructions for each of these tasks.
For information about calculating unit load requirements, see Appendix F, “Unit
Load Calculation”.
For detailed information about modules and their specifications (including
line/trunk and extension capacity), see the descriptions of hardware components
contained in the Pocket Reference.

2

Forms Needed
■

Equipment List (if available)

■

Form 1, System Planning

Capacity for Lines/Trunks

2

Line/trunk capacity is the number of lines/trunks that can be connected to the
control unit. This section contains instructions for calculating the systems capacity
for lines/trunks, according to the system’s module types.

Planning Form Instructions
1.

In the table in the Line/Trunk Capacity section of Form 1, System Planning,
fill in the number of each type of line/trunk module on the appropriate line of
the Number of Modules column.

2.

Add the column and record the result at the bottom of the column on the
System Totals line.

3.

For each module type noted, multiply the value in the Number of Modules
column by the value in the Trunks Supported by Module column; write the
results in the appropriate row under Total Trunks by Module Type.

4.

Add the column and record the total line/trunk capacity of the system at the
bottom of the column, on the System Totals line.

2

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Planning Module Placement

Capacity for Extensions

Page 2-3

2

Extension capacity is the number of extensions that can be connected to the
control unit. In most cases, the number of physical jacks on the modules indicates
capacity. Most loop-start and ground-start modules have one or two power-failure
transfer (PFT) jacks used to connect a single-line telephone in case of a power
failure, and not counted in system capacity. Every four line jacks has one
associated PFT jack.
One extension number is automatically assigned to each extension jack, whether
or not equipment is connected to it, except for the 008 MLX, 408 GS/LS-MLX, and
008 OPT modules:
■

008 MLX and 408 GS/LS-MLX Modules. Two extension numbers are
assigned to each physical jack: the first for an MLX telephone and the
second for any equipment connected to the telephone through an MFM,
ISDN terminal adapter (such as the Ascend Pipeline 25 or 50), or any 2B
data desktop video endpoint.
NOTE:
When using the 008 MLX or 408 GS/LS-MLX module for data or
video, you must use Version 28 of the module.

■

008 OPT Module. The system recognizes this module as an 012 module.
Therefore, even though the OPT module has only 8 physical jacks, it uses
12 ports of capacity. An extension number is assigned to each of the 8
physical jacks.

This section contains instructions for calculating the system’s extension capacity,
according to the number of certain module types.

Planning Form Instructions
1.

In the table under the Extension Capacity section of Form 1, fill in the
number of each type of extension module on the appropriate line of the
Number of Modules column.
■

Each 100D module is assigned 24 logical IDs, even though the
module has only 1 physical trunk jack.

■

Each 800 NI-BRI module is assigned 2 logical IDs per physical trunk
jack for a total of 16 logical IDs.

2.

Add the column and record the result at the bottom of the column
(System Totals line).

3.

For each module, multiply the value in the Number of Modules column by
the value in the Physical Jacks per Module column and record the results
on the appropriate line in the Physical Jacks by Module Type column.

4.

Add the column and record the results at the bottom of the column
(System Totals).

2

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Planning Module Placement

5.

Page 2-4

To determine the number of extensions assigned for each module type,
multiply the value in the Physical Jacks by Module Type column by the
value in the Extensions Assigned column and write the results in the
appropriate row in the Total Extensions Assigned column.
NOTE:
Since the system assigns an additional four extensions to each
008 OPT module, you must first calculate the Extensions Assigned
by multiplying the number of 008 OPT modules (noted in the Number
of Modules column) by 4 and then add this subtotal to the number
noted in the Physical Jacks by Module Type column.

6.

Add the column and record the result at the bottom of the column
(System Totals).

Control Unit Diagram—Module Placement

2

This section describes how to use the Control Unit Diagram on Form 1 (page 2) to
map the placement of the modules according to certain guidelines. Figure 2–1 on
page -6 provides an example of a Control Unit Diagram for a system with 32
lines/trunks and 52 extensions. In addition, this section describes how to identify
each jack on each module with respect to type (line/trunk or extension) and its
associated logical ID. Each physical jack on the control unit is numbered
sequentially from bottom to top and left to right with logical IDs as follows:
■

Extension jacks are numbered from 1 to 200.

■

Line/trunk jacks are numbered from 1 to 80.

This sequence of logical IDs is the basis for connecting components to the control
unit, as well as for the assignment of extension numbers and line/trunk numbers.

Planning Form Instructions
NOTE:
The Unit Load blocks above the diagram are reserved for equipment
changes or maintenance. A Lucent Technologies representative or
authorized dealer computes these values manually.

2

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Planning Module Placement

1.

Issue 1
August 1998
Page 2-5

On the Control Unit Diagram of Form 1 (page 2), record the type of module
to be installed in each slot by writing the module name (for example,
008 MLX) on the slanted lines at the top of each slot. Use the following
guidelines:
■

Indicate the power supply module in the far left slot of each carrier.

■

Indicate the processor module in Slot 00 of the basic carrier.

■

Indicate line/trunk and extension modules in any order in Slots 01
through 17, with the following conditions:
— Group the modules in each carrier from left to right with no
empty slots between modules. (The system does not
recognize modules in slots that follow an empty slot; slots to
the right of the last module can be left empty.)
— (Hybrid/PBX mode only) If the system includes a Queued
Call Console (QCC), the first line/trunk and/or extension
module must be a 408 GS/LS-MLX or 008 MLX module.
— (All modes) Current 012 T/R, 008 OPT, and 016 T/R modules
have built-in ring generators and are compatible with earlier
releases. The 012 T/R module [517J13 (28)] has a ring
equivalency number (REN) of 2.2 and rings only four ports at
a time, although eight jacks can be used for applications. The
016 T/R module (517C34) has a REN of ≥ 4, can ring 16
ports at a time, and has no restriction on the number of jacks
that can be used for applications.
— Group all 800 DID, 100D, 800 NI-BRI, and 400EM modules
together according to type; this helps save time in system
programming.

NOTES:
1. Due to limitations in the 391A, 391A1, and 391A2 power supplies, the
number of 800 NI-BRI modules plus 100D modules in a single carrier
cannot exceed three. If you have more than three modules, you must
install the additional modules in an expansion carrier. This restriction
does not apply to the 391C1 or 391A3 power supply.
2. In Release 6.0 or later, if the switch is part of a private network and a
tandem PRI trunk (programmed as Legend-PBX or Legend-NTWK) has
some B-channels that would bring the total number of trunks over the
system limit of 80, the 100D module for that tandem PRI trunk should be
placed in the last slot in the carrier. In this manner, the 100D module will
contain the last lines in the system, and any B-channel over the 80
line/trunk limit will be ignored. However, the D-channel will still function
even if the 100D module exceeds the line capacity of the system. The
number of B-channels must be the same on each networked system. See
the Network Reference for additional information.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Control Unit Configuration
Planning Module Placement

2.

Page 2-6

For each line/trunk and extension jack of each module, write the type of
jack (X = extension; and L/T = line/trunk) and the associated logical ID,
keeping in mind the following:
■

Each 100D module is assigned 24 logical IDs, even though the
module has only 1 physical trunk jack.

■

Each 800 NI-BRI module is assigned 2 logical IDs per physical trunk
jack for a total of 16 logical IDs.

■

The 008 OPT module is assigned 12 logical IDs, even though the
module has only 8 physical extension jacks.

■

Power-failure transfer (PFT) jacks are not assigned logical IDs.

NOTES:
1. If the system will have one or more PFT telephones (maximum: 20),
indicate on the Control Unit Diagram the modules that will have PFT
telephones connected to their PFT jacks; write PFT in the modules. A PFT
telephone can be connected to a PFT jack on a 400 LS, 400 GS/LS/TTR,
800, 800 GS/LS, 800 GS/LS-ID, 408, 408 GS/LS, or 408 GS/LS-MLX
module. Touch-tone PFT telephones must be connected to jacks with
touch-tone lines/trunks.

Power
Supply

00

01

L/T8
L/T7
L/T6
L/T5

X16
X15
X14
X13
X12
X11
X10
X9

X24
X23
X22
X21
X20
X19
X18
X17

02 03

L/T12
L/T11
L/T10
L/T9

X32
X31
X30
X29
X28
X27
X26
X25

04 05

BASIC CARRIER

Figure 2–1.

Ring Generator

X8
X7
X6
X5
X4
X3
X2
X1

L/T4
L/T3
L/T2
L/T1

80
0

GS
80 /LS
0

40
8

L/T24 L/T32
L/T23 L/T31
L/T22 L/T30
L/T21 L/T29
L/T16 L/T20 L/T28
L/T15 L/T19 L/T27
L/T14 L/T18 L/T26
X44 L/T13 L/T17 L/T25
X43
X42
X41
X40
X39
X38
X37
X36
X35
X34
X33

X52
X51
X50
X49
X48
X47
X46
X45

06 07 08 09 10 11
EXPANSION CARRIER

Sample Control Unit Diagram

Power
Supply

Ring Generator

Power
Supply

01
2

ML
40 X
0
GS
/LS
/TT
R

OO
8

40
8

OO
8

M
40 LX
8

2. You need a ground-start button on a PFT telephone connected to a
ground-start trunk.

Ring Generator

2

12 13 14 15 16 17
EXPANSION CARRIER

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Recording System Operating Conditions

Recording System Operating
Conditions

Page 2-7

2

This section contains instructions for recording the following system operating
conditions:
■

Programming equipment to be used and its extension jack assignment

■

Mode of operation

■

Language choice

■

Enable and disable Automatic Maintenance Busy

■

A reminder to set the system date

■

Backup schedule

■

Identifying system console extensions

■

Second Dial Tone Timer

■

Identifying system applications

2

Forms Needed
Form 1, System Planning

Programming Equipment

2

Two types of equipment can be used for system programming:
■

An MLX-20L telephone identified as a system programming console. The
telephone is connected to the first (lowest) extension jack (which is
factory-set for system programming) on the first MLX module.

■

A personal computer with System Programming and Maintenance (SPM)
software. The PC connects to the lowest jack on the processor module.

Planning Form Instructions
1.

Under the Programming Equipment heading in the System Operating
Conditions section on Form 1 (page 2), do one of the following:
■

If the system will use a system programming console, check the
System Programming Console box.

■

If the system will use a PC with SPM software, check the PC with
SPM Software box.

NOTES:
1. In conjunction with the MLX-20L telephone and the PC, a PCMCIA card is
required for Release 3.0 and later of the communications system. Check
the box labeled PCMCIA Memory Card.
2. The first (lowest) extension jack on the first MLX module is factory-set for
system programming and as the primary operator position. Since the
primary operator position cannot be reassigned, you may want to change
the system programming assignment to ensure that future programming
sessions do not interfere with the operator’s work.

2

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Recording System Operating Conditions

2.

3.

Page 2-8

Do one of the following:
■

If you checked System Programming Console, proceed to Step 3.

■

If you checked PC with SPM Software, skip to the next section,
“System Mode.”

To change the factory-set system programming jack, write in the new
logical ID using the information from the Control Unit Diagram.

If you want the system programming jack to be different from that of system
operators, change the programming assignment to any one of extension jacks 2
through 5 on the first MLX module in the control unit (the lowest jack on the
module is extension jack 1). You fill in the extension number of the jack later.

2

System Mode

The mode of operation determines how outside lines/trunks are provided to users,
the types of operator consoles allowed, the features available, and how they work.
Each system is registered with the Federal Communications Commission (FCC)
to operate as a Private Branch Exchange (PBX), Hybrid, or Key system (factory
setting). However, you can program the system to operate in any of the three
modes: Hybrid/PBX, Key, or Behind Switch.

Planning Form Instructions
Under the System Mode heading in the System Operating Conditions section of
Form 1 (page 2), check one of the following:
■

If the system will operate in Key mode, check Key. (This is the factory
setting.) If need be, this mode can be changed to Hybrid/PBX mode at
another time.

■

If the system will operate in Hybrid/PBX mode, check Hybrid/PBX.

■

If the system will be connected behind a larger system or a Centrex
system, check Behind Switch and record the host’s dial codes for the
Transfer, Conference, and Drop features so users can access these
features on the larger system.

■

If you check Permanent Key, the switch in the back of the processor
module must be placed in the Permanent Key position. The switch cannot
be changed without changing the FCC registration of the system.

2

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Recording System Operating Conditions

Language Selection

Page 2-9

2

In Release 1.1 and later versions of the system, language-specific operation is
available in English, French, and Spanish. The language selection affects
prompts and displays on user telephones, SPM system programming displays,
SMDR records, and printed reports.
This feature works as follows:
■

The MLX-10D, MLX-20L, and MLX-28D display telephones, and the
MLX-10 nondisplay telephones are available in three separate versions,
each with the factory-set buttons in the language of choice.

■

The system can be programmed to operate in one of the languages, but an
individual with an MLX telephone can override the system language by
selecting any one of the three languages for his or her own telephone.

This section describes how to record the selected language for the system and, if
desired, to set a different language for SMDR and printers.
NOTE:
If you plan to set a different language for an individual telephone, record the
language selection on Form 6b as described in Chapter 4, “Features”.

Planning Form Instructions:
Under the Language Selection heading in the System Operating Conditions
section of Form 1 (page 2):
1.

To select a systemwide language, check one of the following: English (the
factory setting), French, or Spanish.

2.

To set a different language for SMDR, check one of the following: English
(the factory setting), French, or Spanish.

3.

To set a different language for printed reports, check one of the following:
English (the factory setting), French, or Spanish.

2

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Recording System Operating Conditions

Automatic Maintenance Busy

Page 2-10

2

The factory setting for Automatic Maintenance Busy is Disable, which means that
faulty lines/trunks are not automatically put in a maintenance-busy state.
In Key and Behind Switch modes, Automatic Maintenance Busy usually remains
disabled. If you plan to group lines/trunks into pools in Hybrid/PBX mode, enable
Automatic Maintenance Busy to provide optimal system performance.
For a detailed description of this feature (including considerations and feature
interactions), see the Feature Reference.

2

Planning Form Instructions
Under the Automatic Maintenance Busy heading in the System Operating
Conditions section of Form 1, page 2, do one of the following:
■

To keep the factory setting (no maintenance-busy state), check Disable.

■

To enable Automatic Maintenance Busy, check Enable.

Set System Date

2

The system date is the month, day, and year, shown on display telephones and
SMDR reports. For information on SMDR, see “System Features” in Chapter 4.
Error reports used by authorized technicians for maintenance also show the
system date and time.
These sections on the planning form remind you to set the system date when you
perform the initial programming for the system.

Planning Form Instructions
Check Yes under the Set System Date heading on Form 1 as a reminder to set
the current date.

2

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Recording System Operating Conditions

Page 2-11

2

Backup

Backup makes a copy of the customized system data on a translation memory
card. A backup is made after each system upgrade, service technician visit, or
major system reconfiguration.
NOTE:
If Automatic Backup is used, the customer must ensure that a valid
PCMCIA Translation card is in the processor slot at the time of the backup.
Otherwise, the Automatic Backup feature will be canceled and the
customer must reset it.

2

Planning Form Instructions
Check Automatic if weekly or daily backup procedures are planned. Record the
day and time in the blank space for weekly backups or the time of day for daily
backups.
Check Manual if you plan manual backup procedures.

System Consoles

2

To make programming easier, use this section to summarize information about the
consoles in the system.

Planning Form Instructions
Under the System Consoles heading, check the type(s) of consoles:
■

For Queued Call Consoles, check the QCC(s) box and enter the extension
numbers (if known).

■

For Direct-Line Consoles, check the DLC(s) box and enter the extension
numbers (if known).

2

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Recording System Operating Conditions

Second Dial Tone Timer

Page 2-12

2

In some instances, after dialing a star code the CO responds with a second dial
tone as a prompt to enter additional digits. Once a star code is accepted by the
communications system, the Second Dial Tone Timer is activated and set to the
programmed value. If dialing is attempted before the Second Dial Tone Timer
expires, the call is treated as though it had violated calling restrictions and is not
completed.

!

SecurityAlert:
If the Second Dial Tone Timer is set to 0 ms and a caller begins dialing
additional digits before the second dial tone, system restrictions may be
bypassed and a restricted call may be routed. Careful administration of the
Second Dial Tone Timer prevents the caller from bypassing call restrictions
in this manner.

Marked System Speed Dial entries (entries that do not display) are not affected by
the Second Dial Tone Timer setting. If the Central Office does not immediately
supply dial tone when a star code is entered and a Marked System Speed Dial
entry uses star codes, then the appropriate number of pauses (each 1.5 seconds)
must be programmed in the entry following each star code.

2

Planning Form Instructions
Under the Second Dial Tone Timer heading, enter the desired value. Valid entries
are 0–5000 ms, in increments of 200 ms. The factory setting is 0.

2

Applications

Several call-handling and management applications can be used with the system,
including voice mail and messaging; call accounting and reporting; and call
management, distribution, and reporting. This section contains instructions for
noting those applications that will be used with this system.

!

CAUTION:
General information about these applications is contained in the Feature
Reference. However, to ensure proper service, you must review the
documentation provided with the application itself.

Planning Form Instructions
On Form 1 (pages 3 and 4):
1.

Check the name of each application that will be connected to the system.

2.

For each application name you check, you may want to include pertinent
information in the Notes section. For example, you can note the version of
the application installed at the customer’s site.

2

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Numbering the System

Page 2-13

2

This section describes the assignment of numbers to extensions.
NOTE:
Assigning numbers to calling groups, paging groups, park zones, and
remote access is described later in this book.
The process of numbering extensions consists of the following tasks:
■

Identifying Extension Jacks. Using the placement of modules in the
control unit as a guide (see the Control Unit Diagram on Form 1),
determine the order in which to connect telephones and other equipment to
the control unit. To do this, identify the extension jack types available by
module and then match system components (for example, operator
positions or telephone types) with the jacks that support them.

■

Renumbering. If the system-assigned extension numbers are not
appropriate for the customer’s business, change them. The system offers
two automatic numbering plans (2-digit and 3-digit numbers), as well as the
option of creating a unique numbering plan with extension numbers of 1 to
4 digits. Each of these three plans allows renumbering of all or selected
extensions.

■

Updating Planning Information. Add information to Form 1 and to the
floor plan as appropriate.

This section contains instructions for completing each of these tasks. The Feature
Reference provides detailed information about system numbering and the three
numbering plans.

Forms Needed
■

Floor plan

■

Equipment List (if available)

■

Form 1, System Planning

■

Form 2a, System Numbering: Extension Jacks

■

Form 2b, System Numbering: Digital Adjuncts

2

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Identifying Extension Jacks

Page 2-14

2

Identifying extension jacks consists of the following tasks:
■

Determining which extension jack types are available according to the
types of modules in the control unit.

■

Matching the telephones and other equipment to the jacks that support
them, in the following order:
— Primary operator position
— Additional operator positions
— CTI link port
— Extension jack pairs (for analog multiline telephones only with Voice
Announce to Busy feature and/or voice and data)
— MLX telephones
— Analog multiline telephones
— Tip/ring equipment and applications

2

Planning Form Instructions
Before you begin, review the floor plan and Equipment List (if available) to identify
the equipment and the number of each kind of connection needed, as well as to
obtain other information you need to fill in the forms:
■

Number, type(s), and user name and/or location of operator consoles

■

Number and user name and/or location of analog multiline telephones that
will use the Voice Announce to Busy feature or voice and data

■

Number of non-operator MLX telephones and user names and/or locations

■

Number and user name and/or location of analog multiline telephones

■

Number and user name and/or location of tip/ring equipment

■

Names of optional applications

Module Types and Extension Jack Types

2

The module type determines the type of extension jack used. For example, the
016 T/R module has 16 basic telephone jacks. Table 2–1 lists the extension jack
types and the equipment that can be connected to these jacks.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Table 2–1.

Issue 1
August 1998
Page 2-15

Application Ports

Module

Ext.
Jack Type

No.
of Jacks Used to Connect

008
408
408 GS/LS

Analog

8
8
8

Analog multiline telephones
TransTalk Wireless telephones
Call Management System (CMS)*

008 MLX

Digital

8

MLX telephones with or without PassageWay
Direct Connect Solution
CTI link
Desktop video endpoints† and/or
Group Video endpoints†
Digital data devices, such as an ISDN terminal
adapter†**

408 GS/LS-MLX

012
016

8

Basic
Telephone

008 OPT

MERLIN
LEGEND Mail

Analog

12
16

Tip/ring equipment, such as:
Single-line telephones
Delay Announcement Devices
Adjuncts, such as analog modems or fax
machines or MERLIN® Identifier
Optional applications:
Enhanced Service Center
Messaging 2000
Intuity™ AUDIX VS
MERLIN MAIL® Voice Messaging System*
AUDIX® Voice Power (IS II or III)*

8‡

Tip/ring equipment in another building or off
premises
Off-Premises Range Extender

0§

Provides MERLIN LEGEND Mail

* No longer orderable.
† When using the 008 MLX or 408 GS/LS-MLX module for data or video, you must use Version 28 of
the module.
** ISDN terminal adapters include such devices as: Ascend Pipeline 25PX or 50.
‡ The system uses 12 logical IDs for an 008 OPT module, even though only eight will have equipment
attached to them. Do not use an 008 OPT module for applications (such as MERLIN LEGEND Mail,
Messaging 2000, or Intuity AUDIX VS). Be sure to leave the extra four ports blank on Form 2a.
§
The MERLIN LEGEND Mail module has 7 dedicated internal ports, but assigns 12 total extensions.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Page 2-16

2

Planning Form Instructions
Refer to the completed Control Unit Diagram (Form 1) and Table 2–1 above to
mark the extension jack types on Form 2a:
1.

For each extension module noted in the Control Unit Diagram (beginning
with Slot 01), write in the type of module in the Mod. Type column of
Form 2a and, after the appropriate logical ID (Log. ID) number, draw a line
to indicate the end of that module.
For example, if the first module in the control unit is an 008 MLX module
that has eight jacks, write 008 MLX in the Mod. Type column and draw a
line after Logical ID 8.
NOTE:
If your list includes an 008 OPT module, draw a line after the twelfth
logical ID, but cross off the last four logical IDs, since these jacks
cannot be used to physically connect telephone equipment. The
extension numbers of these logical IDs can be used, however, for
applications requiring phantom extensions.

2.

In the Jack Type column of Form 2a, do one of the following to indicate the
type of each extension jack next to its logical ID:
■

If the jack is analog, check A.

■

If the jack is digital, check D.

■

If the jack is basic telephone, check B.

You are now ready to match the system telephones and other equipment to these
available jacks. After calculating touch-tone receivers as described in the next
section, begin matching equipment and jacks with Jack for Primary Operator
Position, and proceed through the subsequent sections as appropriate for the
system.

Touch-Tone Receivers (TTRs)

2

Use these guidelines for calculating the system requirements for touch-tone
receivers for systems both with and without a voice messaging system (VMS).
The number of TTRs needed in a MERLIN LEGEND system should be calculated
before the system is installed so that you can order the modules required to
supply the TTRs. However, as the volume of calls increases and more
applications are added to the system, TTRs may also need to be added. A system
that exhibits one or more of the following symptoms may need more TTRs:
■

Single-line telephone users do not get dial tone when they lift the handset
to dial out.

■

The voice messaging system fails to transfer calls.

■

Calls fail to ring or go to coverage prematurely.

■

Reorder tone on UDP/ARS calls using tandem tie trunks.

■

Delay in MWL tie trunks when tie trunks are available.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Page 2-17

Table 2–2 lists the modules that supply TTRs to the MERLIN LEGEND
Communications System.
Table 2–2.

Modules with Touch-Tone Receivers

Module

Number of TTRs

008 OPT

2

012 T/R

2

016 T/R

4

400 GS/LS/TTR

4

400 LS

4

800 DID

2

800 GS/LS-ID

2

MERLIN LEGEND Mail Module

2

A voice messaging system (VMS) requires a certain number of TTRs in addition
to any system requirements for TTRs. The number of TTRs depends on the
number of ports used by the voice messaging system (see Table 2–3). TTRs are
also required in private networks using E&M, T1 tie, and tandem tie trunks.
NOTE:
A VMS cannot be directly connected to the 008 OPT module. However, the
TTRs supplied by the 008 OPT module can be used by the VMS.
Table 2–3.

Touch-Tone Receivers Required by Voice Messaging Systems

Number of VMS Ports

Number of TTRs Required

1

1

2

1

3

2

4

2

6

3

8

4
1

6

18

8

12

1. If a 12 port MERLIN LEGEND Enhanced Service Center is used, 8 TTRs are required.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Issue 1
August 1998
Page 2-18

Table 2–4 estimates the total number of TTRs required in the system, based on
call volume and whether the system uses account codes. The call volume per
hour in this table includes all calls originating from single-line telephones, calls on
tie lines, incoming remote access and Direct Inward Dial (DID) calls.
NOTE:
You must consider the call traffic across a private network when estimating
the number of required TTRs. This includes calls on analog tandem tie
trunks and T1-emulated tandem tie trunks. In addition, if your private
network includes Centralized Voice Messaging, you must consider the call
traffic coming across the private network for the voice messaging system
and the TTRs required for the updating of Message Waiting lights
(Release 6.1 or later systems). For this updating, a TTR is required at the
sending end and the receiving end. If the systems in the private network
are connected by PRI trunks, no additional TTRs are needed.
Table 2–4.

System Requirements for Touch-Tone Receivers

TTRs Required
Calls/Hour No Account Codes Account Codes Used
110
2
4
180
4
6
350
4
8
420
6
8
610
6
10
710
8
10

In Release 6.0 and later systems, the use of the Prompt-Based Overflow setting,
which allows callers to request overflow coverage while waiting in a calling group
queue, requires TTRs for primary and secondary delay announcement devices
that present the option to callers.
Table 2–5 shows the TTRs required for primary delay announcement devices
when using the Prompt-Based Overflow setting.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Table 2–5.

Issue 1
August 1998
Page 2-19

TTRs Required for Primary Delay Announcement Devices

Number of Devices
1
2
3
4
5
6
7
8 or more

Number of TTRs Required
1
2
3
4
4
5
5
6

Table 2–6 shows the TTRs required for secondary delay announcement devices
when using the Prompt-Based Overflow setting.
Table 2–6.

TTRs Required for Secondary Delay Announcement Devices

Number of Devices
1
2
3
4
5
6
7
8
9
10 or more

Number of TTRs Required
1
1
1
2
2
2
3
3
3
4

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Issue 1
August 1998
Page 2-20

To calculate the total number of TTRs that are required by the system, do the
following:
1.

If the system has a VMS, use Table 2–3 to find the number of TTRs
required by the system to support the VMS.

2.

Estimate the hourly call volume for all calls originating from single-line
telephones, incoming calls (including private network tandem tie trunks) on
Remote Access and DID lines, all calls on tie lines, and calls routed to the
VMS. Use Table 2–4 to find the system requirements for TTRs based on
the estimated hourly call volume, and whether Account Codes are used.
NOTE:
You must consider the call traffic across a private network when
estimating the number of required TTRs. This includes calls on
analog tandem tie trunks and T1-emulated tandem tie trunks. In
addition, if your private network includes Centralized Voice
Messaging, you must consider the call traffic coming across the
private network for the voice messaging system and the TTRs
required for the updating of Message Waiting lights (Release 6.1 or
later systems). For this updating, a TTR is required at the sending
end and the receiving end. If the systems in the private network
are connected by PRI trunks, no additional TTRs are needed.

3.

Add the number of TTRs obtained in Step 1 and Step 2. If the Group
Calling Prompt-Based Overflow setting (Release 6.0 and later systems) is
not being used, go to Step 6.

4.

If the Group Calling Prompt-Based Overflow feature is being used, add the
number of TTRs needed for the primary delay announcement devices that
are assigned to those calling groups. Use Table 2–5 to determine the TTR
requirements for the primary delay announcement devices.

5.

If applicable, add the number of TTRs needed for the secondary delay
announcement devices that are assigned to calling groups using the
Prompt-Based Overflow feature. Use Table 2–6 to determine the TTR
requirements for the secondary delay announcement devices.
NOTE:
If no announcement is used on a primary or secondary delay
announcement device, no TTRs are needed.

6.

Use Table 2–2 for information on the number of TTRs provided by each
type of module, and to determine the number of TTRs already supplied.

7.

Compare the total TTRs needed to the total TTRs already supplied to
determine if additional TTRs are required.

8.

Add a new module if more TTRs are required.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Jack for Primary Operator Position

Page 2-21

2

The factory setting for the primary operator position is the lowest extension jack
on the first MLX or analog multiline telephone module. You cannot change the
factory setting for the primary operator position.
The primary operator position uses two types of operator consoles:
■

Direct-Line Console (DLC). Can be assigned to either a digital or
analog extension jack.

■

Queued Call Console (QCC). Can be assigned only to a digital
extension jack, and the MLX-20L is the only telephone that can be
used as a QCC.

If the system includes QCCs, the primary operator position must be a QCC.

Planning Form Instructions
Mark jack assignments on Form 2a:
1.

Do one of the following:
■

If the system uses a system programming console, proceed to
Step 2.

■

If the system does not use a system programming console, skip to
Step 5.

2.

Obtain the logical ID of the extension jack for the system programming
console by referring to the System Operating Conditions heading, Form 1
(page 2).

3.

Identify the logical ID for the system programming console by writing SPC
beside the appropriate logical ID in the Log. ID column of Form 2a.

4.

Write either the name of the person who will program the system or the
location of the system programming console in the Person, Location, or
Function column. Then proceed to Step 5.

5.

Do one of the following:

6.

■

To indicate the primary QCC operator position for a system with one
or more QCCs, proceed to Step 6.

■

To indicate the primary DLC operator position for a system with one
or more DLCs, skip to Step 7.

To indicate the primary QCC operator position:
■

Locate the first extension jack showing a D (digital) jack type and
write QCC beside the preprinted logical ID number.

■

Write the name or location of the primary QCC operator in the
Person, Location, or Function column.

■

On Form 1 (page 2), write the extension of the QCC under System
Consoles.

2

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

7.

Page 2-22

To indicate the primary DLC operator position:
■

Locate the first extension jack showing a jack type of D (digital) or A
(analog) and write DLC beside the preprinted logical ID number.

■

Write the name or location of the primary DLC operator in the
Person, Location, or Function column.

■

On Form 1 (page 2), write the extension of the DLC under System
Consoles.

Proceed to the next section, “Jacks for Additional Operator Positions”.

2

Jacks for Additional Operator Positions

Use these instructions only if the system has more than one operator position.
Otherwise, skip to the next section, “Extension Jack Pairs for Analog Telephones”.
The maximum number of operator positions is shown in Table 2–7.
Table 2–7.
Position

Maximum Number of Operator Positions
Telephone

Maximum

QCC

MLX-20L

4

DLC

MLX-20L

8

MLX-28D
DLC

Analog multiline
telephones

8

Any combination of operator positions can be assigned as long as no more than
four are QCCs and the total combined number is no more than eight. For
example, a system can have a combination that consists of four QCCs, two MLX
DLCs, and two analog DLCs. The Call Management System (CMS) equipment
connects to analog extension jacks assigned as DLC positions. You must assign
two DLC positions for each CMS (maximum of two) connected to the system on
analog multiline modules.

Planning Form Instructions
NOTE:
For each CMS connected to the system, you must assign two analog DLC
positions. These two DLCs do not need to have the factory setting
extension numbers but do need to be on the same module.

2

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Issue 1
August 1998
Page 2-23

1.

On the Control Unit Diagram on Form 1, determine which extension jacks
can be used as operator positions by circling the first and fifth extension
jacks on digital or analog modules, until you have reached the maximum
number of eight positions.

2.

On Form 2a, mark the extension jacks to be used as additional operator
positions.

3.

Do one of the following:

4.

5.

6.

■

If the system has additional QCCs, proceed to Step 4.

■

If the system has additional DLCs, skip to Step 5.

For each additional QCC:
■

Write QCC next to the preprinted logical ID for each additional QCC
position. Be sure to assign QCCs to only the first and fifth extension
jacks on each digital module.

■

Write the name or location of each additional QCC operator in the
Person, Location, or Function column.

■

On Form 1 (page 2), write the extension number of each additional
QCC in the System Consoles box.

For each additional DLC:
■

Write DLC next to the preprinted logical ID for each additional DLC
position, including DLC positions used for calling group supervisors
and for the optional CMSs. Be sure to assign DLCs to only the first
and fifth extension jacks on each digital or analog module.

■

Write the name or location of each additional DLC operator in the
Person, Location, or Function column.

■

On Form 1 (page 2), write the extension number of each additional
DLC in the System Consoles box.

If the system includes any Call Management Systems, write CMS in the
Person, Location, or Function column next to the logical ID for the two DLC
positions assigned for each CMS.

Proceed to the next section, “Extension Jack Pairs for Analog Telephones”.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Extension Jack Pairs for Analog Telephones

Page 2-24

2

Use these instructions only if the system has analog multiline telephones.
Otherwise, skip to the next section, “Jacks for MLX Telephones”.
MLX telephones can use the Voice Announce to Busy feature or simultaneous
voice and data without requiring a second extension jack.
Analog multiline telephones require an additional extension jack to use Voice
Announce to Busy or voice and data. The jacks must be an odd-numbered analog
extension jack and the next higher (even-numbered) analog extension jack. The
system assigns individual extension numbers to each of the jacks. The extension
number associated with the first (odd-numbered) extension jack in the pair is the
telephones extension number. Calls cannot be placed to the extension number
associated with the even-numbered extension jack. (For information about
renumbering jacks, see System Renumbering later in this chapter.)
You can assign Voice Announce to Busy or voice and data to any of the analog
multiline telephones in the system, but you cannot assign both to the same
telephone.

Planning Form Instructions
On Form 2a, mark the pairs of jacks for analog multiline telephones that have
Voice Announce to Busy or voice and data:
1.

In the Log. ID column, draw a box around the pair of extension jack
numbers that you plan to assign to each analog multiline extension with
either feature.

2.

In the Person, Location, or Function column, next to the first
(odd-numbered logical ID) number of each boxed pair, identify the
extension by person or location.

3.

In the Person, Location, or Function column, next to the second
(even-numbered logical ID) number of each boxed pair, do one of the
following:
■

For the Voice Announce to Busy feature, write voice/voice.

■

For voice and data, write voice/data.

Proceed to the next section, “Jacks for MLX Telephones”.

2

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Jacks for MLX Telephones

Page 2-25

2

Use these instructions only if the system has non-operator MLX telephones, ISDN
terminal adapters (such as the Ascend Pipeline 25PX or 50) used to connect a
data terminal, or digital data/video stations (such as a videoconferencing station)
to assign to digital extension jacks on 008 MLX and 408 GS/LS-MLX modules.
Otherwise, skip to the next section, “Jacks for Analog Multiline Telephones”. To
plan connections for digital data equipment, see Chapter 5, “Data
Communications”.
NOTE:
When using the 008 MLX or 408 GS/LS-MLX module for data, video, or as
a CTI link, you must use Version 28 of the module.
The system assigns two extensions, although only one logical ID is assigned to
each digital extension jack. For MLX telephones, one extension number is
automatically assigned to the MLX telephone physically connected to the digital
extension jack. The second extension number is reserved for an adjunct, such as
an analog modem or Delay Announcement Device, that can be connected to the
MLX telephone through a Multi-Function Module (MFM). For information about
renumbering jacks, see “System Renumbering” later in this chapter.
The system automatically assigns both extension numbers whether or not the
extension includes an MFM or ISDN terminal adapter. Calls can be placed to both
extension numbers independently.
The MFM can operate as an interface for either a Supplemental Alert Adapter or a
tip/ring device. The Supplemental Alert Adapter (SAA) setting on the MFM is used
when the MFM connects an external alert such as a bell or horn. The tip/ring (T/R)
setting is used when the MFM connects a tip/ring device such as an answering
machine or an analog modem.
NOTES:
1. The system capacity for endpoints is decreased by two whenever an
MLX telephone is used.
2. In Behind Switch mode, the system automatically assigns two prime lines
to each port on an MLX module — one for the MLX telephone and one for
the device connected to the MFM. If an MFM is not connected to an MLX
telephone or the MLX port is not used, the prime line for the MFM can be
removed. The prime line can then be assigned to another user.
When PRI, NI-1 BRI, or T1 Switched 56 lines/trunks are assigned to an MLX jack,
digital data/video stations may use two B-channels simultaneously (2B Data) to
place or receive high-speed data/video calls. For more information on planning for
video applications, see Chapter 5, “Data Communications”.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Issue 1
August 1998
Page 2-26

In Release 5.0 and later, if you want Computer Telephony Integration (CTI)
capability, you must assign an MLX jack (port) as the CTI link. In Release 5.0 and
later, the CTI link communicates with the PassageWay Telephony Services for
Netware product implemented on a server running Netware 3.12 or 4.1 or later. In
Release 6.1 and later, the CTI link may communicate with either the CentreVu
Computer-Telephony Release 3.1 or later on a server running Windows NT 4.0
Server or Windows NT 4.0 Workstation, or PassageWay Telephony Services for
Netware, to provide CTI services.
These CTI services enable a desktop computer running a certified PC application
to provide computer-based features to users. The CTI link port must be selected
from ports 2, 3, 4, 6, 7, or 8. The CTI link port cannot be the potential operator port
or the console programming port.

Planning Form Instructions
Use the floor plan and Equipment List (if available) to verify the location of any
video stations and all remaining MLX telephones and adjuncts connected to them.
1.

2.

On Form 2a, mark the extension jack assignments for the video stations
and the remaining MLX telephones:
a.

In the Jack Type column, make sure D is checked next to the logical
ID for each digital extension jack.

b.

In the Person, Location, or Function column, identify each video
station or MLX telephone by the user’s name, location, or function.

c.

If an extension port will be a CTI link, Write CTI Link in the Person,
Location, or Function column, and Label column, and put a check
mark in the CTI Link column. If this is a CTI link, skip to Step 3. The
CTI link port must be selected from ports 2, 3, 4, 6, 7, or 8. The CTI
link port cannot be the potential operator port or the console
programming port.

Using the information from Form 2a, mark the digital extension adjuncts
and video stations on Form 2b, System Numbering: Digital Adjuncts:
a.

Do one of the following:
— If the jack does not have an adjunct connected, write None in
the Adjuncts column and skip to Step 3.
— If an adjunct is connected to the MLX telephone, proceed to
Step b.

b.

If an adjunct is connected to the MLX telephone, enter the type of
adjunct (such as MFM-SAA, MFM-T/R, MFM-DA, ER1000, 7500B,
ASC 25PX/50, or ASC-VSX) in the Adjuncts column.

2

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

c.

Page 2-27

If a digital data or video station will be connected to the jack, and the
equipment supports 2B Data (such as a videoconferencing system
using a BRI interface or a v.35 interface and an ISDN terminal
adapter that supports 2B Data), check the box in the 2B column.
NOTE:
Do not connect equipment that does not support 2B Data (such as
G4 FAX, or a videoconferencing system using a v.35 interface and
an ISDN terminal adapter that does not support 2B Data) to an MLX
jack configured as a 2B Data port.

d.
3.

If a digital data or video system is connected to the jack, enter the
extension number in the MLX Telephone Ext. No. column.

Identify the type of equipment connected to the jack or the ISDN terminal
adapter connected to the jack. Also, record the person, location, or function
if desired.

Proceed to the next section, “Jacks for Analog Multiline Telephones”.

Jacks for Analog Multiline Telephones

2

Use these instructions only if the system includes 408, 408 GS/LS or 008
modules. Otherwise, skip to the next section, “Jacks for Tip/Ring Equipment and
Applications”.
Certain features should be used differently when a General-Purpose Adapter
(GPA) is connected to an analog multiline telephone and configured using the
Automatic setting. These configurations include:
■

GPA connected to an answering machine and an analog multiline
telephone with Auto Answer All button programmed.

■

GPA connected to an answering machine and an analog multiline
telephone programmed as a member of a calling group.
NOTE:
The answering machine may be used as either a primary or
secondary Delay Announcement Device provided it hangs up when
the announcement has finished.

■

GPA connected to an analog multiline telephone programmed for voice and
data.
NOTE:
An MLX telephone with an MFM installed is preferred for these applications.

When these configurations are used, lift the handset before activating features
that automatically turn on the speakerphone. Examples of features that
automatically turn on the speakerphone are Authorization Codes, Auto Dial, Last
Number Dial, and Saved Number Dial.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Page 2-28

Assign analog extension jacks for all remaining non-operator analog multiline
telephones in the system.

2

Planning Form Instructions
On Form 2a, mark the extension assignments for the remaining analog multiline
telephones:
1.

In the Jack Type column, make sure A is checked next to the logical ID for
each analog extension jack.

2.

In the Person, Location, or Function column, identify each analog multiline
telephone by the user’s name, location, or function.

Jacks for the CTI Link Application

2

Use these instructions only if the system has 008 MLX and 408 GS/LS-MLX
modules and users will be using CTI applications and a CTI Server (PassageWay
Telephony Services for NetWare or CentreVu Computer-Telephony Services for
Windows NT). Otherwise, skip to the next section, “Jacks for Tip/Ring Equipment
and Applications.”
The CTI link allows the computer users to interact directly with the
communications system and obtain access to features through the use of a
computer. Once installation is completed, the CTI port does not need feature
programming, but the port and extension information must be recorded to be used
when programming the network features.
If an MLX or analog multiline telephone extension is going to have a CTI-capable
program installed on the extension’s worktop PC, then you need to identify both
the CTI link extension (the MLX port extension that connects to the CTI Server),
and the MLX or analog multiline telephone extensions that will have the
CTI-capable program installed. Single-line telephones cannot make use of CTI.
If the CTI link is on the first MLX module in the system, then perform
administration for the CTI link using SPM. If the CTI link is not on the first MLX
module, then you can use the system programming console to do the
programming.
CTI can be used only on Release 5.0 and later communications systems in
Hybrid/PBX mode.
To get the Incoming Caller ID (ICLID) information, LS-ID delay must be set to On
(factory setting is Off).
To use a CTI application for Call Control features (Hold, Hold retrieve, Consult,
Transfer, or Conference), the call must be on an SA button.
A monitored extension is one that is connected to a CTI application that can
handle the call; the application should be used to handle the calls. An
unmonitored extension is not connected to a CTI application.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Issue 1
August 1998
Page 2-29

To receive ANI or Caller ID (if available) information for incoming alerting calls,
calls must:
■

Arrive on an SA button or be transferred by an unmonitored DLC or a QCC.

■

After a call has been answered, the call may arrive at any type of facility
button.

For calls that arrive on a personal line and are first answered by a DLC, transfers
must be activated manually, using the telephone. (The CTI Client PC Transfer
function only works with calls received on SA buttons.) In this situation, the
following holds true:
■

If a DLC is an unmonitored extension, and the DLC transfers a call to a
monitored extension, it sends Caller ID/ICLID/ANI information to, and
initiates a screen pop at the transfer receiver’s Client PC.

■

If the DLC is a monitored extension, the DLC receives screen pop but does
not send this information to the transfer receiver.

If an unmonitored, non-attendant transfers a call, the recipient will not get the ANI
or Caller ID information at the application, even though it may be seen on the
telephone’s display.
Extensions that interact with a CTI-capable program on a computer (extensions
marked Computer Telephony Integrated Client PC) should not have Microphone
Disable programmed.
The CTI link must be connected to an extension that is on an MLX port module
(008 MLX or 408 MLX). However, the extension cannot be on a module of
firmware vintage 29, the console programming port, or a potential operator
position in the first or fifth port on the module. CTI link programming removes
2B Data programming for a port. If you want to keep a port programmed as a
2B data port, do not assign it as a CTI link port.
The CTI link extension must directly connect to the CTI card on the CTI Server.
Adapters, MFMs, and passive bus arrangements are not supported on this port.

Planning Form Instructions
On Form 2a mark the box under the CTI Link column for the extension that will
connect the control unit to the CTI Server. The CTI link cannot be on an extension
that is a potential operator (gray on the planning form), or a console programming
port. If you want to keep a port programmed as a 2B data port, do not assign it as
a CTI link port.
On form 4b or 4d, check the Yes box under Computer Telephony Integrated Client
PC, or on form 5a or 5b, check the CTI PC adjunct box, if a computer at the same
location as the extension will have a CTI-capable program (client) installed.

2

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Issue 1
August 1998
Page 2-30

Jacks for Tip/Ring Equipment and Applications 2
Use these instructions only if the system includes 012 T/R, 016 T/R, or 008 OPT
modules. Otherwise, skip to the next section, “Labels”.
Assign the basic telephone jacks on the 012 T/R, 016 T/R, or 008 OPT modules to
any tip/ring equipment such as single-line telephones, fax machines, analog
modems, or Group Calling Delay Announcement Devices. The hardware design
of the 008 OPT module includes an interface for off-premises telephones, which
supplies increased gain levels and protection.
If assigning basic telephone jacks on an 016 T/R module, the Ringing Frequency
may be set to either 20-Hz (Type A) or 25-Hz (Type E). The Ringing Frequency is
programmable on each 016 T/R module and affects all ports on that module.
Several optional applications, if used with the system, require basic jacks on a
012 T/R or 016 T/R module: Enhanced Service Center, Messaging 2000,
Intuity AUDIX, Lucent Technologies Attendant1, AUDIX Voice Power-Integrated
Solution II (IS II)* or III (IS III)*, and Integrated Voice Power Automated
Attendant-IS II* or IS III*. Do not use the 008 OPT module for these applications.
The system can accept up to eight application ports (extension jacks for
applications) using the 012 T/R module. All 16 ports on the 016 T/R module may
be used for applications.
Table 2–8 shows, by application, the number of ports used, the number of TTRs
required, and the number of additional single-line telephones that can be added to
the modules. Use this table as a guideline.

1.

No longer orderable.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Table 2–8.

Page 2-31

Application Ports

Application

Ports

TTRs

MERLIN LEGEND Mail

2
4
6

1
1
2

NA

Messaging 2000

4
6
8
12
16

2
3
4
5
6

2
1
0
0
0

Intuity AUDIX

4
6
8
10
12

2
3
4
5
6

2
1
0
0
0

Enhanced Service Center (ESC)

12
16

8
8

0
0

CONVERSANT

(see Note 3)

1

Telephones

2
4

1
2

3 + 1 for the modem
2 + 1 for the modem

Lucent Technologies Attendant*

1
2
3
4

1
1
2
2

6 + 1 for programming
5 + 1 for programming
4 + 1 for programming
3 + 1 for programming

AUDIX Voice Power*

2
4
6
8

1
2
3
4

6
4
2
0

MERLIN MAIL

1. No longer orderable.

NOTES:
1. Older versions of the 012 T/R module, (apparatus codes 517C13–517F13) if one or
more applications are used, only four tip/ring devices may be assigned to the
module where the application is assigned, regardless of how many jacks are open.
2. The applications in Table 2–8 do not work properly with 012 T/R modules
manufactured for older MERLIN II systems. These applications must be connected
to 016 T/R modules or 012 T/R modules with code 517C13 or higher labeled on the
top of the module. Modules with code 517A13 or 517B13 can be used to connect
single-line telephones only. They do not provide the disconnect signal required by
answering machines and applications. Do not use the 008 OPT module for
applications such as Enhanced Service Center, Messaging 2000, or Intuity AUDIX.
3. When planning for CONVERSANT, refer to the documentation provided with the
application and contact the SDSC (1 888 297-4700 and follow the prompts to reach
the CONVERSANT split) for information on TTRs and ports.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Issue 1
August 1998
Page 2-32

Planning Form Instructions
On Form 2a, mark the extension jack assignments on the 012 T/R, 016 T/R,
MERLIN LEGEND Mail, and 008 OPT modules:
1.

In the Jack Type column, make sure B is checked next to the logical ID for
each basic telephone jack.

2.

In the Person, Location, or Function column, identify each T/R device by
the users name or location and by type, such as single-line telephone, fax,
modem, or Delay Announcement Device.

3.

If the system includes optional applications, indicate the application on the
appropriate line in the Appl column:
■

To indicate MERLIN LEGEND Mail, write ML Mail.

■

To indicate Messaging 2000, write M2000.

■

To indicate Intuity AUDIX, write Intuity.

■

To indicate Enhanced Service Center, write ESC.

■

To indicate CONVERSANT, write CONV.

■

To indicate MERLIN MAIL voice messaging system, write Mail.

■

To indicate Lucent Technologies Attendant, write Lucent A.

■

To indicate AUDIX Voice Power IS II or IS III, write AVP.

■

To indicate Integrated Voice Power Automated Attendant-IS II, write
IVP-AA.

■

To indicate no applications, write None.

4.

If the system has Messaging 2000 or AUDIX Voice Power, also write port
in the Appl column for any logical IDs that are being used for fax ports.

5.

If the system is to be part of a Centralized Voice Messaging system
(Release 6.1 and later systems only), check Yes under the Centralized
Voice Messaging heading. Also check Yes on page 4 of the MERLIN
LEGEND R6 Design Implementation Guide form located in Appendix I. If
not part of a Centralized Voice Messaging system, check No on both forms.
NOTE:
For more information on Centralized Voice Messaging, see the
Network Reference.

6.

For each 016 T/R module, if applicable, indicate the Ringing Frequency for
that module. Enter 20-Hz or 25-Hz in the Ring Freq. column for all ports on
the 016 T/R module. When configuring a system in the United States or
Canada, generally the 20-Hz setting is applicable. The factory setting is
20-Hz.

Proceed to the next section, “Labels”.

2

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Page 2-33

2

Labels

This section contains instructions to associate alphanumeric labels with extension
numbers so that both the name of the caller and the extension number appear on
display telephones.

2

Planning Form Instructions
On the appropriate line in the Label column on Form 2a, write the label
(maximum: 7 characters) to be displayed for each telephone.
Proceed to the next section, “System Renumbering”.

System Renumbering

2

The selection of a numbering plan depends on the customer’s needs. Each of the
systems numbering plans (2-digit, 3-digit, and Set Up Space) allows you to
renumber all or selected extensions. If you do not need to renumber extensions,
skip to the last section of this chapter, “Updating Planning Information”.
In Release 6.0 and later systems (Hybrid/PBX mode only), the Uniform Dial Plan
(UDP) allows you to choose non-local dial plan numbering to specify the
numbering of extensions connected to remote systems in a private network and
allow users on your system to access those extensions as if they were connected
to your own system. When renumbering a system that is part of a private network,
see the Network Reference for information.

!

CAUTION:
Before programming the private network ranges, set up the local dial plan. If
the ranges are programmed in the network, and then 2-digit, 3-digit, or
Set Up Space factory settings are used, all network ranges on that switch
are erased.
Before the system is renumbered, the AUDIX Voice Power channel
assignments should be deleted (through AUDIX Voice Power) for the
extensions being renumbered. When the renumbering for the system is
complete, AUDIX Voice Power channels for the renumbered extensions
should be added.

Figure 2–2 through Figure 2–4 list the extension numbers according to the three
numbering plans: 2-digit, 3-digit, and Set Up Space. The numbers are arranged in
blocks according to the first digit. The type of equipment or feature they are
assigned is shown in the block. The shaded areas of the table indicate extension
numbers automatically assigned by the system. The unshaded areas indicate the
extension numbers available for reassignment. Use the appropriate plan-specific
instructions that follow to mark Forms 2a and 2b with extension number assignments.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Issue 1
August 1998
Page 2-34

For detailed information about the numbering plans (including considerations,
constraints, and feature interactions that may affect selection), see the Feature
Reference.
NOTE:
If the system includes Call Management System (CMS), it assigns
extension numbers to agent splits. The CMS agent extension numbers
must be two digits. Therefore, use the 2-digit numbering plan for CMS. For
more information, see the CMS documentation.

0
1
2
3
4
5
6

7

8
9
*

Operator Console (not flexible) 0
Extensions 10−19
Extensions 20−29
Extensions 30−39
Extensions 40−49
Extensions 50−59
Extensions 60−66
Extra
6843− Extra MFMs/
6993−
Extensions
Terminal Adapters 6999
6849
6700−6842
6850−6992
Main Pool
MFMs/
767− Calling Groups
Paging
70
Terminal Adapters 769 770–791,7920−7929
Groups
710−766
793−799
800*
Trunks 801−880
Park
889†
Pools
881−888
890−899
ARS Access (Hybrid/PBX Mode) / Idle Line Access 9

Listed Directory Number (QCC Queue)

† Remote Access

NOTE: “0” and “10” are the same station.

Figure 2–2.

Extension Numbers for 2-Digit Numbering Plan

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

0
1
2
3
4
5
6
7

Main Pool
70
800*

8
9
*

Page 2-35

Operator Console (not flexible) 0
Extensions 100−199
Extensions 200−299
MFMs/Terminal Adapters 300–399
MFMs/Terminal Adapters 400−499
500−599
600−699
Calling Groups
71−76
770−791, 7920−7929
Trunks
Park
889†
801−880
881−888
ARS Access (Hybrid/PBX mode)/Idle Line Access

Paging
Groups
793−799
Pools
890−899

Listed Directory Number (QCC)

† Remote Access

NOTE: “0” and “100” are the same station.

Figure 2–3.

0
1
2
3
4
5
6
7

8
9

Extension Numbers for 3-Digit Numbering Plan

Operator Console (not flexible) 0
100−
−199
200−
−299
300−
−399
400−
−499
500−
−599
600−
−699
Main Pool Extensions MFMs/Terminal 7500−
−7699 Calling Group
70
Adapters
7100−
−7299
770−
−791,
7300−
−7499
7920−
−7929
800*
Trunks
Park
889†
801−
−880
881−
−888
ARS Access (Hybrid/PBX mode)/Idle Line Access 9

Paging
Groups
793−
−799
Pools
890−
−899

* Listed Directory Number (QCC).
† Remote Access

NOTE: “ 0” and “7001” are the same station.

Figure 2–4.

Extension Numbers for Set Up Space Numbering Plan

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

2

Control Unit Configuration
Numbering the System

Page 2-36

2

Planning Form Instructions
Use Figure 2–2 through Figure 2–4 as you record extension number information:
1.

On Form 2a and 2b, if this switch is part of a private network, check Yes
under the Networked Switch heading. If the switch is not part of a private
network, check No.
NOTE:
For more information, see the Network Reference.

2.

Identify the 2-digit, 3-digit, or Set Up Space numbering system you will be
using under the Factory Set column on Form 2b, by circling the name of the
appropriate numbering system.

3.

Do one of the following:
■

■

If you do not need to renumber any of the factory-set extension
numbers:
a.

Check the 2-Digit, 3-Digit, or Set Up Space box under the
Renumber System heading on Form 2a to indicate the
numbering plan you’re using.

b.

Skip to the next section, Updating Planning Information.

If you want to renumber only a few of the extensions and there are
enough numbers available for 2- and 3-digit numbering plans:
a.

Check the 2-Digit, the 3-Digit, or the Set Up Space box to
indicate the numbering plan you’re using. Be sure to check
Selected Extension Numbers under the Renumber System
heading on Form 2a, page 1.

b.

Write the new extension number(s) in the Renumber to
columns on Form 2a and Form 2b.

Proceed to the next section, “Updating Planning Information”.

Updating Planning Information

2

On the floor plan, add the extension number beneath the symbol for each
telephone and adjunct. If you are using a system programming console, go to
Form 1, System Planning, in the System Operating Conditions section and add
the new extension number of the console in the space next to Ext. No.
NOTE:
The remaining columns on Form 2a (Eqpt., Label, Old Ext. No., and
Wire No.) are completed by the technician during installation.
To complete the forms for lines/trunks, proceed to Chapter 3, “Lines/Trunks”.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Issue 1
August 1998

Lines/Trunks

Page 3-1

3

Lines/Trunks

3

Planning for lines/trunks consists of the following tasks:
1.

Identifying Line/Trunk Jacks. Use the placement of modules in the
control unit (see the Control Unit Diagram on Form 1) as a guide to
determine in what order to connect trunks to the control unit. To do this,
identify the line/trunk jack types available by module and then match trunks
and auxiliary equipment with the jacks that support them.

2.

Selecting Line/Trunk Options. According to the requirements of the
customer, choose from available options for the incoming trunks connected
to the system.

3.

Assigning Lines/Trunks to User Extensions. Assign lines/trunks to
telephones and DLCs.

4.

Assigning Telephone Buttons. Assign buttons to Hybrid/PBX mode
telephones, to Key and Behind Switch mode telephones, and to DLCs.
NOTE:
If the switch is part of a private network, the following tasks must also be
performed to plan for lines/trunks: Labeling the Network Trunks, PRI Switch
Type (Legend-PBX or Legend-NTWK), and Switch Identifiers. See the
Network Reference for information.

This chapter contains instructions for completing each of these tasks. You should
become familiar with line/trunk types and options, as well as the requirements of
the system before you attempt to perform the procedures in this chapter. It is also
critical that you understand what services the local telephone company can
provide.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Identifying Line/Trunk Jacks

Identifying Line/Trunk Jacks

Page 3-2

3

Identifying line/trunk jacks consists of the following tasks:
1.

Determining which line/trunk jack types are available according to the types
of modules in the control unit

2.

Matching incoming trunks to the jacks that support them

3.

Designating jacks for auxiliary equipment (if any)

This section contains instructions for completing all of these tasks.

3

Forms Needed
■

Form 1, System Planning

■

Form 2c, System Numbering: Line/Trunk Jacks

You also need the local telephone company’s line/trunk information.

Module Types and Line/Trunk Jack Types

3

The line/trunk jack type is determined by the type of module. Table 3–1 lists the
line/trunk jack types and the incoming line/trunk or auxiliary equipment that can be
connected to these jacks.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Issue 1
August 1998

Lines/Trunks
Identifying Line/Trunk Jacks

Table 3–1.

Page 3-3

Line/Trunk Jack Types

Module Type

Line/Trunk
Jack Type

Number of
Jacks

400
800
408

Loop-start (LS) 4
8
4

Used to Connect
Line/Trunk Types: Basic,
Special Purpose (FX, WATS)
Auxiliary Equipment: Music On Hold,
Loudspeaker paging system,
Maintenance Alarm, MERLIN
Identifier

400 GS/LS
Ground-start/
800 GS/LS
loop-start
408 GS/LS
(GS/LS)
408 GS/LS-MLX
800 GS/LS-ID

4
8
4
4
8

Line/Trunk Types: Basic,
Special Purpose (FX, WATS)

800 DID
DID
(Hybrid/PBX)

8

DID

800 NI-BRI

NI-1 BRI

8 (16 channels) NI-1 BRI

400EM

Tie

4

100D

DS1

1 (24 channels) T1
T1 Switched 56 Data
PRI

Auxiliary Equipment: Music On Hold,
Loudspeaker paging system,
Maintenance Alarm, MERLIN
Identifier

Tie

NOTES:
1. You cannot mix T1 and Primary Rate Interface (PRI) service on the same
100D module. Any of the following AT&T Switched Network (ASN)
Services can be provided through a T1 or PRI facility: Megacom WATS,
Megacom 800, Software Defined Network (SDN), and MultiQuest. PRI
also supports Call-by-Call Service Selection and some ACCUNET
switched digital services. T1 supports Shared Access for Switched
Services (SASS) and ACCUNET Switched Digital Service (or other
circuit-switched data service) at 56-kbps. Both support Dialed Number
Identification Service (DNIS).
2. The MERLIN LEGEND Communications System supports Centrex
service with loop-start lines only. The system does not support a timed
switchhook flash with ground-start trunks or ground-start emulation on
DS1 facilities in any mode of operation (Hybrid/PBX, Key, or Behind
Switch).

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Identifying Line/Trunk Jacks

Page 3-4

3. The MERLIN LEGEND Communications System does not support timed
switchhook flash with NI-1 BRI lines. Pressing the Recall button on a
MERLIN LEGEND telephone will be ignored. If the Recall button is stored
as part of an Auto Dial string, it will not be sent out over an NI-1 BRI line,
or stored for Last Number Dial or Saved Number Dial when calling on an
NI-1 BRI line.
4. The MERLIN LEGEND Communications System does not support BRI
features such as Local Area Signaling Services (LASS), CO Transfer,
and other Centrex offerings.
5. Trunks used for incoming caller line identification (ICLID) service should
not have any equipment other than the MERLIN LEGEND line port
connected to them. Connecting other equipment (such as alarms,
autodialers, and so on) may result in distorted or lost ICLID data.
6. Trunks assigned as either the system Music on Hold or External Page
Port cannot be assigned as a Group Calling trunk.

LS-ID Delay Option

3

The LS-ID Delay option is available through the 800 GS/LS-ID module and is
programmed for each trunk. It prevents applications and adjuncts from answering
before the Caller ID information is processed.
Use the LS-ID Delay option only if the following conditions apply:
■

If the adjunct or application cannot be programmed to answer on the
second or later ring, see the documentation for the adjunct or application.

■

If the first option applies (as with headsets using Auto Answer All) and line
buttons receiving Caller ID cannot be programmed for Delay Ring, for
example, auto attendants.
NOTES:
1. It is recommended that trunks with the LS-ID Delay option be used as
incoming trunks only.
2. If no delay is programmed, the caller may hear one or two extra bursts of
ringback while the person receiving the call has not yet heard a ring.
3. If the option is programmed on a two-way trunk, the system will not seize
a trunk from the pool for an outgoing call when that trunk is receiving an
incoming call.
4. Use the LS-ID Delay option if the adjunct or application does not allow
line buttons to be set for Delay Ring.
5. If the option is programmed on a trunk programmed as a Group Calling
trunk, the system will not dispense the call to either the Group Calling
queue or to any calling group member until either the LS-ID Delay timer
expires or the system software is informed that ICLID information is
unavailable.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Identifying Line/Trunk Jacks

Issue 1
August 1998
Page 3-5

Planning Form Instructions
Refer to the completed Control Unit Diagram on Form 1 to mark line/trunk jack
types on Form 2c:
1.

For each module with line/trunk jacks noted in the Control Unit Diagram
(beginning with Slot 01), write in the type of module and its slot number in
the Module Type and Slot No. column of Form 2c; after the appropriate
Log. ID number, draw a line to indicate the logical IDs (and therefore, the
line/trunk jacks) that correspond to that module.
If the system has 100D (DS1) modules, keep in mind that even though the
module has only one physical jack, the 100D module supports up to 24
endpoints. Therefore, 24 logical IDs and associated line/trunk numbers are
assigned to each module.
The 800 NI-BRI module supports up to 16 endpoints, therefore 16 logical
IDs and associated line/trunk numbers are assigned to each 800 NI-BRI
module even though the module has only eight physical jacks.

2.

In the Jack Type column of Form 2c, for all modules except 100D modules,
write the jack type for each logical ID. Use the codes shown in Table 3–2.

Table 3–2.

Codes for Line/Trunk Jacks

Jack Type Code
LS
GS/LS
DID
Tie
T1-GS
T1-LS
T1-Tie1
T1-DID
T1-S56
PRI
BRI

Line/Trunk Type
Loop-start
Ground-start/loop-start
DID
Tie
DS1 connectivity used to emulate GS
DS1 connectivity used to emulate LS
DS1 connectivity used to emulate tie or for digital data service
DS1 connectivity used to emulate DID
DS1 connectivity used for digital data
DS1 connectivity used for PRI service
NI-1 BRI

1. T1 Switched 56 digital data is also available using T1-Tie trunks. See the “Tie Trunks”
section later in this chapter.

3.

For systems that include a 100D module, do one of the following in the
Jack Type column:
■

If the module will emulate trunks or will be used for digital data
transmission, write the appropriate jack type code (see Table 3–2)
for the channels being used (for example, T1-LS, T1-TIE, or T1-S56),
or write T1 if the channels are not being used at this time.

■

If the module will connect services (such as, Megacom and
Megacom 800), write PRI for all 24 logical IDs of PRI-type modules.

You may now match incoming trunks to the available jacks as described in the
next section.

3

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Identifying Line/Trunk Jacks

Incoming Line/Trunk Type

Page 3-6

3

Use the procedure in this section to match incoming trunks to the continuous
sequence of line/trunk jacks on the control unit, beginning with the first line/trunk
jack (logical ID 1).
NOTE:
(Key mode only) If the system is registered with the FCC registration
number of AS59CM-7914-KF-E, and the processor module has been
modified for Permanent Key mode, you can connect loop-start trunks to the
GS/LS type line/trunk jacks. With the KF registration number, ground-start
trunks are allowed only when the system includes DS1 connectivity
dedicated as a T1 type and the channels are used to emulate ground-start
trunks.
This procedure also includes instructions for assigning a label to identify the
line/trunk being used.

Planning Form Instructions
1.

In the Incoming Line/Trunk Type column of Form 2c, write the type of
line/trunk you plan to connect to each line/trunk jack, T1 channel or BRI
channel: Main No., personal line, FX (Foreign Exchange), WATS (include
band), DID, or Tie. (Contact the local telephone company for line/trunk
information.) Use the following guidelines:
■

Group trunks together according to type: basic loop-start or
ground-start trunks, and special-purpose loop-start or ground-start
trunks. (DID, PRI, T1, BRI and tie trunks are automatically grouped
according to type since they require specific types of modules.) The
local telephone company supplies the information you need to
identify the specific trunks connected to each line/trunk jack on each
DID and tie trunk module and each channel on each 100D or 800
NI-BRI module.

■

Use line/trunk jacks at the beginning of the sequence for basic
ground-start and/or basic loop-start trunks. Use jacks later in the
sequence for special-purpose trunks such as WATS or FX.

■

If a line/trunk such as WATS is only inbound or only outbound (not
two-way), include that information along with the line/trunk type.

3

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Identifying Line/Trunk Jacks

2.

Issue 1
August 1998
Page 3-7

If the jack type shown in the Jack Type column is GS/LS, then write either

GS or LS to indicate the line/trunk type in the Incoming Line/Trunk Type
column. For a T1 or NI-1 BRI trunk not used at this time, write unequipped.
For other T1 or PRI facilities, the kind of service connected (such as
Megacom 800) will be filled in later.
NOTE:
In the next step, be sure the line/trunk type associated with each
telephone number matches the jack type. Also, if you have
800 NI-BRI modules or have dedicated 100D module channels to
emulate loop-start, ground-start, and/or tie trunks, the local
telephone company will supply the telephone number associated
with each of the channels on the BRI or DS1 facility.
3.

In the Telephone Number or Equipment column, write the telephone
number for each incoming line/trunk (as supplied by the local telephone
company) on the row with the logical ID for its line/trunk jack. If you do not
know the telephone number, leave the column blank and enter the
information later.

4.

In the Label column, write the label for each line/trunk on the appropriate
line. The labels can contain up to seven characters, including capital
letters, numbers, ampersand (&), dash (-), space, colon (:), asterisk (*), and
pound sign (#).

The remaining entries on this form are covered in “Selecting Line/Trunk Options,”
later in this chapter. If the system does not have auxiliary equipment (for example,
Music On Hold or a loudspeaker paging system), skip to “Selecting Line/Trunk
Options” in this chapter.
Figure 3–1 shows an example of a partially completed Form 2c.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Identifying Line/Trunk Jacks

Page 3-8

Incoming
Trunk
Type
Jack
(Main No.,
Pool
Module
Type
Personal Telephone
DialType
(LS, GS,
ReLine,
Number
Out number WATS,
and Slot Log. DID, Tie, Trunk
or
No.
ID
etc.)
No. Code†‡
To
FX, etc.) Equipment

008
MLX
01

008
MLX
02

Figure 3–1.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

GS
GS
GS
GS
GS
GS
GS
GS
GS
GS
GS
GS
GS
GS
GS
GS

801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816

Basic GS
Basic GS
Basic GS
Basic GS
Basic GS
Basic GS
Basic GS
Basic GS
Basic GS
Basic GS
Basic GS
Basic GS
Basic GS

Partially Completed System Form 2c

555-1200 1
555-1201 2
555-1202 3
555-1203 4
555-1204 5
555-1205 6
555-1206 7
555-1207
555-1208
555-1209
555-1210

Label

LOCAL
LOCAL
LOCAL
LOCAL
LOCAL
LOCAL
LOCAL

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Identifying Line/Trunk Jacks

Page 3-9

Jacks for Auxiliary Equipment

3

Use these instructions only if the system has auxiliary equipment: Music On Hold,
MERLIN Identifier, a loudspeaker paging system, or a Maintenance Alarm.
Otherwise, skip to the next section, “Function Information.”
NOTE:
MERLIN Identifier does not require new wiring and is compatible with all
system releases.
Only connect auxiliary equipment to loop-start or ground-start/loop-start jack
types. You cannot use a line/trunk jack for auxiliary equipment on an 800 DID,
100D, 800 NI-BRI, or 400EM module.
To make it easier to add incoming trunks in the future, connect auxiliary
equipment to the last line/trunk jack(s) on the rightmost module with either LS or
GS/LS line/trunk jacks.

Planning Form Instructions
1.

Review the floor plan and Equipment List (if available) to confirm the
auxiliary equipment to be connected.

2.

At the top of Form 2c, fill in the line/trunk numbers for each type of auxiliary
equipment planned:
■

For Music On Hold, write the line/trunk number of the line/trunk jack
designated for this equipment, and identify the music source (tape
player, radio, or Music On Hold) on the Music On Hold line.
NOTE:
If the system uses equipment that rebroadcasts music or
other copyrighted materials, the customer may be required to
obtain a copyright license from, and pay license fees to, a
third party such as the American Society of Composers,
Artists, and Producers (ASCAP) or Broadcast Music
Incorporated (BMI). The Magic on Hold system, which does
not require such a license, can be purchased from a Lucent
Technologies representative.

■

For Loudspeaker Paging, on the appropriate row, write the line/trunk
numbers (maximum of 3) of the line/trunk jack(s) designated for the
paging equipment.

■

For Maintenance Alarm, on the appropriate row, write the line/trunk
number of the line/trunk jack designated for the Maintenance Alarm
external alert.
NOTE:
The last item, Loop-Start Reliable Disconnect, refers to a line/trunk
option and is completed later in this chapter.

3

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Identifying Line/Trunk Jacks

Function Information

Page 3-10

3

If the system has a Voice Messaging System (such as Messaging 2000), you can
use the Function column to indicate which service is available for those jacks. You
can also use this column to indicate whether a jack connects a personal line and,
therefore, has an owner.

Planning Form Instructions
In the Function column of Form 2c, do one of the following:
■

If a jack is used for a special purpose, note the purpose. For example, if the
system has Messaging 2000 with fax capability, indicate the service by
writing one of the following for the appropriate jack:
— For Automated Attendant, write AA.
— For Call Answer, write CA.
— For Information Service, write IS.
— For Message Drop, write MD.
— For Voice Mail, write VM.
— For Fax Response, write FR.

■

If a jack is used for a personal line, write the extension number of the
telephone.

Proceed to the next section, “Selecting Line/Trunk Options.”

3

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Selecting Line/Trunk Options

Page 3-11

3

You can select the following options for the incoming trunks connected to the
system:
■

Loop-Start Reliable Disconnect

■

Outmode Signaling

■

Toll-Call Prefix Dialing Requirements (Toll Type)

■

Hold Disconnect Interval

■

QCC Operator to Receive Calls (Hybrid/PBX mode only)

■

QCC Queue Priority (Hybrid/PBX mode only)

■

Pools

■

Remote Access

■

DS1 Connectivity

■

Tie Trunks

■

DID Trunks

■

NI-1 BRI Connectivity
NOTE:
If incoming trunks are part of a private network, the Switch Identifier must
also be programmed. See the Network Reference for information.

This section contains instructions for selecting line/trunk options for incoming
trunks. In addition, because some systems outside of the US have slow dial tones
from their local telephone companies, this section also includes instructions for
compensating for slow dial tone.

Forms Needed
■

Form 1, System Planning

■

Form 2c, System Numbering: Line/Trunk Jacks

■

Form 3a, Incoming Trunks: Remote Access

■

Form 3b, Incoming Trunks: DS1 Connectivity (100D Module)

■

Form 3c, Incoming Trunks: Tie

■

Form 3d, Incoming Trunks: DID

■

Form 3i, Incoming Trunks: BRI Options (800 NI-BRI module)

3

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Loop-Start Reliable Disconnect

Page 3-12

3

Disconnect signals on incoming calls on loop-start trunks are classified as one of
the following:
■

Reliable. A disconnect signal is sent to the system by the local telephone
company shortly after a caller hangs up. Loop-start trunks must be reliable
for remote call forwarding and trunk-to-trunk transfer. Also, reliable
disconnect is strongly recommended for remote call transfers, and VMSs
such as MERLIN LEGEND Mail.
NOTE:
If the local telephone company uses a short hold disconnect interval,
do not specify a reliable disconnect signal. Also, to ensure proper
voice messaging operation, and for private network systems, the
system must have ground-start or loop-start trunks with reliable
disconnect.

■

!

Unreliable. A disconnect signal is not sent by the local telephone company
on every call.

SecurityAlert:
Toll fraud can occur when loop-start lines/trunks are used with unreliable
disconnect. If the calling party stays on the line after the called party hangs
up, the central office will return a dial tone at the conclusion of the call
enabling the caller to place another call as if it were being placed from your
company.

Since the disconnect signal on most loop-start trunks is unreliable, the factory
setting for the disconnect signal is Unreliable.
Before you change the setting, check with the telephone company to determine
whether the disconnect signals for the loop-start trunks are reliable and to obtain
the length of the hold disconnect interval.
If you select Reliable disconnect, you can set the interval after which the line/trunk
is released as described in “Hold Disconnect Interval” later in this section.
Trunk-to-trunk transfer is programmed on a per-extension basis and should
remain disabled even if the loop-start trunk has reliable disconnect. See the
“Trunk-to-Trunk Transfer” section in Chapter 4.

Planning Form Instructions
At the top of Form 2c, under the Loop-Start Reliable Disconnect heading, choose
one of the following:
■

If the loop-start trunks have an unreliable disconnect signal, check the No
box (the factory setting).

■

If the loop-start trunks have a reliable disconnect signal, check Yes.

3

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Outmode Signaling

Page 3-13

3

The system is factory-set to generate touch-tone signals when users dial outside
calls. Identify any rotary-dial trunks that are connected to the system so that
rotary-dial signals can be used for these trunks.
NOTE:
Touch-tone, single-line telephone users cannot make calls using rotary-dial
trunks unless their phones allow them to switch between touch tones and
rotary dial pulses. Check with the local or long-distance telephone company
to determine which, if any, trunks connected to the system are rotary-dial
trunks.

3

Planning Form Instructions
In the Outmode Signaling column on Form 2c, do one of the following:
■

For touch-tone trunks (factory setting), put a check in the TT column.

■

For rotary-dial trunks, put a check in the R column.

Toll Type Prefix Required

3

Toll Type allows the system to classify calls as either local or toll, based on the
number dialed by the user. Normally, people have to dial a toll-call prefix
(1 or 0) before dialing the area code and telephone number for a toll call. In some
areas this is not necessary; dialing a prefix depends on local telephone company
requirements and the type of line/trunk used.
Find out from the local telephone company which trunks require a toll-call prefix.
This information is used by the system when a toll call is placed by an extension
on ground-start or loop-start trunks.
For reliable toll restriction, telephone company trunks must require 1 or 0 for toll
calls. Also, the Toll Type feature does not apply to tie trunks.

Planning Form Instructions
On Form 2c, in the Toll Type Prefix Required for LD column, check Yes next to any
trunks on which people need to dial a prefix when placing toll calls.

3

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Hold Disconnect Interval

Page 3-14

3

This option allows you to set the number of milliseconds (ms) before the line/trunk
is released when a caller on hold hangs up and abandons the call. Local
telephone companies use either a long (450 ms) or short (50 ms) interval. The
factory setting for the system is the long interval, since it is the interval used by
most telephone companies.
Check with the local telephone company for the disconnect interval used.
If the local telephone company uses the short interval, you must change the
factory setting. If you do not change the setting, when a caller waiting on hold
hangs up, the line/trunk is not released.

Planning Form Instructions
In the Hold Disc. Interval column on Form 2c, do one of the following:
■

To change to a short hold disconnect interval (50 ms), put a check in the
Short column.
NOTE:
If the local telephone company uses a short hold disconnect interval,
be sure you have checked No for Loop-Start Reliable Disconnect, as
described earlier in this section.

■

To keep the factory setting, a long hold disconnect interval (450 ms), put a
check in the Long column.

3

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

QCC Operator to Receive Calls
(Hybrid/PBX Mode Only)

Page 3-15

3

Use these instructions only if the system has one or more QCCs. Otherwise, skip
to “Remote Access.”
Assigning the QCC operator to receive calls on a line/trunk determines whether
incoming calls on the line/trunk ring into the QCC queue and which QCC operator
position answers the calls. This applies to Hybrid/PBX mode only.
NOTES:
1. If an operator presses the programmed Backup On (or Position Busy)
button on the console, any incoming calls are directed to other operator
positions (regardless of whether they normally receive such calls) or to
the programmed backup extension number. For more information, see
“Position-Busy Backup” in the “Queued Call Console (Hybrid/PBX Mode
Only)” section of Chapter 4.
2. Trunks assigned to ring into the QCC queue cannot be assigned as
Group Calling lines/pools.

Planning Form Instructions
For each ground-start, loop-start, and automatic-in tie line/trunk on Form 2c, write
one of the following in the QCC Operator to Receive Calls column:
■

If you do not want the calls received on the line/trunk to ring into the QCC
queue, write No (factory setting).

■

If you want all QCC operators to receive incoming calls on a line/trunk,
write All.

■

If you want to specify one or more QCC operators to receive incoming calls
on a line/trunk, write any combination of the extension numbers for up to
four operator positions.

If you wrote All or specified extension numbers in this procedure, then proceed to
the next section, “QCC Queue Priority Level.” Otherwise, skip to the following
section, “Pools (Hybrid/PBX Mode Only).”

3

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

QCC Queue Priority Level
(Hybrid/PBX Mode Only)

Page 3-16

3

The QCC queue priority determines the order in which calls on each line/trunk are
sent to QCC operator positions. You set the priority for each individual line/trunk.
Considerations to be used in deciding the priority level are discussed in the
description of Queued Call Consoles in the Feature Reference.
Since incoming calls on DID and non-automatic-in tie trunks route to specific
extension numbers, you cannot assign a QCC queue priority for these types of
trunks. Also, QCC queue priority cannot be assigned to private network tandem
trunk types (Legend-PBX or Legend-NTWK). However, calls received can be
directed to the Listed Directory Number (LDN) which has queue priority set.

3

Planning Form Instructions
On Form 2c, for each line/trunk with All or an extension number in the QCC
Operator to Receive Calls column, write the priority level (1 to 7) in the QCC
Queue Priority Level column for each line/trunk used for incoming calls. (A value
of 1 indicates the highest priority; a value of 7 indicates the lowest. The factory-set
priority for calls received on all trunks programmed to ring in the queue is 4.)

Pools (Hybrid/PBX Mode Only)

3

The system can have up to 11 pools with factory-set dial-out codes of 70 and 890
through 899. When the system is set up, pools are assigned automatically (see
the Feature Reference). If you want any lines/trunks grouped in a pool, you must
manually assign each line/trunk to the pool of your choice. Use the instructions in
this section.
NOTES:
1. Pools can be assigned to calling groups and all trunks within the pool are
directed to members of the calling group. Individual trunks within a pool
cannot be assigned to calling groups.
2. If the pool contains any dial-in trunks (such as DID trunks), the pool
cannot be assigned to a calling group. Also, pools with private network
tandem trunks should not be assigned to calling groups.
Decide whether to change the dial-out codes. Apply the same considerations as
you do for reassigning extension numbers.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Issue 1
August 1998

Lines/Trunks
Selecting Line/Trunk Options

Page 3-17

Planning Form Instructions
1.

2.

3.

Use the following guidelines to determine which trunks to group into pools:
■

Each pool should contain trunks of the same type (basic, WATS, FX,
or tie). Ground-start and loop-start trunks of the same type (for
example, WATS or FX) can be mixed in the same pool.

■

Do not mix different calling areas of WATS or FX trunks to different
cities or include both inbound-only and outbound-only trunks within
the same pool. DID trunks and/or trunks used for auxiliary
equipment cannot be grouped in pools. T1 Switched 56 data lines
should not be mixed with trunks used for voice calls. If you plan to
assign Pool buttons on telephones, do not group dial-in-only tie
trunks in pools.

■

In typical pooled systems, all the trunks are grouped in pools except
those mentioned previously, single special-purpose trunks, and any
basic trunks that are needed as personal lines assigned to a button
on a telephone.

■

Group the trunks for the main pool first. This should be the local
trunks capable of accepting 411, 911, and so on. If your system
includes ground-start basic trunks, reassign them from the dial-890
extension pool to the main pool. After these trunks are assigned to
the main pool, decide how to arrange the rest of the trunks in the
remaining pools. For private network systems, refer to the Network
Reference for additional information.

Indicate the dial-out code in the Pool/Dial-Out Code column on Form 2c by
doing one of the following:
■

To keep the factory set dial-out code, write the code.

■

To change the factory-set dial-out code:
a.

Write the new number in the Renumber to column.

b.

On Form 2d, System Numbering: Special Renumbers, write
the new number in the Renumber to column of the Pools
section of the form.

On Form 2c, use the Function column to identify different calling areas of
WATS trunks and different destinations of FX trunks.

Proceed to the next section, “Remote Access.”

3

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

3

Remote Access

!

Page 3-18

SecurityAlert:
The Remote Access feature of your system, if you choose to use it, permits
off-premises callers to access the system from a remote telephone by using
an 800 number or a 7- or 10-digit telephone number. The system returns an
acknowledgment signaling the user to enter his or her barrier code, which is
selected and programmed by the system manager. After the barrier code is
accepted, the system returns dial tone to the user. If you do not program
specific egress restrictions, the user will be able to place any call normally
dialed from a telephone associated with the system. Such an off-premises
network call is originated at, and will be billed from, the system location.
The Remote Access feature, as designed, helps the customer, through
proper programming, to minimize the ability of unauthorized persons to gain
access to the network. Most commonly, phone numbers and codes are
compromised when overheard in a public location, through theft of a wallet
or purse containing access information, or through carelessness (writing
codes on a piece of paper and improperly discarding it). Additionally,
hackers may use a computer to dial an access code and then publish the
information to other hackers.
(See Appendix A, “Customer Support Information,” for more information
about security.)

Use these instructions only if remote users need access to the system. Systems
that are part of a private network need to use these instructions to modify Remote
Access so that users can access remote trunks. Otherwise, skip to the next
section, “DS1 Connectivity (100D Module).”
The Remote Access feature allows people to use the system from a remote
location. It also allows remote system programming and maintenance by a
qualified technician.
You can assign remote access to any incoming line/trunk connected to the system
except T1 Switched 56 data facilities, DID and dial-in tie trunks, and private
network tandem trunks. (For DID, the routing digits supplied by the central office
must match the remote access code.)
This section contains instructions for:
■

Renumbering the remote access code from the factory setting

■

Allowing access to the Automatic Callback feature

■

Designating trunks for remote access

■

Specifying shared or dedicated access

■

Assigning barrier codes and class-of-restriction for security

■

Allowing access to private network tandem trunks

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Issue 1
August 1998
Page 3-19

For detailed information about these options, see the Feature Reference.
You may want to assign remote access to only a few trunks and increase the
number later if more are needed.
NOTES:
1. If you want to allow remote access on DID trunks, the routing digits
supplied by the central office must match the factory-set remote access
code (889) or the remote access code assigned to the system in the
following procedure.
2. Trunks programmed for both remote access and Group Calling will
receive remote access treatment only.
3. Remote access callers may not log in to a calling group but may call the
calling group by dialing the group access number.
4. Private network calls may use the Remote Access feature if the remote
access code is included in the non-local dial plan.

Planning Form Instructions
1.

See “Numbering the System” in Chapter 2. Review the numbers available
in the numbering plan you have selected. Before you begin planning
remote access, to assure that TTRs are available, check the Control Unit
Diagram on Form 1 to verify that one or more of the following types of
modules are present: 400 LS, 400 GS/LS/TTR, 008 OPT, 800 DID
(Hybrid/PBX mode only), 800 GS/LS-ID, 012 T/R, or 016 T/R modules.

2.

Under the DID and Private Network Tie Trunks heading at the top of Form
3a, Incoming Trunks: Remote Access, do one of the following:
■

To keep the factory-set access code, check Remote Access Code:
889 and proceed to Step 3.

■

To change the factory-set access code:
a.

Check Renumber to and write the new number on the line
provided.

b.

On Form 2d, System Numbering: Special Renumbers, write
the new number in the Renumber to column of the Remote
Access Code section at the bottom of the form. Proceed to
Step 3.

3

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Issue 1
August 1998

Lines/Trunks
Selecting Line/Trunk Options

3.

Page 3-20

Under the Automatic Callback heading at the top of Form 3a, check one of
the following:
■

If you do not want remote callers to use the Automatic Callback
feature, check Disable (factory setting).

■

To allow remote callers to use this feature, check Enable.
NOTE:
Private network calls to Remote Access cannot use the
Automatic Callback feature.

4.

Under the Barrier Required for Private Network Tie Trunks heading, check
one of the following:
■

If any of the following conditions apply, check Yes.
— You plan to assign barrier codes to these trunks.
— Private network Tie calls are allowed access to PSTN trunks
using ARS.
— Private network Tie calls pass through the system (use
Tandem switching).

■

!

If no barrier codes are planned for these trunks, check No.

SecurityAlert:
To help prevent toll fraud, barrier codes should always be assigned. The
barrier codes should also be the maximum length allowed.

5.

Under the Barrier Codes Required for Non-Tie Trunks (DID, PRI private
network calls, and PRI Dial-Plan routing) heading, check one of the
following:
■

If any of the following conditions apply, check Yes.
— You plan to assign barrier codes to these trunks.
— Private network PRI calls are allowed access to PSTN trunks
using ARS.
— Private network PRI calls pass through the system (use
Tandem switching).

■

!

If no barrier codes are planned for these trunks, check No.

SecurityAlert:
To help prevent toll fraud, barrier codes should always be assigned. The
barrier codes should also be the maximum length allowed.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

6.

Page 3-21

Remote access should not be assigned to DID trunks and private network
tandem trunks that are used for incoming customer calls. However, for all
trunks to which you are assigning remote access:
a.

b.

7.

Issue 1
August 1998

Transfer the information from Form 2c, System Numbering:
Line/Trunk Jacks to Form 3a:
1.

Write the logical ID and line/trunk number in the applicable
columns.

2.

Check either the DID or Priv. Net. Tie Trunk column or the
Non-Tie Trunk column.

3.

Complete the Line/Trunk Type and Description column.
Include the different calling areas of WATS trunks and
different destinations of FX trunks. If a private network trunk,
write Network.

For each line/trunk, check the Dedicated column (to indicate that it is
always used for remote access) or the Shared column (to indicate
that it is used for remote access when the system is in Night Service
operation). Do not check either column for private network trunks.

For Class-of-Restriction without Barrier Codes on Form 3a (page 3),
complete the DID and Private Network Tie Trunks and Non-Tie Trunks
sections as follows:
a.

Under the Network Calls heading, check one of the boxes using the
following information:
— If the switch is not part of a private network, check None.
— If the switch is part of a private network, and tandem calls will
pass through this system, check Tandem.
— If the switch is part of a private network, and network calls will
be allowed to access PSTN trunks, check ARS.
NOTE:
If Tandem or ARS is selected under Network Calls, the Restriction
should be set to Unrestricted. For additional information on private
networks, see the Network Reference.

b.

!

For Restriction, check one of the following three boxes:
Unrestricted, Outward Restrict (to keep the factory setting), or Toll
Restrict.

SecurityAlert:
It is recommended that Outward Restrict be set at all times; otherwise, toll
fraud can occur. If the switch is part of a private network and restrictions
need to be changed from Outward Restricted, barrier codes should be
required.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

c.

Issue 1
August 1998
Page 3-22

Under the Disallowed List Access heading, check the box if you plan
to assign disallowed lists.
NOTE:
Instructions for filling in the ARS Restriction Level and
Disallowed List numbers are included in Chapter 4,
“Features.”

8.

!

Form 3a (page 4) identifies programming information for four barrier codes.
If more barrier codes are planned, make the appropriate number of copies
of Form 3a, page 4. A maximum of 16 barrier codes is allowed.

SecurityAlert:
Barrier codes of at least 11 digits should be assigned to help prevent toll
fraud.
For Class-of-Restriction with Barrier Codes on Form 3a (page 4), do the
following for each barrier code:
a.

Write the barrier code number in the space provided, numbering
them sequentially beginning with 1.

b.

Write the 4- to 11-digit barrier code in the Digits space. The star is
added to the end of the barrier code. For security reasons, you may
want to record the code elsewhere.

c.

For Restriction, check one of the following three boxes:
Unrestricted, Outward Restrict (to keep the factory setting), or Toll
Restrict.

d.

Under the Disallowed List Access headings, check the boxes if you
plan to assign disallowed lists.
NOTE:
Instructions for filling in the ARS Restriction Level and
Disallowed List numbers are included in Chapter 4,
“Features.”

Proceed to the next section, “DS1 Connectivity (100D Module).”

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

DS1 Connectivity (100D Module)

Page 3-23

3

Use these instructions only if the system has a 100D module. Otherwise, skip to
“Tie Trunks.”
Digital Signal 1 (DS1) connectivity involves the transmission of digital signals in
DS1 format. The interface that enables the system to allow DS1 connections is
the 100D module. The system can have up to three 100D modules. Each 100D
module supports up to 24 logical endpoints (IDs) or ports (one for each channel),
even though the module has only one jack.
The 100D module can be configured to operate with either of the following types
of service:
■

T1 (factory setting). To transmit and receive voice and analog data and,
with T1 Switched 56 service, digital data.

■

PRI (Primary Rate Interface). To transmit and receive voice, analog, and
digital data.

To ensure the proper protocol between both ends of the DS1 connection, the
following options should be set for both types of service:
■

Type of Service

■

Frame Format

■

Suppression (Line Code)

■

Signaling mode

■

Line Compensation

■

Clock Synchronization

■

Channel Service Unit (CSU) setting

Additional settings must be entered for both services, especially for PRI and T1
Switched 56 service. Appropriate settings are determined by the transmission
facility to which the module is connected and/or is supplied by the service
provider. This section contains instructions for both T1 and PRI services.
NOTE:
PRI service for Release 2.0 through Release 4.1 systems requires that the
service provider’s switching equipment be either a 4ESS Generic 13
through 16, 5ESS Generic 6, or a 5ESS serving the FTS2000 (federal
government only) network. PRI service for a Release 1.0 or Release 1.1
system requires that the switching equipment be a 4ESS Generic 13
through Generic 16 switch. Release 4.2 and later systems require that the
service provider’s switching equipment may be any of the above systems,
or a DMS-100, DMS-250, or DEX600E.
If DS1s are to be used for private networks, see the Network Reference before
you begin this section and as you work through these instructions.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Page 3-24

3

Planning Form Instructions
On Form 2c, System Numbering: Line/Trunk Jacks:
1.

For all trunks listed as “PRI” in the Jack Type column:
NOTE:
You cannot use Channel 24 for services.

2.

a.

Write the kind of service to be connected to each channel in the
Incoming Line/Trunk Type column. If the PRI channel is being used
in a private network, write NTWK and the switch identifier in this
column.

b.

Write unequipped in the Incoming Line/Trunk Type column for any
channel not used at this time.

For all trunks listed as T1-Tie that do not show an unequipped entry in the
Incoming Line/Trunk Type column, write the kind of service connected to
each channel in the Incoming Line/Trunk Type column.
NOTE:
If you use common-channel signaling, you cannot use Channel 24
and program the module for tie-trunk emulation.

3.

T1 Service

Do one of the following:
a.

To select settings for T1 and T1 Switched 56, continue to the next
section, “T1 Service.” For T1 Switched 56 service, you must also
complete the “T1 Switched 56” section.

b.

To select settings for PRI, skip to “PRI Service.”

3

T1 service allows the emulation of different analog lines. You can also order
services, such as Megacom 800, over the channels. The capacity, however, is
limited to voice calls and data calls using a modem. In addition, beginning with
Release 4.0 of the MERLIN LEGEND Communications System, T1 supports
ACCUNET Switched Digital Service (or other circuit-switched data service) at
56-kbps when the T1 channel or T1-Tie trunk is configured as T1 Switched 56.
Release 6.0 and later systems allow T1 service to provide PRI or T1 Tie service in
a private network.
The planning form instructions below apply to both T1 and T1 Switched 56 service
except where noted. If you are configuring channels for T1 Switched 56 service,
complete these instructions then proceed to the “T1 Switched 56 – Network”
section that immediately follows. If configuring T1-Tie trunks for T1 Switched 56
service, proceed to the “Tie Trunks” section after completing these instructions. If
you are planning to use T1 service as PRI trunks in a private network, check the
PRI box under Type of Service on Form 3b (page 1) and proceed to the “PRI
Service” section. See the Network Reference for more information regarding
configuration for use in a private network.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Issue 1
August 1998

Lines/Trunks
Selecting Line/Trunk Options

Page 3-25

Planning Form Instructions
On Form 3b (page 1), Incoming Trunks: DS1 Connectivity (100D Module), for
each 100D module in the system:
1.

In the Module Slot No. space, write the number of the control unit slot that
contains the module (see the Control Unit Diagram on Form 1).
NOTE:
If more than one 100D module is used, complete the first box,
Module 1, to show the options assigned to the 100D module in the
lowest number control unit slot. Use the second box for the second
lowest-numbered slot, and the last box for the highest-numbered
slot.

2.

Under Type of Service, check T1 (the factory-setting).
NOTES:
1. For T1 or T1 Switched 56 service, the T1 box must be checked
on the form. (If you leave this blank, and T1 is not specified
during programming, the 100D module will not be programmed.)
2. Steps 3, 4, 5, and 6 must match the service provider settings.
Check with the provider if necessary. See “Obtaining Telephone
Company Information,” in Chapter 1, for more information.

3.

In the table under the T1 Trunks heading, write the channel number(s) for
each trunk type and/or, for Tie or All Tie, check the Tie-PBX, Toll, or S56
boxes.

4.

Under the Frame Format heading, do one of the following:

5.

6.

7.

a.

To retain the factory setting, check D4 Compatible.

b.

To change the factory setting, check Extended Superframe (ESF).

Under the Suppression (Line Code) heading, do one of the following:
a.

To retain the factory setting, check AMI-ZCS.

b.

To change the factory setting, check B8ZS.

Under the Signaling Mode heading, for all boxes that describe T1 modules,
do one of the following:
a.

To retain the factory setting of robbed-bit signaling, check
Robbed-Bit Signaling (RBS).

b.

To change the factory setting to common-channel signaling, check
Common-Channel Signaling (CCS).

Under the Line Compensation heading:
a.

Fill in the approximate distance (number of cable feet) between the
100D module and its channel service unit (CSU) or other far-end
connection in the space provided next to Cable Feet.

b.

Use Table 3–3 to select the Line Compensation setting needed.
(The factory setting is 1.)

3

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Table 3–3.

Page 3-26

Line Compensation Settings

Setting
1 (factory setting)
2
3
4
5

*

Issue 1
August 1998

dB Loss
-0.6
-1.2
-1.8
-2.4
-3.0

Cable Feet*
0−133
133−266
266−399
399−533
533−655

Based on 22-gauge cable.

8.

If the system includes both 800 NI-BRI and 100D modules, clock synchronization planning should be completed at the same time. There is only one
primary/secondary/tertiary clock for both 800 NI-BRI modules and 100D
modules, with the same system programming screens used for both types.
Plan your clock source administration to minimize the need for clock
switching, which is known to cause noise on active calls.
NOTE:
The following information is for planning clock synchronization in
systems that are not part of a private network. For planning clock
synchronization in a private network configuration, see the Network
Reference.
Under Priority in the Clock Synchronization section, do one of the following:
■

If installing only one 100D module:
— To keep the factory setting, check Primary (that is, this
module provides synchronization for the system).
— If the synchronization source is other than through the 100D
module, check None.

■

If installing more than one 100D module, decide which module, if
any, provides the primary synchronization:
— If Module 1 provides clock synchronization, check Primary in
the first box (the factory setting).
— If Module 2 (or Module 3) provides clock synchronization,
check Primary in the box that describes that 100D module.
— If the synchronization source is other than through a 100D
module, check None.

9.

If assigning backup synchronization:
a.

In the box that describes the 100D module providing secondary
synchronization, check Secondary.

b.

In the box that describes the 100D module providing tertiary back
up, check Tertiary.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

10.

Issue 1
August 1998
Page 3-27

Under the Source subheading in each box, do one of the following:
■

To retain the factory setting, check Loop (that is, the system uses
the clock of the far-end connection).

■

To change the setting, check Local (that is, the clock is
free-running).
NOTE:
The MERLIN LEGEND system must be set to Loop if the
clock Source is coming from the network. The Local setting
is generated from the MERLIN LEGEND system and must be
used whenever connecting two MERLIN LEGEND systems
or a MERLIN LEGEND system and a DEFINITY system
(Tie trunk). In a Tie trunk configuration, one system MUST
have the clock Source set to Local and the other MUST be
set to Loop.

11.

Under the Activation subheading in each box, do one of the following:
■

If loop clock synchronization is taking place, check Active (factory
setting).

■

If the clock is free-running, check Not Active.
NOTE:
Normally, the primary synchronization source is set to Active
and other modules are set to Not Active.

12.

If incoming ground-start or loop-start trunks are to be emulated, then
record the CSU setting under the Channel Service Unit heading by doing
one of the following:
a.

To retain the factory setting, check Foreign Exchange.

b.

To change the factory setting, check Special Access.

To set up T1 channels for T1 Switched 56 service, continue with the next section.
To set up T1 Switched 56 service on T1-Tie trunks, proceed to the section entitled
“Tie Trunks.” To set up a 100D module for PRI service, proceed to the section
entitled “PRI Service.”

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Issue 1
August 1998
Page 3-28

T1 Switched 56 – Network

3

Use these instructions only if channels on a 100D module are to be programmed
as T1 Switched 56 channels. The instructions provided in the “T1 Service” section
must be completed first.
T1 Switched 56 service provides high speed digital data services (up to 56-kbps
per channel) to the network as well as digital Tie trunk services. This allows you to
use your T1 facilities for basic digital data and file transfer needs, as well as for
more sophisticated personal and/or group video conferencing.
NOTES:
1. T1 Switched 56 service is supported only in Hybrid/PBX or Key mode.
2. Incoming data calls that attempt to route to busy data endpoints,
unassigned Dial Plan numbers, or ports that are not equipped with data
endpoints will not be connected.
This section contains instructions for configuring those T1 Switched 56 options
that apply to the T1 network interface. For information specific to digital Tie trunk
planning, refer to the “Tie Trunks” section of this chapter.
The following options are covered in this section:
■

Direction

■

Incoming and Outgoing Signaling Type

■

Incoming and Outgoing Signaling Mode

■

Dial Plan Routing options (incoming services)

After completing the procedure for filling in the module information on Form 3b,
pages 1 and 2, continue to the next section to fill in T1 Switched 56 options.

Planning Form Instructions
On Form 3b (page 11), T1 Switched 56 Options, for each T1 channel programmed
for T1 Switched 56 service:
1.

Select the Channel Direction.
■

2.

Select either Incoming, Outgoing, or Two Way. The factory setting
is Two Way.

Select both the Incoming and Outgoing Signaling Mode.
■

Select either Touch-tone or Rotary. The factory setting is
Touch-tone.

3

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

3.

Issue 1
August 1998
Page 3-29

Select both the Incoming and Outgoing Signaling Type.
■

Select either Wink, Auto, or Delay. The factory setting is Wink.

The Incoming Signaling Type selected will determine the Incoming Routing
Method:
■

If the Incoming Signaling Type is set to Auto, the Incoming Routing
Method is Line Appearance Routing. Incoming data calls are
typically terminated at a data extension/endpoint that has a personal
line appearance. The 1B data call may also terminate at a data
extension/endpoint in a calling group.

■

If the Incoming Signaling Type is set to Wink or Delay, the Incoming
Routing Method is Dial Plan Routing. Incoming data calls are
routed by dial plan and may terminate to an SA button on any data
extension within the system.
If the switch is part of a private network, data calls can be routed to
another switch in the network. T1-emulated tie lines need to be
assigned to a pool and programmed to a route. The route must be
marked as Data Only.

4.

If the Incoming Signaling Type is programmed as Wink or Delay and
incoming data calls are routed by dial plan, you may have to manipulate
the incoming digits by deleting or adding digits. This is because, in many
cases, the digits that are sent by the service provider may not match the
programmed dial plan. See the Network Reference for more information.
Enter the following Dial Plan Routing options:
■

Expected Number of Digits. Check the expected number of digits
(1–4). The factory setting is 3.

■

Number of Digits to Delete. Check the number of digits to delete
(0–4) in order to match the Dial Plan. The factory setting is 0.

■

Specific Digits to Add. Enter the specific digits to add (1–9999) to
the collected digits in order to determine a routing pattern. If no
digits are to be added, check 0. The factory setting is 0.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Page 3-30

3

PRI Service

Use these instructions only if the type of service on a 100D module is PRI.
Otherwise, skip to the next section, “Tie Trunks.”
NOTE:
For private PRI network trunks, see the “T1 Service” section earlier in this
chapter and the Network Reference. Do not use the PSTN PRI service.
PRI is a standard access arrangement of Integrated Services Digital Network
(ISDN) service that may be used to connect the system to another switch over a
DS1 facility.
This section contains instructions for recording decisions about the following
options for each PRI facility:
■

B-channel groups

■

PRI services (incoming and outgoing) according to B-channel group

■

Line Appearance Routing (incoming services)

■

Dial Plan Routing (incoming services; Hybrid/PBX mode only)

■

Outgoing Tables (Network Selection Table, Special Services Table, and
Call-by-Call Service Table)

■

Telephone Number to Send station identification or automatic numbering
information (SID-ANI) information

■

Test Telephone Number(s)

■

Timers and Counters

■

Terminal Equipment Identifier (TEI)

After completing the procedure for filling in the module information on Form 3b,
pages 1 and 2, continue to the next section to fill in PRI options.
NOTES:
1. The PRI service type must be selected before entering the PRI
information during system programming.
2. Because of the complexity of the timer, counter, and terminal equipment
identifier information, the factory settings should rarely be changed.
Incorrect settings can have an adverse affect on the operation of PRI
facilities.
3. If there is more than one 100D module set up for PRI service or you have
more than eight B-channel groups assigned to a module, make copies of
Form 3b (page 4) as necessary.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Issue 1
August 1998
Page 3-31

Module Information

3

Use the procedure in this section to fill in module information on pages 1 and 2 of
Form 3b, Incoming Trunks: DS1 Connectivity (100D Module). Then proceed to the
next section, “PRI Options.”

Planning Form Instructions
On Form 3b (page 1), Incoming Trunks: DS1 Connectivity (100D Module), for
each 100D module with PRI service:
1.

In the module Slot No. space, write the number of the control unit slot that
contains the module (see the Control Unit Diagram on Form 1).
NOTE:
If more than one 100D module is used, complete the first box,
Module 1, to show the options assigned to the 100D module in the
lowest-numbered control unit slot. Use the second box for the
second lowest-numbered slot and the last box for the
highest-numbered slot.

2.

Under the Type of Service heading, check PRI. (During programming, PRI
must be selected here before the PRI options information is entered. When
it is selected, the system restarts.)

3.

Under the Switch Type (PRI Service Only) heading, check the PRI switch
type. If the switch is part of a private network, check either Legend-PBX or
Legend-NTWK.
NOTE:
If the switch is part of a private network and is connected to a
DEFINITY switch, select Legend-PBX. If the switch is connected to
another MERLIN LEGEND system, one switch must be configured
as Legend-PBX and the other is configured as Legend-NTWK. See
the Network Reference for more information.

4.

Under the Frame Format heading, change the factory setting by checking
the Extended Superframe (ESF) box.

5.

Under the Suppression (Line Code) heading, change the factory setting by
checking the B8ZS box.

6.

Under the Signaling Mode heading, check Common-Channel Signaling
(CCS).
NOTE:
CCS is automatically assigned when PRI is selected. Also,
Channel 24 cannot be used for voice or data transmissions.

3

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

7.

Page 3-32

Under the Line Compensation heading:
a.

Fill in the approximate distance (number of cable feet) between the
100D module and its CSU or other far-end connection in the space
before Cable Feet.

b.

Use Table 3–4 to select the line compensation setting needed. (The
factory setting is 1.)

Table 3–4.

Line Compensation Settings

Setting
1 (factory setting)
2
3
4
5
*

Issue 1
August 1998

dB Loss
-0.6
-1.2
-1.8
-2.4
-3.0

Cable Feet*
0−133
133−266
266−399
399−533
533−655

Based on 22-gauge cable.

8.

If the system includes both 800 NI-BRI and 100D modules, clock synchronization planning should be completed at the same time. There is only one
primary/secondary/tertiary clock for both 800 NI-BRI modules and 100D
modules, with the same system programming screens used for both types.
If the switch is part of a private network, clock synchronization needs to be
coordinated for the entire network. See the Network Reference for
information.
Plan your clock source administration to minimize the need for clock
switching, which is known to cause noise on active calls.
Under Priority in the Clock Synchronization section, do one of the following:
■

If installing only one 100D module:
— To keep the factory setting, check Primary (that is, this
module provides synchronization for the system).
— If the synchronization source is other than through the 100D
module, check None.

■

If installing more than one 100D module, decide which module, if
any, provides the primary synchronization:
— If Module 1 provides clock synchronization, check Primary in
the first box (the factory setting).
— If Module 2 (or Module 3) provides clock synchronization,
check Primary in the box that describes that 100D module.
— If the synchronization source is other than through a 100D
module, check None.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

9.

10.

11.

12.

Issue 1
August 1998
Page 3-33

If assigning backup synchronization:
a.

In the box that describes the 100D module providing secondary
synchronization, check Secondary.

b.

In the box that describes the 100D module providing tertiary back
up, check Tertiary.

Under the Source subheading in each box, do one of the following:
■

To retain the factory setting (that is, the system uses the clock of the
far-end connection), check Loop.

■

To change the setting (the clock is free-running), check Local.

The typical setup for the primary synchronization source is Active, and
other modules are set to Not Active. Under the Activation subheading in
each box, do one of the following:
■

If loop clock synchronization is taking place, check Active (factory
setting).

■

If the clock is free-running, check Not Active.

Under the Channel Service Unit heading, check Foreign Exchange.

PRI Options
If the switch is part of a private network, the PRI options are automatically set. If
the switch is not part of a private network, after you have completed the module
information on pages 1 and 2 of Form 3b, Incoming Trunks: DS1 Connectivity
(100D Module), use the instructions in this section to record these PRI options:
■

Assigning B-channels to groups

■

Associating outgoing and incoming services to the groups

■

For groups with incoming services, selecting an incoming routing method
(Dial Plan Routing or Line Appearance) and providing routing information

■

For groups with outgoing services, completing the Network Selection,
Special Services, and Call-by-Call Service tables

■

Identifying the trunk and telephone numbers sent to the network for caller
identification

■

Assigning a test number used for maintenance by the service provider,
changing timers and counters from the factory settings, and assigning the
Terminal Equipment Identifier (TEI)

All channels assigned to a group must be on the same 100D module. Also, the
order of the B-channel groups is not important. When programmed for PRI, the
single DS1 jack on the 100D module supports 23 B-channels (the Channel 24
superframe transmits signaling mode information).

!

CAUTION:
The order in which channels are assigned within a group must be the exact
opposite of the order in which the telephone company’s switch hunts
through for a channel. Consult with the service provider to determine what
the correct order should be.

3

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Issue 1
August 1998
Page 3-34

Planning Form Instructions
1.

2.

To assign B-channels to groups, determine which channels to group
together and then record each group on Form 3b (page 3), under the
B-Channel Groups heading:
a.

Write the group number (1−80) under the B-Channel Group No.
heading (start with 1 and number sequentially).

b.

Write the slot and port number of each B-channel assigned to the
group (see Form 2c, System Numbering: Line/Trunk Jacks). To
determine the port number, assume that port 1 is at the bottom of
the module to which you are assigning B-channels.

c.

For all channels you plan to associate with the group, write the trunk
number (see Form 2c, System Numbering: Line/Trunk Jacks).

To assign service to each B-channel group, complete Form 3b (page 4) as
follows: If there is more than one 100D module set up for PRI service or
you have more than eight B-channel groups assigned to a module, make
copies of Form 3b (page 4) as necessary.
a.

In the Module Slot No. space, write the number of the control unit
slot that contains the module as noted on pages 1 and 2 of this form.

b.

Under the B-Channel Group No. heading, copy the B-Channel
group numbers from Form 3b (page 3).

c.

Write the services to be associated with each group under the
Outgoing Services and Incoming Services headings. Select from the
following services:
■

AT&T Toll. (for 4ESS or 5ESS, see Form 3b, page 1)
Megacom WATS, Megacom 800, ACCUNET SDS, Software
Defined Network (SDN), MultiQuest, and Long Distance.

■

5ESS Local. (For switch type 5ESS, see Form 3b, page 1)
OUTWATS, 56/64 Digital, Virtual Private Network, and
INWATS.

■

MCI Toll. (for DMS-250 or DEX600E, see Form 3b, page 1)
MCI Prism, MCI VNet, MCI 800 and MCI 900.

■

DMS-100 Local. (for a DMS-100, see Form 3b, page 1) DMS
Private Network, DMS INWATS (Inward Wide Area Telephone Service), DMS OUTWATS (Outward Wide Area Telephone Service), DMS FX (Foreign Exchange), DMS Tie
Trunk.

■

Other. Call-by-Call, Other.
NOTE:
If a B-channel group has more than one outgoing service,
then enter Call-by-Call on Form 3b, page 4, under the
Outgoing column instead of itemizing the services. Form 3b,
page 8, is where you enter specific services with specific
dial-out patterns.

3

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Issue 1
August 1998

Lines/Trunks
Selecting Line/Trunk Options

d.

3.

Page 3-35

If the group has incoming services assigned, do one of the following:
■

If the routing will be Dial Plan Routing (Hybrid/PBX mode
only), check Dial Plan Routing.

■

If the routing will be by line appearance, check Line
Appearance.

For all B-channel groups that are programmed to route calls by line
appearance, assign a telephone number to each line in the B-channel
group. Record the information on Form 3b (page 5):
a.

Write the B-channel group numbers and the trunk number(s) from
Form 3b (page 3).

b.

In the Telephone Number column, write the unique inbound routing
telephone number (the “directory number”) of up to 12 digits,
furnished by the PRI service provider.
NOTE:
The factory does not preassign a telephone number. The telephone
number you assign should be the same sent to the system by the
network. The number should also be unique within the same
B-channel group and must be different from the associated test
telephone number. (Test telephone numbers are assigned later in
this procedure.)

4.

For all B-channel groups you plan to assign to Dial Plan Routing, you must
program the Dial Plan Routing table to direct the system to properly route
calls. Record table entries (maximum: 16 entries) on Form 3b (page 6):
a.

b.

For the entry to be activated, a service must be entered. In the
Service cell, write one of the following:
■

AT&T Toll. (for 4ESS or 5ESS, see Form 3b, page 1)
Megacom WATS, Megacom 800, ACCUNET SDS, Software
Defined Network (SDN), MultiQuest, and Long Distance.

■

5ESS Local. (For switch type 5ESS, see Form 3b, page 1)
OUTWATS, 56/64 Digital, Virtual Private Network, and
INWATS.

■

MCI Toll. (for DMS-250 or DEX600E, see Form 3b, page 1)
MCI Prism, MCI VNet, MCI 800 and MCI 900.

■

DMS-100 Local. (for a DMS-100, see Form 3b, page 1) DMS
Private Network, DMS INWATS (Inward Wide Area Telephone Service), DMS OUTWATS (Outward Wide Area Telephone Service), DMS FX (Foreign Exchange), DMS Tie
Trunk.

■

Other. Call-by-Call, Other.

In the Pattern to Match cell, write the exact pattern to match if you
have more than one block of incoming numbers. If you want to
match any pattern, leave it blank.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

5.

Issue 1
August 1998
Page 3-36

c.

In the Total Digits in Dialed Number cell, write the total number of
digits (0−14) expected in the dialed number; 0 is a wildcard, that is,
match any number. (Contact the service provider for the appropriate
number.)

d.

After the match has been made, do one of the following to enable
the system to determine where to direct the call:
■

To delete digits, write the number of digits to delete (0−14).
(The system deletes from the first digit forward.)

■

To add digits, write the exact digits to enter (up to four digits)
as a prefix, for example, 7128. The factory setting is blank.
(The system adds the digits to the beginning of the number.)

In the Network Selection Table of the outgoing tables on Form 3b (page 7),
the dial pattern represents the dial code for specifying a long-distance
common carrier; the asterisks represent the digits in the common carrier
identification. If the telephone company has directed you to change this
information, obtain the correct entry from them. But note that the dial
pattern must come first. Entry 1 represents current national standards for
specifying long-distance carriers (asterisks represent the common carrier
code wildcard so that anything will match). Entry 0 represents the coming
national standards. The remaining entries are reserved for future use.
NOTE:
The Network Selection Table and the Special Services Table contain
factory settings that reflect U.S. standards for public telephone
network access. These factory settings can be modified to conform
to other standards. However, you should not change them unless the
telephone company explicitly instructs you to do so.

6.

7.

In the Special Services Table:
a.

In the Pattern to Match cell, write the exact dial pattern to match.
(No wildcards are permitted.)

b.

In the Operator cell, indicate Local Operator (OP), Presubscribed
Operator (P), or No Operator service (none) associated with the
pattern.

c.

In the Type of No. cell, indicate whether the pattern is for calling
National (N) or International (I).

d.

To delete digits, write the number of digits to delete (0−4). (The
system deletes from the first digit forward.)

For all call-by-call B-channel groups, to route all outgoing calls over a
call-by-call B-channel group, you must program the Call-by-Call Service
Table to direct the system to properly route calls. Record table entries
(maximum: 10) on Form 3b (page 8):
a.

In the Pattern to Match cell, write the dial pattern to match (up to 8
digits). No wildcards are permitted.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

b.

Issue 1
August 1998
Page 3-37

In the Call Type cell, indicate the type(s) of calls that will be
associated with the pattern by doing one of the following:
■

If all outgoing calls will be voice calls (for example, Megacom
WATS), write Voice.

■

If all outgoing calls will be data only (for example,
ACCUNET), write Data.

■

If outgoing calls may be either voice or data (for example,
SDN), write Both.

NOTE:
If you indicate Both, make sure the service can support both voice
and data calls.
c.

d.
8.

In the Service cell, write one of the following:
■

AT&T Toll. (for 4ESS or 5ESS, see Form 3b, page 1)
Megacom WATS, Megacom 800, ACCUNET SDS, Software
Defined Network (SDN), MultiQuest, and Long Distance.

■

5ESS Local. (For switch type 5ESS, see Form 3b, page 1)
OUTWATS, 56/64 Digital, Virtual Private Network, and
INWATS.

■

MCI Toll. (for DMS-250 or DEX600E, see Form 3b, page 1)
MCI Prism, MCI VNet, MCI 800 and MCI 900.

■

DMS-100 Local. (for a DMS-100, see Form 3b, page 1) DMS
Private Network, DMS INWATS (Inward Wide Area
Telephone Service), DMS OUTWATS (Outward Wide Area
Telephone Service), DMS FX (Foreign Exchange), DMS Tie
Trunk.

■

Other. Call-by-Call, Other.

If the system will need to delete digits, write the number of digits to
delete (0−8). (The system deletes from the first digit onward.)

On Form 3b, check the appropriate box for the information that will be sent
to the network for outgoing PRI calls. Check Extension Only, Base Number
with Extension, or Line Telephone Number.
If you check Line Telephone Number, do the following:
■

Identify the trunk number.

■

Write the telephone number (up to 12 digits) that identifies the
company as the caller in the Telephone Number to Send column.
NOTE:
There is no factory-assigned telephone number. If you assign a
number, it does not have to be unique. Also, the availability of caller
identification information may be limited by your local-serving
jurisdiction, by availability, or by central office equipment.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Issue 1
August 1998

Lines/Trunks
Selecting Line/Trunk Options

9.

Page 3-38

If available, assign a test telephone number that is used for maintenance
by the service provider. For each 100D module with a PRI service type,
write the test telephone number (up to 12 digits) used for maintenance next
to the module number under the Test Telephone Numbers heading on
Form 3b (page 10).
NOTE:
The factory does not assign a test telephone number. You must
assign the same number as that furnished by the PRI service
provider. It must be different from the numbers assigned to other
channels associated with the same B-channel group.

10.

11.

Under the Timers and Counters heading, do one of the following:
■

To keep the factory setting, leave the Change to column blank.

■

To change the factory setting for any timer or counter, write the new
threshold on the appropriate line in the Change to column.

Under the Terminal Equipment Identifier (TEI) heading, do one of the
following:
■

To keep the factory-set TEI, check 0.

■

To change the factory-set TEI, write a value from 1 to 63 in the
space provided.

NOTE:
If the system includes DS1 connectivity, all local offerings of DS1
configurations must be reviewed by Lucent Technologies Sales and Design
Support Center (SDSC) personnel to ensure compatibility. For more
information, see Appendix D, “T1/PRI Review.” Also, information required
by the facilities vendor is discussed in Appendix E, DS1 Connectivity
Ordering.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Page 3-39

3

Tie Trunks

Use these instructions only if the system has tie trunks, including tie trunks
emulated through a DS1 connection. Otherwise, skip to the next section, “DID
Trunks (Hybrid/PBX Mode Only).”
If configuring T1-Tie trunks, including those with Switched 56 digital data service,
complete the instructions in the “T1 Service” section first.
Tie trunks must be configured to match central office requirements or the
configuration of the system to which they tie. Review tie trunk operations and
make the following decisions about the way each tie trunk operates:
■

Direction

■

Signaling type

■

E & M Signaling

■

Dial mode

■

Dial tone

■

Answer supervision time

■

Disconnect time

■

Private network tandem trunks
NOTE:
See the Network Reference for information on private networking.

This section contains instructions for each of these options.

Planning Form Instructions
1.

Transfer the trunk identification from Form 2c, System Numbering:
Line/Trunk Jacks, to Form 3c, Incoming Trunks: Tie. Write the logical ID
and trunk number for each tie trunk connected to the system.

2.

Under the Direction heading on Form 3c, check the direction for each tie
trunk next to its trunk number:

3.

■

If the tie trunk is two-way, check the Two Way (factory-setting)
column. Use this option for private networks.

■

If the trunk is one-way, check either the Outgoing column or the
Incoming column.

Under the Signaling Type (Intype/Outtype) heading, check the appropriate
column for either In or Out under the Wink, Delay, Immediate, or Automatic
columns for each tie trunk. For T1 facilities used for services (for example,
Megacom), consider the direction of the tie trunk and how trunk
assignments will be made. Then select from the following:

3

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Issue 1
August 1998
Page 3-40

NOTES:
1. Check the same signaling type used by the system to which you
are connecting. For incoming-only or two-way tie trunks, the
incoming type must be the same as the outgoing type of the
remote system. For outgoing-only or two-way tie trunks, the
outgoing type must be the same as the incoming type of the
remote system.
2. Wink is the factory setting and is the preferred type, followed by
Delay then Immediate. Immediate does not work with touch-tone
dial mode. Use Delay for private networks.
3. Automatic incoming signaling is required if the CO switch is a
Lucent Technologies 5ESS or Northern Telecom DMS-100 and
incoming calls are programmed to route by Line Appearance.
Immediate Dial outgoing signaling should not be used for digital
emulated Tie trunks using T1 Switched 56 service due to the
lack of trunk integrity checking.
4. Dial-in E&M Tie trunks cannot be assigned to ring into a calling
group. Only Auto-in Tie trunks can be assigned to ring into a
calling group.

4.

■

One-way, Outgoing Tie Trunks. All outgoing calls are placed using
Automatic Route Selection, and tie trunks are not assigned to
personal line or Pool buttons on telephones. Select wink signaling.

■

One-way, Outgoing Tie Trunks. Tie trunks are assigned to
personal line or Pool buttons on telephones. Select immediate
signaling.

■

One-way, Incoming Tie Trunks. Dialed Number Identification
Service (DNIS) is included. Select wink signaling.

Under the E&M Signal heading, select one of the following signaling types
to be used on the tie trunks:
NOTE:
E&M Signaling does not apply to digital emulated Tie trunks using T1
Switched 56 service and should not be set during administration of
those trunks.
■

If the tie trunks are connected to the other system through the local
telephone company, check 1S (the factory setting).

■

If the tie trunks are connected directly to a system that uses type 1S
signaling and is located near this system, check 1C.
NOTE:
The 1C option assumes that the two systems are connected
together without any provisioned facility, and without any
signaling treatment equipment. When connecting a MERLIN
LEGEND switch to another MERLIN LEGEND switch, use 1C
on one switch and 1S on the other.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options
■

Issue 1
August 1998
Page 3-41

If the tie trunks are connected directly to a system that uses type 5
signaling and is located near this system, check 5.
NOTE:
When connecting a MERLIN LEGEND switch to a DEFINITY
switch, use the Type 5 signaling type.

5.

To select dial mode:
a.

Under the Inmode heading, check either the Touch-Tone column or
Rotary column (factory setting) for each incoming-only and each
two-way tie trunk. Use Touch-Tone for private networks.
NOTES:
1. If you have checked the Incoming or two-way column for a
tie-trunk’s direction and Immediate for its incoming signaling
type, you cannot use the Touch-Tone setting for Inmode.
2. Touch-Tone outmode can be used with Outtype Immediate
trunks, but Touch-Tone inmode cannot be used with Intype
Immediate Trunks.

b.

6.

7.

8.

Under the Outmode heading, check either the Touch-Tone column
or the Rotary column (factory setting) for each outgoing-only and
each two-way tie trunk.

To indicate whether the system provides a dial tone for people calling in on
a tie trunk, check one of the following for each tie trunk under the Dial Tone
heading:
■

If the system provides a dial tone, check Remote (factory setting).
Use this setting for private networks.

■

If the system does not provide a dial tone, check Local.

For Answer Supv. Time, do one of the following:
■

To keep the factory setting, check the 300 column. Use this setting
for private networks.

■

To change to a new value, write the new value (20 to 4800 ms) in
the Other column. (Use 20-ms increments.)

Under the Disconnect Time heading, do one of the following:
■

To keep the factory setting, check the 300 column. Use this setting
for private networks.

■

To change to a new value, write the new value (140 to 2400 ms) in
the Other column. (Use 10-ms increments.)

Proceed to the next section, “DID Trunks (Hybrid/PBX Mode Only).”

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

DID Trunks (Hybrid/PBX Mode Only)

Page 3-42

3

Use these instructions only if Direct Inward Dial (DID) trunks are connected to the
system. Otherwise, skip to the next section, “NI-1 BRI Connectivity.”

!

SecurityAlert:
DID numbers that correspond to the remote access code can be used to
make calls on the system’s trunks, leading to toll abuse and/or fraud. (See
Appendix A, “Customer Support Information,” for more information about
security.)

This section contains instructions for setting the following options for DID trunks:
■

Type of DID Trunks

■

Expected Digits

■

Delete Digits

■

Add Digits

■

Signaling

■

Invalid Destination

■

Trunks Included in Blocks

These options are assigned to blocks of trunks. A maximum of two blocks is
permitted.
If you want to allow remote access on DID trunks, one of the telephone numbers
assigned by the telephone company must match the remote access dial code.
The factory setting is 889.
If two-way DID service is available from the local telephone company, it is typically
set up as Tie trunk service.
NOTES:
1. If the system will have two blocks, make a copy of Form 3d and write the
block number in the Block Number space. Check with the local telephone
company to determine the number of digits sent.
2. DID trunks cannot be assigned to ring into a calling group.

!

CAUTION:
Since the system can have only two blocks of DID trunks, when configuring
a private network, careful planning of both immediate and future needs is
essential when ordering DID trunks from the local telephone company. See
the Network Reference for additional information.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Issue 1
August 1998
Page 3-43

Planning Form Instructions
1.

2.

3.

4.

5.

6.

On Form 3d, under the Type heading, do one of the following:
■

To keep the factory setting, check the Wink-Start box.

■

To change the type, check the Immediate-Start box.

Under the Expected Digits heading on Form 3d, do one of the following:
■

To show that the telephone company sends the factory-set number
of digits, check the box labeled 3.

■

To show the number of digits sent by the telephone company, check
one of the boxes labeled 1, 2, or 4.

Compare the number of digits sent by the local telephone company to the
number of digits in the system numbering plan, and do one of the following:
■

If the system’s numbering plan matches the number of digits sent by
the telephone company, check 0 (the factory setting) under the
Delete Digits and Add Digits headings.

■

If the number of digits sent by the local telephone company is more
than the number of digits in the system numbering plan, specify that
one to four digits be deleted from the telephone company digits by
checking the appropriate number (1, 2, 3, or 4) under the Delete
Digits heading.

■

If the number of digits sent by the local telephone company is fewer
than the number of digits in the system’s numbering plan, specify
the specific digits (1−9999) to be added to the digits sent; check the
Add these digits box under the Add Digits heading and then write
the specific digits to be added in the space provided.

Under the Signaling heading, do one of the following:
■

To keep the factory-set signal, check Rotary.

■

To change the setting, check Touch-Tone. (You cannot have
touch-tone if you selected Immediate-Start.)

Under the Invalid Destination heading, do one of the following. (The Invalid
Destination setting applies to both blocks. You cannot specify a different
setting for each block.)
■

To indicate that calls to unassigned extension numbers go to the
backup position (usually the primary operator), check Send to
backup position.

■

To indicate that calls to unassigned extension numbers should
receive a fast busy signal, check Return to fast busy.

Group DID trunks into each block by assigning the DID trunks according to
how incoming calls must be routed to reach the proper local and non-local
extension numbers, and transfer the information from Form 2c, System
Numbering: Line/Trunk Jacks to the Trunks Included in Block section of
Form 3d. Write the logical ID, trunk number, and telephone number in the
applicable columns.

3

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

7.

Page 3-44

Select the disconnect time for each DID trunk by doing one of the following
under the Disconnect Time heading:
■

To keep the factory setting, check 500 ms.

■

To change the disconnect time, write the new value (10 to 2550 ms)
in the Other column.

Proceed to the next section, “NI-1 BRI Connectivity.”

NI-1 BRI Connectivity

3

To ensure proper operation of the BRI line features, the following options must be
set on the MERLIN LEGEND system during system programming:
■

Service Profile Identifier (SPID) for each BRI line B-channel

■

Directory Number (DN) for each BRI line B-channel

■

Clock Synchronization for the system

■

Timers for each BRI module (system provides defaults)

The following affect the operation of the MERLIN LEGEND system. However, they
are programmed on the Central Office (CO) switch:
■

Service Configuration of the BRI lines (IOC “S”, Multiline Hunt)

■

Hunting pattern for a Multiline Hunt configuration

Service Profile

3

A Service Profile (SP) defines the interface on a BRI line between a CO and an
ISDN terminal. It specifies the parameters and their values necessary to provide
services to the terminal. There are standardized capability packages called ISDN
Ordering Codes (IOCs) that are configured on the CO at subscription time. The
IOC contains information necessary for the CO to provide service to the system.
The MERLIN LEGEND system supports the IOC “S” capability package, which
provides alternate voice/circuit-switched data on two B-channels with no packet
data capability or supplementary voice features, except for the Calling Party
Number/Billing Number (CPN/BN) feature, if available.
In addition to the IOC “S” capability package, the MERLIN LEGEND system supports Multiline Hunt (MLH) service for alternate voice and data hunting if the CO is
a Lucent Technologies 5ESS or Northern Telecom DMS-100 switch. For a Siemens SSC EWSD switch, MLH service must be provisioned as either voice or
data hunting. MLH service is provided through the Multiline Hunt Group (MLHG)
feature on Northern Telecom DMS-100 switches, and through the Series Completion feature on Lucent Technologies 5ESS and Siemens SSC EWSD switches.
NOTE:
The MLHG feature on the Lucent Technologies 5ESS and Siemens SSC
EWSD switches is not recommended for use with the MERLIN LEGEND
system.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Issue 1
August 1998
Page 3-45

MLH service may be configured in either a linear or circular pattern. Current
testing of the MERLIN LEGEND system with the CO switches supports linear
hunting on a Lucent Technologies 5ESS switch, and circular hunting on the
Northern Telecom DMS-100 and Siemens SSC EWSD switches. Other
configurations are possible, but they are not guaranteed to work with the MERLIN
LEGEND system.
The Service Profile consists of the following:
■

A Service Profile Identifier (SPID), which is a unique identifier used by the
CO to associate an ISDN terminal with a Service Profile.

■

A Directory Number (DN) for each BRI line B-channel. This DN is usually
the local phone number that was assigned by the service provider.

■

If MLH service is not subscribed, only one call to a particular DN will be
accepted at any given time, and any station with the line appearance of the
BRI line will alert. If MLH is subscribed, the CO will automatically hunt for
the next available B-channel within the hunt group and deliver multiple calls
to the same DN. If all B-channels are in use, subsequent calls to the same
DN will receive standard CO treatment (such as busy tone).

■

Optional features:
— Calling Party Number/Billing Number (CPN/BN) can also be ordered
at subscription time.

The local telephone company normally provides two SPIDs and DNs for each BRI
line (also called a Digital Subscriber Line [DSL]) ordered. The SPID consists of a
string of digits 0 through 9 not more than 20 digits in length. The DN consists of a
string of digits 0 through 9 not more than 10 digits in length. Each DSL will use two
lines on Form 3i, Incoming Trunks: BRI Options (800 NI-BRI Module).

Planning Form Instructions
1.

Transfer the following information from 2c, System Numbering: Trunk
Jacks, to Form 3i, Incoming Trunks: BRI Options (800 NI-BRI Module):
■

Write the logical ID in the “Logical ID” column. Skip a line between
each entry.

■

Write the line number in the “Line Number” column.
NOTE:
Refer to the information provided by the local telephone company to
enter the information below.

2.

Write the two DNs for each BRI line in the “Directory Number” column.

3.

Write the two SPIDs assigned to each BRI line in the “Service Profile
Identifier” column.

3

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Page 3-46

Refer to the NI-1 BRI Planner form for the information needed to complete the
next sections.
4.

Indicate the Service Configuration of the Central Office switch:
■

If configured with IOC package “S”, place a check in the IOC “S”
column under the “Service Configuration” heading.

■

If configured with MLH service, indicate the type of hunt group
provisioned by entering a V (voice only hunt group), D (data only
hunt group), or V/D (voice/data hunt group) in either the “MLHG” or
“Series Comp.” column under the “Service Configuration” heading
as appropriate.
NOTES:
1. IOC package “S” is available on the Lucent Technologies 5ESS,
Northern Telecom DMS-100, and Siemens SSC EWSD
switches.
2. If configured with MLH service, the MLHG feature must be used
if the CO is a Northern Telecom DMS-100 switch. The Series
Completion feature must be used if the CO is a Lucent
Technologies 5ESS or Siemens SSC EWSD switch.
3. The MERLIN LEGEND system does not support Voice/Data hunt
groups with the Siemens SSC EWSD central office switch.

5.

If configured with MLH (using either the MLHG or Series Completion
feature), indicate whether the hunt pattern is linear or circular, by placing a
check in the appropriate column under the “Hunt Pattern” heading.

6.

Indicate the features available on each BRI line:
■

If CPN/BN is available, place a check in the “CPN/BN” column, as
appropriate.

Clock Synchronization

3

NOTE:
The following information is for planning clock synchronization in systems
that are not part of a private network. For planning clock synchronization in
a private network configuration, see the Network Reference.
If the system includes both 800 NI-BRI and 100D modules, clock synchronization
planning should be completed at the same time. There is only one
primary/secondary/tertiary clock for both 800 NI-BRI modules and 100D modules,
with the same system programming screens used for both types.
Plan your clock source administration to minimize the need for clock switching,
which is known to cause noise on active calls.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Issue 1
August 1998
Page 3-47

The primary, secondary and tertiary clock sources, all three of which should be
programmed if possible, should be set in the following order:
1.

The loop clock sources on BRI ports with DSLs in service. If at all possible,
all three clock sources should be on the same 800 NI-BRI module.

2.

The loop clock source on any 100D module connected to the CO and in
service.

3.

The loop clock source on any 100D module in T1 mode operating in a
tie-trunk configuration.

4.

The local clock source on any 100D module.

If no administration has been performed, upon Frigid Start (system start-up), the
first 100D or NI-1 BRI port that is in service will be the default primary loop clock
source.
NOTE:
Extra BRI DSLs which are not in service should never be programmed as
clock sources.

Planning Form Instructions
Refer to Form 1, System Planning, Control Unit Diagram. Complete the following
information on Form 3i, Incoming Trunks: BRI Options (800 NI-BRI Module),
page 2:
1.

To keep the factory setting (the first slot and port found in the system
provides synchronization for the system), or if assigning a different module
to provide primary clock synchronization:
■

Enter the slot and/or DSL number (BRI only) under “Primary Clock
Synchronization.”

■

Under the “Source” subheading, check “Loop” to indicate that the
system uses the clock of the far-end connection (factory setting) or
“Local” to indicate the clock is free-running (100D modules only).
NOTE:
The only option for an 800 NI-BRI module is loop, which is
automatically assigned and is not programmable.

2.

If assigning secondary or tertiary backup synchronization:
■

Enter the slot and DSL number (BRI only) under “Secondary Clock
Synchronization” and/or “Tertiary Clock Synchronization.”

■

Under the “Source” subheading in each column, check “Loop” to
indicate that the system uses the clock of the far-end connection
(factory setting) or “Local” to indicate the clock is free-running
(100D modules only).
NOTE:
The only option for an 800 NI-BRI module is loop, which is
automatically assigned and is not administrable.

3

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Page 3-48

3

Timers

Timers ensure that the system takes the appropriate corrective action when the
expected response is not received from the network during normal operation.

!

CAUTION:
Since incorrect settings can hinder the operation of BRI facilities, consult
with a Lucent Technologies representative or authorized dealer before
making changes. The factory-set thresholds are standard settings and
should rarely be changed.

The timers, descriptions, factory settings, and allowable thresholds are shown in
Table 3–5.

3

Planning Form Instructions
On Form 3i, Incoming Trunks: BRI Options (800 NI-BRI Module), under the
“Timers and Counters” heading on page 2:
1.

Table 3–5.

For each timer:
■

To keep the factory setting, check the first box under the timer name.

■

To change the factory setting, check the second box under the timer
name and write the new threshold in the space provided.

NI-1 BRI Timers

Name Description

Factory
Setting

Allowable
Threshold

T200

The minimum time which Layer 2 must wait
1,000 ms
for an acknowledgment of a link establishment
frame, an information frame, or a polling
supervisory frame, before initiating
retransmission procedures.

T203

The maximum time for which the Layer 2
link can remain inactive.

33 seconds 10–255 seconds, in
increments of 1 second

T303

The delay in CO response after the system
has sent a SETUP message to initiate an
outgoing call.

4 seconds

T305

The delay in response from the CO after the
system has initiated a DISConnect message
for call clearing.

30 seconds 2−60 seconds, in
increments of 1 second

T308

The delay in response from the CO after the 4 seconds
system has sent a RELease message for call
clearing.

500−5,000 ms, in
increments of 500 ms

2–10 seconds, in
increments of 1 second

2−10 seconds, in
increments of 1 second

If this system is installed outside of the U.S., continue to the next section.
Otherwise, skip to the following section, “Assigning Lines/Trunks.”

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Selecting Line/Trunk Options

Page 3-49

Compensating for Slow Dial Tone (International) 3
If this system is being installed outside of the US, problems can arise because of
slow dial tone from local telephone companies due to the limitations of their
switching equipment. If this is the case, be aware of the following:
■

Users should be instructed to wait for dial tone before they dial. (Due to
changes made to internal timers, the system will allow the delay.)

■

The following features cannot be used:
— Automatic Route Selection
— Remote Call Forwarding
— Remote Access (outgoing)
— Tie trunks (configuration-dependent)
— Delay option on rotary lines
— Autodial, Last Number Dial, Saved Number Dial, and Callback
queue
Also, the slow dial tone may cause problems with transferring a call, joining
a call, and end-to-end signaling.

■

Additional touch-tone receiver (TTR) boards may be needed for the
system. The number of TTRs can be increased by adding 400 GS/LS or
016 T/R modules, each of which provides four TTRs or by adding 008 OPT,
012 T/R, 800 GS/LS-ID, or 800 DID modules, each of which provides two
TTRs.

To determine the number of TTRs needed, perform a traffic study on the number
of outgoing single-line telephone calls/busy hour, and the number of incoming
calls/busy hour routed to applications such as MERLIN LEGEND Mail. Then use
Table 3–6 to determine the number of TTRs required.
Table 3–6.

Total Number of TTRs Required

Calls per Hour
110
180
350
420
610
710

Dial-Tone Delay
0 sec
15 sec
4
4
6
6
8
10
8
10
10
12
10
14

30 sec
6
8
10
12
14
16

45 sec
6
10
10
14
16
18

60 sec
8
10
14
14
18
20

75 sec
8
10
14
16
20
22

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Assigning Lines/Trunks

Page 3-50

Assigning Lines/Trunks

3

This section contains instructions for assigning lines/trunks to telephones and
Direct-Line Consoles.
NOTE:
To assign lines/trunks to data-only stations, follow the instructions in
Chapter 5, “Data Communications.”

Forms Needed
■

Form 2a, System Numbering: Extension Jacks

■

Form 2b, System Numbering: Digital Adjuncts

■

Use the following forms as appropriate for telephones and consoles in the
system. Make one copy of the appropriate form for each extension.

3

— Form 4b, Analog Multiline Telephone
— Form 4d, MLX Telephone
— Form 4e, MFM Adjunct: MLX Telephone
— Form 4f, Tip/Ring Equipment
— Form 5a, Direct-Line Console (DLC): Analog
— Form 5b, Direct-Line Console (DLC): Digital
— Form 5c, MFM Adjunct: DLC

Planning Form Instructions
1.

2.

On page 1 of Forms 4b, 4d, 5a, and 5b, transfer the following user
information from Form 2a, System Numbering: Extension Jacks to each
copy of each of these telephone forms:
a.

Write the logical ID in the Logical ID space.

b.

Write the extension number in the Extension No. space.

c.

Write the name of the person or the location of the equipment in the
Person or Location space.

For any voice/voice or voice/data entries in the Person or Location column
of Form 2a, indicate the type of extension jack pairs under the Extension
Jack Pair heading on Forms 4b and 5a, by doing one of the following:
■

Check the Voice Announce to Busy (voice/voice) box, and enter the
logical ID and extension number under the Even-numbered jack
heading.

■

Check the Simultaneous Voice and Data (voice/data) box, and enter
the logical ID and extension number under the Even-numbered jack
heading.

3

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Assigning Lines/Trunks

3.

4.

Issue 1
August 1998
Page 3-51

For any adjuncts connected to an MLX telephone using an MFM, fill in the
following user information from Form 2b, System Numbering: Digital
Adjuncts, on Forms 4e and 5c in the Connected to MLX extension No.
space:
a.

Write the extension number in the Extension No. space.

b.

Write the name of the person or the location of the equipment in the
Person or Location space.

Identify the equipment at each extension (see the floor plan):
a.

Check the box that describes the telephone, console model, or type
of tip/ring equipment.

b.

Check the box under Adjuncts that describes the adjuncts at the
extension. (Checking the Data terminal box is informational only.)

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Assigning Telephone Buttons

Assigning Telephone Buttons

Page 3-52

3

This section contains instructions for assigning buttons to:
■

Telephones in Hybrid/PBX mode

■

Telephones in Key and Behind Switch mode

■

DLCs

3

Forms Needed
■

Form 4b, Analog Multiline Telephone

■

Form 4d, MLX Telephone

■

Form 4e, MFM Adjunct: MLX Telephone

■

Form 4f, Tip/Ring Equipment

■

Form 5a, Direct-Line Console (DLC): Analog

■

Form 5b, Direct-Line Console (DLC): Digital

■

Form 5c, MFM Adjunct: DLC

Telephones in Hybrid/PBX Mode

3

This section contains instructions for assigning the following kinds of buttons to
telephones, or to adjuncts connected to an MLX telephone using an MFM
(excluding QCC operator positions):
■

System Access Ring (SA Ring) button

■

System Access Voice (SA Voice) button

■

System Access Originate Only (SA Orig Only) button

■

Shared System Access (SSA) button

■

Personal line button

■

Pool button

■

Loudspeaker Paging button

The system automatically assigns certain kinds of line buttons, depending on the
type of equipment. For nonoperator multiline telephones, the system assigns
SA Ring, SA Voice, and SA Orig Only buttons (see Figure 3–2 and Figure 3–3).

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Assigning Telephone Buttons

Page 3-53

22

24

24

28

21

23

23

27

10

15

5
3

8

2

7

9

4

20
13

18

12

17

19

14

28
3

2

1

Figure 3–2.

8

SA Orig.
Only
1

6

SA
Voice

5

SA
Ring

4

18

13

20
7

6

11

16

10

15

9

14

17

12

16

11

Factory-Set Assignment, MLX Telephones
(Hybrid/PBX Mode)

Although equipment such as single-line telephones, analog modems, and fax
machines do not have buttons, the system treats these as multiline telephones
with 34 buttons.
The system assigns one SA Ring, one SA Voice, and one SA Orig Only button
to every adjunct connected through an MFM to an MLX telephone. For equipment
connected to an 012 T/R, 016 T/R, or 008 OPT module, the system assigns two
SA Ring buttons and one SA Orig Only button.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Assigning Telephone Buttons

Page 3-54

34 BUTTON
22 BUTTON
10 BUTTON
5 BUTTON

5

10

11

23

4

9

12

24

SA
Orig Only

3

8

13

25

SA
Voice

2

7

14

26

SA
Ring

1

6

15

27

16

28

17

29

18

30

19

31

20

32

21

33

22

34

Figure 3–3.

Factory-Set Assignment, Analog Multiline Telephones
(Hybrid/PBX Mode)

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Assigning Telephone Buttons

Guidelines for Button Assignments

Page 3-55

3

Use the following guidelines for assigning buttons to telephones or to adjuncts
connected to an MLX telephone.
NOTE:
When assigning buttons to telephones or adjuncts, keep in mind that BRI
lines are not automatically assigned to telephones or DLCs.
For multiline telephone users:
■

For non-operator multiline telephones, you can assign SA Voice, SA Ring,
and SA Orig Only buttons to the first 10 buttons on each telephone, and
up to 27 SSA buttons to each telephone. However, it is recommended that
the factory setting of 3 SA buttons be used to ensure that when each user
is busy on a call, at least one additional button is available to receive a call
and another is available to make a call. This leaves the rest of the buttons
on multiline telephones free for customizing.

■

On a DLC, there can be 10 SA buttons (including SA Orig Only), but no
SSA buttons. The factory setting for SA buttons is 2. It is recommended
that additional SA buttons be added to ensure that the operator can
transfer calls.

■

On a QCC, no buttons can be programmed. However, if the QCC Voice
Announce feature has been enabled, the Call 5 button becomes a VA
(Voice Announce) button.

■

If you plan to use Automatic Route Selection (ARS), consider keeping the
factory-set button assignments. Since ARS picks the appropriate route,
there is no need for Pool buttons.

■

Consider assigning SSA buttons to small groups of users who need to
answer and distribute each other’s calls easily or join conversations. Each
SSA button you assign corresponds to an SA Ring or SA Voice button on
another telephone. Therefore, to provide complete coverage within the
group, you must be sure that each SA Ring and SA Voice button assigned
to a telephone is also assigned to other members of the group. Each
SA Ring or SA Voice button on a telephone can be assigned as an SSA
button on up to 16 other telephones.

■

Assign a Pool button when a specific trunk pool (for example, BRI, WATS
or FX) is used frequently. Also consider assigning Pool buttons if you do
not plan to use ARS and the system includes only one or two pools. Do not
assign network pools to telephones.

■

Assign personal line buttons when an exclusive private number is needed,
for example, for a company executive. Any line/trunk connected to the
system can be used as a personal line, as long as it is not in a trunk pool.
Do not assign network trunks to telephones.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Assigning Telephone Buttons

Issue 1
August 1998
Page 3-56

For single-line telephones, analog modems, fax machines, or any other device
connected to an 012 T/R, 016 T/R, or 008 OPT module:
■

The settings for SA buttons can be changed (see below); however, factory
settings should be adequate to meet most user needs, since SA buttons
can be used to make and receive both inside and outside calls.

■

Single-line telephones cannot have additional SA or SSA buttons.
However, single-line telephones connected through an 012 T/R, 016 T/R,
or 008 OPT module can have SA buttons removed. Removing all but one
SA button from single-line telephones disables features such as Transfer,
Conference, and any other feature that requires more than one SA button.

■

If you want the extension to receive outside calls on a specific line/trunk,
assign a personal line button; if you want the extensions to receive outside
calls on a line/trunk included in a pool, assign a Pool button.

For adjuncts connected using an MFM, it is recommended that you change the
Button 2 assignment to SA Orig Only and remove the Button 3 assignment.

Planning Form Instructions
1.

Using the guidelines above, select the types of buttons to assign to each
telephone.

2.

Complete the Button Diagram page of each copy of Forms 4b, 4c, 4d, 4e,
and 4f.
NOTE:
The button diagrams for DLCs (Forms 5a and 5b) will be completed
later.
a.

b.

On buttons 1 through 27, indicate the types of System Access
buttons by circling SA for SA Voice, SA Ring, or SA Orig Only, and
writing Ring or Voice or SA Orig Only buttons and writing Shared SA,
Pool, or Personal line. Then do the following as appropriate:
■

For an SSA button, include the number of the extension with
the associated SA button (see Form 2a), and the button
number on that telephone.

■

For a Pool button, include the pool’s extension number (see
Form 2c).

■

For a personal line button, include the telephone number and
record the line/trunk numbers (see Form 2c).

■

Indicate whether all but one SA button will be removed from
single-line telephones on Form 4f.

Assign Loudspeaker Page buttons by selecting the button and
writing Page on it.

If the system includes one or more DLCs, proceed to “Direct-Line Consoles” later
in this section. Otherwise, proceed to Chapter 4, “Features,” to record feature
assignments on these forms for each extension.

3

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Assigning Telephone Buttons

Telephones in Key and Behind Switch Mode

Page 3-57

3

The line buttons you assign to the telephones, or to the adjuncts connected
through an MLX telephone using an MFM, are the following:
■

Intercom Ring (ICOM Ring) button

■

Intercom Voice (ICOM Voice) button

■

Intercom Originate Only (ICOM Orig Only) button

■

Loudspeaker Paging button

■

Personal line button (Key mode only)

■

Prime line button (Behind Switch mode only)
NOTE:
In Behind Switch operating mode, the system automatically assigns two
prime lines to each port on an MLX module — one for the MLX telephone
and one for the device connected to the Multi-Function Module (MFM). If an
MFM is not connected to an MLX telephone or the MLX port is not used, the
prime line for the MFM can be removed. The prime line can then be
assigned to other users.

Factory Assignments

3

The system automatically assigns certain kinds of line buttons depending on the
type of equipment and the mode of operation:
■

In Key mode, the system assigns an ICOM Ring button and an
ICOM Voice button; the first eight outside lines connected to the control
unit are assigned to each nonoperator multiline telephone, beginning with
Button 3.

■

In the Behind Switch mode, the system assigns an ICOM Voice button, an
ICOM Ring button, and one prime line button (Button 3) to every
nonoperator multiline telephone.

■

For either mode, the line/trunk assignment is the same for both analog
multiline and MLX telephones.

Figure 3–4 illustrates the factory-set button assignments for MLX telephones.
Figure 3–5 illustrates the factory-set button assignments for analog multiline
telephones.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Assigning Telephone Buttons

Page 3-58

22

24

26

28

21

23

25

27

5

10

15

20

4

9

14

19

3

8

13

18

2

Icom
Voice

7

12

17

1

Icom
Ring

6

11

16

MLX-28D

MLX-20L

MLX-10 or ML X-10DP

Key Mode:
Up to 8 personal line
buttons are assigned
beginning with button 3.

Figure 3–4.

Behind Switch Mode:
One prime line button
is assigned to button 3.

Factory-Set Assignment, MLX Telephones
(Key and Behind Switch Modes)

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Assigning Telephone Buttons

Page 3-59

34 BUTTON
22 BUTTON
10 BUTTON
5 BUTTON

5

10

11

23

4

9

12

24

3

8

13

25

Icom
Voice

2

7

14

26

Icom
Ring

1

6

15

27

16

28

17

29

18

30

19

31

20

32

21

33

22

34

Figure 3–5.

Factory-Set Assignment, Analog Multiline Telephones
(Key and Behind Switch Modes)

Although equipment such as single-line telephones, analog modems, and fax
machines do not have buttons, the system treats these as multiline telephones
with 34 buttons. In both Key and Behind Switch modes, the system assigns no
outside lines to this type of equipment. The system assigns two ICOM Ring
buttons to equipment connected to an 012 T/R, 016 T/R, or 008 OPT module. The
system assigns an ICOM Ring and an ICOM Voice button to every adjunct
connected through an MFM. You MUST remove the ICOM Voice button.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Assigning Telephone Buttons

Guidelines for Button Assignments

Page 3-60

3

This section contains guidelines for assigning buttons in Key or Behind Switch
mode.

Key Mode
Use the following guidelines to assign buttons for a system in Key mode.
NOTE:
When assigning buttons in Key mode, keep in mind that BRI lines are not
automatically assigned to telephones or DLCs.
For Key mode with multiline telephone users:
■

You can assign ICOM Voice, ICOM Ring, or ICOM Orig Only buttons to
each extension.

■

Assign additional ICOM Ring, ICOM Voice, or an ICOM Orig Only button
for people who frequently receive or make transferred calls. The ICOM
Orig Only button ensures that if all intercom buttons are busy, at least one
is still available to make a call or to transfer the current call.

■

Assign additional outside lines, including special-purpose lines such as
WATS or FX.

■

Remove or rearrange the eight factory-set line assignments, if desired.

■

For all types of telephones for which you want the extension user to receive
outside calls on a specific line, assign a personal line to a button on the
telephone or adjunct.

■

Consider assigning a Loudspeaker Paging button to make announcements
over an optional loudspeaker connected to the control unit. To make an
announcement, users press the button and speak into the handset. They
do not need to dial the extension of the loudspeaker paging system.

For Key mode with single-line telephone users, analog modems, fax machines, or
any other device connected to an 012 T/R, 016 T/R, or 008 OPT module or to an
MFM:
■

You can assign a combination of up to 10 ICOM Ring or ICOM Orig Only
buttons to each extension. (At least one intercom button must be assigned
to each single-line telephone or adjunct connected to an MLX telephone
using an MFM.) ICOM Voice buttons should not be assigned on single-line
telephones.

■

If you want the extension user to receive outside calls on a specific line,
assign a personal line to a button on the telephone or adjunct. The
extension user is automatically connected to the intercom line when the
receiver is lifted, and the user can select an outside line by dialing the
dial-out code (usually a ).

3

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Assigning Telephone Buttons

Issue 1
August 1998
Page 3-61

Behind Switch Mode

3

Use the following guidelines to assign buttons for a system in Behind Switch
mode.
NOTE:
For adjuncts connected using an MFM, you should change the Button 2
assignment to ICOM Orig Only and remove the Button 3 assignment.
For Behind Switch mode with multiline telephones:
■

You can assign additional lines and any outside lines connected directly to
the control unit, including special-purpose lines.

■

If a loudspeaker paging system is to be connected to the control unit,
include a programmed Loudspeaker Paging button to make
announcements over the loudspeaker system. To make an announcement,
users press the button and speak into the handset. They do not need to
dial the extension of the loudspeaker paging system.

For Behind Switch mode with single-line telephones, analog modems, fax
machines, or any other devices connected to an 012 T/R, 016 T/R, or 008 OPT
module or to an MFM, you can assign additional lines and any outside lines
connected directly to the control unit, including special-purpose lines.

Planning Form Instructions
1.

Using the guidelines above for Key and Behind Switch modes, select the
types of buttons to assign to each telephone.

2.

Complete the Button Diagram page of each copy of Forms 4b, 4d, 4e, 4f,
and 5c, by doing one of the following:

3.

4.

■

To keep the factory-set assignments, proceed to Step 3.

■

To change the factory-set assignments, skip to Step 4.

To keep the factory-set assignments:
■

For multiline telephones in Key mode, fill in the telephone number
on Buttons 3 through 10. Record the line numbers (see Form 2c).

■

For multiline telephones in Behind Switch mode, fill in the extension
number of the prime line on Button 3.

To change the factory-set assignments:
a.

On Buttons 1 through 10, indicate the type of intercom button by
circling ICOM for ICOM Voice, ICOM Ring, or ICOM Orig Only, and
writing Ring, Voice, or Orig Only.

b.

Fill in the telephone numbers (or prime-line extension numbers) to
be assigned or changed. Start with Button 3 and record the line
numbers on the diagram (see Form 3b).

c.

Assign programmed Loudspeaker Paging buttons by selecting the
button and writing Page on it.

3

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Assigning Telephone Buttons

Page 3-62

3

Direct-Line Consoles

Use these instructions only if the system has one or more DLCs. Otherwise,
proceed to Chapter 4, “Features,” to record feature assignments on the forms for
each extension.
NOTE:
For more information on DLCs, see the Feature Reference.
The number of line, Direct Station Selector (DSS), and programmed feature
buttons assigned to a DLC depends on the type of telephone and the number of
lines/trunks connected to the system. The factory setting for DLCs is that, in
addition to an SA Voice and an SA Ring button, or ICOM buttons, as many
lines/trunks as possible are assigned to each console. Each line/trunk appears on
a separate button, which means that the number of lines/trunks assigned is limited
to the number of buttons on the console (up to a maximum of 32 buttons on the
34-button analog DLC).
If a DSS is present, the system assigns a DSS button for each extension number
associated with an extension and special-feature buttons that are used by the
DLC operator for call-handling functions.
Figure 3–6 and Figure 3–7 show initial line/trunk and feature assignments for MLX
and analog DLC consoles. Refer to the appropriate figure as you select line/trunk
assignments for DLCs.
NOTE:
System Access buttons appear on DLCs in Hybrid/PBX mode. Intercom
buttons appear on DLCs in Key or Behind Switch mode.

22

24

24

28

21

23

23

27

10

15

5
3

8

2

7

9

4

20
13

18

12

17

19

14

28
8

3

18

13

20
1
2

1

Figure 3–6.

6

SA Icom
Voice

5

SA Icom
Ring

4

7

6

MLX Direct-Line Console

11

16

10

15

9

14

17

12

16

11

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Assigning Telephone Buttons

Page 3-63

DISPLAY CONSOLE WITH DSS
34 BUTTON
22 BUTTON

3 5

8 10

9 11

2 4

7 9

10

12

1 3

6 8

11

13

21
22
23

23

10

20

30

40

24

11

21

31

41

25

12

22

32

42

26

13

23

33

43

SA Icom
Voice

2

5 7

12 14

24

SA Icom
Ring

1

4

6

13 15

25

27

14

24

34

44

14 16

28
26

15

25

35

45

17

27 29

16

26

36

46

16 18

28 30

17

27

37

47

17 19

31
29

15

18

28

38

48

32

19

29

39

49

19 21

Night
Serv 31 33

Trnsfr

Recall

Conf

Drop

20 22

Send/
Remove 34
Msg 32

Shift 1

Shift 2

Shift 3

Msg
Stat

18 20

Alarm
30

Note: Alarm, Night Service, and Send/Remove Msg will be replaced
with Lines 30, 31, and 32 if the system has that many lines.

Figure 3–7.

Analog Direct-Line Console
NOTE:
If the system has more than 29 lines, Alarm, Night Service, and
Send/Remove Message are replaced with lines 30, 31, and 32.

The system assigns lines/trunks to buttons on DLCs in the order in which the
lines/trunks are connected to the control unit. You can change the factory-set
assignments by removing, adding, or changing the order in which lines/trunks are
assigned to buttons for each DLC operator.
If the system has more than the number of factory-assigned lines/trunks to
operator consoles, be sure to change the line/trunk assignment so that all
lines/trunks you want answered by a DLC operator appear on at least one
operator position.
Decide which lines/trunks should appear on each DLC operator console based on
each operator’s call-handling responsibilities. All operators may not need the
same assignments. DLC operators who are responsible for answering calls for
specific groups usually need only the lines/trunks used by group members.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

3

Lines/Trunks
Assigning Telephone Buttons

Issue 1
August 1998
Page 3-64

If the system includes a loudspeaker paging system, consider assigning a
programmed Loudspeaker Paging button to DLC positions for one-touch access
to the paging equipment. If the system has fewer than 30 lines, the operator-only
features (Alarm, Night Service, and Send/Remove Messages) are
factory-assigned as shown in Figure 3–6. The factory assignments can be
changed through centralized telephone programming or by a DLC operator.

Planning Form Instructions
Complete the Button Diagram page on each copy of Form 5a and Form 5b:
1.

For the Ring and Voice buttons, circle SA or Icom.

2.

Write the telephone number of the line/trunk you want to assign in the
space on the Button Diagram page. Record each line/trunk number (see
Form 2c).

3.

Assign Alarm, Night Service, or Send/Remove Message buttons by
labeling the appropriate button Alarm, Nite Svc, or Snd/Rem Msg.

4.

Assign programmed Loudspeaker Paging buttons by selecting the button
and writing Page on it.

Proceed to Chapter 4, “Features,” to complete the remaining sections of these
forms.

3

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Issue 1
August 1998

Features

Page 4-1

4

Features

4

The system offers many optional features. This chapter contains instructions for
assigning features in the following categories:
■

Telephone and Extension Features. Individual telephones, consoles, or
adjuncts are assigned these features. Some features may be assigned to
other equipment at an extension.

■

Operator Features. All operator consoles are assigned these features.

■

Group-Assigned Features. These features are used by functional groups
of users (such as separate departments).

■

System Features. All or most users on the system use these features.

Detailed information about all features (including the considerations, constraints,
and feature interactions that may impact their use) is contained in the Feature
Reference. You should be familiar with this information before you attempt to
perform the procedures in this chapter.
Since certain features are optional, you can simply skip those sections that do not
apply to the system.
Each individual telephone form is a complete record for that specific telephone for
planning, programming, and subsequent reference by the system manager. Some
features noted on the individual telephone forms are not described in this book,
for example, Abbreviated Ring, Call Waiting, and Automatic Line Selection. For
more information about these features, see the Feature Reference.
NOTE:
Except for some telephone-specific features, for example, microphone
operation, many of the features described in this chapter can be assigned
to other equipment, such as a data terminal or fax machine. Therefore,
throughout this chapter, the more general term “extension” is often used
instead of, or in addition to, “telephone.”

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Telephone and Extension Features

Telephone and Extension Features

Page 4-2

4

This section contains instructions for assigning some optional features to
extensions. These features may be used by both system operators and general
users:
■

Pool Dial-Out Code Restriction (Hybrid/PBX mode only)

■

Calling Restrictions

■

Forced Account Code Entry (not QCC)

■

Microphone Operation

■

Remote Call Forwarding (not QCC)

■

Fax Message-Waiting Receiver and Threshold

■

Trunk-to-Trunk Transfer

■

HotLine (single-line telephones only)

■

Service Observing (MLX only for Service Observer, any telephone for a
Service Observing group member except QCC or CTI link)
NOTES:
1. Service Observing button is administrable only via centralized telephone
programming.
2. Service Observing may be subject to federal, state, or local laws, rules, or
regulations or require the consent of one or both of the call parties. You
must check in your jurisdiction and comply with all applicable laws, rules,
and regulations before using this feature. Failure to comply may result in
severe penalties.

The system programmer and/or network administrator assigns these features.
There are additional extension features noted on the forms but not covered in this
book. Individuals normally program these features at their telephones, although
the system manager may also program these features using centralized
telephone programming. You may, however, want to complete the information on
the forms so they can serve as a complete summary of features for each
extension. Detailed information about these and all features is contained in the
Feature Reference. Instructions for using centralized telephone programming are
included in System Programming. For users who want to program features on
their own telephones, information and procedures are contained in the user and
operator guides.
You may choose the Extension Copy feature to create a template that can then be
copied to other similar extensions whose users require the same features. This
feature is also described later in this section.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Telephone and Extension Features

Forms Needed
■

Form 2a, System Numbering: Extension Jacks

■

Form 4b, Analog Multiline Telephone

■

Form 4d, MLX Telephone

■

Form 4e, MFM Adjunct: MLX Telephone

■

Form 4f, Tip/Ring Equipment

■

Form 5a, Direct-Line Console (DLC): Analog

■

Form 5b, Direct-Line Console (DLC): Digital

■

Form 5c, MFM Adjunct: DLC

■

Form 5d, Queued Call Console (QCC)

■

Form 6b, Optional Extension Features

■

Form 6g, Call Restriction Assignments and Lists

■

Form 6h, Authorization Codes

■

Form 6i, Pool Dial-Out Code Restrictions

■

Form 11, Service Observing: Group Assignment

■

Floor plan

Issue 1
August 1998
Page 4-3

4

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Telephone and Extension Features

Issue 1
August 1998
Page 4-4

Queued Call Console (Hybrid/PBX Mode Only) 4
Use these instructions if the system includes one or more QCCs. Otherwise, skip
to the next section, “Pool Dial-Out Code Restriction (Hybrid/PBX Mode Only).”

4

Planning Form Instructions
1.

Transfer the user information from Form 2a, System Numbering: Extension
Jacks to each copy of Form 5d, by filling in the Logical ID, Extension No.,
and Person or Location spaces. Use the Button Diagram on Form 5d, as a
guide for labeling the operator console buttons. You cannot change the
button assignments shown. However, if the QCC Voice Announce feature
is enabled, the Call 5 button becomes a VA (Voice Announce) button.
Refer to the “Operator Features” section later in this chapter.

2.

Check the box under the Adjuncts heading that applies to the equipment at
the extension (see the floor plan).

3.

Under Message Center Operator, check No if the QCC will not be a
message center, or Yes if it will be a message center.
NOTE:
If a calling group member is programmed as a QCC, the station is removed
from the calling group. If a Service Observing group member is
programmed as a QCC, the station is removed from the Service Observing
group. If a Service Observer station is programmed as a QCC, the station is
removed as a Service Observer.

Proceed to the next section, “Pool Dial-Out Code Restriction (Hybrid/PBX Mode
Only).”

Pool Dial-Out Code Restriction
(Hybrid/PBX Mode Only)

4

This section contains instructions to tailor the use of dial-out access codes by
restricting extensions from making calls on specific trunk pools (for example,
those consisting of special-purpose lines/trunks such as WATS or FX), or to
reserve trunk pools for data communications only.

Planning Form Instructions
Use Form 6i to identify those extensions that are restricted from using some
dial-out access codes. The factory setting is for all extensions to be restricted from
using all dial-out access codes. This form only identifies extensions that are to
remain restricted. Extensions that are not listed on this form must have their
restrictions removed through system administration. All extensions should be
restricted from dialing private network pools.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Telephone and Extension Features

Calling Restrictions

Page 4-5

4

This section contains instructions to restrict selected extensions from making
outside calls — for example, for telephones in a reception area and to control
toll-call abuse  but still allow local and intercom calls.

!

SecurityAlert:
Calling restrictions [for example, Disallowed Lists, toll restriction, Facility
Restriction (FRL) Levels] should be programmed, as appropriate, to
minimize toll fraud abuse. Refer to the “Calling Restrictions” section in the
Feature Reference for additional information on programming calling
restrictions.

Planning Form Instructions
If these restrictions are too limited, use “Allowed Lists” and “Disallowed Lists,” as
described later in this chapter.
Use Form 6h to identify Authorization Codes for use by the users of certain
extensions. After Form 6h is filled in, remove it from the forms set and keep it in a
secure place.
Use Form 6g, Call Restriction Assignments and Lists, to identify the extensions
with calling restriction assignments. List the extensions with calling restrictions in
the Ext. No. column and the type of restriction in the Restriction Type column. The
factory setting is Restricted.
NOTE:
Setting this option to Outward Restrict or Toll Restrict does not allow
reliable toll restriction on telephone company lines/trunks that do not
require 1 or 0 for toll calls. The Toll Type setting of 1 or 0 allows the system
to classify calls as either local or toll, based on the number a user dials.
Dialing a prefix depends on local telephone company requirements and the
type of trunk being used. The system must be programmed to designate
whether or not to restrict users from dialing calls to certain areas. The Toll
Type feature does not apply to DID trunks or private network tandem
trunks.
To restrict the extension from making outside calls so only intercom or private
network calls can be made, check the Outward Restriction column.
To restrict the extension from making toll calls so only intercom, local, or private
network calls can be made, check the Toll Restriction column.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Telephone and Extension Features

Forced Account Code Entry

Page 4-6

4

This section contains instructions for setting up the system to associate calls with
corresponding accounts, clients, or projects for billing and accounting purposes.

4

Planning Form Instructions
Use Form 6b to identify extensions requiring Forced Account Code Entry. Under
the Forced Account Code Entry heading on Form 6b, do one of the following:
■

To allow users to make calls without entering an account code, check the
No (factory setting) box.

■

To require users to enter an account code, check the Yes box.

Microphone Operation

4

This section contains instructions to disable the microphones on MLX telephones
when they are used in areas where use of the speakerphone is disruptive.
Extensions that interact with a CTI-capable program on a computer (extensions
marked Computer Telephony Integrated Client PC on forms 4b or 4d) should not
have their microphones disabled.
NOTE:
The microphones on analog multiline telephones cannot be disabled.

Planning Form Instructions
Under the Microphone heading on Form 6b, do one of the following:
■

To allow speakerphone use (factory setting), check Enable.

■

To prevent speakerphone use, check Disable.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Telephone and Extension Features

Remote Call Forwarding

Page 4-7

4

This section contains instructions to allow users to forward calls to outside
numbers and to allow users to “screen” their calls through use of the Forwarding
Delay option. With the Forwarding Delay option activated, incoming calls ring at
the called station a specified number of times (from 1 to 9 rings) before the call is
forwarded.

!

SecurityAlert:
Remote Call Forwarding can only be used securely when used on
ground-start line/trunks or loop-start lines/trunks with “reliable disconnect”
(sometimes referred to as forward disconnect or disconnect supervision).
Toll fraud can occur when loop-start lines/trunks are used with unreliable
disconnect. If the calling party stays on the line after the called party hangs
up, the central office will return a dial tone at the conclusion of the call,
enabling the caller to place another call as if it were being placed from your
company.

Remote Call Forwarding and the Forwarding Delay option are programmed for
each extension. Assign these features to selected extensions, for example, for
people who often work away from the office. Remote Call Forwarding cannot be
assigned to QCCs. If there is a personal line assigned to a telephone, you can
specify that calls on that line be forwarded to an outside number if the extension is
the principal user of the personal line.
Ensure that the number of rings for Remote Call Forwarding is less than the
Coverage Delay or call will not forward.

Planning Form Instructions
1.

2.

Under the Remote Call Forwarding heading on Form 6b, do one of the
following:
■

To prevent users from forwarding calls to outside numbers (factory
setting), check the Not Allowed column and proceed to the next
section, “Fax Message-Waiting Receiver.”

■

To provide Remote Call Forwarding, check the Allowed column,
then proceed to Step 2.

If you want a user to be able to forward the incoming calls on a specific line
or lines to another number, write the extension number in the spaces
provided on Form 6c, Principal User of Personal Line.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Telephone and Extension Features

3.

Page 4-8

If Remote Call Forwarding is enabled, do one of the following:
■

If you wish to disable the Forwarding Delay option, enter 0 in the
Delay (0–9) column under the Remote Call Forwarding heading on
Form 6b. This causes incoming calls to be forwarded immediately.

■

If wish to enable the Forwarding Delay option for an extension, enter
the number of times an incoming call should ring at the called
extension (1–9 rings) before the incoming call is forwarded.
NOTES:
1. If Do Not Disturb (DND) and Forwarding Delay are both active,
DND overrides the Forwarding Delay and the call is forwarded
immediately.
2. Due to the timing of when the ringing signal is applied to a
single-line telephone, and the interval of that ringing signal,
single-line telephones may appear to have their calls forwarded
one ring sooner than the programmed number.

Fax Message-Waiting Receiver

4

Use these instructions only when the system has fax machines connected directly
to the control unit by way of an 008 OPT, 016 T/R, or 012 T/R module or
connected to an MLX telephone using a Multi-Function Module (MFM). Otherwise,
skip to the next section, “Operator Features.”
Fax machines cannot use General-Purpose Adapters (GPAs) because they
cannot auto dial through the GPA.
This section contains instructions to designate from one to four telephones to
receive message-waiting indications when a fax is received on a specific fax
machine, and to specify the length of time before the system assumes a fax has
arrived and sends the message-waiting indication.

Planning Form Instructions
Use Form 6d to identify up to 16 fax machine extension numbers and up to four
receiver extension numbers for each fax number.
The System Notification Threshold setting can be left at the factory setting of
10 seconds or changed and identified on the line at the top of the form for up to
30 seconds.
NOTE:
You will fill in the rest of the optional telephone features later.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Telephone and Extension Features

Trunk-to-Trunk Transfer

Page 4-9

4

This section contains instructions to allow or disallow trunk-to-trunk transfer at
each extension.
If trunk-to-trunk transfer is disallowed on an extension in a private network, the
extension cannot transfer an outside call to a local system trunk connected to the
PSTN. See the Network Reference for more information.
Trunk-to-trunk transfer may only be performed on ground-start trunks and
loop-start trunks with reliable disconnect. As of Release 4.0, trunk-to-trunk
transfer may be performed on BRI, Tie lines, PRI, ground-start trunks, and
loop-start trunks that have reliable disconnect.
Trunk-to-trunk transfer is factory set to disabled and may be enabled for a specific
extension. Single-line telephones are restricted from completing a trunk-to-trunk
transfer.

Planning Form Instructions
Use Form 6b to identify extensions permitted to perform trunk-to-trunk transfers.
Under the Trunk-to-Trunk Transfer heading on Form 6b, do one of the following:
■

To block an extension from completing a trunk-to-trunk transfer, check the
No (factory setting) box.

■

To allow an extension to complete trunk-to-trunk transfers, check Yes.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Telephone and Extension Features

Page 4-10

4

HotLine

The HotLine feature is available only for single-line telephones and devices
connected to a port on an 008 OPT, 012 T/R, or 016 T/R module. A single-line
telephone connected to an MFM cannot use the HotLine feature. This feature
enables you to set up a telephone to dial one specific number once the telephone
goes off-hook. The number that is dialed is the first personal speed dial (code 01)
programmed on the single-line telephone using centralized telephone
programming or extension programming. (Extension programming is only
available before the HotLine feature is activated.)
A HotLine extension can call a private network extension. See the Network
Reference for information.
NOTE:
In Release 6.0 and later systems, after the Hotline extension number has
been assigned, the FRL value for the Hotline extension number should be
set to 6. This ensures that, regardless of the FRL value assigned to the
route(s) in the UDP Routing Table connecting two switches in a private
network, placing a UDP call from switch A directly connected to switch B
using the Hotline feature will not fail due to the FRL.

Planning Form Instructions
On Form 4f specify if this device will use the HotLine Feature. Under the HotLine
heading on Form 4f, do one of the following:
■

To set the extension to not use the HotLine feature, check the Off (factory
setting) box.

■

To set the extension to be a HotLine extension, check the On box. Enter
the extension or telephone number that the HotLine extension dials when it
is taken off-hook in the space provided below the On box.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Telephone and Extension Features

Page 4-11

4

Extension Copy

The Extension Copy feature enables you to copy an extension’s programmed
buttons (with some exceptions) to one or more extensions. The features are
individually programmed on one extension to create a template that can then be
copied to other extensions in the system. You can make additional copies of these
forms and have several templates for different groups of users.
Only similar types of extensions can be copied to each other (that is, analog to
analog and MLX to MLX) because both extension types have different button
layouts. For a system that has both telephone types, you would need at least two
templates, one for analog and one for MLX.
NOTE:
A Multi-Function Module (MFM) extension can be copied to or from another
MFM extension. An analog DLC extension can only be copied to another
analog DLC extension. An MLX DLC extension can only be copied to
another MLX DLC extension. Single-line telephones and QCCs cannot use
the Extension Copy feature.
Table 4–1 contains a list of the features that can be copied and whether the
features apply to analog telephones, MLX telephones, or both. Following the table
is a list of operator features that can be copied.
Table 4–1.

Features That Can Be Copied

Feature
Account Code Entry
Authorization Code
Auto Answer All
Auto Answer Intercom
Auto Dial Inside
Auto Dial Outside
Barge-In
Camp-on
Conference*
Coverage Off
Coverage VMS Off
*

Analog
and MLX

Analog Only

MLX
Only

ä
ä
ä
ä
ä
ä
ä
ä
ä
ä
ä

Behind Switch mode only.

Continued on next page

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Telephone and Extension Features

Table 4–1.

Page 4-12

Features That Can Be Copied (Continued)

Feature

Analog and
MLX

Data Status

ä

Direct Voice Mail

ä

Do Not Disturb

ä

Drop*

ä

Extension Status 2 (Non-operator)

ä

Extension Status 1 (Non-operator)

ä

Analog Only

MLX
Only

ä

Feature Button
Forward

ä

Group Calling

ä

Group Paging

ä

Headset Auto Answer

ä

Headset Hang Up

ä

Headset Status

ä

Headset/Handset Mute

ä

Last Number Dial†

ä

Messaging:
ä

Delete Message
Leave Message

ä

Message Light Off

ä
ä

Next Message
Posted Message
Return Call

ä

Scroll

ä

Park
*
†

ä

ä

Behind Switch mode only.
Number is not copied.

Continued on next page

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Telephone and Extension Features

Table 4–1.

Page 4-13

Features That Can Be Copied (Continued)
Analog and
MLX

Feature

Analog Only

MLX
Only

Pickup:
Group

ä

General

ä

Extension

ä

Line

ä

Privacy

ä

Recall

ä

Reminder Service:
Set

ä

Cancel

ä

Saved Number Dial†

ä

Selective Callback

ä

Signaling

ä

System Access:‡

*
†
‡

SA Originate Only

ä

Voice Attribute on Button

ä

Ring Attribute on Button

ä

System Speed Dial

ä

Transfer*

ä

Behind Switch mode only.
Number is not copied.
Ringing options (No, Delay, and Immediate Ring) are copied with the button.

The following are operator features that can be copied:
■

Alarm

■

Extension Status Off

■

Extension Status 1

■

Extension Status 2

■

Missed Reminder

■

Night Service

■

Operator Park

■

Send/Remove Message

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Telephone and Extension Features

Page 4-14

4

Planning Form Instructions
1.

On page 1 of Form 4a and/or Form 4c, write the extension number of the
Master Extension and the extensions to which this template will be copied.

2.

Complete the Button Diagram on page 2 of Form 4a and/or Form 4c,
assigning features to the buttons.

3.

On the individual telephone forms (Forms 4b, 4d, 4e, 5a, 5b, and 5c) do the
following:
a.

By the extension information at the top of each page, check Copied
from Master Extension No. and write the extension number of the
Master Extension.

b.

Under every form’s Button Diagram heading, check the See Master
Extension box.

4

Cover Ring Delay

Beginning with Release 4.1, the following ring delay options can be programmed
for extensions:
■

The Group Coverage Ring Delay is programmed on individual sender
extensions and replaces the Coverage Delay Interval programmed on a
systemwide basis in previous releases.

■

When used in conjunction with Secondary Cover buttons, consider the
following when setting the value:
— When secondary cover buttons are programmed for a sender, set
the value such that when the Group Coverage Ring Delay is added
to the Primary Cover Ring Delay, the result is greater than the
Secondary Ring Delay plus two rings (the fixed Secondary Cover
Delay Interval).

■

The Primary Cover Ring Delay and Secondary Cover Ring Delay are
programmed on individual sender extensions and replace the Delay Ring
Interval programmed on a systemwide basis.

Forms Needed
■

Form 4b, Analog Multiline Telephone

■

Form 4d, MLX Telephone

■

Form 4e, MFM Adjunct: MLX Telephone

■

Form 4f, Tip/Ring Equipment

■

Form 5a, Direct-Line Console (DLC): Analog

■

Form 5b, Direct-Line Console (DLC): Digital

■

Form 5c, MFM Adjunct: DLC

■

Form 7c, Group Coverage

4

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Telephone and Extension Features

Issue 1
August 1998
Page 4-15

Planning Form Instructions
1.

After assigning Individual Coverage for each receiver telephone, locate the
appropriate form for each sender telephone (Form 4b, 4d, 4f, 5a, or 5b)

2.

Under the Primary Cover Ring Delay heading, do one of the following:

3.

■

To keep the factory-set delay, check the 2 rings box.

■

To change the factory-set delay, check the second box and write the
number of rings (1–6) in the space provided.

Under the Secondary Cover Ring Delay heading, do one of the following:
■

To keep the factory-set delay, check the 2 rings box.

■

To change the factory-set delay, check the second box and write the
number of rings (1–6) in the space provided.

4.

After assigning senders to Group Coverage on form 7c, locate the
appropriate form for each sender telephone (Form 4b, 4d, 4f, 5a, or 5b).

5.

Under the Group Coverage Ring Delay heading, do one of the following:
■

To keep the factory-set delay, check the 3 rings box.

■

To change the factory-set delay, check the second box and write the
number of rings (1–9) in the space provided.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Telephone and Extension Features

Service Observing

Page 4-16

4

This section contains instructions for setting up Service Observing so that a
designated observer can monitor a call at any station that is a member of the
Service Observer’s group. Service Observing is available only in Release 6.1 and
later systems.
NOTE:
Service Observing may be subject to federal, state, or local laws, rules, or
regulations or require the consent of one or both of the call parties. You
must check in your jurisdiction and comply with all applicable laws, rules,
and regulations before using this feature. Failure to comply may result in
severe penalties.
You can establish up to 16 Service Observing groups on a system. Each group
consists of one Service Observer and a list of the stations (up to the system
maximum of 200) that the observer is allowed to monitor. A warning tone is
programmed on a per group basis to provide an audible indication that a station is
being observed.
NOTES:
1. Any MLX station (except QCC or CTI link) may be a Service Observing
station.
2. A Service Observing button must be assigned to the observers MLX
telephone and is programmed only via Centralized Telephone
Programming.
3. Any station (except QCC or CTI link) may be a group member.
4. If a station becomes a QCC or CTI link, it is removed from all Service
Observing groups.
5. A Service Observer may be a member of another Service Observing
group. Any station may be a member of more than one Service
Observing group.
6. The Service Observer and all extensions in a Service Observing group
must be on the local switch.
7. Data, video, page, and reminder service calls, and calls at VMI ports and
delay announcement devices cannot be observed.

Forms Needed
■

Form 4d, MLX Telephone

■

Form 5b, Direct-Line Console (DLC): Digital

■

Form 11, Service Observing: Group Assignment

4

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Telephone and Extension Features

Issue 1
August 1998
Page 4-17

Planning Form Instructions
Determine which stations will be assigned as Service Observers and complete the
following on page 1 of Form 4d and 5b:
■

In the Centralized Programming Requirements section, check the Assign
Service Observing Button box for each MLX telephone that will have a
Service Observing button assigned. Any station with a programmed
Service Observing button may be assigned as an Observer station.

Determine the number of Service Observing groups needed. Then, for each
group, complete the following on Form 11:
1.

Write the group number in the Group No. space.

2.

Write the extension number for the group Observer in the Observer Ext.
No. space. The Observer’s station must have a Service Observing button.

3.

Check the appropriate option under the Warning Tone heading.
■

To keep the factory-set option and provide a warning tone to indicate
that the station is being monitored, check the Yes box.

■

If a warning tone will not be provided when a station is being
monitored, check the No box.

4.

Write the extension number for each group member in the Member Ext.
No. column.

5.

Write each Service Observing group member’s name in the Member Name
column.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Operator Features

Operator Features

Page 4-18

4

Operator features apply only to DLCs, QCCs, and any Direct Station Selectors
(DSSs) connected to them.

4

Forms Needed
■

Form 2a, System Numbering: Extension Jacks

■

Form 2d, System Numbering: Special Renumbers

■

Form 5d, Queued Call Console (QCC)

■

Form 6a, Optional Operator Features

Direct-Line Console

4

Use these instructions only if the system has one or more DLCs. Otherwise, skip
to the next section, “Queued Call Console (Hybrid/PBX Mode Only).” This section
contains instructions for the Operator Hold Timer and DLC Automatic Hold
features.

Operator Hold Timer

4

This section contains instructions to set the operator hold timer to track the
number of seconds callers are on hold for an operator. When a caller is on hold
longer than the number of seconds programmed for the timer, the operator is
reminded of the call by a single ring.

4

Planning Form Instructions
Under the Operator Hold Timer heading on Form 6a, do one of the following:
■

To keep the factory setting, check 60 Seconds.

■

To change the factory setting, check the second box and write the number
of seconds (10 to 255 seconds) in the space provided.

DLC Automatic Hold

4

This section contains instructions to set DLC Automatic Hold to place calls on hold
automatically when the operator presses another line button.

Planning Form Instructions
Under the DLC Automatic Hold heading on Form 6a, do one of the following:
■

To keep the factory setting (no DLC Automatic Hold), check Disable.

■

To automatically put calls on hold when another line button is pressed,
check Enable.

If the system includes one or more QCCs, proceed to the next section. Otherwise,
skip to the following section, “Direct Station Selector.”

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Operator Features

Page 4-19

Queued Call Console (Hybrid/PBX Mode Only) 4
Use these instructions only if the system has one or more QCCs. Otherwise, skip
to the next section, “Direct Station Selector.”
This section contains instructions to set the following QCC operator features:
■

Hold Return

■

Automatic Hold or Release

■

Calls-in-Queue Alert

■

Queue Over Threshold

■

Elevate Priority

■

Message Center Operation

■

Automatic or Manual Directed Call Completion

■

Return Ring

■

Position-Busy Backup

■

Operator Hold Timer

■

Call Types

■

Voice Announce

4

Hold Return

This section contains instructions to specify whether calls put on hold by a QCC
operator stay on hold indefinitely, or are returned to the QCC queue after the Hold
Timer has expired twice.

Planning Form Instructions
Under the Hold Return heading on Form 6a, do one of the following:
■

To indicate that calls stay on hold after the hold timer has expired twice,
check the Remain on hold (factory setting) box.

■

To indicate that calls on hold return to the QCC queue after the hold timer
has expired twice, check the Return to queue box.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Operator Features

Automatic Hold or Release

Page 4-20

4

This section contains instructions to specify whether a call that is in progress on a
Call button is automatically put on hold (Automatic Hold) or disconnected
(Automatic Release), when the operator presses another Call button.

4

Planning Form Instructions
Under the Automatic Hold or Release heading on Form 6a, do one of the
following:
■

To specify that calls are automatically disconnected, check the Automatic
Release box (factory setting).

■

To specify that calls are automatically put on hold when another Call button
is pressed, check the Automatic Hold box.

Calls-in-Queue Alert

4

This section contains instructions for setting the Calls-in-Queue Alert option to
notify QCC operators (with a single beep) when a new call enters the QCC queue.

4

Planning Form Instructions
Under the Calls-in-Queue Alert heading on Form 6a, do one of the following:
■

To keep the factory setting (QCC operators are not notified when calls are
waiting in queue), check the Disable box.

■

To specify that particular QCC operators are notified (with a single beep)
when a call enters the queue, check the Enable box and, in the space
provided, write the extension number of each QCC position that receives
the notification (see Form 2a or Form 5d).

Queue Over Threshold

4

This section contains instructions to specify the maximum number of calls allowed
in the QCC queue before operators are notified (with a tone through the receiver
or headset) that calls are waiting.

Planning Form Instructions
Under the Queue Over Threshold heading on Form 6a, do one of the following:
■

To keep the factory setting (operators are not notified), check the 0 calls
box.

■

To indicate that operators are notified when calls are waiting in the queue,
check the second box and write the maximum number of calls in the queue
before notification (any number from 1 through 99) in the space provided.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Operator Features

Page 4-21

4

Elevate Priority

This section contains instructions to arrange the QCC queue so that important
business calls are answered first.
NOTE:
During high-volume calling periods this means that only high-priority calls
are delivered to a QCC within a reasonable amount of time, and low-priority
calls go unanswered. To review call priority assignments, see “QCC Queue
Priority Level” in Chapter 3, “Lines/Trunks.”
The setting for the Elevate Priority option determines the length of time (in
seconds) before the calls waiting in the QCC queue are automatically assigned a
higher level of priority. Although the priority of every call in the queue is then
increased to a higher level, a call is never increased to the highest priority (1)
because priority 1 calls are those that must reach the operator as quickly as
possible.

4

Planning Form Instructions
Under the Elevate Priority heading on Form 6a, do one of the following:
■

To indicate that the order of priority is not changed, check the 0 Seconds
box (the factory setting).

■

To indicate that call priority is reordered, check the second box and write
the number of seconds in the space provided. (Select any number from 5
through 30 depending on the number of priority levels assigned to calls
ringing into the queue and the volume of incoming calls. The
recommendation for typical systems is 8 seconds.)

Message Center

4

This section contains instructions to assign this feature when there is more than
one QCC operator position and the customer wants one centralized location
where employees retrieve messages. Usually only one message center position is
necessary, but there can be several QCCs in one room sharing messaging duties.
The Message Center option allows you to designate a QCC as a message center
with the following options automatically set:
■

The only incoming calls that go to the message center QCC are calls to the
extension number of the QCC and calls sent to the QCC using Forward or
Follow Me.

■

Returning calls (such as those sent to an extension, operator-parked, and
camp-on calls) go to the message center QCC. This means that the
message center position is different from that of the system operator who
originally answered the call.

■

Group Coverage calls go to the QCC message center.

■

DID calls to invalid destinations (unassigned extension numbers) go to the
QCC message center.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Operator Features

Page 4-22

4

Planning Form Instructions
Under the Message Center heading on Form 6a, do one of the following:
■

To indicate that no message center operator is assigned, check the No box.

■

To assign a message center, check the second box and write the extension
of the QCC operator position in the space provided (see Form 2a or 5d).

Directed Call Completion

4

Use these instructions only if the system has a QCC with a Direct Station Selector
(DSS). Otherwise, skip to the next section, “Return Ring.”
This section contains instructions for changing the factory setting for Directed Call
Completion from Automatic to Manual (that is, the QCC operator must press the
Release button when using a DSS button to direct a call).
NOTE:
If the QCC operator uses the DSS to transfer calls across a private network,
the operator may want to use manual completion to avoid transfer without
return to busy. If you subscribe to ANI or ICLID and automatic completion is
selected, the ANI and ICLID information will be sent but calls will not return
on busy.

4

Planning Form Instructions
Under the Extended Call Completion heading on Form 6a, do one of the following:
■

To keep the factory setting, check the Automatic completion box.

■

To require the operator to use the Release button to direct calls, check the
Manual completion box.

4

Return Ring

This section contains instructions to specify the number of rings before an
unanswered call is returned from the extension where it was sent to the QCC
queue (or QCC message center position).
If the system includes a voice mail system, you should increase this number to
ensure that the voice mail system gets the call before it is returned.

Planning Form Instructions
Under the Return Ring heading on Form 6a, do one of the following:
■

To keep the factory setting, check the 4 Rings box.

■

To change the factory setting, check the second box and write the number
of rings you want to assign in the space provided (1–15 rings).

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Operator Features

Position-Busy Backup

Page 4-23

4

This section contains instructions to assign another telephone to receive calls
when all QCC operator consoles are in a position-busy state. Only a calling group
can be assigned as a backup for a QCC operator position. If a backup is not
designated, the system does not allow the last available operator position to go
into the position-busy state.

4

Planning Form Instructions
Under the Backup On heading on Form 6a, do one of the following:
■

To indicate that no backup is assigned, check the No box (factory setting).

■

To designate a backup, check the second box. The extension number of
the backup calling group will be completed later.

Operator Hold Timer

4

This section contains instructions to set the system to track the number of
seconds that callers are on hold at an operator console. When a caller is on hold
longer than the number of seconds programmed for the timer, the operator is
reminded by a single ring.

Planning Form Instructions
Under the Operator Hold Timer heading on Form 6a, do one of the following:
■

To keep the factory setting, check the 60 Seconds box (factory setting).

■

To change the factory setting, check the second box and write the number
of seconds (from 10 to 255 seconds) in the space provided.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Operator Features

Page 4-24

4

Call Types

This section contains instructions to assign a QCC operator to receive certain
types of calls and to set the QCC queue priority level.

4

Planning Form Instructions
The Group Coverage Calls section on the back of Form 6a will be completed later
in this chapter.
Under the Call Types heading on Form 6a (page 2):
1.

In the QCC Operator to Receive Calls column, for each call type, do one of
the following:
■

If QCC operators are not to receive the call type, write None.

■

If one or more QCC operators are to receive the call type, write any
combination of the extension number(s). See Form 2a or 5d.
NOTE:
You cannot assign an operator to either Follow Me calls or calls to
QCC operator extensions.

2.

In the QCC Queue Priority Level column, write the level for each call type.
Assign a value of 1 (high priority) through 7 (low priority). The factory
setting is 4.

Voice Announce

4

This section contains instructions to enable a QCC operator to originate Voice
Announce (VA) calls. When enabled, the Call 5 button on the QCC can originate
Voice Announce calls.
NOTE:
QCCs cannot receive Voice Announce calls.

Planning Form Instructions
Under the Voice Announce heading on Form 6a, do one of the following:
■

To prevent QCC operators from originating Voice Announce calls, check
the Disable box (factory setting).

■

To allow QCC operators to originate Voice Announce calls, check the
Enable box.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Operator Features

Direct Station Selector

Page 4-25

4

Use these instructions only if the system has Direct Station Selectors (DSSs)
connected to MLX operator consoles. Otherwise, skip to the next section,
“Group-Assigned Features.”
This section contains instructions for recording the range of extensions assigned
to the Page buttons, and for renumbering the extensions for Park so that the
extensions fall within the Page button ranges.

DSS Page Buttons

4

This section contains instructions for recording the range of extensions assigned
to each of three Page buttons. The three Page buttons should be set to reach
ranges of numbers that include the extension numbers in the extension
numbering plan (including non-local extensions if the system is in a private
network configuration) and reflect the number of extensions available:
■

If one DSS is connected to an operator console, set each Page button for a
range of 50 numbers (matching the 50 available extensions).

■

If two DSSs are connected, set each Page button for a range of 100
numbers. The Page buttons then control 100 extensions, 50 on each DSS.
NOTE:
If two DSSs are used, the Page buttons on the second DSS are not active.

4

Planning Form Instructions
In the Page Buttons table under the Direct Station Selector heading of Form 6a
(page 1), write the beginning extension for the range of the 50 or 100 extension
numbers for each Page button. Assign the lowest extension numbers in the plan
to the first Page button, the middle range of numbers to the second Page button,
and the highest extension numbers to the third Page button. (Use the information
from Form 2a, System Numbering: Extension Jacks to assign the range of
extensions for each Page button.) Also, record this information on Form 2d under
the DSS Page Buttons heading.

4

Park Zones

This section contains instructions to enable operators with a DSS to have
one-touch use of Park. The system automatically reserves eight extensions
(881−888) for system operator park zones; only system operators can use these
park zone extensions to park calls. Consider changing these factory-set
extensions to numbers that fall within the Page button ranges. The same
considerations apply as those used during reassignment of extension numbers.

Planning Form Instructions
In the Call Park Codes table under Direct Station Selector on Form 6a:
■

Write the new Zone numbers assigned in the Renumber to columns.

■

On Form 2d, System Numbering: Special Renumbers, write the new
numbers in the Renumber to column of the Park Zone section of that form.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Group-Assigned Features

Group-Assigned Features

Page 4-26

4

The system offers the following features to facilitate the call-handling
responsibilities of groups of users:
■

Call Pickup Groups

■

Group Paging

■

Coverage

■

Group Calling

This section contains instructions for recording information about these features.
To determine whether any of the group-assigned features are appropriate for
system users, see the analysis of the Employee Communication Survey.

Forms Needed
■

Form 2a, System Numbering: Extension Jacks

■

Form 2d, System Numbering: Special Renumbers

■

Form 4b, Analog Multiline Telephone

■

Form 4d, MLX Telephone

■

Form 5a, Direct-Line Console (DLC): Analog

■

Form 5b, Direct-Line Console (DLC): Digital

■

Form 6a, Optional Operator Features

■

Form 7a, Call Pickup Groups

■

Form 7b, Group Paging

■

Form 7c, Group Coverage

■

Form 7d, Group Calling

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Group-Assigned Features

Call Pickup Groups

Page 4-27

4

This section contains instructions for assigning this feature to employees who
work in a common area and who do not have a support person for coverage. You
can assign up to 30 call pickup groups with up to 15 telephones for each group.
Each telephone can be assigned to only one group.
NOTE:
This feature is similar to the Coverage feature presented later in this
chapter. Compare these features before choosing the appropriate feature
for the system.

4

Planning Form Instructions
1.

Form 7a holds the programming information for eight Call Pickup groups.
Make additional copes of the form if more groups are planned. Review the
analysis of question 10 on the Employee Communication Survey, and
determine the number of call pickup groups needed (maximum of 30).

2.

For each group, write the group number in the Group Number space. Start
with 1 and number the groups sequentially.

3.

Write the name of a group, such as Customer Service in the Group ID
space (see the survey analysis).

4.

Write the extension number for each group member in the Ext. No. column
(see Form 2a).

5.

Write each group member’s name or location in the Person or Location
column (see Form 2a).

Group Paging

4

This section contains instructions for setting the system to allow users to make
voice announcements that are heard by a particular group of employees with
speakerphones or by everyone who has a speakerphone.
You can assign six paging groups of selected employees, such as secretarial
pools, committee members, or departments, who need to hear announcements.
Each group can have as many as 10 extension numbers.
The seventh paging group is factory-set to page all extension numbers. This
group is useful if the system does not have a loudspeaker paging system.
The system automatically reserves extension numbers 793–799 for paging
groups. Extension 799 is the Page All group. Decide whether to keep or to
reassign the factory-set extension numbers. Keep in mind that you can provide
one-touch use of Group Paging to operators with DSSs if you renumber to
extensions within the Page 1, 2, or 3 button ranges or set the Page 1, 2, or 3
buttons so the operators can access them.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Group-Assigned Features

Page 4-28

4

Planning Form Instructions
1.

Determine the number of paging groups needed.

2.

For each group, write the name of the group, such as Sales, in the Group
ID space on Form 7b.

3.

To change the factory-set extension numbers:
a.

Write the new numbers in the Renumber to space.

b.

On Form 2d, System Numbering: Special Renumbers, write the new
numbers in the Renumber to column of the Group Paging section of
that form.

4.

Write the extension number for each group member in the Ext. No. column
(see Form 2a).

5.

Write each group member’s name or location in the Person or Location
column (see Form 2a).

4

Coverage

Coverage allows calls to extensions (called senders) to be covered by one or
more other extensions (called receivers). Coverage can be individual or
group-assigned. This section contains instructions for both types. See “Call
Restriction” earlier in this chapter for more information.

Forms Needed
■

Form 2a, System Numbering: Extension Jacks

■

Form 4b, Analog Multiline Telephone

■

Form 4d, MLX Telephone

■

Form 5a, Direct-Line Console (DLC): Analog

■

Form 5b, Direct-Line Console (DLC): Digital

■

Form 6a, Optional Operator Features

■

Form 8a, System Features

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Group-Assigned Features

Individual Coverage

Page 4-29

4

This section contains instructions to allow an arrangement in which calls from one
sender are covered by one or more receivers. A receiver can provide primary
Individual Coverage or secondary Individual Coverage.
A sender can have calls covered by up to eight receivers, and a receiver (such as
a secretary) can provide Individual Coverage for more than one sender (up to
eight buttons on one receiver telephone). Any type of telephone can be a sender;
only a multiline telephone with programmable buttons available can be a receiver.
The receiver must have a programmed Cover button for each sender whose calls
are being covered.
NOTE:
See “Coverage” in the Feature Reference for additional information.
Calls on lines programmed for No Ring cannot be covered.
If a principal user is assigned, calls that would be sent to Group Coverage are
sent only to the principal’s Group Coverage receivers. If the principal user has
Remote Call Forwarding on, calls are sent to an outside number rather than to the
coverage receivers.

Planning Form Instructions
1.

Review the Employee Communication Survey analysis and determine
which users (senders) need Individual Coverage.
NOTE:
Single-line telephones cannot be receivers, and QCCs cannot be senders
or receivers.

2.

On the appropriate form for each receiver telephone (Form 4b, 4d, 4f, 5a,
or 5b), locate an available button on the Button Diagram and write
Ind Cover and the sender’s extension number. Write P to indicate primary
or S to indicate secondary Individual Coverage.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Group-Assigned Features

Page 4-30

4

Group Coverage

In Group Coverage, senders are organized into groups, and calls received by any
member of the group are sent to a receiver.
Any type of telephone (excluding QCCs) can be a member of a coverage group;
however, no individual sender can be a member of more than one group. A
maximum of 32 coverage groups can be set up, and there is no limit to the
number of senders in each group. Three types of receivers can be programmed:
calling groups, or the QCC queue and/or multiline telephones.
NOTE:
Group Coverage can be used alone or can be set up to work with either primary or secondary Individual Coverage, or both. This allows callers to get
personal attention from the primary and/or secondary Individual Coverage
receiver and backup from Group Coverage. For example, a receiver such
as a secretary can have a Primary Cover button to provide Individual Coverage for a sender who is also a member of a coverage group.

Planning Form Instructions
1.

Form 7c holds information for eight coverage groups. Make additional
copies of the form if more groups are planned. Review the Employee
Communication Survey analysis and determine the senders to be grouped.

2.

Form 8a is used to identify system features. Under the Coverage Delay
Interval heading at the top of Form 8a, do one of the following:

3.

■

To keep the factory-set interval, check the 3 rings box.

■

To change the factory-set interval, check the second box and write
the number of rings (1–9) in the space provided.

Under the Delay Ring Interval heading (Release 4.0 and earlier systems
only), do one of the following:
■

To keep the factory-set interval, check the 2 rings box.

■

To change the factory-set interval, check the second box and write
the number of rings (1–6) in the space provided.

4

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Group-Assigned Features

4.

Issue 1
August 1998
Page 4-31

On Form 7c:
a.

Write the group number in the Group No. space. Start with 1 and
number the groups sequentially.
NOTE:
If a group is the coverage group for AUDIX Voice Power1
(the factory setting is Group No. 30 but can be changed),
write AUDIX by the group number and list the extensions of
AUDIX Voice Power subscribers (see Form 2a).

b.

List the extension numbers of all senders in the group in the upper
block (see Form 2a).

c.

List the receivers for the group in the lower block by doing one of the
following:
NOTES:
1. If you have not yet created calling groups, you must defer
naming them as receivers until later.
2. If the system includes a voice mail system, see that system’s
documentation for completing the receivers. In addition, if the
system is part of a private network with Centralized Voice
Messaging, see the Network Reference.

5.

6.

1.

■

Designate a calling group as a receiver by checking the
Calling Group box (see Form 7d).

■

Designate the QCC queue as a receiver (Hybrid/PBX mode
only) by checking the QCC Queue box and/or listing the
extension numbers of all receivers (maximum of eight).

On each copy of Forms 4b, 4d, 5a, and 5b that describes a specific
receiver:
a.

Locate an available button on the Button Diagram.

b.

Write Group Cover and the coverage group number in the space
available.

If designating the QCC Queue as a receiver (Hybrid/PBX mode only), on
the Group Coverage Calls table on Form 6a (page 2):
a.

Write the extension(s) for the QCC operator position(s) to receive
the calls in the QCC Operator to Receive Calls column (see
Form 2a).

b.

Write the priority level for each coverage group’s calls in the QCC
Queue Priority Level column. Assign a value of 1 (highest) through 7
(lowest); the factory setting is 4.

No longer orderable.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Group-Assigned Features

Page 4-32

4

Group Calling

This section contains instructions to group the telephones of people (such as
ticketing agents) who handle the same type of call. Through the Group Calling
feature, all telephones in the group are assigned to a single extension number
that is used by both inside and outside callers to reach the group. The individual
extension numbers of the telephones are still used by callers who need to reach a
specific member of the calling group.
NOTES:
1. The Extension Status feature must be set for the Group Calling/CMS
configuration (which is the factory setting) in order for calling groups to be
available. See the “Extension Status” instructions later in this chapter for
details.
2. In Release 6.1 and later, one non-local member may be in a calling
group. A calling group cannot contain both local and non-local members.
See the Network Reference for information.
3. If calling groups are to be used in conjunction with Centralized Voice
Messaging, see the Network Reference for information.
The system automatically reserves extension numbers 770–791 and 7920–7929
for calling groups (these may be changed). If operators with DSSs need
one-touch Group Calling, renumber the extensions that fall within the Page
button ranges.
If the system has AUDIX Voice Power/Fax Attendant System2, certain extension
numbers are reserved as follows:
7924

Fax Response

7925

Voice Mail

7926

Call Answer

7927

Information Service

7928

Message Drop

770

Automated Attendant

Calling groups can be part of the group assignment for Night Service, as
described later in this chapter.

2.

No longer orderable.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Group-Assigned Features

Issue 1
August 1998
Page 4-33

Planning Form Instructions
1.

Review the Employee Communication Survey analysis and determine the
number of calling groups needed, using the following guidelines:
■

Assign up to 32 calling groups with up to 20 members for each
group. Each telephone user can be a member of only one
calling group.

■

Designate up to 80 lines/trunks to ring directly into a calling group.
Incoming calls on a given line/trunk can be directed to only one
calling group.

■

If the MERLIN LEGEND Mail or other supported VMS is being used,
either on the local system or a remote system (Centralized Voice
Messaging) reserve one or more calling groups for that feature.

■

A calling group may have up to one non-local member (Release 6.1
and later). If a calling group has a non-local member, that is the only
member allowed in the calling group. Local and non-local members
cannot be in the same calling group. A calling group containing a
single non-local member can be used for the same purposes as a
calling group containing only local extensions. This includes night
service, group coverage, calling group overflow coverage, and QCC
queue overflow coverage across a private network to a centralized
VMS/AA, non-local calling group, QCC queue, DLC, or any
individual extension on a remote MERLIN LEGEND, DEFINITY
ECS, or DEFINITY Prologix system, or to the PSTN via UDP
routing.

2.

For each calling group, make a copy of both sides of Form 7d, Group
Calling.

3.

For each group, on the front of Form 7d, list the extensions and lines/trunks
assigned to the group:
a.

Write the group number in the Group No. space. Start with 1 and
number sequentially.

b.

Write the name of the group in the Group Name space. See the
survey analysis.
NOTE:
If the system has MERLIN LEGEND Mail or other supported
VMS, fill in only the group number and group name here,
then fill in the rest of the Group Calling information on the
applicable forms for that VMS.

4

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Issue 1
August 1998

Features
Group-Assigned Features

c.

Page 4-34

Do one of the following:
■

To use a factory-set extension number, write the number in
the space provided (770 for group 1, 771 for group 2, and
so on).

■

To change a factory-set extension number, write the new
number in the Renumber to space, and then on Form 2d,
System Renumbering: Special Renumbers, write the group
name in the Group ID Label column (up to 7 characters), and
the new number in the Renumber to column of the Group
Calling section of that form.

NOTE:
Before you complete the extension number and name entries in Step 4,
read Step 2 on page 4–37 of the instructions in the next section, “Calling
Group Options.”
4.

In the Extensions section of Form 7d, write the extension number of each
member of the group in the Ext. No. column and the name of the person or
location in the Person or Location column (see Form 2a).

5.

In the Trunks/Pools table of Form 7d, for each line/trunk that is to ring
directly into the calling group, write the line/trunk or pool number (see
Form 2c).
NOTES:
1. When a pool is assigned to a calling group, all lines/trunks in the
pool are assigned to the group. Individual trunks within the pool
cannot be assigned to a calling group.
2. If a pool contains any dial-in trunks (such as DID trunks), the
pool cannot be assigned to a calling group. Also, pools with
private network tandem trunks should not be assigned to calling
groups.
3. Pools may be assigned to only one calling group.
4. Lines/trunks assigned as the system Music on Hold or External
Page Port cannot be assigned to a calling group.
5. Before adding to a calling group, you must first remove
lines/trunks from the QCC.

6.

If assigning a calling group as backup for a QCC, under the Position Busy
Backup heading in the Queued Call Console section of Form 6a, Optional
Operator Features, check yes and write the extension number of the
calling group.

7.

To record information for another calling group, repeat this procedure
beginning with Step 3; use a blank Form 7d for each group.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Group-Assigned Features

Calling Group Options

Page 4-35

4

This section contains instructions for the following calling group options:
■

Hunt Type

■

Primary and Secondary Delay Announcements

■

Message-Waiting Receiver

■

Calls-in-Queue Alarm Thresholds

■

External Alert for Calls-in-Queue Alarm

■

Overflow Coverage

■

Overflow Threshold

■

Overflow Threshold Time

■

Prompt-Based Overflow (Release 6.0 and later only)

■

Group Type

■

Queue Control (Release 6.0 and later only)

The order in which the system searches for available calling group members for
subsequent calls can be circular, linear, or according to which agent is most idle
(Release 5.0 or later) and is called the hunt type. The Circular setting searches for
an available calling group member starting with the extension after the last
extension to receive a call. The Linear setting distributes calls starting with the first
extension assigned to the group through system programming. The Most Idle
setting distributes calls according to the most-idle queue. For some applications,
this hunt type is more efficient than the circular method, because it takes into
account the varying duration of calls.
Up to 10 primary and one secondary delay announcement devices can be
designated for each calling group; more than one calling group can use the same
announcement devices. The announcement devices should not be assigned as
group members, and they are outward-restricted to prevent unauthorized calls.
Each calling group can have only one telephone assigned as its message-waiting
receiver. The same telephone can be assigned as the message-waiting receiver
for more than one calling group.
Three Calls-in-Queue Alarm thresholds can be set to more clearly indicate the
real-time status of the calls waiting in the queue according to the behavior of
programmed Calls-in-Queue Alarm buttons. In Release 4.2 and earlier, only one
Calls-in-Queue Alarm Threshold setting is available to activate the LEDs at
programmed Calls-in-Queue Alarm buttons for a calling group.
Using all three levels, the system manager sets Threshold 3 to the highest value,
Threshold 2 to a middle value, and Threshold 1 to the lowest value. A
Calls-in-Queue Alarm button indicates the severity of the alarm conditions in the
following ways:

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Group-Assigned Features

Issue 1
August 1998
Page 4-36

■

If the number of waiting calls is less than the value programmed for
Threshold 1 or drops below that level, the LED is unlit.

■

If the number of waiting calls is greater than or equal to the Threshold 1
value but less than the Threshold 2 value, the LED flashes.

■

If the number of waiting calls is greater than or equal to the Threshold 2
value but less than the value for Threshold 3, the LED winks.

■

If the number of waiting calls is greater than or equal to the highest value,
Threshold 3, the LED lights steadily.

If all three thresholds are set to the same value, the result is one threshold only
with LED state either off or on (steady). If two values are the same, then the result
is two alarm levels (flash, steady). The factory setting is one call for all three
thresholds with LED states of off and steady.
In Release 5.0 and later systems, the primary delay announcements function like
the single announcement available in prior releases. After the delay
announcement (the primary delay announcement in Release 5.0 and later
systems), an inside caller hears a special ringback, a transferred inside caller
hears regular ringback, and an outside caller (including a transferred outside
caller) hears special ringback or Music On Hold, if programmed, until the call is
answered by a calling group member. The delay announcement or primary delay
announcement is played only once while the call is in queue.
In Release 5.0 and later systems, the system manager can specify the extension
for an optional secondary delay announcement and use system programming to
set the interval (0–900 seconds) between announcements. This setting
determines the time before a waiting caller hears the secondary announcement
or, if it is set to repeat, the interval between replays of the secondary
announcement. The secondary announcement can either repeat or play only
once, after which the caller hears ringback or Music On Hold, according to the
rules outlined above. The primary and secondary announcement options, when
used together, allow the system manager to issue an initial message to callers,
followed by a repeating announcement that, for example, urges the caller to stay
on the line and wait for a calling group member.
The external alert designated as a calls-in-queue alarm can be any alerting device
connected through an MFM in the External Alert mode for MLX telephones. That
alert is tied to the third threshold value. The alert stays on as long as the threshold
is exceeded. Only one external alert can be designated for each calling group.
Since the signal is continuous, you should only use lighted external alerting
devices. An alert connected to a Supplemental Alert Adapter for an analog
multiline telephone should not be used as a calls-in-queue alarm.
The Overflow Threshold determines the maximum number of calls (1–99) waiting
in the calling group queue before being sent to the Overflow receiver. The
Overflow Threshold Time determines the maximum amount of time that any call
waits in the queue before being sent to the Overflow receiver. The Overflow
Threshold should be set to a number larger than the third Calls-in-Queue Alarm
Threshold to ensure that the Calls-in-Queue Alarm will alert before calls are sent

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Group-Assigned Features

Issue 1
August 1998
Page 4-37

to the Overflow receiver. If the Overflow Threshold Time is the primary source for
overflow, set the Overflow Threshold to a large number of calls (for example, 99
calls). If you want calls to overflow based on the number of calls in the queue,
disable the Overflow Threshold Time by setting it to 0 seconds.
In Release 6.0 and later systems, Prompt-Based Overflow allows callers waiting
in the queue, and listening to delay announcements, to press the pound key (#) in
order to reach the overflow receiver for the group (which may be the QCC queue
to another calling group, including a calling group assigned for a voice mail
system).
NOTE:
One TTR is allocated while the announcement unit is playing the message
if Prompt-Based Overflow is enabled for a group.
In Release 6.0 and later systems, the system manager can control the number of
calls allowed into the primary calling group queue. Subsequent callers will receive
a busy signal as long as the call was received on the following types of
lines/trunks: DID, PRI facilities programmed for dial-plan routing, and all calls that
are transferred from a VMI port to a local extension.
NOTE:
Remote Access calls to a calling group, coverage calls directed to a calling
group, and calls directed to a calling group through a QCC Position-Busy
backup are not eligible for queue control.

Planning Form Instructions
For each calling group:
1.

On Form 7d (page 2), copy the Group No., ID, and extension number from
the front of the form.

2.

Select the Hunt Type by doing one of the following:
■

To keep the factory-set hunting pattern, check the Circular box.
NOTE:
If you choose a Linear hunt, be sure you have listed the
extension numbers and names in the Extensions section on
Form 7d (page 1), in the order that you want the group
searched. If you have not done this, go back and correct the
front of the form so that the extensions are in the right order.

■

To change the factory-set hunting pattern to Linear, check the Linear
box.

■

To change the factory-set hunting pattern to Most-Idle, check the
Most-Idle box.

4

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Group-Assigned Features

3.

4.

Issue 1
August 1998
Page 4-38

Under the Primary Delay Announcement heading, do one of the following:
■

If there are no announcement devices, check the No box and
proceed to Step 4.

■

To designate one or more announcement devices, check the second
box and write the extension numbers for the devices in the space
provided (see Form 2a or 2b).

Under the Secondary Delay Announcement heading, do one of the
following:
■

If there is no secondary announcement device, check the No box
and proceed to Step 5.

■

To designate a secondary announcement device, check the second
box and write the extension number for the device in the space
provided (see Form 2a or 2b). Also do the following:
— Write in the desired Delay Interval between the primary
announcement and the secondary announcement in
seconds. The Delay Interval is also the time between repeats
of the Secondary Announcement, if the Repeat
Announcement option is set.
NOTE:
As a rule the Delay Interval should never be set less than the
length (in seconds) of the secondary announcement. Ideally,
the Delay Interval should be a multiple of the secondary
announcement’s length, based on the anticipated number of
calls in the queue. For example, if the secondary
announcement length is 10 seconds and five calls are
expected to be in the queue during busy times, then the
Delay Interval should be 50 seconds. For more information
on optimizing the settings for announcements, see the
Feature Reference.
— If you want the secondary announcement to repeat
continuously after the Announcement Delay Interval, then
check the Yes box next to Repeat Announcement. Otherwise
check the No box.

5.

To designate a telephone to receive message-waiting indications for the
group, do one of the following under the Message-Waiting Receiver
heading on Form 7d (page 2):
■

To assign no receiver, check the No box.

■

To assign a receiver, check the second box and write the extension
number of the message-waiting receiver (see Form 2a).

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Group-Assigned Features

6.

7.

8.

9.

10.

11.

Issue 1
August 1998
Page 4-39

Under the First Calls-in-Queue Alarm Threshold heading, do one of the
following:
■

To keep the factory setting, check the 1 Call box.

■

To change the factory-set number of calls allowed in the queue
before members are notified with a flashing LED, check the second
box and write the number of calls (up to 99) in the space provided.

Under the Second Calls-in-Queue Alarm Threshold heading, do one of the
following:
■

To keep the factory setting, check the 1 Call box.

■

To change the factory-set number of calls allowed in the queue
before members are notified with a winking LED, check the second
box and write the number of calls (up to 99) in the space provided.

Under the Third Calls-in-Queue Alarm Threshold heading, do one of the
following:
■

To keep the factory setting, check the 1 Call box.

■

To change the factory-set number of calls allowed in the queue
before members are notified with a steady LED, check the second
box and write the number of calls (up to 99) in the space provided.

Under the External Alert for Calls-in-Queue Alarm heading, do one of the
following:
■

For no external alert for Calls-in-Queue Alarm, check the No box.

■

To designate an external alert when the Third Calls-in-Queue Alarm
Threshold is exceeded, check the second box and write the
extension number for the alert in the space provided (see Form 2b).

Under the Overflow Coverage heading, do one of the following:
■

For no overflow coverage, check the No box.

■

To designate overflow coverage by another calling group, check the
second box and write the calling group number of the overflow
calling group in the space provided.

■

To designate that overflow coverage will be provided by QCC
operators, check the third box and write the QCC LDN (queue)
extension number in the space provided.

Under the Overflow Threshold heading, do one of the following:
■

To keep the factory setting, check the 1 call box.

■

To change the threshold, check the second box and write the
number of calls (up to 99) in the space provided.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
Group-Assigned Features

12.

13.

14.

Issue 1
August 1998
Page 4-40

Under the Overflow Threshold Time heading, do one of the following:
■

To keep the factory setting and disable the Overflow Threshold
Time, check the 0 seconds box.

■

To change the threshold, check the second box and write the
maximum number of seconds (1–900) calls wait in the queue in the
space provided.

Under the Prompt-Based Overflow heading, do one of the following:
■

To keep the factory setting and disable the Prompt-Based Overflow
feature, check the Disabled box.

■

To enable Prompt-Based Overflow, check the Enabled box.

Under the Group Type heading, do one of the following:
■

To keep the factory setting of no automatic login, check the Auto
Logout box.

■

To change the factory setting from Auto Logout, do one of the
following:
— Check the Auto Login box to indicate automatic login for an
extension that should never be logged out, such as a data
extension.
— Check the Integrated VMI box to indicate automatic login for
a VMS that requires special signaling for integrated
operation.
— Check the Generic VMI box to indicate automatic login for a
VMS that does not require special signaling.

15.

To specify the number of calls allowed into the group calling queue, under
the Queue Control heading do one of the following:
■

To keep the factory setting, check the 99 calls box.

■

To change the threshold, check the second box and write the
number of calls (0–98) in the space provided.
NOTE:
Specifying a Queue Control threshold of 0 indicates that no calls are
allowed into the queue (Queue Control is turned off).

Proceed to the next section, “System Features.”

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

System Features

Page 4-41

4

System features affect all users and all or most telephones. For more information
on system features, see the Feature Reference.
This section contains instructions for assigning the following system features:
■

Transfer of calls

■

Camp-On Return Time

■

Call Park Return Time

■

Automatic Callback

■

Extension Status

■

Station Message Detail Recording (SMDR)

■

Inside Dial Tone

■

Reminder Service Cancel

■

Redirect Calls to Unassigned Extension Numbers

■

Recall Timer

■

Interdigit Timers

■

Rotary-Dial Delay

■

Allowed Lists

■

Disallowed Lists

■

Night Service

■

Labeling

■

Automatic Route Selection

Forms Needed
■

Form 3e, Automatic Route Selection Worksheet

■

Form 3f, Automatic Route Selection Tables

■

Form 3g, Automatic Route Selection Default and Special Numbers Tables

■

Form 6e, Allowed Lists

■

Form 6f, Disallowed Lists

■

Form 6g, Call Restriction Assignments and Lists

■

Form 8a, System Features

■

Form 9a, Night Service: Group Assignment

■

Form 9b, Night Service: Outward Restriction

■

Form 9c, Night Service: Time Set

■

Form 10a, Label Form: Posted Message

■

Form 10b, System Speed Dial

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Page 4-42

4

Transfer Options

This section contains instructions for setting the following Transfer feature options
to allow users to transfer outside or inside calls to another telephone:
■

Transfer Return Interval

■

One-Touch Transfer

■

Transfer Audible

■

Type of Transfer
NOTES:
1. Transfer features, and any other feature that requires more than one SA
button, can be disabled on Single-line telephones by removing all but one
SA button through centralized programming. Refer to Form 4f, Tip/Ring
Equipment.
2. If customers with CTI applications will frequently use the Conference
feature, set the system Transfer Type to Ring and not Voice. This will
minimize the possibility of broadcasting a conference over an unattended
speakerphone.
3. If the DLC operator uses the DSS to transfer calls across a private
network, the operator may want to use manual completion to avoid
transfer without return to busy. If you subscribe to ANI or ICLID and
automatic completion is selected, the ANI and ICLID information will be
sent but calls will not return on busy.

Planning Form Instructions
1.

2.

Under the Return Time Interval heading in the Transfer Options section of
Form 8a, do one of the following:
■

To keep the factory setting, check the 4 rings box.

■

To indicate no return for transferred calls, check the 0 rings box.

■

To change the factory-set number of rings, check the third box and
write the number of rings (1–9) in the space provided.

Under the One-Touch Call Handling heading, do one of the following:
■

To keep the factory setting, check the One-Touch Transfer box and
do one of the following:
— Check the Automatic Completion box to keep the factory-set
automatic completion of transfers.
— Check the Manual Completion box to change the factory
setting to manual completion.

■

To change from One-Touch Transfer to One-Touch Hold, check the
One-Touch Hold box.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

3.

Page 4-43

Under the Transfer Audible heading, do one of the following:
NOTE:
If programmed for Music On Hold and a music source is provided,
outside callers who are transferred to a calling group, are waiting in
the queue, or outside callers who are parked or camped-on, will hear
music while they are waiting. If the system uses the Centrex Transfer
via Remote Call Forwarding feature, it is recommended that Transfer
Audible be set to Ringback.

4.

■

If the system should play music while callers are on hold for transfer,
check the Music On Hold box.

■

If the system will not provide music, check the Ringback box.

Under the Type of Transfer heading, do one of the following:
■

For the system to select a Ring button for transferred calls, check
the Ring button box (factory setting).

■

For the system to select a Voice button for transferred calls, check
the Voice button box.

Camp-On Return Time

4

This section contains instructions for designating the number of seconds a caller
waits when transferred to a busy extension by way of the Camp-On feature. If the
telephone is still busy at the end of the programmed interval, the call returns to the
person who transferred the call.

4

Planning Form Instructions
Under the Camp-On Return Time heading on Form 8a, do one of the following:
■

To keep the factory-set interval, check the 90 seconds box.

■

To change the factory-set interval, check the second box and write the
number of seconds (30–300) in the space provided.

Call Park Return Time

4

This section contains instructions for designating the number of seconds a caller
waits when a person uses the Call Park feature to put a call on hold. If the call is
not picked up at the end of the programmed interval, the call returns to the person
who parked the call.

Planning Form Instructions
Under the Call Park Return Time heading on Form 8a, do one of the following:
■

To keep the factory-set interval, check the 180 seconds box.

■

To change the factory-set interval, check the second box and write the
number of seconds (30–300) in the space provided.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Page 4-44

4

Automatic Callback

This section contains instructions for setting the number of rings the system
should use to alert a caller about a callback attempt. After the specified number of
rings, the system abandons the callback attempt.

4

Planning Form Instructions
Under the Automatic Callback Interval heading on Form 8a, do one of the
following:
■

To keep the factory-set interval, check the 3 rings box.

■

To change the factory-set interval, check the second box and write the
number of rings (1–6) in the space provided.

4

Extension Status

This section contains instructions to set Extension Status to allow an operator, a
calling group supervisor, or a Call Management System (CMS) supervisor to
determine the status of a telephone at a glance. The lights next to the buttons on
a DSS or next to Auto Dial buttons programmed with extension numbers indicate
the status of the telephone.
In Hotel mode, Extension Status (ES) affects a station’s calling restrictions. Only
an ES operator can use a DSS to turn off states ES1 or ES2 to remove calling
restrictions. In CMS mode, Extension Status does not affect calling restrictions.
NOTE:
In Hotel mode, an ES-restricted station can call a remote private network
extension.
Decide on the configuration and assign operator positions to monitor extension
status.

Planning Form Instructions
Under the Extension Status heading on Form 8a:
1.

Check the Assign to operator positions box and write the extension number
for each operator position in the space provided. See the appropriate copy
of Form 5a or 5b.

2.

Do one of the following:
■

To keep the factory-set configuration, check the Group Calling/CMS
box.

■

To change the configuration, check the Hotel box.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Station Message Detail Recording (SMDR)

Page 4-45

4

Use these instructions only if connecting a Station Message Detail Recording
(SMDR) device or call accounting application. Otherwise, skip to the next section,
“Inside Dial Tone.”
This section contains instructions for setting up SMDR to keep track of telephone
usage. SMDR works in conjunction with the Call Accounting System (Intuity CAS,
Windows CAS, IS CAS, CAS Plus V3, and MERLIN LEGEND Reporter) or a
serial printer connected to the SMDR port on the control unit. The SMDR port is
the upper RJ-45 jack on the processor module.
Two SMDR report formats are available: the factory-set Basic format or the ISDN
format. The ISDN format is used when the business subscribes to ICLID or to the
AT&T INFO2 automatic number identification service (ANI). When the system is
set for ISDN format, the actual number dialed by the caller appears on the report.
In a PRI private network, the ISDN format may be used to show the caller’s
telephone number. The rest of the fields are identical to the Basic format.
Two options, Calls Reported (non-UDP) and Calls Reported (UDP), determine
what calls are included in the SMDR report. For calls that are not routed using the
non-local dial plan, the options available are to report both incoming and outgoing
calls (factory setting) or outgoing calls only. For calls that are routed using the
non-local dial plan, the options available are to report both incoming and outgoing
calls (factory setting) or none.
NOTES:
1. For outgoing UDP calls, any call that involves the public network will be
logged on the SMDR report regardless of the programmed setting of the
UDP SMDR option. Examples of this type of call include DID calls that get
routed over the private network, CO transfers from one switch to another
in the private network, and UDP ARS calls.
2. For incoming UDP calls, with the exception of UDP calling group calls,
the call will not be logged unless the Calls Reported (UDP) option is set to
Log Incoming/Outgoing. UDP calling group calls (a call made from one
switch in a private network to a calling group on another switch in the
private network) will be logged regardless of the programmed setting of
the UDP SMDR option if the Talk Time option is set to Enable.
The Talk Time option determines whether the SMDR report includes the talk-time
duration in the Talk field. Talk-time duration is the amount of time a calling group
agent spends on an incoming call. If SMDR is used with the MERLIN LEGEND
Reporter, the Talk Time option must be enabled. If SMDR is used with CAS or a
serial printer, the Talk Time option must be disabled.
MERLIN LEGEND Reporter and CAS will not operate concurrently.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Issue 1
August 1998
Page 4-46

If Talk Time is enabled, an asterisk (*) indicates an abandoned call. This occurs
when the calling party disconnects a call being directed to an Auto Login or Auto
Logout calling group before a member answers, even if the call was answered
elsewhere in the system (unless the call is on a loop-start facility that does not
have reliable disconnect supervision).
NOTES:
1. For accurate reports, the system date must be set to the current date
when the system is installed. Be sure you checked the Yes box on Form 1
under Set System Date.
2. For systems where the majority of lines are PRI facilities, the SMDR Call
Length should be programmed for one second.
3. When SMDR is used with the MERLIN LEGEND Reporter, the settings
for Call Length and Calls Reported have no effect on SMDR reporting for
calling group calls.

Planning Form Instructions
In the SMDR Options section of Form 8a:
1.

2.

3.

4.

5.

Under the Call Format heading, do one of the following:
■

To keep the factory-set format, check the Basic box.

■

To change the report format, check the ISDN box.

Under the Call Length heading, do one of the following:
■

To keep the factory-set call length, check the 40 seconds box.

■

To change the factory-set call length, check the second box and
write the number of seconds (0–255) in the space provided.

Under the Calls Reported (non-UDP) heading, do one of the following:
■

To keep the factory setting, check the Incoming and outgoing box.

■

To change the factory setting, check the Outgoing only box.

Under the Calls Reported (UDP) heading, do one of the following:
■

To keep the factory setting, check the Incoming and outgoing box.

■

To change the factory setting, check the None box.

Under Talk Time heading, do one of the following:
■

To keep factory setting, check the Disable box.

■

To change the factory setting, check the Enable box.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Inside Dial Tone

Page 4-47

4

This section contains instructions for specifying whether the system uses an
inside dial tone that is different from or the same as outside line/trunk dial tone.
The factory setting is for a different inside dial tone. How you set the system for
dial tone is a matter of preference.
NOTE:
Regardless of how you set this option, VMSs receive outside dial tones.
Some modems may require outside dial tone to dial out.

4

Planning Form Instructions
Under the Inside Dial Tone heading on Form 8a, do one of the following:
■

To keep the factory-set system inside dial tone, check the Inside box.

■

To change the dial tone to match the outside dial tone, check the Outside
box.

Reminder Service Cancel

4

This section contains instructions for assigning a preset time when the system
cancels all reminders.
Although all users can set and cancel reminder calls for their own telephones, and
DLC system operators can set and cancel reminder calls for any telephone in the
system, Reminder Service Cancel automatically cancels all reminder calls at the
preset time, for example, at the end of the business day when all users have gone
home and are not available to receive reminders.

Planning Form Instructions
Under the Reminder Service Cancel heading on Form 8a, do one of the following:
■

To set no reminder service cancel time, check the No box.

■

To set a time to cancel all reminders in the system, check the second box
and write the time of day in the space provided.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Page 4-48

Calls to Unassigned Extensions

4

This section contains instructions for designating that calls made to unassigned
extension numbers by remote access users or on DID or dial-in tie trunks are
redirected to another extension number, the QCC queue, or a calling group
instead of to the primary operator.
NOTE:
When an Automated Attendant transfers a call to a non-local extension, the
transferring MERLIN LEGEND system monitors the call to ensure that it is
answered. If the non-local extension is not available or the call is not
answered within the transfer redirect timeout period (fixed at 32 seconds),
the call stops ringing at the non-local destination and is redirected to the
extension on the same system as the Automated Attendant that is
programmed to receive redirected calls. This redirect extension can be a
QCC queue, a calling group, or an individual extension.

!

SecurityAlert:
DID numbers that correspond to pool dial-out codes (or facility access
codes) can be used to avoid toll restriction, leading to toll abuse and/or
fraud. (See Appendix A, “Customer Support Information” for more
information about security.)

Planning Form Instructions
Under the Calls to Unassigned Extensions heading on Form 8a, do one of the
following:
■

To keep the factory setting, check the Extension box.

■

To change from the factory-set redirect to the primary operator, check one
of the following:
— To redirect calls to a QCC operator (Hybrid/PBX only), check the
QCC queue box and write the extension number in the space
provided (see Form 2a).
— To redirect calls to another telephone, check the Extension box and
write the extension number in the space provided (see Form 2a).
— To redirect calls to a calling group, check the Calling Group box and
write the calling group extension number in the space provided (see
Form 7d).

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Page 4-49

4

Recall Timer

This section contains instructions for designating the length of the switchhook
flash sent when Recall is used to disconnect a call and receive a new dial tone
without hanging up. The interval of the switchhook flash and how Recall works
depends on the type of telephone being used.
For multiline telephones, the factory setting is 450 ms. If users experience
difficulty with Recall, the interval can be changed to a longer or shorter interval.
The single-line telephone Flash or Recall button transmits a timed switchhook
flash of about half a second.

4

Planning Form Instructions
Under the Recall Timer heading on Form 8a, check one of the following:
■

350 ms

■

450 ms (factory setting)

■

650 ms

■

1 sec

Interdigit Timers

4

Programming for interdigit timers is reserved for Lucent Technologies technical
support personnel or authorized dealers.
Interdigit timers are used by the MERLIN LEGEND system to determine when a
user originating an outside call has completed dialing the digits. The information is
necessary to allow the system to perform subsequent operations. You should not
change the factory settings for interdigit timers unless instructed to do so by
Lucent Technologies technical support or by an authorized dealer.

4

Rotary

This section contains instructions for designating whether dialed digits on
rotary-dial lines/trunks are sent one by one as they are dialed or are stored and
sent when dialing is completed.

Planning Form Instructions
Under the Rotary heading on Form 8a, check one of the following:
■

To store digits and send them when dialing is completed, check the Delay
(factory setting) box.

■

To send digits out as they are dialed, check the No Delay box.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

4

Allowed Lists

!

Page 4-50

SecurityAlert:
If you assign a 0 (zero) as the first digit for any entry in an Allowed List, any
toll restrictions assigned for calls to numbers that can be placed by local or
toll operators are removed.

Use the instructions in this section and the next (“Disallowed Lists”) only if calling
restrictions are assigned to any telephones. Otherwise, skip to the section, “Night
Service.”
This section contains instructions to designate an Allowed List of telephone
numbers that a restricted telephone can dial.
You can design up to eight lists, each with a maximum of 10 numbers. Each
number can have up to six digits, for example, an area code followed by an
exchange. If a toll-call prefix is required, you can include a leading 1, which the
system doesn’t count as one of the six digits. Star codes (such as *67) may also
be included in the list to allow users to access special services offered by the
Central Office (CO). Once you have designed the lists, decide which restricted
telephones have access to the lists. Each restricted telephone can have up to
eight lists.

!

SecurityAlert:
In some instances, after dialing a star code the CO responds with a second
dial tone as a prompt to enter additional digits. If a caller begins dialing
additional digits before the second dial tone, system restrictions may be
bypassed and a restricted call may be routed. Careful administration of the
Second Dial Tone Timer prevents the caller from bypassing call restrictions
in this manner. Refer to the Planning Form Instructions that follow for
information.

If foreign exchange (FX) or tie trunks are connected to the system, you can enter
the exchange in the Allowed List to allow people with restricted telephones to dial
numbers to the area code for the FX or tie trunk. As you design each list, consider
which numbers need to be called by specific groups of restricted users. In a
private network, restricted telephones can dial non-local UDP extensions. The
non-local extension ranges do not need to be put on an Allowed List.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Page 4-51

4

Planning Form Instructions
On Form 6e:
1.

Write the name of the list in the space next to the list number.

2.

Write the allowed area codes, exchanges, and/or star codes in the spaces
provided (a maximum of 10 entries for each list).

3.

If star codes are included in the Allowed List, the Second Dial Tone Timer
must also be programmed. This timer induces a time delay before the user
may dial additional digits after a star code, and is activated once a star
code has been accepted. The dialing of any digits before this timer expires
is treated as if normal restrictions have been violated and the call is not
completed. The timer may be set from 0 to 5000 ms in increments of
200 ms. The factory setting is 0. On Form 1 (page 2), System Planning,
write the desired setting for the Second Dial Tone Timer.

4.

Write the extension numbers of the telephones that need access to the list
in the Allow to Ext. Nos. column (see Form 2a).

5.

If you planned Remote Access with restrictions and want to permit Allowed
List numbers to be called by remote access users, then do the following:
NOTE:
Allowed List Class-of-Restriction assignments apply to all remote
access users and cannot be assigned on an individual basis.
a.

On Form 3a (page 3), Incoming Trunks: Remote Access, in the
Class of Restrictions without Barrier Codes section, write the list
numbers under the Allowed List Access heading for either or both tie
and non-tie trunks.

b.

On all copies of Form 3a (page 4), Class of Restriction with Barrier
Codes, write the list numbers under the Allowed List Access
heading for each barrier code assigned.

Disallowed Lists

4

This section contains instructions for using Disallowed Lists to prevent people
from making calls to specific numbers, whether or not restrictions are specified for
an extension and for Remote Access. You can use this feature instead of
restricting telephones totally from making toll or local calls.

!

SecurityAlert:
Be sure to review the toll fraud information with regard to Disallowed Lists in
Appendix A, “Customer Support Information.”

Use a “wild card” character to indicate that you want calls to an exchange
restricted in every area code. During system programming, a Pause (entered
using the Hold button) indicates a wild card character; therefore, use the letter “p”
to indicate on the form that a wild card character should be programmed.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Issue 1
August 1998
Page 4-52

You can design up to eight lists with a maximum of 10 numbers. Each number can
have up to 11 digits, for example, a leading 1 (if a toll-call prefix is required for
dialing) followed by the area code and telephone number. Star codes (such as
*67) may also be included in the list to block users from accessing special
services offered by the Central Office. Once you have designed the lists, decide
which telephones to restrict. You can assign up to eight lists for each telephone.
Disallowed List 7 is the system default list and includes the numbers most
frequently associated with fraud. The table below lists the factory set entries for
Disallowed List 7.
Table 4–2.

Disallowed List 7 Factory Set Entries
0
10
11
1809
1700
1900
976
1ppp976
✱

NOTES:
1. Users cannot dial a number on an Allowed List if it matches a number on
a Disallowed List assigned to the telephone.
2. For a private network environment, see the Network Reference for
planning Disallowed Lists needed to restrict calls across the private
network.

Planning Form Instructions
On Form 6f:
1.

Write the name of the list in the space next to the list number.

2.

Write the disallowed area codes, exchanges, and/or star codes in the
spaces provided (a maximum of 10 entries for each list). Use the wild card
character (“p”) to restrict an exchange from being dialed in any area code.
For example, to prevent users from directly dialing the 976 exchange in any
area code, write 1 p p p 9 7 6.
NOTE:
On Form 6f (page 3), Disallowed List 7 contains factory set entries
(as shown in Table 4–2 above) and is the factory set disallowed list.
To change the entries in this list, cross out the entry and write the
new values in the space provided.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Page 4-53

3.

Write the extension numbers of the telephones that you want to assign to
the list in the Disallow to Ext. Nos. column (see Form 2a).

4.

Disallowed List Class-of-Restriction assignments apply to all remote
access users and cannot be assigned on an individual basis unless barrier
codes are used. If barrier codes are used, Class-of-Restriction is assigned
to individual barrier codes. Use Form 3a, Incoming Trunks: Remote
Access, if you planned Remote Access and want to restrict callers through
Disallowed Lists. For a private network environment, see the Network
Reference for planning Disallowed Lists needed to restrict calls across the
private network:
a.

!

On Form 3a (page 3), in the Class of Restriction without Barrier
Codes section, write the list numbers under the Disallowed List
Access heading for either or both tie and non-tie trunks.

SecurityAlert:
To help prevent toll fraud, barrier codes should always be required and
should also be set to the maximum length allowed.
b.

On all copies of Form 3a (page 4), Class of Restriction with Barrier
Codes, write the list numbers under the Disallowed List Access
heading for each barrier code.

Call Restriction Summary

4

After the individual telephone forms have been completed, Form 6g, Call
Restriction Assignments and Lists, can be used as a summary and telephone
programming aid for telephone calling restrictions as designated in this chapter.

Planning Form Instructions
On Form 6g:
1.

In the Ext. No. column, do one of the following:
■

Transfer the extension number from the individual telephone forms.

■

If copying from another extension, write the new extension number
and then, in the Copy From column, write the extension from which
calling restrictions for this extension will be copied.

2.

In the Restriction Type column, check the appropriate column: Out. for
Outward Restriction, Toll for Toll Restriction, or No Rest. for No Restriction.

3.

In the Allowed List No. and Disallowed List No. columns, write the
appropriate list numbers from Forms 6e and 6f, respectively.

4.

In the ARS Restriction Levels (FRL) column, write the Facility Restriction
Level (FRL) value noted in the ARS Restriction Level heading on Form 6g.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Page 4-54

4

Night Service

Use these instructions only if Night Service is used for after-hours telephone
operation. Otherwise, skip to the next section, “Labeling.” This section contains
instructions for selecting any combination of the following options for Night
Service:
■

Night Service with Group Assignment

■

Night Service with Outward Restriction

■

Night Service with Time Set

Night Service with Group Assignment

4

This section contains instructions for setting Night Service so that any call that
comes to the operator console while Night Service is in effect rings immediately at
each available telephone in a defined group and/or at a designated calling group.
Calls ring immediately even on lines/trunks set for Delay Ring or No Ring.
You can create up to eight Night Service groups and/or Night Service calling
groups, one for each operator. There is no limit to the number of telephones or
outside lines assigned to each Night Service group, and each telephone or
outside line can be assigned to more than one Night Service group.
A calling group can be the Night Service group for more than one operator, but
only one calling group is allowed for each operator.
A DID call directed to a calling group will not receive Night Service treatment.
Private network calls will receive Night Service treatment.

Planning Form Instructions
In each column on Form 9a, Night Service: Group Assignment, do the following:
1.

In the Operator Ext. No. space, write the extension number for the operator
whose calls are being answered (see Form 2a for the extension number).

2.

In the Trunk No. column, write the line/trunk number for each outside line
that is a member of the Night Service group (see Form 2c for the line/trunk
number).

3.

In the Ext. or Calling Group No. column, write the extension number for
each member of the Night Service group or for a calling group (see Form
2a for the extension number).

4.

In the User or Calling Group Name column, write each Night Service group
member’s name or the name of the calling group (see Form 2a for the
group number).

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Page 4-55

Night Service with Outward Restriction

4

This section contains instructions for setting Night Service so that only authorized
users can place non-emergency calls when Night Service is in effect. This
prevents unauthorized after-hours use of telephones.
Calls to non-local UDP extensions can be made even while Night Service
restricted.
Calls to non-emergency numbers do not go through unless a password is entered
first. You can include up to 10 telephone numbers on the Night Service
Emergency List. If a HotLine extension dials an outside number, that telephone
number should be on the Night Service Emergency List or the extension should
be on the Exclusion List. Each number can have a maximum of 12 digits.
Once you specify that a password is required, the password applies to all
telephones in the system when Night Service is activated at any operator position.
If users need to make after-hours calls and prefer not to enter a password, you
can set up an Exclusion List that exempts those extensions from the password
requirement. Extensions assigned to the Exclusion List keep the normal calling
restrictions, if any are assigned, when Night Service is in effect. However, these
extensions are not protected in any other way from unauthorized after-hours use.

Planning Form Instructions
On Form 9b, Night Service: Outward Restriction:
1.

!

The password must be 4 digits and can include the numbers 0–9 in any
combination. To keep the password private, record it on a separate paper
and not on the form.

SecurityAlert:
Additional steps must be taken to maintain security on ports (such as use of
Disallowed Lists, Outward Restriction, and so on). Refer to Appendix A,
“Customer Support Information” for more information.

2.

Write the numbers to be included in the Telephone No. list in the
Emergency Allowed List section.

3.

To exclude users from the password requirement, complete the Exclusion
List section.
a.

In the Ext. No. column, write the extension number for each
telephone (see Form 2a).

b.

In the Name column, write each user’s name (see Form 2a).

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Night Service with Time Set

Page 4-56

4

This section contains instructions for setting the system to automatically turn Night
Service on and off at the times and on the days of the week you specify. This
ensures that after-hours calls are handled properly even if an operator forgets to
turn on Night Service. Operators can still override the timer and turn Night Service
on or off manually. The feature can also be deactivated through system
programming for special conditions, such as a midweek holiday.

4

Planning Form Instructions
On Form 9c, Night Service: Time Set, write the time of day you want Night Service
turned on (Start Time) and off (Stop Time) for each day of the week. Use 24-hour
numbering, called military time; for example, 5:30 p.m. is 1730 in 24-hour
numbering.
If Night Service is to remain on throughout the day, for example on Sunday, do not
enter on and off times.

Night Service with Coverage Control

4

As of Release 4.1, Night Service Coverage Control automatically controls the
status of programmed VMS Coverage Off buttons.
When the Coverage Control option is enabled, a transition into Night Service
(either by pressing a Night Service button or automatically by the Time Set option)
automatically deactivates the VMS Coverage Off (Release 2.0 or later) buttons
(LED is off) and allows outside calls to go to VMS Coverage at night. When the
system is taken out of Night Service (either by pressing a Night Service button or
automatically by the Time Set option), programmed VMS Coverage Off buttons
are activated (LED is on) and outside calls are prevented from going to VMS
Coverage during the day.
NOTE:
Private network calls act like outside calls and do not go to voice mail when
VMS Coverage Off is activated.
When the Coverage control option is disabled, Night Service status has no effect
on programmed VMS Coverage Off buttons.

Planning Form Instructions
In the Coverage Control section of Form 9c, Night Service: Options, do one of the
following:
■

To keep the factory-setting of disabled, check the Disabled box.

■

To change the factory-setting and enable the Coverage Control option,
check the Enabled box.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Page 4-57

4

Labeling

Labeling enhances the capability of display telephones used with the system.
The following types of labels appear on display telephones:
■

Extensions and calling groups

■

Posted Messages

■

System Directory/System Speed Dial

Labels for extensions are described in Chapter 2, “Control Unit Configuration,”
labels for lines/trunks are described in Chapter 4, “Features,” and labels for calling
groups are described earlier in this chapter.
This section contains instructions for assigning labels for Posted Message and
System Directory/System Speed Dial.

4

Posted Message

This section contains instructions for allowing users to post a message telling
callers who have display telephones why they cannot answer.
There can be as many as 20 messages. Messages 1 through 10, shown on Form
10a, are already programmed in the system, and 10 more can be added, for a
total of 20. In a Release 2.0 or later system, Messages 2 through 9 can be
changed. In a Release 1.0 or 1.1 system, all 10 of the preprogrammed messages
can be changed.

Planning Form Instructions
Posted messages can contain as many as 16 characters, including capital letters,
numbers, ampersand (&), dash (-), space, colon (:), asterisk (*), and pound
sign (#).
On Form 10a, Label Form: Posted Message, do one of the following:
■

To add posted messages for Messages 11 through 20 (for example,
CUSTM MSG 11) write each new message next to its message number
(11 through 20) in the Revised Message column.

■

To change existing messages, cross out the message and write the new
message in the Revised Message column.
NOTE:
In Release 2.0 and later, Message 1, DO NOT DISTURB, cannot be
changed.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Page 4-58

4

System Speed Dial

This section contains instructions for designating systemwide, frequently used
numbers. You can assign and store up to 130 three-digit System Speed Dial
codes. To call one of these numbers, a caller presses the Feature button and
dials a three-digit code.
Assign System Speed Dial codes to telephone numbers that shouldn’t be
displayed on telephones, such as access codes. Entries that do not display are
referred to as Marked System Speed Dial entries. You can also assign labels to
the System Speed Dial codes. These labels are listed in the System Directory so
that MLX telephone users can search for them and dial System Speed Dial
numbers with the touch of a button.

Planning Form Instructions
NOTE:
As a visual aid to distinguish lines during programming, every fourth line on
the form is shaded.
1.

Review the analysis of question 9 on the Employee Communication
Survey.

2.

On Form 10b, System Speed Dial:
a.

Write the label (maximum: 11 characters) to be displayed for the
number in the Name column.

b.

Write each telephone number (maximum: 40 digits) in the
Telephone Number column.

c.

To display no number (Marked System Speed Dial entry), check the
No box in the Display column (the factory setting is Yes).
NOTES:
1. Marked System Speed Dial entries (entries that do not display)
are not affected by the Second Dial Tone Timer setting. If the
Central Office does not immediately supply dial tone when a star
code is entered and a Marked System Speed Dial entry uses
star codes, then the appropriate number of pauses (each 1.5
seconds) must be programmed in the entry following each star
code.
2. When a Marked System Speed Dial number (the dialed number
is suppressed from the display) is used to dial a number, calling
restrictions (such as toll or outward restrictions, or Allowed and
Disallowed Lists) assigned to that extension are overridden.
When an unmarked System Speed Dial or a Personal Speed
Dial number is used to dial a restricted number, the call cannot
be completed unless the number is on the Allowed List for that
extension.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Automatic Route Selection
(Hybrid/PBX Mode Only)

!

Page 4-59

4

SecurityAlert:
ARS should always be used for the best security protection.

This section contains instructions for using Automatic Route Selection (ARS) to
allow the most cost-effective use of lines/trunks connected to the system, which
can mean significant savings for the customer’s business. Routing calls efficiently
is especially important when the business has several different types of
lines/trunks, such as local, WATS, FX, or tie, or uses more than one long-distance
company. If the system is pooled, you can use ARS to specify which trunk pool
should be used for each call, based on the telephone number the caller dials.
ARS tables can be used to route calls across a private network and out to the
PSTN using a remote system’s trunks. See Network Reference for information on
how to set up ARS for the private network.
With ARS, users must dial a  before dialing any 10-digit toll number, even if the
local telephone company does not require a toll-call prefix.
You can define up to 16 ARS tables, each divided into two subpatterns based on
the time of day. Four additional tables are factory-set and are designed to save
programming time.
In this section, you define a set of ARS tables. This set includes a list of area
codes and exchanges associated with each table, the preferred and alternate
routes (if any) for each subpattern, and the Facility Restriction Level (FRL) for
each route. As the system manager becomes more familiar with the calling
patterns of the company and with the intricacies of ARS, he or she may want to
change these patterns to suit the particular installation.

ARS Worksheet

4

This section contains instructions for completing the ARS worksheet (Form 3e) to
decide how to best route calls.
For each trunk pool, you identify the trunk pool number, type of trunk (local, FX,
regional WATS, and so on), whether the calls are toll or local calls, and the
number of area codes or exchanges the pool should serve.
When placing a toll call using ARS, callers dial one of the following:
■

11 Digits. 1 + 3 (area code) + 3 (exchange) + 4 (last 4 digits of the number)

■

8 Digits. 1 + 3 (exchange) + 4 (last 4 digits of the number)

■

7 Digits. 3 (exchange) + 4 (last 4 digits of the number)

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Issue 1
August 1998
Page 4-60

Keep in mind that for 10-digit toll calls, callers must dial 1 before dialing the area
code, even if they don’t normally need to dial a prefix to make a toll call.
Figure 4–1 provides a sample of a completed ARS worksheet.

Planning Form Instructions
1.

Review Form 2c, System Numbering: Line/Trunk Jacks, for the types of
lines/trunks available.

2.

Record the number of exchanges in the local calling area in the blank at the
top of Form 3e, Automatic Route Selection Worksheet. If you are not sure
how many exchanges there are, consult the telephone directory.

3.

Enter the number of each of the trunk pools (factory setting is 70 and
890−899) in the Trunk Pool No. column.
Some trunk pools, such as in-state WATS trunk pools, can be used for both
toll and local calls. (Note that with ARS a local call is any call that doesn’t
require dialing a .)
If you expect people to use a particular trunk pool for both toll and local
calls, enter the number of that trunk pool in the worksheet twice, and
note the reason.

4.

For each trunk pool number entered:
a.

In the Trunk Type column, record the type of trunk (local, FX,
network, regional WATS, and so on) that is in the pool.

b.

Under the Type of Dial heading, check the appropriate column
(Local, Toll, or Network) for the type of call that should be dialed on
each trunk pool:

c.

■

Toll. Any call that has a series of digits beginning with a 1,
followed by an exchange or area code.

■

Local. Any call that is not a toll call. This includes the
seven-digit dialed numbers required in most areas.

■

Network. Any call that will be routed to a non-local switch.

Enter the total number of different area codes or exchanges that the
pool should serve in the Number of Area Codes or Exchanges for
which Trunk Pool Is Used column.
NOTE:
If you do not know the exact number of exchanges or area
codes, write a note such as All area codes in the U.S. except
the 15 served by the regional WATS lines/trunks. Keep in
mind that you are recording how many different area codes or
exchanges the pool should access, not the area codes or
exchanges themselves. This step helps identify the preferred
trunk pools for toll and local calls. (Preferred pools are the
trunk pools in which the system places each call unless a
different route has been specified for that particular type of
call.)

4

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

5.

Issue 1
August 1998
Page 4-61

Under the Preferred Trunk Pools heading:
a.

Determine which of the toll trunk pools is used for calls to the
greatest number of different area codes. Write the number of that
trunk pool in the space next to For toll calls (Table 17). Table 17 is
explained later in this chapter.

b.

Determine which of the local trunk pools is used for calls to the
greatest number of different exchanges. Write the number of that
trunk pool in the space next to For local calls (Table 18). Table 18 is
explained later in this chapter.

Figure 4–1 shows the completed Automatic Route Selection Worksheet for the
fictitious company, McHale and Associates of Denver, Colorado (area code: 303).
McHale has a local trunk pool, an in-state WATS pool, and a cross-country WATS
pool. Because Colorado has three area codes (303, 719, and 970), the in-state
WATS line/trunk can be used for both toll and local calls. Figure 4–1 shows an
example of two entries (for the 303 and 719 area codes) for Pool 890 on the
worksheet.
The cross-country WATS trunk pool serves the greatest number of different area
codes, every area code in the country except the two in Colorado. Therefore, it is
the preferred trunk pool for toll calls.
The in-state WATS trunk pool serves the greatest number of different exchanges.
It is the preferred trunk pool for calls to every exchange in area code 303, except
the 20 exchanges in the local calling area. Therefore, it is the preferred trunk pool
for local calls and some of these are toll calls.
If the local switch will use PSTN lines on a remote switch, see the Network
Reference for the steps necessary to implement this.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Page 4-62

Automatic Route Selection Worksheet*

Number of exchanges in the calling area _______________
Trunk Pool No.

Trunk Type

70
890 (for 303)

Local
in-state WATS

890 (for 719)
891

in-state WATS
Cross-Co. WATS

Preferred Trunk Pools
For toll calls (Table 17)
For local calls (Table 18)

Figure 4–1.

Toll

Type of Dial
Local Network

Number of Area Codes, Exchanges,
or Network Destinations for which
Trunk Pool is Used

20 Exchanges in local area
All exchanges in area code 303
minus 20 in local calling area
1 area code
All area codes in U.S.
except 303 and 719

891
70

Completed ARS Worksheet Automatic Route Selection Tables

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Issue 1
August 1998
Page 4-63

This section contains instructions for using the information you recorded on the
worksheet to prepare the ARS tables. The system can have as many as 20 ARS
tables — 16 are programmed and 4 are factory set (Dial 0, Special Number,
Default Local, and Default Toll tables). Of the 16 programmable tables, each may
contain one of the following types of information:
■

6-Digit Tables. If the cost of calls to another area code varies according to
the exchange, this table can be used to route calls on different trunk pools,
depending on both the area code and the exchange. An area code is the
first entry, and the remaining 99 entries are exchanges within the area
code. The system scans the first six digits of the user-dialed number (area
code and exchange) to route the call.

■

Area Code Tables. These tables are lists of 3-digit area codes. Area code
tables are useful if just one type of line/trunk is used for all calls to each
area code on the list.

■

Local Exchange Tables. These tables list 3-digit exchanges within the
local area code. They can be used to route calls over in-state WATS.

■

1+7 Tables. These tables contain a list of exchanges within the local area
code that require dialing a  but not an area code before the 7 digits.

Because ARS routing requires care and planning, the instructions for filling out the
planning forms are presented a few steps at a time with examples of completed
forms shown after each group of steps. The instructions begin with the
programmable tables (1 through 16) and introduce the factory-set tables midway
through the process.

Planning Form Instructions
Complete Form 3f for each trunk pool listed on the ARS worksheet (Form 3e).
NOTE:
The digits before the blank lines in the Area Code/Exchanges section
represent the table entry number used during programming.
On each copy of Form 3f:
1.

Write the table number in the Table No. space (maximum 16). Start with the
number 1 and proceed sequentially.

2.

Check the appropriate box under the Type of Table heading: 6-Digit, Area
Code, Exchange, or 1+7.

4

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

3.

Issue 1
August 1998
Page 4-64

Do one of the following:
■

If this is not a 1+7 table, skip to Step 4.

■

If this is a 1+7 table, do one of the following:
— If users do not need to dial a  to reach numbers within their
own area code, check the not within area code box (factory
setting).
— If users need to dial a  to reach numbers within their own
area code, check the within area code box.

4.

Complete the Area Code/Exchanges section by doing one of the following:
■

If this is a 6-digit table, write the area code on the blank line next to
entry 001. Then write each exchange to be called in that area code.
Use the numbered lines, beginning with entry 002.
Up to 99 exchanges can be listed in any order. If you need to list
another area code with exchanges, prepare another 6-digit table.

■

If this is an Area Code, Exchange, or 1+7 table, write the area codes
or exchanges on the numbered lines, beginning with entry 001.
Up to 100 area codes or exchanges can be listed in any order, but
area codes and exchanges cannot be on the same table.

Example 1. If a business plans to use Table 1 to route calls to exchanges 333,
444, and 523 in area code 816, the upper section of the completed Form 3f will
look similar to Figure 4–2.
Example 2. If the business plans to use Table 7 to route calls to the northeastern
(band 1) WATS lines/trunks as entries 001 through 015, the upper section of the
completed form will look similar to the one shown in Figure 4–3.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Page 4-65

Automatic Route Selection Tables*
Maximum: 16 Tables. (Make a copy for each table.)

1
Table No. __________
Type of Table
❑ 6-Digit
❑ Area Code
❑ Exchange
❑ 1 + 7, dialing from
❑ within area code
❑ not within area code ✦
Area Code/Exchanges
816
001
021
002 333
022

041
042

061
062

081
082

023
024
025

043
044
045

063
064
065

083
084
085

006
007

026
027

046
047

066
067

086
087

008
009
010

028
029
030

048
049
050

068
069
070

088
089
090

011
012

031
032

051
052

071
072

091
092

013
014
015

033
034
035

053
054
055

073
074

093

016
017

036
037

003
004
005

444
523

018
019

Figure 4–2.

Example 1: Form 3f, 6-Digit Table

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Page 4-66

Form 3f
Automatic Route Selection Tables*
Maximum: 16 Tables. (Make a copy for each table.)

7
Table No. __________
Type of Table
❑ 6-Digit
❑ Area Code
❑ Exchange
❑ 1 + 7, dialing from
❑ within area code
❑ not within area code ✦
Area Code/Exchanges
413
001
021
617
002
022
003
004
005
006
007
008
009
010
011
012
013
014
015

203
508
401
516
518
914
717
201
603
207
215
802
609

016
017

041
042

061
062

081
082

023
024
025

043
044
045

063
064
065

083
084
085

026
027

046
047

066
067

086
087

028
029
030

048
049
050

068
069
070

088
089
090

031
032

051
052

071
072

091
092

033
034
035

053
054
055

073
074

093

036
037

018
019

Figure 4–3.

Subpatterns

Example 2: Form 3f, Area Code Table

4

For each table (1 through 16, and factory-set Tables 17 and 18), you can select
two subpatterns (A and B) that specify routes to be used at different times. You
can specify up to six routes for each subpattern. For example, you may want calls
to certain area codes routed over WATS lines/trunks during the day; after 11 p.m.,
when toll rates are less expensive on basic lines/trunks, you may want the calls
routed over the main pool.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Issue 1
August 1998
Page 4-67

For each of the 12 routes (six for each subpattern), you can specify a Facility
Restriction Level (FRL). The FRL is used to refine the route selection process still
further. Each route is assigned an FRL from 0 through 6 (6 is the most restricted).
Each telephone is also assigned an FRL from 0 through 6 (0 is the most
restricted). Callers (extension or remote access barrier code/trunk) can use the
route only if their FRL is equal to or greater than that specified for the route. You
assign a value of 0 to the route if you want all users to access the route, or 1
through 6 to restrict calling for the route to specific users only.
The form for a typical Area Code Table, illustrated in Figure 4–4, shows a table to
route calls to the 13 area codes served by the northeastern (band 1) WATS lines
beginning at 8 a.m. with no restrictions. The number of the northeastern WATS
pool, 891, is on the first line in the Subpattern A section. The time, 8:00 a.m., is in
the Time of Day space, and an FRL of 0 indicates no restrictions. The 11 p.m. in
the Time of Day space for Subpattern B and Pool 70 in the Pool column indicates
that calls to these area codes are to be routed over the main pool after 11 p.m.

Planning Form Instructions
In the Subpattern sections on Form 3f and Form 3g:
1.

To direct calls differently according to time of day, write a starting time for
each subpattern in the Time of Day space (for example, 8 a.m.).

2.

To complete the Pool column for each subpattern, write the number of the
preferred trunk pool next to the number 1. This is the pool to which calls to
the area codes or exchanges listed in the Area Code/Exchanges section of
this form should be directed.
If you want to designate a backup pool in case all the lines/trunks in the first
choice pool are busy, write the number of the backup trunk pool next to the
number 2, and so on.

3.

To complete the FRL column, enter a value of 0 through 6. Assign a value
of 0 if you want all users to access the route, or 1 through 6 to restrict
calling for the route to specific users only. For all except the Default Local
Table, the factory setting is 3. The Default Local Table factory setting is 2.

4.

If extra digits at the beginning of the dialed number may be required for the
system to place a call on a particular pool, enter the digits (0 through 9) in
the same row as the pool number, in the column under the Other Digits
heading. (See the Other Digits example below, in Figure 4–5.)

These special access or account codes can range from a single digit, such as 9,
to a maximum of 20 digits.
Because calls to the 15 area codes shown on Figure 4–4 should be placed on the
cross-country WATS lines/trunks when all the northeastern WATS lines/trunks are
busy, the number of the cross-country WATS pool, 890, is used in both cases. An
FRL of 4 is assigned to restrict some users from using cross-country WATS
lines/trunks.

4

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Page 4-68

Example: If a business uses a different long-distance company for calls to nine
area codes in Canada, accessing the alternate long-distance company lines
requires getting a local line and dialing seven digits. The completed form for the
Area Code Table that routes these calls to the alternate long-distance company
lines is shown in Figure 4–5.

Form 3f
Automatic Route Selection Tables*
Maximum: 16 Tables. (Make a copy for each table.)

2
Table No. __________
Type of Table
❑ 6-Digit
❑ Area Code
❑ Exchange
❑ 1 + 7, dialing from
❑ within area code
❑ not within area code ✦
Area Code/Exchanges
413
001
021
617
002
022
003
004
005
006
007
008
009
010
011

203
508
401
516
518
914
717
201
603

041
042

061
062

081
082

023
024
025

043
044

063
064
065

083
084
085

026
027

046
047

045

028
029

066

057
058
059
060

039
040

8:00 am
Subpattern A Time of Day _________________
FRL
(3 ✦)‡
______
0
4
______
______

Other
Digits
_______
_______
_______

Absorb
1 _______
2 _______
3 _______

4 _____

______

_______

4 _______ _____

5 _____
6 _____

______
______

_______
_______

5 _______ _____
6 _______ _____

✦ Factory Setting
* Hybrid/PBX mode only
†
Select Voice only, Data only, or Both.
‡
Local Tables Default FRL is 2.

Figure 4–4.

11:00 pm
Subpattern B Time of Day _________________
†

Pool
1 _____
891
890
2 _____
3 _____

Subpattern Example

095
096
097
098
099
100

076
077
078
079
080

Call Type
(Both ✦)
_____
V
V
_____
_____

Pool
1 _____
70
890
2 _____
3 _____
4 _____

FRL
(3 ✦)‡
______
0
4
______
______
______

Other
Digits
_______
_______
_______
_______

Call Type†
Absorb
(Both ✦)
1 _______ _____
V
V
2 _______ _____
3 _______ _____
4 _______ _____

5 _____

______

_______

5 _______ _____

6 _____

______

_______

6 _______ _____

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Page 4-69

Form 3f
Automatic Route Selection Tables*
Maximum: 16 Tables. (Make a copy for each table.)

3
Table No. __________
Type of Table
❑ 6-Digit
❑ Area Code
❑ Exchange
❑ 1 + 7, dialing from
❑ within area code
❑ not within area code ✦
Area Code/Exchanges
001 604
021
002 403
022
003
004
005
006
007
008
009
010

306
204
807
705
519
416
613

041
042

061
062

081
082

023
024
025

043
044
045

063
064

083
084

026
027

046

028

065

057
058
059
060

039
040

Subpattern A Time of Day _________________
Pool
1 _____
70
2 _____
3 _____

FRL
(3 ✦)‡
______
______
______

Other
Digits
_______
905012
_______
_______

4 _____

______

_______

5 _____
6 _____

______
______

_______
_______

Subpattern B Time of Day _________________
Pool
1 _____
2 _____
3 _____

FRL
(3 ✦)‡
______
______
______

Other
Digits
_______
_______
_______

Absorb
1 _______
2 _______
3 _______

4 _______ _____

4 _____

______

_______

4 _______ _____

5 _______ _____
6 _______ _____

5 _____
6 _____

______
______

_______
_______

5 _______ _____
6 _______ _____

†

Absorb
1 _______
2 _______
3 _______

✦ Factory Setting
* Hybrid/PBX mode only
†
Select Voice only, Data only, or Both.
‡
Local Tables Default FRL is 2.

Figure 4–5.

095
096
097
098
099
100

076
077
078
079
080

Other Digits Example

Call Type
(Both ✦)
_____
V
_____
_____

Call Type†
(Both ✦)
_____
_____
_____

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

5.

Issue 1
August 1998
Page 4-70

If the system must absorb certain leading digits dialed by users to place
calls on a particular pool, enter a number in the same row as the pool
number, in the Absorb column.
Use the number 0 if you do not want absorption. Assign a value of 1
through 11 according to the number of digits you want absorbed, starting
with the first digit dialed.

Example: If a company has FX lines/trunks for the 686 exchange in the 901 area
code and wants to allow people to dial those calls the same way they dial toll calls
to other area codes, an absorption number of 4 is assigned to the FX trunk pool,
Pool 893. The completed form for the 6-Digit Table that routes calls to the FX
trunk pool is shown in Figure 4–6.
After ARS is programmed, people in the company illustrated in Figure 4–6 dial
 -;;;; to make these calls. The system absorbs the leading 1 and the
area code and dials only the seven-digit number to place these calls on one of the
FX lines/trunks.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Page 4-71

Form 3f
Automatic Route Selection Tables*
Maximum: 16 Tables. (Make a copy for each table.)

4
Table No. __________
Type of Table
❑ 6-Digit
❑ Area Code
❑ Exchange
❑ 1 + 7, dialing from
❑ within area code
❑ not within area code ✦
Area Code/Exchanges
901
001
021
002 686
022

041
042

061
062

081
082

043
044
045

063
064

083
084

005

023
024
025

006
007

026
027

046

008
009
010

028

003
004

065

057
058
059
060

039
040

Subpattern A Time of Day _________________
Pool
1 _____
893
2 _____
3 _____

FRL
(3 ✦)‡
______
______
______

Other
Digits
_______
_______
_______

4 _____

______

_______

5 _____
6 _____

______
______

_______
_______

Subpattern B Time of Day _________________
Pool
1 _____
2 _____
3 _____

FRL
(3 ✦)‡
______
______
______

Other
Digits
_______
_______
_______

Absorb
1 _______
2 _______
3 _______

4 _______ _____

4 _____

______

_______

4 _______ _____

5 _______ _____
6 _______ _____

5 _____
6 _____

______
______

_______
_______

5 _______ _____
6 _______ _____

†

Absorb
1 _______
4
2 _______
3 _______

Call Type
(Both ✦)
_____
V
_____
_____

✦ Factory Setting
* Hybrid/PBX mode only
†
Select Voice only, Data only, or Both.
‡
Local Tables Default FRL is 2.

Figure 4–6.

095
096
097
098
099
100

076
077
078
079
080

Digit Absorption Example

Call Type†
(Both ✦)
_____
_____
_____

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

6.

Issue 1
August 1998
Page 4-72

To complete the Call Type column, enter one of the following:
■

For voice only calls, write V.

■

For data only calls, write D.

■

For both voice and data calls, write Both.
NOTE:
Pools should be labeled as Voice unless they can support digital
data. Both can be used for BRI, PRI, and private network PRI pools.
Data can be used for T1 Switched 56 pools, and to reserve lines for
data in BRI, PRI, and private network PRI pools.

7.

If you have worked on only one of your planned non-default tables,
complete all copies of Form 3f. Repeat Steps 1 through 6 for each table
(Tables 1 through 16) that you need.

8.

If you have not completed the factory-set tables, do so now:
a.

For Tables 17 (Default Toll) and 18 (Default Local), repeat Steps 1
through 6 to complete the subpattern and pool routing sections.

b.

For the Dial 0 table (Table 19) complete the Pool routing, Facility
Restriction Level (FRL) and Other Digits entries following Steps 2
through 4. If the switch is part of a private network, and the private
network needs to use the Dial 0 table, see the Network Reference
for information.

!

WARNING:
In the next step, assigning a restrictive FRL could impair the ability to
dial 911.

c.

If users need to dial an access code to call the special numbers 411,
611, 811, and 911, record that code on the Special Number Table
20), under the Other Digits heading. Assign the FRL as shown in
Step 3. If the switch is part of a private network, and the private
network needs to use the Special Numbers table, see the Network
Reference for information.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

9.

Issue 1
August 1998
Page 4-73

If restricting extensions, private network calls, and remote access users
from specific routes, locate Form 6g, Call Restriction Assignments and
Lists:
a.

Under the ARS Restriction Level heading on each telephone form,
write the value (0 to 6) you want to assign.

b.

Under the ARS Restriction Level heading on pages 3 and 4 of Form
3a, check the value (0 to 6) you want to assign.

Extension and Remote Access FRL values must be equal to or greater
than the FRL value assigned to routes in order for users to access those
routes. A value of 0 is the most restrictive, and a value of 6 is the least
restrictive. The factory-set FRL value assigned to extensions is 3.
To restrict an extension from specific routes, assign an FRL value to the
extension that is lower than the route’s value.
For example, if you want to limit a user from making calls on pools with
special-use lines/trunks such as WATS, assign a value of 0. If you want a
telephone used by a top executive to have unlimited use of any ARS route,
assign a value of 6.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

4

Features
System Features

Issue 1
August 1998
Page 4-74

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Issue 1
August 1998

Data Communications

Page 5-1

5

Data Communications

5

In addition to voice communications capabilities, the system also supports data
and video communications to enable users to send or receive data, or establish
group or personal video conferences.
NOTE:
To configure the switch to support data communications across a private
network, see the Network Reference for information.
Planning for data and video communications consists of the following tasks:
1.

Planning how the data and/or video equipment connects to extension jacks
on the control unit. This depends on the type of data stations or video
systems.

2.

Creating modem/ISDN terminal adapter pools (pairs of modems and ISDN
terminal adapters) to enable calls between the two types of data stations:
modem data stations and ISDN terminal adapter data stations.

3.

Assigning lines/trunks to data stations and video systems.

4.

Assigning features to data stations.

5.

Creating data hunt groups (DHGs), that is, data calling groups, if there are
modem/ISDN terminal adapter pools with more than one data
communications equipment pair (a modem and an ISDN terminal adapter),
or to designate a group of either modems or ISDN terminal adapters to
receive calls to communicate with a local host computer or local area
network (LAN) workstation.
NOTE:
Modem/ISDN terminal adapter pools are not described in this book.
For information see application note, MERLIN LEGEND
Communications System Modem Pooling.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Issue 1
August 1998

Data Communications

Page 5-2

6.

Configuring MLX jacks for 2B Data (2 B-channel) connectivity. This allows
video systems to use both B-channels on a single MLX jack to establish
high-speed video connections at data rates of up to 128-kbps.
NOTE:
For additional information on 2B Data/Video and for information on
connecting video systems to the MERLIN LEGEND system, refer to
the Data and Video Reference.
For information on ordering desktop video equipment, refer to
Marketing Announcement Letter GBCS-96-05-001 Multi-Vendor
Desktop Videoconferencing Offer.
When using the 008 MLX or 408 GS/LS-MLX module for data or
video, you must use Version 28 of the module.

Following an explanation of the terminology used in this chapter and an overview
of data communications, this chapter contains instructions for planning data and
video communications. Some procedures involve making additional entries on the
forms already completed earlier in this guide; others involve filling out data forms
as described in “Planning Overview,” later in this chapter.
Instructions for using the data and video communications capabilities are
contained in the Data and Video Reference.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Terminology

Page 5-3

5

Terminology
The following terms are used in this chapter:
■

Data Station. A hardware configuration used to send and receive data
(and sometimes voice signals, depending on the equipment). The
configuration includes data terminal equipment (DTE) for input and output
of data, and data communications equipment (DCE) to enable the
transmission of data over digital or analog telephone lines and trunks.
There are two types of data stations:
— Modem Data Station. Connects to the control unit through an
analog extension jack or a T/R jack and requires a modem. Analog
data stations can support analog data and analog voice, analog
data only, or analog data and MLX voice.
— ISDN Terminal Adapter Data Station. Connects to the control unit
through an MLX extension jack and requires an ISDN terminal
adapter (such as the Ascend Pipeline 25PX or 50). ISDN terminal
adapter data stations can support ISDN terminal adapter data and
MLX voice or ISDN terminal adapter data only.

■

Data Terminal Equipment (DTE). Data station equipment, for example, a
PC, host computer, or LAN workstation, from which data is input and/or
output. DTE, which can also be referred to as a data terminal, uses data
communications equipment (DCE) to transmit and receive the digital
signals it requires.

■

Data Communications Equipment (DCE). Data station equipment that
enables the transmission of data over digital or analog telephone lines and
trunks. DTE requires DCE as follows:
— Modem. A type of data communications equipment that converts
the DTE’s outgoing digital signals into analog signals for
transmission over regular (analog) telephone company lines.
Another modem at the receiving data station converts the analog
signals back into digital signals for reception by the DTE (for
example, a PC). An analog data station uses a modem as its DCE.
— ISDN Terminal Adapter. A type of data communications equipment
that transmits digital signals over digital telephone company
facilities, for example, PRI. A digital data station uses an ISDN
terminal adapter (such as the Ascend Pipeline 25PX or 50) as its
DCE.

■

Data Terminal. Data station equipment (for example, a PC, host computer,
LAN workstation, Group IV fax machine, or a group video conferencing
installation) from which data is input and/or output. A data terminal uses
data communications equipment (DCE) to transmit and receive the digital
signals it requires.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Terminology

Issue 1
August 1998
Page 5-4

■

Modem/ISDN Terminal Adapter Pool. A special type of hardware
configuration that combines one or more pairs of DCEs to enable
communication between modems and ISDN terminal adapter data stations.
A pair consists of one modem and one ISDN terminal adapter.
Modem/ISDN terminal adapter pools are set up in one of two ways
depending on the type of data station being used to send data:
analog-to-digital or digital-to-analog. For more information about these
pools, see application note, MERLIN LEGEND Communications System
Modem Pooling.

■

Data Hunt Group (DHG). A data calling group typically used to distribute
calls to modem/ISDN terminal adapter pools that have more than one pair
of DCEs. For more information about DHGs, see the application note,
MERLIN LEGEND Communications System Modem Pooling.

■

Video System. Equipment that allows desktop or group video
conferencing. This equipment connects either directly or through an ISDN
terminal adapter to an MLX jack on the MERLIN LEGEND system. If the
MLX port is programmed as a 2B Data port, the video systems can use
both of the B-channels assigned to the MLX port to provide video. Many
video applications also support data sharing and/or transfer.
NOTE:
If the video system is connected to the MLX jack through an ISDN
terminal adapter, unless the ISDN terminal adapter itself supports 2B
Data communications, it is recommended that the MLX port not be
programmed as a 2B Data port.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
About Data and Video Communications

About Data and Video
Communications

Page 5-5

5

This section provides a high-level overview of the system’s data and video
communications capabilities, followed by more detailed information about some of
the equipment and concepts introduced in this overview.

5

Connectivity

Data communications connectivity enables the system to share resources, as well
as to establish and manage connections between computers and other data
devices.
Video communications connectivity enables users to conduct personal or group
video conferences and to share data and applications (also known as Video
Collaboration).
The system control unit (hardware and software) in conjunction with other external
hardware devices provides data and video connectivity for the following:
■

On-premises analog data stations

■

Connection to off-premises data stations by way of an analog line/trunk
(GS, LS, Tie, or DID), by way of a dedicated analog line/trunk, or by way of
a DS1 Digital Service Link providing emulated GS, LS, Tie or DID trunks

■

On-premises ISDN terminal adapter data stations

■

Connection to off-premises digital data stations by way of a PRI, NI-1 BRI,
or T1 Switched 56 facility (including T1-Tie trunks using T1 Switched 56
service)

■

Connections between two similar types of data stations

■

Connection between a digital data station (on a B-channel) and an analog
data station by way of 2-stage dialing through a modem/ISDN terminal
adapter pool. This configuration is not described in this book; see
application note, MERLIN LEGEND Communications System Modem
Pooling.

■

On-premises host computer access

■

Local area network (LAN) access by way of a modem or ISDN terminal
adapter connected to an RS-232 port on a workstation on the LAN

■

On- and Off-premises personal or group video systems by way of a digital
PRI, NI-1 BRI, or T1 Switched 56 facility (including T1-Tie trunks using T1
Switched 56 service)

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
About Data and Video Communications

Page 5-6

5

Data Stations

A data station is a hardware configuration used to send and receive data (and/or
voice, depending on the equipment). The configuration must include two main
components: data terminal equipment (DTE) for input or output of data, along with
data communication equipment (DCE) to enable the transmission of data over
analog or digital lines/trunks. Depending on the station configuration, it may or
may not include a telephone, either analog or an MLX telephone.
The DTE is usually a PC, but can be a host computer, a LAN workstation, a
printer, an optical scanner, or a video system or other equipment used for data
input and/or output.
The DCE, which is either a modem or an ISDN terminal adapter (such as the
Ascend Pipeline 25PX or 50), allows data from the DTE to be transmitted over
digital or analog telephone lines/trunks. The DCE, which has capabilities similar to
a telephone, also may make the data call, maintain the connection, and terminate
the data call.
NOTE:
The DCE and DTE may have hardware and/or software options that can be
set for transferring and receiving data, such as parity and bit rate. For more
information, refer to the DTE and DCE documentation for configuration
compatibility requirements, options, and guidelines for changing options.
There are two types of data stations:
■

Modem Data Station. This type of data station sends and receives analog
data. It includes a modem as its DCE and is connected to an analog
extension jack or T/R jack on the control unit.

■

ISDN Terminal Adapter Data Station. This type of data station sends and
receives digital data. It includes an ISDN terminal adapter as its DCE and
is connected to a digital extension jack (MLX port) on the control unit.

Within each type, there are several configurations, depending on the station’s
capabilities (for example, voice and data or data only) and, therefore, what
equipment is involved and what type of module it connects to on the control unit.
This section describes each type of data station and the configurations supported
within each type.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
About Data and Video Communications

Modem Data Stations

Page 5-7

5

A modem data station uses a modem as its DCE to send and receive data.
The modem converts digital signals from the DTE at the originating station into
analog signals so the data can be transmitted over analog telephone lines/trunks.
At the receiving station, the modem converts the analog signals back to digital
signals so the DTE at that end can accept them. A modem may provide dialing
and answering capabilities for a modem data station; if not, a telephone can be
connected to dial out.
NOTE:
If an analog multiline telephone is connected to the modem data station, the
telephone and data station can be used at the same time. A voice call can
be made or received while a data call is in progress. A data call cannot be
made or received while a voice call is in progress.
A modem data station can be used to make analog data calls either over the
telephone company network or to a data station inside the system.
The interface for a modem data station is the tip/ring (T/R) interface provided by
one of the following:
■

A General-Purpose Adapter (GPA), connected to an analog multiline
telephone

■

A port on a T/R module (012 T/R, 016 T/R, or 008 OPT)

■

A Multi-Function Module (MFM) adjunct on an MLX telephone

There are different types of modem data stations, depending on the data station
capabilities:
■

Modem voice and analog data (analog voice-and-data)

■

Modem data only

■

Modem data and MLX voice

Each of these use different equipment as described in this section.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
About Data and Video Communications

Page 5-8

5

Analog Voice and Modem Data

This type of modem data station includes an analog multiline telephone, a
modem, and a DTE (a data terminal or PC) (see Figure 5–1). The modem
connects to the control unit through the T/R interface of a General-Purpose
Adapter (GPA). The telephone connects to the system through an analog port on
the control unit.
The port configuration requires two adjacent odd/even extension jacks on a 408,
408 GS/LS, or 008 module in the control unit. The even jack is for voice and the
odd jack is for data. The bridging adapter joins the odd/even jack pair for
connection to the analog multiline telephone. The telephone provides the dialing
capability for the data station.

Data Station
DTE

MERLIN
LEGEND
Control
Unit

DCE

Optical
Scanner
Fax

Digital
Signal

Analog
Signal
MODEM

Analog Extension
Jacks (2)

PC/Terminal
GPA
Host
Computer

Figure 5–1.

Analog Voice and Modem Data

Analog
Multiline
Telephone

MLX
Extension Jack

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
About Data and Video Communications

Page 5-9

5

Modem Data-Only

This type of modem data station includes only DTE and a modem (see
Figure 5–2). The modem connects to the control unit through an analog port on a
T/R module. If the modem does not provide dialing capability, a single-line
telephone can be connected to it to provide dial-out capability; however, the data
station and the telephone cannot be used simultaneously.

Data Station
DTE

MERLIN
LEGEND
Control
Unit

DCE

Optical
Scanner
Fax

Digital
Signal

Credit Card
Verification

Analog
Signal
Modem

Analog or Tip/Ring
Extension Jack

PC Terminal

Host
Computer

Figure 5–2.

Modem Data-Only

Single-line
Telephone
(if required for dialing)

MLX
Extension Jack

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
About Data and Video Communications

Page 5-10

5

MLX Voice and Modem Data

This type of analog data station includes an MLX telephone in addition to the DTE
and modem (see Figure 5–3). The modem connects to the MLX telephone
through the T/R interface of the Multi-Function Module (MFM), which is installed in
the MLX telephone. The telephone connects to the control unit through an MLX
extension jack. The communication capabilities of the MLX telephone and data
station can be used simultaneously.

Data Station
DTE

MERLIN
LEGEND
Control
Unit

DCE

Optical
Scanner
Fax

Digital
Signal

Analog
Signal
Modem

Credit Card
Verification

Analog or Tip/Ring
Extension Jack

PC Terminal
MLX-20L

Host
Computer

Figure 5–3.

More

Menu

Inspct

Digital
Signal
MLX Telephone/
with Multi-Function
Module (MFM)

MLX Voice and Modem Data

v

Volume

v

T/R

Home

Feature

Transfer

HFAI

Conf

Mute

Drop

Speaker

Hold

Message

1

GHI

4

PQRS

7

*

ABC

2

DEF

3

JKL

MNO

5

6

TUV

WXYZ

OPER

#

8

0

9

MLX
Extension Jack

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
About Data and Video Communications

ISDN Terminal Adapter Data Stations

Page 5-11

5

An ISDN terminal adapter data station uses an ISDN terminal adapter as its DCE
to send and receive data and connects to a digital extension jack (MLX port) on
the control unit. If PRI, NI-1 BRI, or T1 Switched 56 facilities (including T1-Tie
trunks using T1 Switched 56 service) are assigned to the MLX port, that port may
be configured as a 1B Data or 2B Data port. In a 1B configuration, only one of the
assigned B-channels is used by the ISDN terminal adapter data station. The 2B
configuration allows the simultaneous use of both B-channels.
The ISDN terminal adapter adapts the DTE to the MLX environment. Instead of
converting digital signals to analog signals as a modem does, the ISDN terminal
adapter maintains a digital data format that allows transmission to another inside
ISDN terminal adapter station or over the PRI, NI-1 BRI, or T1 Switched 56
telephone network.
The ISDN terminal adapter can provide dialing and answering capabilities to the
data station, and can share the MLX extension jack with an MLX telephone.
An ISDN terminal adapter data station can be used to make data calls either over
digital telephone facilities (PRI, NI-1 BRI, or T1 Switched 56 facilities) or to an
ISDN terminal adapter data station inside the system.
There are different types of ISDN terminal adapter data stations depending on the
data station’s capabilities:
■

MLX voice and ISDN terminal adapter data (digital voice-and-data)

■

ISDN terminal adapter (data-only)

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
About Data and Video Communications

Page 5-12

MLX Voice and ISDN Terminal Adapter Data

5

This type of ISDN terminal adapter data station includes an MLX telephone in
addition to the DTE and ISDN terminal adapter (see Figure 5–4). The ISDN
terminal adapter connects to the control unit through an MLX port. The MLX port
is shared by both the telephone and the data station but they operate
independently of each other and can be used simultaneously.
NOTE:
In an MLX voice and ISDN terminal adapter data station, the MLX
telephone cannot contain an MFM.

Data Station
DTE

MERLIN
LEGEND
Control
Unit

DCE

Optical
Scanner
Fax

Analog or Tip/Ring
Extension Jack

Credit Card
Verification
PC Terminal

Host
Computer

Digital
Signal

Terminal
Adapter

MLX
Extension Jack
Digital
Signal

MLX Telephone

Figure 5–4.

MLX Voice and ISDN Terminal Adapter Data

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
About Data and Video Communications

Page 5-13

5

ISDN Terminal Adapter Data-Only

This type of digital data station includes only the DTE and ISDN terminal adapter.
The ISDN terminal adapter connects the DTE to the system through an MLX
extension jack on the control unit (see Figure 5–5). Since the configuration does
not include an MLX telephone, if a 7500B data module is used as the ISDN
terminal adapter, a 440A4 terminating resistor adapter is required.

Data Station
DTE

MERLIN
LEGEND
Control
Unit

DCE

Optical
Scanner
Fax

Analog or Tip/Ring
Extension Jack

Credit Card
Verification
PC Terminal

Host
Computer

Figure 5–5.

Digital
Signal

Terminal
Adapter

ISDN Terminal Adapter Data-Only

MLX
Extension Jack
Digital
Signal

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
About Data and Video Communications

Page 5-14

5

Summary of Data Station Configurations

Table 5–1 describes the extension jacks and equipment required for each data
station configuration.
Table 5–1.

Data Station Configurations

Type of Data
Station

Module and
Jack Type

Analog voice and 2 adjacent extension
Modem data
jacks on one of the
following analog
modules: 408, 408
GS/LS, or 008

Telephone
(for voice)

GPA or Modem or ISDN Data
MFM Terminal Adapter Terminal

Analog multiline
GPA
telephone (and a
BR-241-B1 bridging
adapter)

Modem

PC

Modem data-only 1 extension jack on None*
an 008 OPT, 016 T/R
or 012 T/R module

None

Modem

PC, LAN
workstation, or
local host

MLX voice and
Modem data

1 extension jack on MLX telephone*
an 008 MLX or 408
GS/LS-MLX module

MFM

Modem

PC, or LAN
workstation

MLX voice and
ISDN terminal
adapter data

1 extension jack on MLX telephone
an 008 MLX or 408
GS/LS-MLX module

None

ISDN terminal adapter PC, LAN
workstation, local
host, or video
conferencing

None

ISDN terminal adapter PC, LAN
workstation, local
(If using a 7500B data
host, or video
module, a 440A4
conferencing
terminating resistor

ISDN terminal
1 extension jack on None
adapter data-only an 008 MLX or 408
GS/LS-MLX module

adapter is also
required)
Digital Data/Video 1 extension jack on None
an 008 MLX or 408
GS/LS-MLX module
set as a 2B Data port,
or 2 jacks set as 1B
Data ports†

*
†

None

None if station is
G4 FAX, video
connected by a BRI
conferencing
interface. One ISDN
terminal adapter if the
TA supports 2B Data.
Two ISDN terminal
adapters if the TAs
support only 1B Data.

An analog telephone may be connected.
A digital data/video station that connects directly to an MLX port using either a BRI interface
or a v.35 interface and an ISDN terminal adapter that supports 2B Data, requires only one
MLX port programmed as a 2B Data port. A digital data/video station that connects to an
MLX port using a v.35 interface and an ISDN terminal adapter that does not support
2B Data, requires two 1B Data MLX ports. When using the 008 MLX or 408 GS/LS-MLX
module for digital data or video, you must not use Version 29 of the module.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
About Data and Video Communications

Other Supported Data Terminals

Page 5-15

5

Other data equipment that may be connected to the system include analog data
terminals using modem connections, such as the following:
■

A local host computer

■

Group III (G3) fax machine

■

An output-only device

■

An input-only device

A PC containing an internal modem card can also be connected to a T/R
interface.
Other digital data terminals may be connected using ISDN terminal adapters,
including the following:
■

Group video conferencing system

■

Group IV (G4) fax machine

Other Resource Groups

5

You can create the following types of special groups:
■

Modem-Only Group. Provides access to multiport data equipment, for
example, a caller at a data station calling an online database system at an
outside number, over analog lines/trunks.

■

ISDN Terminal Adapter-Only Group. Provides access to multiport
equipment, for example, a host computer, by assigning the MLX ports
interfacing with the ISDN terminal adapters in the pool to a DHG.

Data Hunt Groups

5

A data hunt group (DHG) is similar to a voice-extension calling group, except that
the group in this case is a group of modems or a group of ISDN terminal adapters
(not both). The group can be used to communicate with a local host computer or
workstation (gateway) on a LAN.
All modems or ISDN terminal adapters in a DHG are assigned to a single
extension number that is used both by inside and outside callers to reach the
group. Users are given the DHG number that corresponds to the pool they need to
reach.
Calls to the group are distributed among group members in a circular pattern. The
system hunts for the first available modem or ISDN terminal adapter, starting with
the one that received the last call. If all group members are unavailable, the caller
hears a ringback tone.
Guidelines for creating DHGs are contained in “Creating Data Hunt Groups,” later
in this chapter.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
About Data and Video Communications

Data Hunt Group Configurations

Page 5-16

5

The following DHG configurations work on the system:
■

ISDN Terminal Adapters. Allows communications with the local host
computer or a workstation (gateway) to a LAN.

■

Modems. Allows communications with the local host computer or a
workstation (gateway) to a LAN.

5

Video Systems

A video system is a hardware configuration that provides video teleconferencing.
The video systems use both B-channels (2B Data) associated with an MLX port to
achieve data rates of up to 128-kbps when using PRI or NI-1 BRI facilities, and
112-kbps when using T1 Switched 56 facilities.
There are two basic types of video teleconferencing:
■

Personal Video Conferencing. This type, also referred to as Desktop
Video Conferencing, typically is a single user communicating with another
individual using their PC.

■

Group Video Conferencing. This type, as the name implies, allows larger
groups of people to communicate with another group at a different location.

Personal Videoconferencing

5

A personal videoconferencing system typically consists of a video camera and an
audio unit connected to a PC. The PC connects directly to any available MLX port
on a 408 MLX or 008 MLX module by way of a BRI interface card.
NOTE:
When using the 008 MLX or 408 GS/LS-MLX module for data or video, you
must use Version 28 of the module.
The MLX port must be configured as a 2B Data port in order to provide the
necessary high-speed data connection needed to support video applications. The
network facilities used by the endpoint connected to the MLX port may be PRI, T1
Switched 56 (both provided by the 100D module), or NI-1 BRI (provided by the
800 NI-BRI module) facilities.
NOTE:
Some applications also provide data and application sharing and transfer
capabilities (video collaboration) in addition to video conferencing.
This configuration, in which the personal video system is the only device
connected to the MLX port, is called the Standalone configuration. Some personal
video systems also offer the capability to support a Passive Bus configuration.
See Figure 5–6 on page -18 for a sample connection diagram.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
About Data and Video Communications

Group Videoconferencing

Page 5-17

5

A group videoconferencing system consists of a video camera, an audio unit, and
a display screen (such as a television) that connect to a coder-decoder (CODEC).
The CODEC converts the analog voice and video signals into digital form for
transmission, and converts the digital signals received back into analog form.
The CODEC may use either a BRI interface to connect directly to an available
MLX port on a 408 MLX or 008 MLX module, or a v.35 interface to connect to an
ISDN terminal adapter (such as the Ascend Pipeline 25PX or 50) which in turn
connects to an MLX port.
NOTE:
When using the 008 MLX or 408 GS/LS-MLX module for data or video, you
must not use Version 29 of the module. Use an earlier or later version.
When the group videoconferencing system uses a BRI interface, or an ISDN
terminal adapter that supports 2B Data, the video system may be connected to a
single MLX port that has been configured as a 2B Data port. This allows the video
system to use both B-Channels assigned to the MLX port, thereby achieving the
high-speed data connection necessary to support video.
If the group videoconferencing system uses a v.35 interface to connect to an
ISDN terminal adapter that does not support 2B Data, then two ISDN terminal
adapters are required (each connecting to a separate MLX port that has been
configured as a 1B Data port) in order to achieve a 2B Data connection.
NOTE:
Do not connect equipment, such as an ISDN terminal adapter or G4 fax
machine, that does not support 2B Data to an MLX port that has been
configured as a 2B Data port. This wastes system resources and may
cause other system errors.
The network facilities used by the endpoint connected to the MLX port may be any
combination of PRI, T1 Switched 56 (both provided by the 100D module), and/or
NI-1 BRI (provided by the 800 NI-BRI module) facilities, however it is
recommended that you use two B-channels of the same type to ensure the best
possible connection. See Figure 5–6 for a sample connection diagram.
NOTE:
See the Network Reference for information on group videoconferencing
over private network tandem trunks.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
About Data and Video Communications

Figure 5–6.

Personal and Group Video Connections

Issue 1
August 1998
Page 5-18

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Planning Overview

Page 5-19

5

Planning Overview

By using the procedures earlier in this book, you should have already reserved
the following:
■

Trunk jacks for outside lines/trunks

■

Extension jacks for voice telephone users

■

Extension jacks for either:
— Analog multiline telephones with a modem data station connected to
a General-Purpose Adapter (GPA)
— MLX telephones with either a modem data station connected using
an MFM or a digital data station connected using an ISDN terminal
adapter
— Digital data/video equipment (such as G4 FAX, and personal or
group video systems) connected either directly to an MLX port or
connected to an MLX port by way of an ISDN terminal adapter

5

Forms Needed
Whether you are planning data options for a new system or modifying an existing
system, you record data communications planning information by making
additional entries on forms already completed earlier in this book, and on the
appropriate data forms shown in Table 5–2. Duplicate the master data forms in
Appendix C, “Data Forms,” and work on the copies. Use the forms listed in Table
5–3, as needed. See application note, MERLIN LEGEND Communications
System Modem Pooling, for details.
NOTE:
Behind Switch mode is not included in these instructions. It works the same
way as Key mode.
Table 5–2.

Data Forms

To Plan New or Modify Existing Systems

Use These Forms

Trunk assignments

1a, Modem Data Station
1b, ISDN Terminal Adapter Data Station

Feature assignments

1a, Modem Data Station
1b, ISDN Terminal Adapter Data Station

Data hunt groups

2, Data Hunt Groups

Digital data and/or video stations

3, Digital Data/Video Station

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Planning Overview

Table 5–3.

Issue 1
August 1998
Page 5-20

System Forms

To Plan
Extension jack connections*
Modem data stations
ISDN terminal adapter data stations
Local host computer connections
LAN workstation access connections
Modem/ISDN terminal adapter pools*
Line/Trunk assignments

Feature assignment

Form Needed
2a, System Numbering: Extension Jacks (for
all configurations)

2a, System Numbering: Extension Jacks
2b, System Numbering: Digital Adjuncts
2c, System Numbering: Line/Trunk Jacks
2a, System Numbering: Extension Jacks
2b, System Numbering: Digital Adjuncts
4d, MLX Telephones
4b, Analog Multiline Telephone
4e, MFM Adjunct: MLX Telephone
5b, Direct-Line Console (DLC): Digital
5c, MFM Adjunct: DLC

Dial-out code (Hybrid/PBX only)

2c, System Numbering: Line/Trunk Jacks

ARS Facility Restriction Level
(Hybrid/PBX only)

3f, Automatic Route Selection Tables
3g, Automatic Route Selection Default and
Special Numbers Table

Data hunt groups

2c, System Numbering: Line/Trunk Jacks
2d, System Numbering: Special Renumbers
7d, Group Calling

*

You must make an entry for extension jack connections.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Assigning Extension Jacks

Page 5-21

Assigning Extension Jacks

5

Following some guidelines about digital extension jacks, this section contains
procedures to plan extension jack connections for the following:
■

Modem data-only stations

■

ISDN terminal adapter data-only stations

■

Local host computer data stations

■

LAN workstations

■

Video systems (personal or group)

For each type of data station, planning how the data equipment connects to
extension jacks on the control unit involves the following tasks:

Table 5–4.

1.

Review Form 2a, on which you entered codes (A for analog, D for digital,
and B for basic telephone) and find the telephone type and the user,
location, or function for each data station to be connected. Table 5–4 lists
extension jack types, the corresponding module types, and the equipment
that can be connected.

2.

Add the extension jack assignments to Form 2a.

Extension Jack Types

Jack Type Module Type

Connects

Analog

008
408
408 GS/LS

Analog multiline telephones (including analog voice-and-data stations
with a modem connected through a GPA)

Digital

008 MLX
MLX telephones (including MLX voice-modem data stations)
408 GS/LS-MLX MLX telephones (including MLX voice and ISDN terminal adapter
stations)
ISDN terminal adapter data terminals (such as PCs)
Video systems (personal or group)

Basic

012
016

T/R equipment:
Single-line telephones
Adjuncts, such as fax or answering machines
Modem data-only stations

008 OPT

Tip/ring equipment in another building or offsite

Before you assign extension jacks for ISDN terminal adapter data stations, review
the guidelines in the next section, “Guidelines for Digital Extension Jacks.”

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Assigning Extension Jacks

Guidelines for Digital Extension Jacks

Page 5-22

5

Although only one logical ID is assigned to each digital extension jack, the system
automatically assigns two extension numbers:
■

The first extension number shown on Form 2a is assigned to an MLX
telephone connected to the extension jack.

■

The second extension number assigned to each jack is reserved for an
adjunct, such as an ISDN terminal adapter data terminal or desktop video
endpoint, connected to the MLX telephone.

■

If a personal or group video system is connected to the MLX port,
extension numbers are assigned to the video system for use in 2B Data
connections.

Both extension numbers are assigned automatically, whether or not the extension
includes an ISDN terminal adapter. Calls can be placed to both extension
numbers independently. Note that an MLX extension cannot have both an ISDN
terminal adapter and an MFM.
Also, when configuring digital data equipment connections to an MLX port, the
following requirements and/or restrictions must be applied:
■

If using a 7500B data module as an ISDN terminal adapter, and it is the
only ISDN terminal adapter data station on the MLX port (no MLX
telephone is connected), a 440A4 terminating resistor adapter must be
configured to provide 100-ohm termination for each transmission pair. The
7500B data module does not provide termination.

■

An MLX telephone is independent from the ISDN terminal adapter;
however, the telephone may cause channel conflict between the telephone
and the ISDN terminal adapter when the telephone is voice-signaled while
active on a call. If a slight chance of data call blocking is unacceptable, an
MLX telephone should not be connected to an ISDN terminal adapter used
in a data station configuration.

■

The maximum cord length from an MLX telephone to an ISDN terminal
adapter is 80 feet (24 meters). This should be considered if you plan to use
the voice capability of a port by connecting an MLX telephone far from the
ISDN terminal adapter.

■

Do not connect an ISDN terminal adapter that does not support 2B Data to
an MLX port that has been programmed as a 2B Data port.

■

When using the 008 MLX or 408 GS/LS-MLX module for data or video, you
must use Version 28 of the module.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Assigning Extension Jacks

Modem Data-Only Stations

Page 5-23

5

A modem data-only station consists of a data terminal connected to the control
unit using an internal or external modem. This station does not include a
telephone.
Assign a basic telephone extension jack on an 012 T/R, 016 T/R, or 008 OPT
module; either an on- or off-premises extension can be connected to an 008 OPT
module.

5

Planning Form Instructions
Record the extension jack assignments for modem data stations on Form 2a,
System Numbering: Extension Jacks:
1.

In the Jack Type column, make sure there is a B next to the number for
each basic extension jack.

2.

In the Person, Location, or Function column, write modem and then identify
each modem data station by person, location, or function.

ISDN Terminal Adapter Data-Only Stations

5

An ISDN terminal adapter data-only station consists of a PC or a data terminal
connected to an ISDN terminal adapter. Each ISDN terminal adapter data station
connects to a digital extension jack on an 008 MLX or 408 GS/LS-MLX module.

Planning Form Instructions
Record the extension jack assignments for ISDN terminal adapter data stations
on Form 2a, System Numbering: Extension Jacks:
1.

In the Jack Type column, make sure there is a D next to the number for
each digital extension jack.

2.

In the Person, Location or Function column, write ISDN-TA and identify
each ISDN terminal adapter data station by person, location, or function.

3.

Fill in Form 2b with the extension number of the ISDN terminal adapter.

5

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Assigning Extension Jacks

Local Host Computer Data Stations

Page 5-24

5

A local host computer data station consists of a local host computer, a data
terminal for that computer, and one or more ISDN terminal adapters and/or
modems.
Assign each ISDN terminal adapter used for access to a host computer to a digital
extension jack on an 008 MLX or 408 GS/LS-MLX module. Assign each modem
to a basic telephone extension jack on an 012 T/R, 016 T/R, or 008 OPT module.
If you have a limited number of ISDN terminal adapters or modems to share
among many users, assign some or all of the modems or ISDN terminal adapters
to a DHG. In this way, users can access all the devices in the DHG by dialing one
extension number.
Users access the computer by placing a data call to the extension number for
either an ISDN terminal adapter or modem (or DHG) — depending on the user’s
type of data station — that is assigned for communication with the local host
computer.

Planning Form Instructions
Record the extension jack assignments for local host computer access extensions
on Form 2a, System Numbering: Extension Jacks.
NOTE:
Before you assign extension jacks for a local host computer, review the
guidelines in “Guidelines for Digital Extension Jacks,” earlier in this section.
1.

2.

For each digital extension jack used to connect an ISDN terminal adapter:
a.

In the Jack Type column, make sure there is a D next to the number
for each digital extension.

b.

In the Person Location, or Function column, write
Terminal Adapter-host.

For each basic telephone extension jack you plan to use to connect a
modem:
a.

In the Jack Type column, make sure there is a B next to the number.

b.

In the Person, Location or Function column, write modem-host.

5

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Assigning Extension Jacks

Page 5-25

5

LAN Workstations

A Local Area Network (LAN) consists of workstations (PCs) connected together to
share resources. The system connects to the LAN through a workstation that
functions as a gateway, providing ports for modem and ISDN terminal adapter
connections.
Assign each ISDN terminal adapter used for access to a LAN workstation to a
digital jack on an 008 MLX or 408 GS/LS-MLX module. Each modem must be
connected to a basic telephone extension jack on an 012 T/R, 016 T/R, or
008 OPT module.
If you have a limited number of ISDN terminal adapters or modems to share
among many users, assign some or all of the modems or ISDN terminal adapters
to a DHG. In this way, users can access all the devices in the DHG by dialing one
extension number.
Users access the computer by placing a data call to the extension number for
either an ISDN terminal adapter or modem (or DHG) — depending on the user’s
type of data station — that is assigned for communication with the local host
computer.

Planning Form Instructions
Record the extension jack assignments for access to a workstation on a LAN on
Form 2a, System Numbering: Extension Jacks.
1.

For each digital extension jack used to connect an ISDN terminal adapter:
a.
b.

In the Jack Type column, make sure there is a D next to the number
for each digital extension.
In the Person Location, or Function column, write

Terminal Adapter-LAN.
2.

For each basic telephone extension jack you plan to use to connect a
modem:
a.

In the Jack Type column, make sure there is a B next to the number
for each basic telephone extension jack used to connect a modem.

b.

In the Person, Location or Function column, write modem-LAN.

5

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Assigning Extension Jacks

Page 5-26

5

Video Systems

Video systems may connect to an MLX port on the MERLIN LEGEND system
either directly through a BRI interface, or by way of a v.35 interface and an ISDN
terminal adapter.
Assign each video system that is connected directly to the MLX port, or connected
to an ISDN terminal adapter that supports 2B Data, to one digital jack configured
as a 2B Data port on an 008 MLX or 408 GS/LS-MLX module.
Assign each video system that is connected to an MLX port by way of an ISDN
terminal adapter that does not support 2B Data to two separate digital jacks
configured as 1B Data ports on an 008 MLX or 408 GS/LS-MLX module.

Planning Form Instructions
Record the extension jack assignments for video systems on Form 2a, System
Numbering: Extension Jacks.
1.

In the Jack Type column, make sure there is a D next to the number for
each digital extension.

2.

In the Person, Location, or Function column, enter the type of equipment
connected.

5

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Assigning Lines/Trunks to Data and Video Stations

Assigning Lines/Trunks to Data and
Video Stations

Page 5-27

5

The following types of outside lines/trunks are used to make and receive data
calls to and from data stations outside of the system:
■

Loop-Start (LS). This is the standard line/trunk for homes and small
businesses, and can be used to communicate with outside modem data
stations. Video calls are not made over loop-start lines/trunks. Loop-start
lines/trunks are the least expensive lines/trunks in some areas but have the
following disadvantages:
— They do not protect against glare, a condition that occurs when an
outside call is made at the same time that an incoming call arrives
on the same line/trunk.
— They may not provide reliable far-end disconnect for toll restriction.

!

SecurityAlert:
Toll fraud can occur when loop-start lines/trunks are used with unreliable
disconnect. If the calling party stays on the line after the called party hangs
up, the central office returns a dial tone at the conclusion of the call enabling
the caller to place another call as if it were being placed from your company.
■

Ground-Start (GS). This line/trunk is preferred for communication with
outside modem data stations. Ground-start lines/trunks provide improved
signaling and reliable far-end disconnect for secure toll restriction. Video
calls are not made over ground-start lines/trunks.

The following kinds of outside ground-start or loop-start lines/trunks can be used
for data communications:
— Basic lines/trunks
— Wide area telecommunications service (WATS)
— 800 service (inbound WATS)
— Foreign exchange (FX)
Ground-start/loop-start lines/trunks connect to ground-start/loop-start jacks on the
following types of modules in the control unit:
— 800 GS/LS
— 400 GS/LS/TTR
— 408 (LS lines/trunks only)
— 408 GS/LS
— 400 (LS lines/trunks only)
— 800 (LS lines/trunks only)
— 408 GS/LS-MLX
— 800 GS/LS-ID

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Assigning Lines/Trunks to Data and Video Stations
■

Issue 1
August 1998
Page 5-28

Analog/Digital Tie. This trunk type “ties” two telephone switching systems
together, providing access to all telephones or data equipment on each
system. Analog Tie trunks are used for data communication with modem
data stations connected to a system at a different location, such as a
different floor of a building, a different building, or a different city or state.
Analog Tie trunks connect to a jack on a 400EM module in the control unit.
Video calls are not made over analog Tie lines/trunks.
Digital Tie trunks are used for digital data communications, such as G4 fax
and videoconferencing, with digital data/video stations connected to a
system at a different location, such as a different floor of a building, a
different building, or a different city or state. Digital Tie trunks are emulated
by T1 facilities connected to a 100D module in the control unit. Video and
digital data calls may be made over digital Tie lines/trunks.

■

Direct Inward Dial (DID). Incoming calls reach specific individuals or
facilities in the system without the help of a system operator. DID trunks are
available only in Hybrid/PBX mode. A DID trunk is used to receive
incoming calls from outside modem data stations. It is not used for
outgoing calls. A DID trunk connects to a jack on an 800 DID module in the
control unit. Video calls are not made over DID lines/trunks.

■

Digital Signal 1 (DS1). This facility carries digital signals in the DS1
format. A DS1 facility can be used for communication with outside digital or
modem data stations, including video systems. A DS1 facility connects to
the jack on a 100D module in the control unit. Even though there is only
one physical jack, the 100D module supports up to 24 logical endpoints for
voice and data calls; each DS0 channel in the DS1 signal corresponds to a
trunk or logical ID.
A DS1 facility provides either T1 (including T1 Switched 56 for digital
data/video calls) or PRI access:
— T1 (factory setting). The 24 channels on a T1 facility can be
programmed individually in any combination to emulate a loop-start,
ground-start, E&M tie, DID, or Switched 56 digital data trunk, so a
single 100D module can replace 24 outside lines/trunks. When T1
Switched 56 service is used, high-speed video connections at data
rates of 56-kbps per channel (112-kbps for 2B Data) are possible.
— PRI. The standard format for ISDN services provided by connection
to a 5ESS central office (CO) switch or a 4ESS or DEFINITY toll
switch. PRI facilities provide several benefits, including increased
speed of data calls to an outside destination, INFO-2 automatic call
identification (ANI) service, dynamic B-channel assignment,
improved toll restriction, reliable indication of far-end disconnect,
and improved SMDR. Twenty-three channels can be programmed
for individual services (Channel 24 is reserved for signaling
purposes). PRI facilities may also be used for high-speed video calls
at data rates of up to 64-kbps per B-channel (128-kbps total for 2B
Data).

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Issue 1
August 1998

Data Communications
Assigning Lines/Trunks to Data and Video Stations

Page 5-29

The 100D module supports any combination of the following AT&T
Switched Network services:
— ACCUNET Switched Digital Service for 56-kbps and 64-kbps
restricted and 64-kbps clear (unrestricted) circuit-switched data calls
(PRI only)
— ACCUNET Switched 56 Service for 56-kbps (restricted or
unrestricted) data calls (T1 only)
— Megacom 800 for incoming domestic toll-free voice calls
— Megacom WATS service for outgoing domestic long-distance voice
calls
— Software-Defined Network (SDN) for circuit-switched voice and data
calls at up to 56 kbps
■

In Release 4.2 and later systems, these MCI services are also available:
— MCI PRISM
— MCI Vnet
— MCI 800
— MCI 900

■

In Release 4.2 and later systems, these local exchange carrier services are
also available:
— DMS Private
— DMS INWATS
— DMS OUTWATS
— DMS FX
— DMS Tie Trunk

■

NI-1 BRI. Basic Rate Interface (BRI) is a protocol within the ISDN standard
that provides digital voice, data, and video connectivity. NI-1 BRI facilities
connect to a jack on the 800 NI-BRI module, with each facility providing two
B-channels per jack (total of 16 NI-1 BRI channels per 800 NI-BRI module).
BRI facilities provide data rates of up to 64-kbps clear (unrestricted)
circuit-switched data calls per B-channel (128-kbps total for 2B Data).

To assign lines/trunks to data stations, you decide on the types of line buttons that
are assigned to the data communications equipment at each data station. The
data stations are:
■

Analog voice and modem data stations and MLX voice and modem data
stations

■

MLX voice and ISDN terminal adapter data stations, including telephones

■

Modem data-only stations

■

ISDN terminal adapter data-only stations

■

Digital data/video stations

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Issue 1
August 1998

Data Communications
Assigning Lines/Trunks to Data and Video Stations

Page 5-30

The system treats each data station, except for analog voice and modem data
stations, as an extension with a 34-button telephone.
When you choose the mode of operation (Key, Behind Switch, or Hybrid/PBX),
Intercom (ICOM) or System Access (SA) buttons are assigned automatically to
every extension connected to the control unit. However, you can customize the
system by changing the factory-set assignments and reassigning line buttons.
The number and types of buttons assigned depends on the mode chosen and the
type of extension jack you are using.
NOTE:
Trunks cannot be independently assigned to analog voice and modem data
stations. The line/trunk assignment for the telephone also includes the
modem extension; therefore, these instructions are not used for these types
of data stations.

Forms Needed
■

Data Form 1a, Modem Data Stations

■

Data Form 1b, Data Stations

■

Form 4e, MFM Adjunct: MLX Telephone

■

Form 5c, MFM Adjunct: DLC

Planning Form Instructions
You should have already filled out preliminary information on Forms 4e and 5c
when you planned voice communications. The lines/trunks for MLX telephones
have already been assigned.
There are two different forms for data stations:
■

Data Form 1a. Use this form for modem data-only stations and for modems
used to communicate with the local host computer and to communicate
with a workstation on a LAN.

■

Data Form 1b. Use this form for ISDN terminal adapters and ISDN terminal
adapter data stations used to communicate with the local host computer or
with a workstation on a LAN.

Make enough copies of each data form so that you can complete one form for
each data station. Complete each form:
1.

From Form 2a, System Numbering: Extension Jacks, obtain the
identification information for each data station.

5

5

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Assigning Lines/Trunks to Data and Video Stations

2.

Page 5-31

Record the information on the appropriate data form (2a or 2b) for each
data station and for each modem and ISDN terminal adapter used to
communicate with a local host computer or with a workstation on a LAN:
a.

In the Logical ID space, write the logical ID for each extension.

b.

In the Extension No. space, write the extension number for each
extension.

c.

In the Person or Location space, write the name of the person or the
location of the data equipment.

d.

Under the Data Station Use heading, indicate the purpose of the
data station by checking one of the following boxes: Individual use,
Local host computer, or LAN workstation.

Assigning Line Buttons in Hybrid/PBX Mode

5

The line buttons you can assign to data stations are as follows:
■

System Access Ring (SA Ring). Used to make and receive inside and
outside data calls. To make outside calls, the user selects an outside
line/trunk by dialing either the code for Automatic Route Selection (ARS) or
the dial-out code for the trunk pool. Users at ISDN terminal adapter data
stations and video endpoints can also dial the line/trunk number (801-880)
to select an outside line/trunk.

■

Personal Line. Used to make and receive outside data calls from a data
station on a specific outside line/trunk. A personal line is an outside
line/trunk assigned to a line button on one or more data or voice stations.
The outside line/trunk cannot be a member of a pool.
To dedicate an outside line/trunk for data calls and have the calls
automatically answered by data equipment, do not assign the same
outside line/trunk to both data equipment and telephones because
modems answer voice calls as data calls.
On analog voice-and modem data stations, a personal line can be used to
receive incoming calls. A personal line can be used for outgoing calls by
selecting the line button on the analog multiline telephone, dialing, and
then activating the modem connected through a GPA.
On ISDN terminal adapter data stations, a personal line can be used to
make and receive outside data calls. To select the line/trunk for an outgoing
call, the caller dials the line/trunk number (801–880). To allow the user at
an ISDN terminal adapter data station access to the digital network for
making and receiving calls to outside digital data stations, assign PRI,
NI-1 BRI, or T1 Switched 56 (including T1-Tie lines using Switched 56
service) facilities as personal lines.

■

Pool. Used when you want the voice and data station to make and receive
outside data calls on a specific trunk pool (for example, a pool with PRI
facilities) without dialing a dial-out code. The Pool button is used to make
and receive only outside calls. Automatic Line Selection should be set to
the Pool button in order to place calls on it.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Issue 1
August 1998

Data Communications
Assigning Lines/Trunks to Data and Video Stations

Page 5-32

NOTES:
1. Do not assign System Access Voice (SA Voice) buttons to data
communications equipment.
2. You must use PRI facilities with a digital data service such as ACCUNET
Switched Digital Service, a Software Defined Network (SDN), T1
Switched 56 facilities, or NI-1 BRI facilities for digital data calls.
3. T1 facilities that are not using Switched 56 service can be used for
modem data and analog voice calls and can be assigned to telephones to
allow the voice user to make and receive voice calls using these types of
facilities.
The following line button assignments are factory set for Hybrid/PBX mode and
are prerecorded on the Button Diagram on Data Forms 1a and 1b:
■

One System Access Originate Only (SA Orig Only) button and two System
Access Ring (SA Ring) buttons are assigned to all data equipment
connected to an 012 T/R, 016 T/R, or 008 OPT module.

■

One System Access Originate Only (SA Orig Only) button, one System
Access Ring (SA Ring) button, and a System Access Voice (SA Voice)
button are assigned to all data equipment connected to a digital extension
jack on an 008 MLX or 408 GS/LS-MLX module. Remove the SA Voice
button (see Form 5c, page 1).

The factory settings can be changed; however, the settings should be adequate to
meet most user needs, since System Access lines can be used to make both
inside and outside data calls. Each data extension must have at least one SA
button, or two SA buttons for making 2B Data calls. If making 2B Data calls with
two personal line buttons, you must also have two SA buttons.
If you want an ISDN terminal adapter data station to make and receive outside
data calls on a specific outside line/trunk, assign a personal line button. To make
calls on a personal line, set the Automatic Line Selection to that line.

Assigning Pools and Lines/Trunks
(Hybrid/PBX Mode Only)

5

If you want the voice and data station to make and receive outside calls on a
specific trunk pool, assign a Pool button.
To dedicate a specific line/trunk or pool to receive outside data calls, assign a
personal line or pool to a data station or DHG.
To dedicate specific lines/trunks for use in data communications only (such as PRI
channels or other special data lines), consider grouping those lines/trunks in a
pool.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Assigning Lines/Trunks to Data and Video Stations

Page 5-33

If the system uses ARS, follow the instructions on ARS earlier in this book to
specify routes for outgoing data calls.
To restrict non-data users from dial access to data trunk pools, use the “Pool
Dial-Out Code (Hybrid/PBX Mode Only)” instructions later in this chapter.

5

Forms Needed
■

Form 2c, System Numbering: Line/Trunk Jacks

■

Data Form 1a, Modem Data Station

■

Data Form 1b, ISDN Terminal Adapter Data Station

5

Planning Form Instructions
Record your decisions for each data station on the Hybrid/PBX Mode Button
Diagram of Data Form 1a or 1b.
1.

If you want to assign personal lines to the data station, write Personal Line
and the telephone number (from Form 2c) of the outside line on the
appropriate button. For ISDN terminal adapter data stations, include the
line/trunk number.

2.

If you want to assign a pool to the data station, write Pool and the pool’s
extension number (from Form 2c) on the appropriate button.
NOTE:
On modem data stations from which the user does not need to make inside
calls, you can assign only personal lines or pools; when going off-hook, the
user or equipment gets a telephone company line/trunk by Automatic Line
Selection.

Assigning Line Buttons in Key Mode

5

There are two kinds of line buttons you can assign to data stations used to make
and receive data calls:
■

Intercom Ring. Used to make and receive inside data calls only.

■

Outside Line/Trunk. Used to make and receive outside data calls on a
specific outside line/trunk. An outside line/trunk can be assigned to a line
button on one or more data stations or voice extensions. To dedicate an
outside line/trunk for data calls and have the calls automatically answered
at a data station, do not assign the same outside line/trunk to data stations
and to telephones, because modems answer voice calls as data calls.

For digital data stations, the outside line/trunk can be used to make and receive
outside data calls. For an outgoing call, the user dials the line number (801-880)
to select the line/trunk.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Assigning Lines/Trunks to Data and Video Stations

Issue 1
August 1998
Page 5-34

To allow the user at an ISDN terminal adapter data station access to the digital
network for making and receiving calls to outside digital data stations, assign PRI
facilities with digital data service such as ACCUNET Switched Digital Service and
Software Defined Network (SDN), NI-1 BRI, or T1 Switched 56 facilities to ISDN
terminal adapter data stations. If these facilities are not available, the ISDN
terminal adapter data station user can make calls over the regular analog
telephone network only by using a digital-to-analog modem pool, described in
application note, MERLIN LEGEND Communications System Modem Pooling.
NOTE:
PRI and NI-1 BRI facilities are also used for analog data and voice calls and
can be assigned to telephones to allow the voice user to make and receive
voice calls using these types of facilities.
The following line button assignments are factory-set for Key mode and are
prerecorded on the Button Diagram on Data Forms 1a and 1b. Two Intercom Ring
(ICOM Ring) buttons are assigned to the following:
■

Data equipment connected to an 012 T/R, 016 T/R, or 008 OPT module

■

All equipment connected to a digital extension jack on an 008 MLX or
408 GS/LS-MLX module

The factory settings can be changed; however, at least one ICOM button must be
assigned to each data station. To allow a user to make and receive outside data
calls, you must assign an outside trunk to the data station.
To dedicate a specific line to receive outside data calls, assign an outside
line/trunk to a data station, DHG, LAN workstation, or local host computer.
On a digital or analog data station, the user selects an outside line/trunk by dialing
the Idle Line Preference code (usually 9) on an ICOM button. On an ISDN
terminal adapter data station, the user can also select lines/trunks assigned to the
extension by dialing the line number (801–880) assigned to that outside line/trunk.
It is extremely important that the factory-set Idle Line Preference (the line to which
the user is connected automatically when going off-hook) not be changed. The
user must be connected to an intercom line to activate features such as Privacy or
to select an available outside line/trunk by dialing the Idle Line Preference code.

Planning Form Instructions
Using Form 2c, System Numbering: Line/Trunk Jacks as reference, record your
decisions for each data station on the Key mode Button Diagram of Data Form 1a
or 1b. If you want to assign outside lines/trunks to the data station, write the
telephone number (from Form 2c) of the outside line/trunk on the appropriate
button. For ISDN terminal adapter data stations, include the line/trunk number.

5

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Assigning Features to Data Stations

Assigning Features to Data Stations

Page 5-35

5

Many of the features used for voice calls (as described earlier in this guide) can
also be assigned to data stations. This section describes these features and how
to assign them to each ISDN terminal adapter or modem data station. This
includes: modem data stations with an MLX telephone using an MFM, ISDN
terminal adapter data stations with a telephone, and modem and ISDN terminal
adapter data-only stations (data stations with no telephone).
NOTE:
Features cannot be independently assigned to modem data stations
connected to analog multiline telephones using a General-Purpose Adapter
(GPA). The feature assignment for the telephone also includes the modem;
therefore, the following planning instructions are not used for these types of
data stations.
The following optional features can be assigned to data stations:
■

Account Code Entry. This feature allows tracking of outgoing data calls
for billing, forecasting, or budget reports.

■

Auto Answer All. This feature allows a modem with automatic answering
capability to answer data calls when the user is away from the data station.
Supports analog voice and modem data stations only.

■

Automatic Route Selection (Hybrid/PBX Mode Only). This feature routes
calls over outside lines/trunks according to the number dialed and the
lines/trunks available. Therefore, the system can be programmed to select
the least expensive route for each data call over either PRI, NI-1 BRI, or T1
Switched 56 facilities.

■

Calling Restrictions. These features inhibit line access, and allow
companies to control and manage communications costs for outgoing data
calls.

■

Data Status. This button allows monitoring of station activity (busy, not
busy) at any data station. Although this feature is similar to having an
Inside Auto Dial or Signaling button because it lights the green LED to
indicate extension-busy status, pressing the button has no effect. It does
not dial the data extension number. Thus, the button does not interfere with
a data call in progress, unlike an Auto Dial button, which dials its
programmed number.

■

Personal Lines. This feature provides direct access from an ISDN terminal
adapter data station to outside lines that support the PRI, NI-1 BRI, or T1
Switched 56 interface.

■

Idle Line Preference. This feature automatically selects the first available
line for data calls.

■

Last Number Dialed. This feature automatically places a call to the last
number dialed from that data station. The dialing sequence must include
dial-out code for outside calls.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Assigning Features to Data Stations

Issue 1
August 1998
Page 5-36

■

Personal Speed Dial. These 2-digit numbers are programmed for quick
dialing of frequently used numbers. The dialing sequence requires a
dial-out code for outside calls.

■

Privacy. This feature prevents loss of data by ensuring that data transmission is not interrupted accidentally. Privacy is automatic for data calls on
ISDN terminal adapter data stations and on analog voice and modem data
stations. Privacy is activated manually on modem data-only stations.

■

System Speed Dial. This feature allows quick dialing of numbers that are
used often systemwide. The dialing sequence requires a dial-out code for
outside calls. The System Speed Dial feature is programmed systemwide
for both voice and data stations. Follow the instructions earlier in this book
to assign System Speed Dial codes to data station users.
NOTE:
Certain system (voice) features interfere with data connections. The
following system features must be disabled for the data station:
■

Voice Announce

■

Call Waiting

■

Automatic Callback

For detailed information about these features, refer to the Feature Reference. For
information on planning for features not described in this section, use the
guidelines presented in the appropriate sections earlier in this book.

Forms Needed
■

Data Form 1a, Modem Data Station

■

Data Form 1b, ISDN Terminal Adapter Data Station

■

Form 4e, MFM Adjunct: MLX Telephones

■

Form 5c, MFM Adjunct: DLC

5

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Assigning Features to Data Stations

Pool Dial-Out Code (Hybrid/PBX Mode Only)

Page 5-37

5

Use these instructions only if the system is operating in Hybrid/PBX mode.
The factory setting is for all extensions, including data stations, to be restricted
from using all dial-out access codes. You can unrestrict data stations to allow the
user access to one or more trunk pools by dialing the pool dial-out code.
The dial-out code restriction places data calls only on specific trunk pools. For
example, you may want to restrict users to trunk pools that are made up of special
data lines such as PRI channels used for data services, or to reserve other trunk
pools for voice communications only.

5

Planning Form Instructions
Use the Optional Features section of Data Form 1a or 1b for each data extension
to record your decisions:
1.

In the Optional Features section, under the Pool Dial-Out Code Restriction
heading:
— Check Unrestricted from following codes and list the codes in the
space provided for unrestricted use.
— Check Restricted from following codes and list the codes in the
spaces provided for restricted use. The factory setting is restricted
for all codes.

2.

Use Form 2c, System Numbering: Line/Trunk Jacks to locate the dial-out
codes for each pool that the data station is restricted from using. Write the
dial-out codes on the lines below the Yes box.

Calling Restrictions

5

When the system is first set up, all data stations are restricted. This means that
only inside (intercom) calls may be made, local and long-distance calls may not
be placed from any data station. However, you can unrestrict selected data
stations to allow local and long-distance calls.

Planning Form Instructions
Use the Optional Features section of Data Form 1a or 1b for each data station to
record your decisions. Under the Call Restriction heading, do one of the following:
■

If you do not want calling restrictions for this data station, check the
Unrestricted box.

■

If you want the data station restricted from making any outside calls, check
the Outward Restrict box (factory setting).

■

If you want the data station restricted from making long-distance calls
(intercom and local calls can be made), check the Toll Restrict box.

5

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Assigning Features to Data Stations

Forced Account Code Entry

Page 5-38

5

The Forced Account Code Entry feature is used for billing or for tracking data calls
by requiring data extension users to enter account codes (1 to 16 digits) for
outside calls. Assign this feature to data stations so that you can associate
outgoing data calls with specific client accounts.
NOTE:
Account codes cannot be used to track incoming calls to data stations.

5

Planning Form Instructions
To record your decisions, use the Optional Features section of Data Form 1a or 1b
for each data station. Under the Forced Account Code Entry heading, do one of
the following:
■

If the user must enter an account code for outgoing calls, check the Yes
box.

■

If you do not want the feature assigned to the data station, check the No
box (the factory setting).

ARS Facility Restriction Level
(Hybrid/PBX Mode Only)

5

Use these instructions only if the system is operating in Hybrid/PBX mode.
If the system uses ARS for data calls, you can assign a Facility Restriction Level
(FRL) to each data station. This value (0–6) corresponds to the FRL assigned to
each route and is used to restrict data users from access to specific routes. Before
restricting a data station, review the values assigned to each route.
To restrict a data station from specific routes, assign an FRL value lower than the
route’s lowest value. (Values equal to or greater than the route’s values allow data
extension users to access those routes.) A value of 0 is the most restrictive, and a
value of 6 is the least restrictive. The factory setting is 3.
For example, to give a modem data station unlimited use of any ARS route,
assign a value of 6. If you have ISDN terminal adapter data stations, assign a
value of 0 to prevent users from inadvertently using ARS to select an analog line
for outside data calls.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Assigning Features to Data Stations

Page 5-39

5

Planning Form Instructions
1.

Using Form 3f, Automatic Route Selection Tables and Form 3g, Automatic
Route Selection Default and Special Numbers Table, review the values
assigned to the routes.

2.

In the Optional Features section of Data Form 1a or 1b for each data
station to record your decisions about Facility Restriction Level, do one of
the following:
■

Check 3 to keep the factory setting.

■

To change the setting, write the value (0–6) for the ARS Facility
Restriction level you want to assign to each data station.

System Speed Dial Codes

5

To avoid giving the telephone number of a remote computer to modem pool users,
assign a System Speed Dial code to the telephone number. Users can dial this
3-digit code to place data calls to the remote computer.
For data calls, the telephone number programmed for a System Speed Dial code
must include the access code (the dial-out code or the ARS dial-out code) if
required.
To specify that the remote computer’s telephone number does not appear on call
reports, use the “System Speed Dial” instructions in Chapter 4 of this book.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Creating Data Hunt Groups

Creating Data Hunt Groups

Page 5-40

5

Use these instructions if the system has a group of modems or ISDN terminal
adapters.
DHGs are data calling groups that provide uniform call distribution among a group
of modems or a group of ISDN terminal adapters (such as the Ascend Pipeline
25PX or 50). DHGs support the following:
■

Modem pools

■

Dedicated lines for data service

■

A local host computer

■

A workstation that functions as a gateway on a LAN

For more information, see the “Planning Overview,” earlier in this chapter. For
information on modem pools, see application note, MERLIN LEGEND
Communications System Modem Pooling.

5

Guidelines

Use the following guidelines for the procedure in this section:
■

Members of a DHG must be extension jacks of the same type: all analog or
all MLX.

■

You can assign up to 32 DHGs or calling groups, or a combination of both
types. Each DHG can have a maximum of 20 members and each data
station can be a member of only one DHG.

■

You can designate particular lines/trunks or pools (Hybrid/PBX mode only)
to ring directly into a DHG. However, incoming calls on a given line/trunk
can be directed to only one DHG.

■

Extension numbers 770–791 and 7920–7929 are reserved automatically
for calling groups and DHGs. If you want to change the extension numbers
assigned to a DHG, see the information about reassigning extension
numbers described in Chapter 2, “Control Unit Configuration.” The same
considerations apply to data stations and voice extensions.

Forms Needed
■

Form 2a, System Numbering: Extension Jacks

■

Form 2c, System Numbering: Line/Trunk Jacks

■

If the system has trunk pools (Hybrid/PBX mode only) Form 2c, System
Numbering: Line/Trunk Jacks

■

If the system includes voice calling groups, Form 7d, Group Calling

■

If you plan to renumber the factory-set extensions, Form 2d, System
Numbering: Special Renumbers

5

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Creating Data Hunt Groups

Issue 1
August 1998
Page 5-41

Planning Form Instructions
Make enough copies of Data Form 2, Data Hunt Groups, for the number of data
hunt groups you plan. For each DHG:
1.

Write the group number (1–32) in the Group Number space.

2.

Write the name of the group in the Group ID space.

3.

Write the factory-set extension number for the DHG in the space provided.
NOTE:
Check all pages of Form 7d to be sure that you have not assigned
the extension to a voice calling group.

4.

If you want to reassign the factory-set extension number for the DHG, write
the new number in the Renumber To space. Also write the new extension
number you want to reassign in the calling group or DHG on Form 2d,
System Numbering: Special Renumber.

5.

Under the Purpose of Group heading, indicate the group use: local host
computer access workstation, LAN access, and so forth.

6.

In the Stations area, write the extension number of each member of the
group in the Ext. No. column and the name of the person or location in the
Person or Location column.

7.

In the Trunks or Pool area, for each line/trunk or pool that you want to ring
directly into the DHG, write the line/trunk number or pool extension number
next to the logical ID in the Trunk or Pool column. (See Form 2b for the
line/trunk numbers and Form 2c for the pool extension number.)

5

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Digital Data/Video Stations

Digital Data/Video Stations

Page 5-42

5

Use these instructions if the system has digital data/video endpoints.
NOTE:
See the Network Reference for information on digital data/video stations on
a private network.
Digital data/video endpoints provide access to voice, as well as high speed digital
data and video services over PRI, NI-1 BRI, or T1 Switched 56 facilities. Incoming
data/video calls may be received using:
■

Dial Plan Routing (PRI and T1 Switched 56 Data)

■

Tie Line Routing (PRI and T1 Switched 56 Data)

■

Personal Lines

Outgoing data/video calls may be placed using:
■

Pool Access

■

Automatic Route Selection (ARS)

■

Personal Lines

For more information, see the “Planning Overview,” earlier in this chapter.

Forms Needed
■

Form 2a, System Numbering: Extension Jacks

■

Data Form 3, Digital Data/Video Stations

Planning Form Instructions
Make enough copies of Data Form 3, Digital Data/Video Stations, for the number
of digital data/video stations you plan. For each:
1.

From Form 2a, System Numbering: Extension Jacks, obtain the
identification information for each digital data/video station.

2.

Record the information on Data Form 3, Digital Data/Video Stations.

3.

a.

In the Logical ID space, write the logical ID for each extension.

b.

In the Extension No. space, write the extension number for each
extension.

c.

In the Equipment, Person, Location space, write the type of
data/video endpoint, and the name of the person or the location of
the equipment.

In the Data/Video Type space, place a check mark in the 1B or 2B column
to indicate whether this endpoint uses one or two B-channels.

5

5

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Digital Data/Video Stations

4.

Issue 1
August 1998
Page 5-43

In the Digital Facilities space, enter the method used to access incoming
and outgoing facilities.
a.

b.

In the Digital Facilities In space, enter one of the following for
incoming data/video calls:
1.

If personal lines are used to receive data/video calls, enter
the line/trunk number for each personal line. For example,
801/802.

2.

If Dial Plan Routing is used to route incoming data/video calls
(PRI and T1 Switched 56 facilities only), enter Dial Plan
Routing.

3.

If Tie Line Routing is used to route incoming data/video calls
(PRI and T1 Switched 56 facilities only), enter Tie Line
Routing.

In the Digital Facilities Out space, enter one of the following for
outgoing data/video calls:
1.

If personal lines are used to place outgoing data/video calls,
enter the line/trunk number for each personal line. For
example, 801/802.

2.

If Pool Access is used to place outgoing data/video calls,
enter the pool access number. For example, 890.

3.

If Automatic Route Selection (ARS) is used to place outgoing
data/video calls, enter the ARS access code. The ARS
access code factory setting is 9.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

5

Data Communications
Digital Data/Video Stations

Issue 1
August 1998
Page 5-44

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

6

Modifications

Page 6-1

6

Modifications

6

This chapter contains instructions for adding trunks, auxiliary equipment, or more
telephones to an existing system. It includes the following:
■

The actions that you must take to add to the system

■

The interrelated options or features that you should consider

■

The forms that must be revised or completed

To modify the system, perform the following tasks:
1.

Decide what to change and identify the programming needed.

2.

Complete (or revise) the appropriate planning forms.

3.

Program the modification using instructions in System Programming.
NOTE:
If you need to modify a private network (such as adding a new switch to the
network or modifying one or more switches in the network), see the
Network Reference for information.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

6

Modifications
Preparation

Page 6-2

6

Preparation
To prepare for modifying the system:
1.

Collect the package of completed planning forms. Although you may need
to revise only one or two forms, you should have all completed forms
available for reference.

2.

Review Chapter 1, “Before You Begin,” for details on preparation for
planning activities.

3.

Before revising the forms, analyze and document the changes planned.
For example:

4.

■

If adding extensions to the system, revise the floor plan to show the
location of the new telephones and the kind of equipment to be
used.

■

If activating a feature such as System Speed Dial, survey
employees to identify the numbers that should be programmed into
the speed dial file.

Review security information in Appendix A, “Customer Support
Information,” for details on how to minimize the risk of toll fraud.

Adding to the System

6

Adding to the system is defined as increasing its capacity or capability. This
increase may mean adding more or different kinds of lines/trunks, connecting
auxiliary equipment, or installing more telephones, consoles, or T/R equipment.

Forms Needed
■

Form 1, System Planning

■

Form 2a, System Numbering: Extension Jacks

■

Form 2c, System Numbering: Line/Trunk Jacks

Planning Form Instructions
1.

Determine the specific type of line/trunk, auxiliary equipment, or
telephones to be added. Use Table 6–1 to determine the type of line/trunk
and/or extension module needed to support the additional equipment.

6

6

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

6

Modifications
Adding to the System

Table 6–1.

Page 6-3

Required Line/Trunk and/or Extension Modules

Module

100D

800
NIBRI

400
400
GS/
EM 400 LS

800
800
008
GS/
DID 800 OPT LS

800
GS/L
S-ID

408
008
GS/L 408
008 MLX 012 016 408 S
MLX

LS trunks
GS trunks
Tie trunks
DID trunks
T1 service
Emulated LS trunks
Emulated GS trunks
Emulated Tie trunks
PRI services
T1 Switched 56
service
NI-1 BRI services
Remote Access
Loudspeaker Paging
Maintenance Alarm
Music On Hold
MLX DLC
QCC
Analog DLC
MLX telephone
Analog multiline
telephone
Tip/ring equipment
Off-premises
telephone

NOTES:
1. DS1 connectivity configured for T1 operation provides 24 channels.
2. T1-Tie trunks may be configured to use Switched 56 service.
3. NI-1 BRI service provides 16 channels per 800 NI-BRI module.
4. If you are planning for Remote Access, at least one module with
touch-tone receivers (TTRs) must be installed.
5. If analog multiline telephones require either voice and data or Voice
Announce to Busy, two consecutive telephone jacks are required.
6. If you are connecting T/R equipment to the 008, 408, or 408 GS/LS
modules, a GPA is required.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

6

Modifications
Adding to the System

2.

3.

4.

Issue 1
August 1998
Page 6-4

On Form 1 (page 2), System Planning, review the completed Control Unit
Diagram and determine whether the module type needed is present. Do
one of the following:
■

If the module is not in the control unit, skip to Step 4.

■

If the module type needed is already in the control unit, proceed to
Step 3.

Determine whether there are jacks available on the module for the new
line/trunk, auxiliary equipment, or telephone by referring to Form 2a,
System Numbering: Extension Jacks, or Form 2c, System Numbering:
Line/Trunk Jacks. Do one of the following:
■

If there are sufficient jacks available on an existing module, plan to
connect the added line/trunk, equipment or telephone to them. Skip
to Step 6.

■

If no jacks are available, proceed to Step 4.

Plan the placement of the new module required to support the line/trunk,
auxiliary equipment, or telephone by reviewing the guidelines that follow
and deciding where the new module should be placed.
■

The power supply module must be placed in the far left slot of each
carrier.

■

The processor module must be installed in Slot 0 of the basic carrier.

■

Line/trunk and/or extension modules can be placed in any order in
Slots 1 through 17 (with two expansion carriers), with the following
conditions:
— Install the modules in each carrier from left to right, with no
empty slots between modules.
— If the system includes a QCC, the 008 MLX module that
supports it must be the first extension module in the control
unit.
— Place all older 008 OPT modules (Apparatus Codes
517A28–517C28) and 012 T/R modules (Apparatus Codes
from 517C13–517F13) in carriers with ring generators
installed in the power supply module. Current versions of
008 OPT modules (Apparatus Code 517D28), 012 T/R
modules [Apparatus Code 517G13(28)], and 016 T/R
modules (Apparatus Code 517A34) have built-in ring
generators and can be mixed in carriers with the older
modules that already have a generator in place.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

6

Issue 1
August 1998

Modifications
Adding to the System

5.

Page 6-5

Do one of the following:
NOTE:
Placing additional modules in the control unit requires a recalculation
of unit loads. See Appendix F, "Unit Load Calculation".
■

If the control unit has an available slot to the right, and the
guidelines permit placement there, proceed to Step 6.

■

If you must rearrange existing modules to accommodate the
new one, skip to Step 7.

6.

Revise or complete the required planning form(s) according to the
directions shown in Table 6–2, Table 6–3, and Table 6–4.

7.

If you rearrange modules in the control unit, the numbering plan reverts to
the factory-set 2-digit plan. You must then reprogram the system:
a.

Obtain a blank set of planning forms; copy them from Appendix B of
this book or order them separately.

b.

Locate the Equipment List (if available), the local telephone
company line/trunk information list, the floor plan, and the Employee
Communication Survey forms. If any of these materials have been
revised, find both the original and revised versions.

c.

Work through System Planning, beginning with Chapter 2, “Control
Unit Configuration.”

When you have completed modifying existing forms or completing new forms,
program the modification(s) following the instructions in System Programming.
Table 6–2.

Adding New Trunks

If Adding ...
Loop-start or
ground-start trunks

Complete these Forms
All columns of Form 2c, System Numbering: Line/Trunk Jacks

DS1 trunks

All Columns of Form 2c, System Numbering: Line/Trunk Jacks and
Form 3b, Incoming Trunks: DS1 Connectivity (100D Module)

NI-1 BRI trunks

All Columns of Form 2c, System Numbering: Line/Trunk Jacks and
Form 3i, Incoming Trunks: BRI Options (800 NI-BRI Module)
All columns of Form 2c, System Numbering: Line/Trunk Jacks and
Form 3c, Incoming Trunks: Tie
All columns of Form 2c, System Numbering: Line/Trunk Jacks and
Form 3d, Incoming Trunks: DID

Tie trunks
DID facilities

Consider revisions to Form 3a, Incoming Trunks: Remote Access.
Consider revisions to Form 2c, System Numbering: Line/Trunk Jacks
(labels) and Forms 3e through 3g for ARS.
Button Diagram on copies of Forms 4a through 4f, and 5a through 5d
If a personal line is assigned, consider Remote Call Forwarding.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

6

Issue 1
August 1998

Modifications
Adding to the System

Table 6–3.

Page 6-6

Adding Auxiliary Equipment

If Adding ...

Complete

Maintenance Alarm, Music On Hold,
Loudspeaker Paging

Form 2c, System Numbering: Line/Trunk Jacks

Table 6–4.

Adding New Extensions

If Adding ...

Complete

New Extensions

All columns of Form 2a, System Numbering: Extension Jacks
Copy of appropriate telephone/operator Forms 4a through 4f,
and 5a through 5d
Consider revisions to:
Group Assigned Features (Forms 7a through 7d)
Allowed and Disallowed List assignments (Forms 6e and 6f)
Night Service assignments (Forms 9a through 9c)
Extension Labels (Form 2a)

Operator console

Consider revisions to:
Optional Operator Features (Form 6a)
Extension Status assignment (Form 8a)

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Upgrading

7

Page 7-1

7

Upgrading

!

7

WARNING:
The following procedures are to be used by qualified technicians or service personnel
only. Installation or maintenance of this product by anyone other than qualified
personnel may damage or impair the product; your limited warranty does not cover
such damage. For details, see your limited warranty in Appendix A, “Customer Support
Information.”
Hazardous electrical voltages are present inside this product.
This chapter contains information about upgrading the system to Release 6.1. You
can perform the following upgrades:
■

From Release 1.0 to Release 6.1

■

From Release 1.1 to Release 6.1

■

From Release 2.0 to Release 6.1

■

From Release 2.1 to Release 6.1

■

From Release 3.0 to Release 6.1

■

From Release 3.1 to Release 6.1

■

From Release 4.0 to Release 6.1

■

From Release 4.1 to Release 6.1

■

From Release 4.2 to Release 6.1

■

From Release 5.0 to Release 6.1

■

From Release 6.0 to Release 6.1

MERLIN II Communications System programming cannot be upgraded to this
communications system. Any upgrades from MERLIN II must be considered a
new installation to MERLIN LEGEND.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

7

Upgrading
Upgrading to Release 6.1

Upgrading to Release 6.1

Page 7-2

7

This section contains an overview of upgrading from Releases 1.0, 1.1, 2.0, 2.1,
3.0, 3.1, 4.0, 4.1, 4.2, 5.0, and 6.0 to Release 6.1.

Upgrade Overview

7

To upgrade to Release 6.1, you must back up, convert, and restore system
programming information. Any version of SPM may be used to perform the
system back up. To convert and restore the system programming back up file,
SPM Version 6.25 or later must be used. You must also have (or install) a
processor module with a PCMCIA memory card slot, and a forced installation
PCMCIA memory card with Release 6.1 system software.
NOTE:
The version of SPM packaged with Intuity does not support conversion. The
most current version of SPM is available for download from NSAC.
Perform the following tasks:
1.

Back up the system programming.

2.

Install SPM Version 6.25 or later (if not already installed).

3.

Refer to Table 7–1 to determine if the backup file needs to be converted to
Release 6.1 format. If required, convert the backup file. Check the warning
messages regarding Setup Space; determine if you want to accept the files
as Setup Space or not.

4.

Power down the system.

5.

If the system already has a processor module with a PCMCIA memory card
slot installed, proceed to Step 6. Otherwise, install a new processor module
in Slot 0 then continue this procedure with Step 7.

6.

If a new processor module was installed in Step 5, go to Step 7. Otherwise,
insert a Release 6.1 forced installation memory card into the PCMCIA
memory card slot on the processor module.

7.

Power up the system. If the Release 6.1 forced installation card was
inserted in Step 6, a frigid start will occur.

8.

Restore the system programming.

9.

Program new features.

For more detailed information and procedures (including error conditions and
recovery as well as procedures for translation conversion), see Maintenance and
Troubleshooting, System Programming and Maintenance, and System
Programming.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

7

Upgrading
Upgrading to Release 6.1

Page 7-3

7

Compatibility

It is important to understand the compatibility between files created on each of the
different versions of SPM, not only for upgrading, but also for programming.
Table 7–1 summarizes programming compatibility. (It is assumed that the majority
of the programming is done in surrogate mode and backed up on disk).
Table 7–1.

Programming Compatibility

SPM
Version

Program
Backup from

Restore on
1.0
1.1
2.0/2.1

3.0

3.1

4.0

4.1/4.2

5.0

6.0

6.1

1.13

1.0

yes

no

no

no

no

no

no

no

no

no

1.16

1.0

yes

yes

no

no

no

no

no

no

no

no

2.09

1.0

yes

yes

yes1

no

no

no

no

no

no

no

2.16

1.0

yes

yes

yes*

no

no

no

no

no

no

no

3.18

1.0

yes

yes

yes*

yes*

yes* no

no

no

no

no

4.15

1.0

yes

yes

yes*

yes*

yes* yes* no

no

no

no

4.25

1.0

yes

yes

yes*

yes*

yes* yes* yes*

no

no

no

5.15

1.0

yes

yes

yes*

yes*

yes* yes* yes*

yes* no

no

6.15

1.0

yes

yes

yes*

yes*

yes* yes* yes*

yes* yes* no

6.25

1.0

yes

yes

yes*

yes*

yes* yes* yes*

yes* yes* yes*

1.16

1.1

no

yes

no

no

no

no

no

no

no

no

2.09

1.1

no

yes

yes*

no

no

no

no

no

no

no

2.16

1.1

no

yes

yes*

no

no

no

no

no

no

no

3.18

1.1

no

yes

yes*

yes*

yes* no

no

no

no

no

4.15

1.1

no

yes

yes*

yes*

yes* yes* no

no

no

no

4.25

1.1

no

yes

yes*

yes*

yes* yes* yes*

no

no

no

5.15

1.1

no

yes

yes*

yes*

yes* yes* yes*

yes* no

no

6.15

1.1

no

yes

yes*

yes*

yes* yes* yes*

yes* yes* no

6.25

1.1

no

yes

yes*

yes*

yes* yes* yes*

yes* yes* yes*

2.09

2.0

no

no

yes

no

no

no

no

no

no

no

2.16

2.0

no

no

yes

no

no

no

no

no

no

no

3.18

2.0

no

no

yes

yes*

yes* no

no

no

no

no

4.15

2.0

no

no

yes

yes*

yes* yes* no

no

no

no

4.25

2.0

no

no

yes*

yes*

yes* yes* yes*

no

no

no

5.15

2.0

no

no

yes*

yes*

yes* yes* yes*

yes* no

no

6.15

2.0

no

no

yes*

yes*

yes* yes* yes*

yes* yes* no

6.25

2.0

no

no

yes*

yes*

yes* yes* yes*

yes* yes* yes*

Continued on next page

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

7

Upgrading
Upgrading to Release 6.1

Table 7–1.

Page 7-4

Programming Compatibility (Continued)

SPM
Version

Program
Backup from

Restore on
1.0
1.1
2.0/2.1

3.0

3.1

4.0

2.16

2.1

no

no

no

no

no

no

no

no

no

no

3.18

2.1

no

no

no

yes*

yes* no

no

no

no

no

4.15

2.1

no

no

no

yes*

yes* yes* no

no

no

no

4.25

2.1

no

no

no

yes*

yes* yes* yes*

no

no

no

5.15

2.1

no

no

no

yes*

yes* yes* yes*

yes* no

no

6.15

2.1

no

no

no

yes*

yes* yes* yes*

yes* yes* no

6.25

2.1

no

no

no

yes*

yes* yes* yes*

yes* yes* yes*

3.18

3.0

no

no

no

no

no

no

4.15

3.0

no

no

no

no

no

yes* no

no

no

no

4.25

3.0

no

no

no

no

no

yes* yes*

no

no

no

5.15

3.0

no

no

no

no

no

yes* yes*

yes* no

no

6.15

3.0

no

no

no

no

no

yes* yes*

yes* yes* no

no

4.1/4.2

no

5.0

6.0

no

6.1

no

6.25

3.0

no

no

no

no

no

yes* yes*

yes* yes* yes*

3.18

3.1

no

no

no

no

no

no

no

no

no

no

4.15

3.1

no

no

no

no

no

no

no

no

no

no

4.25

3.1

no

no

no

no

yes

yes* yes*

no

no

no

5.15

3.1

no

no

no

no

yes

yes* yes*

yes* no

no

6.15

3.1

no

no

no

no

yes

yes* yes*

yes* yes* no

6.25

3.1

no

no

no

no

yes

yes* yes*

yes* yes* yes*

4.15

4.0

no

no

no

no

no

yes

no

no

no

4.25

4.0

no

no

no

no

no

yes

yes*

no

no

no

5.15

4.0

no

no

no

no

no

yes

yes*

yes* no

no

6.15

4.0

no

no

no

no

no

yes

yes*

yes* yes* no

6.25

4.0

no

no

no

no

no

yes

yes*

yes* yes* yes*

4.25

4.1/4.2

no

no

no

no

no

no

yes

no

no

no

5.15

4.1/4.2

no

no

no

no

no

no

yes

yes* no

no

6.15

4.1/4.2

no

no

no

no

no

no

yes

yes* yes* no

6.25

4.1/4.2

no

no

no

no

no

no

yes

yes* yes* yes*

5.15

5.0

no

no

no

no

no

no

no

yes

no

6.15

5.0

no

no

no

no

no

no

no

yes

yes* no

6.25

5.0

no

no

no

no

no

no

no

yes

yes* yes*

6.15

6.0

no

no

no

no

no

no

no

no

yes

6.25

6.0

no

no

no

no

no

no

no

no

yes

yes*

6.25

6.1

no

no

no

no

no

no

no

no

no

yes

1. The backup file must be converted before it is restored.

no

no

no

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

7

Upgrading
Release 6.1 Forms

Page 7-5

7

Release 6.1 Forms

Changes made to the planning forms for Release 6.1 reflect enhancements made
for Release 6.1.
Table 7–2 compares the planning forms for each major release.
Table 7–2.

Planning Forms

1.0 2.0 3.0 4.0/5.0 6.0 6.1 6.1 Form Title
N/A N/A

Employee Communication Survey

1

1

1

1

1

1

System Planning

2a

2a

2a

2a

2a

2a

System Numbering: Extension Jacks

2b

2b

2b

2b

2b

2b

System Numbering: Digital Adjuncts

2c

2c

2c

2c

2c

2c

System Numbering: Line/Trunk Jacks

2d

2d

2d

2d

2d

2d

System Numbering: Special Renumbers

2e
3a

(1.0 form, Technician’s Run Sheet now included on Form 2c)
3a

3a

3a

3a

3a

3c

3b

3b

3b

3b

3b

Incoming Trunks: DS1 Connectivity (100D Module)

3d

3c

3c

3c

3c

3c

Incoming Trunks: Tie

3e

3d

3d

3d

3d

3d

Incoming Trunks: DID

3e

3e

3e

3e

Automatic Route Selection Worksheet

3f

3f

3f

3f

Automatic Route Selection Tables

3g

3g

3g

3g

Automatic Route Selection Default and Special Numbers Tables

3h

3h

3h

3h

LS-ID Delay

3b

Incoming Trunks: Remote Access
(1.0 form, Incoming Trunks — Pools now included on Form 2a)

3i

3i

3i

Incoming Trunks: BRI Options (800 NI-BRI Module)

4a

4a

4a

4a

4a

Extension Copy: Analog Multiline Telephone Template

4b

4b

4b

4b

4b

Analog Multiline Telephone

4c

4c

4c

4c

4c

Extension Copy: MLX Telephone Template

4b

4d

4d

4d

4d

4d

MLX Telephone

4b

4e

4e

4e

4e

4e

MFM Adjunct: MLX Telephone

4c

4f

4f

4f

4f

4f

Tip/Ring Equipment

5a

5a

5a

5a

5a

5a

Direct-Line Console (DLC): Analog

5b

5b

5b

5b

5b

5b

Direct-Line Console (DLC): Digital

5b

5c

5c

5c

5c

5c

MFM Adjunct: DLC

5c

5d

5d

5d

5d

5d

Queued Call Console (QCC)

4a

Continued on next page

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

7

Upgrading
Release 6.1 Forms

Table 7–2.

Issue 1
August 1998
Page 7-6

Planning Forms (Continued)

1.0 2.0 3.0 4.0/5.0 6.0 6.1 6.1 Form Title
6a

6a

6a

6a

6a

6a

Optional Operator Features

6b

6b

6b

6b

Optional Extension Features

6c

6c

6c

6c

Principal User of Personal Line

6d

6d

6d

6d

Message-Waiting Receivers

6e

6e

6e

6e

Allowed Lists

6f

6f

6f

6f

Disallowed Lists

6g

6g

6g

6g

Call Restriction Assignments and Lists

6h

6h

6h

6h

Authorization Codes

6i

6i

6i

6i

Pool Dial-Out Code Restrictions

6b

6b

Call Pickup Groups

6c

6c

Group Paging

6d

6d

Group Coverage

6e

6e

Group Calling

6f

6f

System Features

6g

6g

Allowed Lists

6h

6h

Disallowed Lists

6i

Call Restriction Assignments and Lists

7a

7a

Night Service: Group Assignment

7b

7b

7a

7a

7a

Call Pickup Groups
Night Service: Outward Restriction

7b
7c

7a
7b

7b

7b

7c

Group Paging
Night Service: Time Set

7c

7c

7c

7c

Group Coverage

7d

7d

7d

7d

Group Calling

8a

(1.0 form, Label Form — Trunks, now included on Form 2c)
8a

8b

8a

8a

8a

System Features
(1.0 form, Label Form — Stations and Calling Groups, now
included on Form 2a)

8c

8a

Label Form: Posted Message

8d

8b

System Speed Dial

Continued on next page

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

7

Upgrading
Release 6.1 Forms

Table 7–2.

Issue 1
August 1998
Page 7-7

Planning Forms (Continued)

1.0 2.0 3.0 4.0/5.0 6.0 6.1 6.1 Form Title
9a
9b
9c

9a

Automatic Route Selection Worksheet
9a

9a

9a

9a

9b

9b

9b

9b

9b

Night Service: Group Assignment
Automatic Route Selection Tables

9c

Night Service: Outward Restriction
Automatic Route Selection Default and Special Numbers Tables

9c

9c

9c

9c

Night Service: Time Set

10a 10a

10a 10a Label Form: Posted Message

10b 10b

10b 10b System Speed Dial
11

Service Observing: Group Assignment

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

7

Upgrading
Release 6.1 Forms

Issue 1
August 1998
Page 7-8

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

A Customer Support Information
Support Telephone Number

Page A-1

Customer
A
Support Information

Support Telephone Number

A
1

In the USA only, Lucent Technologies provides a toll-tree customer Helpline
(1 800 628-2888) 24 hours a day. If you need assistance when installing,
programming, or using your system, call the Helpline or your Lucent Technologies
representative. Consultation charges may apply.
Outside the USA, if you need assistance when installing, programming, or using
your system, contact your Lucent Technologies representative.

Federal Communications Commission
(FCC) Electromagnetic Interference
Information
1
This equipment has been tested and found to comply with the limits for a Class A
digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to
provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment. This equipment generates, uses, and can
radiate radio frequency energy and, if not installed and used in accordance with
the instruction manual, may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause harmful
interference, in which case the user will be required to correct the interference at
his or her own expense.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

A Customer Support Information
Canadian Department of Communications (DOC) Interference Information

Canadian Department of
Communications (DOC)
Interference Information

Page A-2

1

This digital apparatus does not exceed the Class A limits for radio noise
emissions set out in the radio interference regulations of the Canadian
Department of Communications.
Le Présent Appareil Numérique n’émet pas de bruits radioélectriques dépassant
les limites applicables aux appareils numériques de la classe A préscrites dans le
règlement sur le brouillage radioélectrique edicté par le ministère des
Communications du Canada.

FCC Notification and
Repair Information

1

This equipment is registered with the FCC in accordance with Part 68 of its rules.
In compliance with those rules, you are advised of the following:
■

Means of Connection. Connection of this equipment to the telephone
network shall be through a standard network interface jack, USOC RJ11C,
RJ14C, RJ21X. Connection to E&M tie trunks requires a USOC RJ2GX.
Connection to off-premises extensions requires a USOC RJ11C or RJ14C.
Connection to 1.544-Mbps digital facilities must be through a USOC RJ48C
or RJ48X. Connection to DID requires a USOC RJ11C, RJ14C, or RJ21X.
These USOCs must be ordered from your telephone company. Connection
to 56-Kbps or 64-Kbps facilities requires a USOC RJ11C, RJ14C, or RJ21.

■

Party Lines and Coin Telephones. This equipment may not be used with
party lines or coin telephone lines.

■

Notification of Local Telephone Company. Before connecting this
equipment, you or your equipment supplier must notify your local telephone
company’s business office of the following:
— The telephone number(s) you will be using with this equipment

 The appropriate registration number and ringer equivalence number
(REN), which can be found on the back or bottom of the control unit,
as follows:

 If this equipment is to be used as a Key system, report the
registration number AS593M-72914-KF-E.

 If the system provides both manual and automatic selection of
incoming/outgoing access to the network, report the registration
number AS593M-72682-MF-E.

 If there are no directly terminated trunks, or if the only directly
terminated facilities are personal lines, report the registration number
AS5USA-65646-PF-E.

 The REN (Ringer Equivalence Number) for all three systems is 1.5A.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

A Customer Support Information
FCC Notification and Repair Information

Page A-3

— The facility interface code (FIC) and service order code (SOC):

 For tie line connection, the FIC is TL31M and the SOC is 9.0F.
 For connection to off-premises stations, the FIC is OL13C and the
SOC is 9.0F.

 For equipment to be connected to DID facilities, the FIC is 02RV2-T
and the SOC is AS.2.

 For equipment to be connected to 1.544-Mbps digital service, the
SOC is 6.0P and the FIC is:
— 04DU9-BN for D4 framing format with AMI zero code
suppression
— 04DU9-DN for D4 framing format with bipolar 8 zero
code suppression (B8ZS).04DU9-IKN for extended
superframe format (ESF) with AMI zero code
suppression
— 04DU9-ISN with ESF and B8ZS

 For equipment to be connected to 56-Kbps or 64-Kbps digital
facilities, the FIC is 021S5 and the SOC is 6.0Y.
— The quantities and USOC numbers of the jacks required
— For each jack, the sequence in which lines are to be connected, the line
types, the FIC, and the REN by position when applicable
■

Ringer Equivalence Number (REN). The REN is used to determine the
number of devices that may be connected to the telephone line. Excessive
RENs on the line may result in the devices not ringing in response to an
incoming call. In most, but not all, areas the sum of the RENs should not
exceed five (5.0). To be certain of the number of devices that may be
connected to the line, as determined by the total RENs, contact the local
telephone company to determine the maximum REN for the calling area.

■

Disconnection. You must also notify your local telephone company if and
when this equipment is permanently disconnected from the line(s).

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

A Customer Support Information
Installation and Operational Procedures

Installation and
Operational Procedures

Page A-4

1

The manuals for your system contain information about installation and
operational procedures.
■

Repair Instructions. If you experience trouble because your equipment is
malfunctioning, the FCC requires that the equipment not be used and that it
be disconnected from the network until the problem has been corrected.
Repairs to this equipment can be made only by the manufacturers, their
authorized agents, or others who may be authorized by the FCC. In the
event repairs are needed on this equipment, contact your authorized
Lucent Technologies dealer or, in the USA only, contact the National
Service Assistance Center (NSAC) at 1 800 628-2888.

■

Rights of the Local Telephone Company. If this equipment causes harm
to the telephone network, the local telephone company may discontinue
your service temporarily. If possible, they will notify you in advance. But if
advance notice is not practical, you will be notified as soon as possible.
You will also be informed of your right to file a complaint with the FCC.

■

Changes by the Local Telephone Company. Your local telephone
company may make changes in its facilities, equipment, operations, or
procedures that affect the proper functioning of this equipment. If they do,
you will be notified in advance to give you an opportunity to maintain
uninterrupted telephone service.

■

Hearing Aid Compatibility. The custom telephone sets for this system are
compatible with inductively coupled hearing aids, as prescribed by the
FCC.

■

Automatic Dialers. WHEN PROGRAMMING EMERGENCY NUMBERS
AND/OR MAKING TEST CALLS TO EMERGENCY NUMBERS:
— Remain on the line and briefly explain to the dispatcher the reason for
the call.
— Perform such activities in off-peak hours, such as early morning or late
evening.

■

Direct Inward Dialing (DID). This equipment returns answer supervision
signals to the PSTN when:
— Answered by the called station
— Answered by the attendant
— Routed to a recorded announcement that can be administered by the
customer premises equipment user
— Routed to a dial prompt

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

A Customer Support Information
DOC Notification and Repair Information

Page A-5

This equipment returns answer supervision on all DID calls forwarded back
to the PSTN. Permissible exceptions occur when:
— A call is unanswered
— A busy tone is received
— A reorder tone is received

Allowing this equipment to be operated in such a manner as not to provide
proper answer supervision signaling is in violation of Part 68 FCC rules.
New Network Area and Exchange Codes. The MERLIN LEGEND
Communications System software does not restrict access to any new area codes
or exchange codes established by a local telephone company. If the user has
established toll restrictions on the system that could restrict access, then the user
should check the lists of allowed and disallowed dial codes and modify them as
needed.
Equal Access Codes. This equipment is capable of providing users access to
interstate providers of operator services through the use of access codes.
Modification of this equipment by call aggregators to block access dialing codes is
a violation of the Telephone Operator Consumers Act of 1990.

DOC Notification and
Repair Information

1

NOTICE: The Canadian Department of Communications (DOC) label identifies
certified equipment. This certification means that the equipment meets certain
protective, operational, and safety requirements of the telecommunications
network. The DOC does not guarantee the equipment will operate to the user’s
satisfaction.
Before installing this equipment, users should ensure that it is permissible to
connect it to the facilities of the local telecommunications company. The
equipment must also be installed using an acceptable method of connection. In
some cases, the company’s inside wiring for single-line individual service may be
extended by means of a certified connector assembly (telephone extension cord).
The customer should be aware that compliance with the above conditions may not
prevent degradation of service in some situations.
Repairs to certified equipment should be made by an authorized Canadian
maintenance facility designated by the supplier. Any repairs or alterations made
by the user to this equipment, or any equipment malfunctions, may give the
telecommunications company cause to request the user to disconnect the
equipment.
Users should ensure for their own protection that the electrical ground
connections of the power utility, telephone lines, and internal metallic water pipe
system, if present, are connected. This precaution may be particularly important in
rural areas.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

A Customer Support Information
Renseignements sur la notification du ministère des Communications du Canada

!

Page A-6

CAUTION:
Users should not attempt to make such connections themselves, but should
contact the appropriate electrical inspection authority or electrician, as
appropriate.

To prevent overloading, the Load Number (LN) assigned to each terminal device
denotes the percentage of the total load to be connected to a telephone loop used
by the device. The termination on a loop may consist of any combination of
devices, subject only to the requirement that the total of the Load Numbers of all
the devices does not exceed 100.
DOC Certification No.: 230 4095A
CSA Certification No.: LR 56260
Load No.: 6

Renseignements sur la notification du
ministère des Communications du
Canada et la réparation
1
AVIS: L’étiquette du ministère des Communications du Canada identifie le
matériel homologué. Cette étiquette certifie que le matériel est conforme à
certaines normes de protection, d’exploitation et de sécurité des réseaux de
télécommunications. Le Ministère n’assure toutefois pas que le matériel
fonctionnera à la satisfaction de l’utilisateur.
Avant d’installer ce matériel, l’utilisateur doit s’assurer qu’il est permis de le
raccorder aux installations de l’entreprise locale de télécommunication. Le
matériel doit également être installé en suivant une méthode acceptée de
raccordement. Dans certains cas, les fils intérieurs de l’enterprise utilisés pour un
service individuel à ligne unique peuvent être prolongés au moyen d’un dispositif
homologué de raccordement (cordon prolongateur téléphonique interne).
L’abonné ne doit pas oublier qu’il est possible que la conformité aux conditions
énoncées ci-dessus n’empêchent pas la dégradation du service dans certaines
situations. Actuellement, les entreprises de télécommunication ne permettent pas
que l’on raccorde leur matériel à des jacks d’abonné, sauf dans les cas précis
prévus pas les tarifs particuliers de ces entreprises.
Les réparations de matériel homologué doivent être effectuées par un centre
d’entretien canadien autorisé désigné par le fournisseur. La compagnie de
télécommunications peut demander à l’utilisateur de débrancher un appareil à la
suite de réparations ou de modifications effectuées par l’utilisateur ou à cause de
mauvais fonctionnement.
Pour sa propre protection, l’utilisateur doit s’assurer que tous les fils de mise à la
terre de la source d’énergie électrique, des lignes téléphoniques et des
canalisations d’eau métalliques, s’il y en a, sont raccordés ensemble. Cette
précaution est particuliérement importante dans les régions rurales.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

A Customer Support Information
Renseignements sur la notification du ministère des Communications du Canada

Page A-7

AVERTISSEMENT: L’utilisateur ne doit pas tenter de faire ces raccordements
lui-même; il doit avoir recours à un service d’inspection des installations
électriques, ou à un électricien, selon le cas.
L’indice de charge (IC) assigné à chaque dispositif terminal indique, pour éviter
toute surcharge, le pourcentage de la charge totale qui peut être raccordée à un
circuit téléphonique bouclé utilisé par ce dispositif. La terminaison du circuit
bouclé peut être constituée de n’importe quelle combinaison de dispositifs, pourvu
que la somme des indices de charge de l’ensemble des dispositifs ne dépasse
pas 100.
No d’homologation: 230 4095A
No de certification: CSA LR 56260
L’indice de charge: 6

MADE IN U.S.A.

This digital apparatus does not exceed the Class A limits for radio
noise emissions set out in the radio interference reguations of the
Canadian Department of Communications.
Le présent appareil numérique n’émet pas de bruits radioélectriques
dépassant les limites applicables aux appareils numériques de la
classe A prescrites dans le Règlement sur le brouillage
radioélectrique édicté par le ministère Communications du Canada.

LR 56260

WARNING: If equipment is used for
out–of–building applications, approved
secondary protectors are required. See
Installation Manual.

AVERTISSEMENT: Si l’equipment est utilisé
pour des applications extérieures,
l’installation d’un protector secondair est
requise. Voir le manuel d’Installation.

CANADA

DR ID

Ministère des Communications
du Canada emplacement de
l’étiquette

Use only Lucent Technologies manufactured MERLIN LEGEND
circuit modules, carrier assemblies, and power units, as specified in
the Installation Manual, in this product. There are no user
serviceable parts inside. Contact your authorized agent for service
and repair.

®

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

TELEPHONE
EQUIPMENT

Complies with Part 68, FCC Rules. See the SystemReference
Manual for proper FCC Classification.
FCC Reg. Nos. MF: AS593M-72682-MF-E
KF: AS593M-72914-KF-E
PF: AS5USA-65646-PF-E
REN: 1.5A

Renseignements sur la notification du ministère des Communications du Canada

UL
®

LISTED
538E

A Customer Support Information

Model 511A Control Unit

This device complies with Part 15 of the FCC Rules. Operation is
subject to the following two conditions: (1) this device may not
cause harmful interference, and (2) this device must accept any
interference received, including interference that may cause
undesired operation.

MERLIN LEGEND D.O.C.
Location Label Placement

MERLIN LEGEND

Issue 1
August 1998

Page A-8

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

A Customer Support Information
Security of Your System: Preventing Toll Fraud

Security of Your System:
Preventing Toll Fraud

Page A-9

1

As a customer of a new telephone system, you should be aware that there is an
increasing problem of telephone toll fraud. Telephone toll fraud can occur in many
forms, despite the numerous efforts of telephone companies and telephone
equipment manufacturers to control it. Some individuals use electronic devices to
eliminate or falsify records of these calls. Others charge calls to someone else’s
number by illegally using lost or stolen calling cards, billing innocent parties,
clipping on to someone else’s line, or breaking into someone else’s telephone
equipment physically or electronically. In certain instances, unauthorized
individuals make connections to the telephone network through the use of the
Remote Access features of your system.
The Remote Access features of your system, if you choose to use them, permit
off-premises callers to access the system from a remote telephone by using a
telephone number with or without a barrier code. The system returns an
acknowledgment signaling the user to key in his or her barrier code, which is
selected and administered by the system manager. After the barrier code is
accepted, the system returns dial tone to the user. In Release 3.1 and later
systems, barrier codes are by default restricted from making outside calls. In prior
releases, if you do not program specific outward calling restrictions, the user is
able to place any call normally dialed from a telephone associated with the
system. Such an off-premises network call is originated at, and will be billed from,
the system location.
The Remote Access feature, as designed, helps the customer, through proper
administration, to minimize the ability of unauthorized persons to gain access to
the network. Most commonly, phone numbers and codes are compromised when
overheard in a public location, through theft of a wallet or purse containing access
information, or through carelessness (for example, writing codes on a piece of
paper and improperly discarding it). Additionally, hackers may use a computer to
dial an access code and then publish the information to other hackers. Enormous
charges can be run up quickly. It is the customer’s responsibility to take the
appropriate steps to properly implement the features, evaluate and administer the
various restriction levels, protect access codes, and distribute access codes only
to individuals who have been fully advised of the sensitive nature of the access
information.
Common carriers are required by law to collect their tariffed charges. While these
charges are fraudulent charges made by persons with criminal intent, applicable
tariffs state that the customer of record is responsible for payment of all
long-distance or other network charges. Lucent Technologies cannot be
responsible for such charges and will not make any allowance or give any credit
for charges that result from unauthorized access.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

A Customer Support Information
Toll Fraud Prevention

Page A-10

To minimize the risk of unauthorized access to your communications system:
■

Use an unpublished Remote Access number.

■

Assign access codes randomly to users on a need-to-have basis, keeping
a log of all authorized users and assigning one code to one person.

■

Use random-sequence access codes, which are less likely to be easily
broken.

■

Use the longest-length access codes the system allows.

■

Deactivate all unassigned codes promptly.

■

Ensure that Remote Access users are aware of their responsibility to keep
the telephone number and any access codes secure.

■

When possible, restrict the off-network capability of off-premises callers,
using calling restrictions, Facility Restriction Levels (FRLs) (Hybrid/PBX
mode only), and Disallowed List capabilities. In Release 3.1 and later
systems, a prepared Disallowed List (number 7) is provided and is
designed to prevent the types of calls that toll-fraud abusers often make.

■

When possible, block out-of-hours calling.

■

Frequently monitor system call detail reports for quicker detection of any
unauthorized or abnormal calling patterns.

■

Limit Remote Call Forwarding to persons on a need-to-have basis.

■

Change access codes every 90 days.

■

Use the longest-length barrier codes possible, following the guidelines for
passwords. (See See “Choosing Passwords” on page A–19.)

Toll Fraud Prevention

1

Toll fraud is the unauthorized use of your telecommunications system by third
parties to make long-distance telephone calls. Under the law, you, the customer,
are responsible for paying part or all of those unauthorized calls. Thus, the
following information is of critical importance.
Unauthorized persons concentrate their activities in two areas with the MERLIN
LEGEND Communications System:
■

They try to transfer out of the MERLIN LEGEND Communications System
to gain access to an outgoing trunk and make long-distance calls.

■

They try to locate unused or unprotected mailboxes and use them as
drop-off points for their own messages.

The following is a discussion of how toll fraud is often perpetrated and ways to
prevent unauthorized access that can lead to toll fraud.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

A Customer Support Information
Toll Fraud Prevention

Physical Security, Social Engineering, and
General Security Measures

Page A-11

1

Criminals called hackers may attempt to gain unauthorized access to your
communications system and voice messaging system in order to use the system
features. Hackers often attempt to trick employees into providing them with
access to a network facility (line/trunk) or a network operator. This is referred to as
social engineering. Hackers may pose as telephone company employees and
employees of Lucent Technologies or your authorized dealer. Hackers will go
through a company’s trash to find directories, dialing instructions, and other
information that will enable them to break into the system. The more
knowledgeable they appear to be about the employee names, departments,
telephone numbers, and the internal procedures of your company, the more likely
it is that they will be able to trick an employee into helping them.

Preventive Measures

1

Take the following preventive measures to limit the risk of unauthorized access by
hackers:
■

Provide good physical security for the room containing your
telecommunications equipment and the room with administrative tools,
records, and system manager information. These areas should be locked
when not attended.

■

Provide a secure trash disposal for all sensitive information, including
telephone directories, call accounting records, or anything that may supply
information about your communications system. This trash should be
shredded.

■

Educate employees that hackers may try to trick them into providing them
with dial tone or dialing a number for them. All reports of trouble, requests
for moving extensions, or any other administrative details associated with
the MERLIN LEGEND Communications System should be handled by one
person (the system manager) or within a specified department. Anyone
claiming to be a telephone company representative should be referred to
this person or department.

■

No one outside of Lucent Technologies needs to use the MERLIN
LEGEND Communications System to test facilities (lines/trunks). If a caller
identifies him- or herself as a Lucent Technologies employee, the system
manager should ask for a telephone number where the caller can be
reached. The system manager should be able to recognize the number as
a Lucent Technologies telephone number. Before connecting the caller to
the administrative port of the MERLIN LEGEND Communications System,
the system manager should feel comfortable that a good reason to do so
exists. In any event, it is not advisable to give anyone access to network
facilities or operators, or to dial a number at the request of the caller.

■

Any time a call appears to be suspicious, call the Lucent Technologies BCS
Fraud Intervention Center at 1 800 628-2888 (fraud intervention for
System 25, PARTNER® and MERLIN systems).

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

A Customer Support Information
Toll Fraud Prevention
■

Page A-12

Customers should also take advantage of Lucent Technologies monitoring
SM
services and devices, such as the NetPROTECT family of
®
fraud-detection services, CAS with HackerTracker , and CAT Terminal with
Watchdog. Call 1 800 638-7233 to get more information on these Lucent
Technologies fraud detection services and products.

Security Risks Associated with Transferring
through Voice Messaging Systems

1

Toll fraud hackers try to dial into a voice mailbox and then execute a transfer by
dialing
7. The hacker then dials an access code (either  for Automatic Route
Selection or a pooled facility code) followed by the appropriate digit string to either
direct dial or access a network operator to complete the call.
NOTE:
In Release 3.1 and later systems, all extensions are initially and by default
restricted from dial access to pools. In order for an extension to use a pool
to access an outside line/trunk, this restriction must be removed.

1

Preventive Measures

Take the following preventive measures to limit the risk of unauthorized transfers
by hackers:
■

Outward restrict all MERLIN LEGEND Communications System voice mail
port extension numbers. This denies access to facilities (lines/trunks). In
Release 3.1 and later systems, voice mail ports are by default outward
restricted.

■

As an additional security step, network dialing for all extensions, including
voice mail port extensions, should be processed through ARS using dial
access code.

!

SECURITYlALERT:
The MERLIN LEGEND Communications System ships with ARS
activated with all extensions set to FRL 3, allowing all international
calling. To prevent toll fraud, ARS FRLs should be established
using:
■

FRL 0 for restriction to internal dialing only

■

FRL 2 for restriction to local network calling only

■

FRL 3 for restriction to domestic long-distance (excluding
area code 809 for the Dominican Republic as this is part of
the North American Numbering Plan, unless 809 is required)

■

FRL 4 for international calling

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

A Customer Support Information
Toll Fraud Prevention

Page A-13
■

In Release 3.1 and later systems, default local and default toll
tables are factory-assigned an FRL of 2. This simplifies the
task of restricting extensions: the FRL for an extension
merely needs to be changed from the default of 3.

■

Each extension should be assigned the appropriate FRL to
match its calling requirements. All voice mail port extensions
not used for Outcalling should be assigned to FRL 0 (the
default setting in Release 3.1 and later).

■

Deny access to pooled facility codes by removing pool dial-out codes 70,
890-899, or any others on your system.

■

Create a Disallowed List or use the pre-prepared Disallowed List number 7
(Release 3.1 and later systems only) to disallow dialing 0, 11, 10, 1700,
1809, 1900, and 976 or 1(wildcard)976. In Release 3.1 and later systems,
Disallowed List number 7 does not include 800 and 1800 and 411 and
1411, but Lucent Technologies recommends that you add them. Assign all
voice mail port extensions to this Disallowed List. Lucent
Technologies recommends assigning Disallowed List number 7. This
is an added layer of security, in case outward restriction is
inadvertently removed. (In Release 3.1 and later systems, voice
messaging ports are assigned by default to Disallowed List number 7.)

If Outcalling is required by voice messaging system extensions:
■

Program an ARS FRL of 2 on voice mail port extension(s) used for
Outcalling.

■

If 800 and 411 numbers are used, remove 1800, 800, 411, and 1411 from
Disallowed List number 7.

■

If Outcalling is allowed to long-distance numbers, build an Allowed List for
the voice mail port extension(s) used for Outcalling. This list should contain
the area code and the first three digits of the local exchange telephone
numbers to be allowed.

Additional general security for voice messaging systems:
■

Use a secure password for the General Mailboxes.

■

The default administration mailbox, 9997, must be reassigned to the
system manager’s mailbox/extension number and securely password
protected.

■

All voice messaging system users must use secure passwords known only
to the user.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

A Customer Support Information
Toll Fraud Prevention

Security Risks Associated with the Automated
Attendant Feature of Voice Messaging Systems

Page A-14

1

Two areas of toll fraud risk associated with the Automated Attendant feature of
voice messaging systems are the following:
■

Pooled facility (line/trunk) access codes are translated to a menu prompt to
allow Remote Access. If a hacker finds this prompt, the hacker has
immediate access. (In Release 3.1 and later systems, dial access to pools
is initially factory-set to restrict all extensions: to allow pool access, this
restriction must be removed by the system manager.)

■

If the Automated Attendant prompts callers to use Remote Call Forwarding
(RCF) to reach an outside telephone number, the system may be
susceptible to toll fraud. An example of this application is a menu or
submenu that says, “To reach our answering service, select prompt
number 5,” and transfers a caller to an external telephone number.
Remote Call Forwarding can be used securely only when the central office
provides “reliable disconnect” (sometimes referred to as forward
disconnect or disconnect supervision), which guarantees that the central
office does not return a dial tone after the called party hangs up. In most
cases, the central office facility is a loop-start line/trunk which does not
provide reliable disconnect. When loop-start lines/trunks are used, if the
calling party stays on the line, the central office does return a dial tone at
the conclusion of the call, enabling the caller to place another call as if it
were being placed from your company. Ground-start trunks provide reliable
disconnect and should be used whenever possible.

Preventive Measures

1

Take the following preventive measures to limit the risk of unauthorized use of the
Automated Attendant feature by hackers:
■

Do not use Automated Attendant prompts for ARS Codes or Pooled Facility
Codes.

■

Assign all unused Automated Attendant Selector Codes to zero, so that
attempts to dial these are routed to the system attendant.

■

If Remote Call Forwarding (RCF) is required, MERLIN LEGEND
Communications System owners should coordinate with their Lucent
Technologies Account Team or authorized dealer to verify the type of
central office facility used for RCF. If it is a ground-start line/trunk, or if it is a
loop-start line/trunk and central office reliable disconnect can be ensured,
then nothing else needs to be done.
NOTE:
In most cases these are loop-start lines/trunks without reliable disconnect.
The local telephone company must be involved in order to change the
facilities used for RCF to ground start lines/trunks. Usually a charge applies
for this change. Also, hardware and software changes may be necessary in

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

A Customer Support Information
Toll Fraud Prevention

Page A-15

the MERLIN LEGEND Communications System. The MERLIN MAIL
MERLIN and MERLIN LEGEND MAIL Automated Attendant feature
merely accesses the RCF feature in the MERLIN LEGEND
Communications System. Without these changes being made, this feature
is highly susceptible to toll fraud. These same preventive measures must
be taken if the RCF feature is active for MERLIN LEGEND
Communications System extensions whether or not it is accessed by an
Automated Attendant menu.

Security Risks Associated with the Remote
Access Feature

1

Remote Access allows the MERLIN LEGEND Communications System owner to
access the system from a remote telephone and make an outgoing call or perform
system administration, using the network facilities (lines/trunks) connected to the
MERLIN LEGEND Communications System. Hackers, scanning the public
switched network by randomly dialing numbers with war dialers (a device that
randomly dials telephone numbers, including 800 numbers, until a modem or dial
tone is obtained), can find this feature, which will return a dial tone to them. They
can even employ war dialers to attempt to discover barrier codes.

Preventive Measures

1

Take the following preventive measures to limit the risk of unauthorized use of the
MERLIN LEGEND Communications System Remote Access feature by hackers:
■

The Remote Access feature can be abused by criminal toll fraud hackers, if
it is not properly administered. Therefore, this feature should not be used
unless there is a strong business need.

■

It is strongly recommended that customers invest in security adjuncts,
which typically use one-time passcode algorithms. These security adjuncts
discourage hackers. Since a secure use of the Remote Access feature
generally offers savings over credit-card calling, the break-even period can
make the investment in security adjuncts worthwhile.

■

If a customer chooses to use the Remote Access feature without a security
adjunct, then multiple barrier codes should be employed, with one per user
if the system permits. The MERLIN LEGEND Communications System
permits a maximum of 16 barrier codes.

■

The maximum length should be used for each barrier code, and should be
changed periodically. Barrier codes, like passwords, should consist of a
random, hard-to-guess sequence of digits. While MERLIN LEGEND
Communications System Release 3.0 permits a barrier code of up to 11
digits, systems prior to Release 3.0 permit barrier codes of up to only four
digits.

If Remote Access is used, an upgrade to MERLIN LEGEND Communications
System Release 3.0 is encouraged to take advantage of the longer barrier code.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

A Customer Support Information
Other Security Hints

Other Security Hints

Page A-16

1

Make sure that the Automated Attendant Selector Codes do not permit outside
line selection.
Multiple layers of security are always recommended to keep your system secure.
Following are a number of measures and guidelines that can help you ensure the
security of your communications system and voice messaging system.

Educating Users

1

Everyone in your company who uses the telephone system is responsible for
system security. Users and attendants/operators need to be aware of how to
recognize and react to potential hacker activity. Informed people are more likely to
cooperate with security measures that often make the system less flexible and
more difficult to use.
■

Never program passwords or authorization codes onto Auto Dial buttons.
Display telephones reveal the programmed numbers and internal abusers
can use the Auto Dial buttons to originate unauthorized calls.

■

Discourage the practice of writing down barrier codes or passwords. If a
barrier code or password needs to be written down, keep it in a secure
place and never discard it while it is active.

■

Instruct operators and attendants to tell their system manager when they
answer a series of calls where there is silence on the other end or the caller
hangs up.

■

Advise users who are assigned voice mailboxes to frequently change
personal passwords and not to choose obvious passwords.

■

Ensure that the system manager advises users with special telephone
privileges (such as Remote Access, Outcalling, and Remote Call
Forwarding) of the potential risks and responsibilities.

■

Be suspicious of any caller who claims to be with the telephone company
and wants to check an outside line. Ask for a callback number, hang up,
and confirm the caller’s identity.

■

Never distribute the office telephone directory to anyone outside the
company; be careful when discarding it (shred the directory).

■

Never accept collect telephone calls.

■

Never discuss your telephone system’s numbering plan with anyone
outside the company.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

A Customer Support Information
Other Security Hints

Educating Operators

Page A-17

1

Operators and attendants need to be especially aware of how to recognize and
react to potential hacker activity. To defend against toll fraud, operators should
follow the guidelines below:
■

Establish procedures to counter social engineering. Social engineering is a
con game that hackers frequently use to obtain information that may help
them gain access to your communications system or voice messaging
system.

■

When callers ask for assistance in placing outside or long-distance calls,
ask for a callback extension.

■

Verify the source. Ask callers claiming to be maintenance or service
personnel for a callback number. Never transfer to *10 without this
verification. Never transfer to extension 900.

■

Remove the headset and/or handset when the console is not in use.

Detecting Toll Fraud

1

To detect toll fraud, users and operators should look for the following:
■

Lost voice mail messages, mailbox lockout, or altered greetings

■

Inability to log into voice mail

■

Inability to get an outside line

■

Foreign language callers

■

Frequent hang-ups

■

Touch-tone sounds

■

Caller or employee complaints that the lines are busy

■

Increases in internal requests for assistance in making outbound calls
(particularly international calls or requests for dial tone)

■

Outsiders trying to obtain sensitive information

■

Callers claiming to be the “phone” company

■

Sudden increase in wrong numbers

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

A Customer Support Information
Other Security Hints

Establishing a Policy

Page A-18

1

As a safeguard against toll fraud, follow these guidelines for your MERLIN
LEGEND Communications System and voice messaging system:
■

Change passwords frequently (at least quarterly). Changing passwords
routinely on a specific date (such as the first of the month) helps users to
remember to do so.

■

Always use the longest-length password allowed.

■

Establish well-controlled procedures for resetting passwords.

■

Limit the number of invalid attempts to access a voice mailbox to five or
less.

■

Monitor access to the MERLIN LEGEND Communications System dial-up
maintenance port. Change the access password regularly and issue it only
to authorized personnel. Disconnect the maintenance port when not in use.
(However, this eliminates Lucent Technologies’ 24-hour maintenance
surveillance capability and may result in additional maintenance costs.)

■

Create a communications system management policy concerning
employee turnover and include these suggestions:
— Delete all unused voice mailboxes in the voice mail system.
— If a terminated employee had Remote Access calling privileges and a
personal authorization code, remove the authorization code
immediately.
— If barrier codes and/or authorization codes were shared by the
terminated employee, these should be changed immediately.

■

Regularly back up your MERLIN LEGEND Communications System files to
ensure a timely recovery should it be required. Schedule regular, off-site
backups.

■

Keep the Remote Maintenance Device turned off when not in use by
Lucent Technologies or your authorized dealer.

■

Limit transfers to registered subscribers only.

■

Use the Security Violations Notification options (Mailbox Lock or Warning
Message) to alert you of any mailbox break-in attempts. Investigate all
incidents.

■

Review security policies and procedures and keep them up-to-date.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

A Customer Support Information
Other Security Hints

Choosing Passwords

Page A-19

1

Passwords should be the maximum length allowed by the system.
Passwords should be hard to guess and should not contain:
■

All the same numbers (for example, 1111, 666666)

■

Sequential characters (for example 123456)

■

Numbers that can be associated with you or your business, such as your
name, birthday, business name, business address, telephone number, or
social security number.

■

Words or commonly used names.

Passwords should be changed regularly, at least on a quarterly basis. Recycling
old passwords is not recommended. Never program passwords (or authorization
codes or barrier codes) onto a speed dial button.

Improving Physical Security

1

You should always limit access to the system console (or attendant console) and
supporting documentation. The following are some recommendations:
■

Keep the system console and supporting documentation in an office that is
secured with a changeable combination lock. Provide the combination only
to those individuals having a real need to enter the office.

■

Keep telephone wiring closets and equipment rooms locked.

■

Keep telephone logs and printed reports in locations that only authorized
personnel can enter.

■

Design distributed reports so they do not reveal password or trunk access
code information.

■

Keep the voice messaging system Remote Maintenance Device turned off.

Limiting Outcalling

1

When Outcalling is used to contact subscribers who are off-site, use the MERLIN
LEGEND Communications System Allowed Lists and Disallowed Lists or
Automatic Route Selection features to minimize toll fraud.
If the Outcalling feature will not be used, outward restrict all voice messaging
system ports. If Outcalling will be used, ports not used for Outcalling should be
Outward Restricted (for MERLIN MAIL Voice Messaging Systems, port 2 on a
2-port system, port 4 on a 4-port system, ports 5 and 6 on a 6-port system; for
MERLIN LEGEND MAIL Voice Messaging Systems, port 7 of the system’s
module). Use Outward Restriction, Toll Restrictions, Allowed Lists, Disallowed
Lists and Facility Restrictions Levels, as appropriate, to minimize the possibility of
toll fraud.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

A Customer Support Information
Limited Warranty and Limitation of Liability

Limited Warranty and
Limitation of Liability

Page A-20

1

Lucent Technologies warrants to you, the customer, that your MERLIN LEGEND
Communications System will be in good working order on the date Lucent
Technologies or its authorized reseller delivers or installs the system, whichever is
later (“Warranty Date”). If you notify Lucent Technologies or its authorized reseller
within one year of the Warranty Date that your system is not in good working
order, Lucent Technologies will without charge to you repair or replace, at its
option, the system components that are not in good working order. Repair or
replacement parts may be new or refurbished and will be provided on an
exchange basis. If Lucent Technologies determines that your system cannot be
repaired or replaced, Lucent Technologies will remove the system and, at your
option, refund the purchase price of your system, or apply the purchase price
towards the purchase of another Lucent Technologies system.
If you purchased your system directly from Lucent Technologies, Lucent
Technologies will perform warranty repair in accordance with the terms and
conditions of the specific type of Lucent Technologies maintenance coverage you
selected. If you purchased your system from a Lucent Technologies-authorized
reseller, contact your reseller for the details of the maintenance plan applicable to
your system.
This Lucent Technologies limited warranty covers damage to the system caused
by power surges, including power surges due to lightning.
The following will not be deemed to impair the good working order of the system,
and Lucent Technologies will not be responsible under the limited warranty for
damages resulting from:
■

Failure to follow Lucent Technologies’ installation, operation, or
maintenance instructions

■

Unauthorized system modification, movement, or alteration

■

Unauthorized use of common carrier communications services accessed
through the system

■

Abuse, misuse, or negligent acts or omissions of the customer and persons
under the customer’s control

■

Acts of third parties and acts of God

LUCENT TECHNOLOGIES’ OBLIGATION TO REPAIR, REPLACE, OR REFUND
AS SET FORTH ABOVE IS YOUR EXCLUSIVE REMEDY.
EXCEPT AS SPECIFICALLY SET FORTH ABOVE, LUCENT TECHNOLOGIES,
ITS AFFILIATES, SUPPLIERS, AND AUTHORIZED RESELLERS MAKE NO
WARRANTIES, EXPRESS OR IMPLIED, AND SPECIFICALLY DISCLAIM ANY
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

A Customer Support Information
Remote Administration and Maintenance

Limitation of Liability

Page A-21

1

Except as provided below, the liability of Lucent Technologies and its affiliates and
suppliers for any claims, losses, damages, or expenses from any cause
whatsoever (including acts or omissions of third parties), regardless of the form of
action, whether in contract, tort, or otherwise, shall not exceed the lesser of:
(1) the direct damages proven; or (2) the repair cost, replacement cost, license
fee, annual rental charge, or purchase price, as the case may be, of the
equipment that gives rise to the claim. Except as provided below, Lucent
Technologies and its affiliates and suppliers shall not be liable for any incidental,
special, reliance, consequential, or indirect loss or damage incurred in connection
with the equipment. As used in this paragraph, consequential damages include,
but are not limited to, the following: lost profits, lost revenues, and losses arising
out of unauthorized use (or charges for such use) of common carrier
telecommunications services or facilities accessed through or connected to the
equipment. For personal injury caused by Lucent Technologies’s negligence,
Lucent Technologies’s liability shall be limited to proven damages to person. No
action or proceeding against Lucent Technologies or its affiliates or
suppliers may be commenced more than twenty-four (24) months after the
cause of action accrues. THIS PARAGRAPH SHALL SURVIVE FAILURE OF
AN EXCLUSIVE REMEDY.

Remote Administration
and Maintenance

1

The Remote Administration and Maintenance feature of your telecommunications
system, if you choose to use it, permits users to change the system features and
capabilities from a remote location.
The Remote Administration and Maintenance feature, through proper
administration, can help you reduce the risk of unauthorized persons gaining
access to the network. However, telephone numbers and access codes can be
compromised when overheard in a public location, or lost through theft of a wallet
or purse containing access information or through carelessness (for example,
writing codes on a piece of paper and improperly discarding them). Additionally,
hackers may use a computer to dial an access code and then publish the
information to other hackers. Substantial charges can accumulate quickly. It is
your responsibility to take appropriate steps to implement the features properly,
evaluate and administer the various restriction levels, and protect and carefully
distribute access codes.
Under applicable tariffs, you will be responsible for payment of toll charges.
Lucent Technologies cannot be responsible for such charges and will not make
any allowance or give any credit resulting from unauthorized access.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

A Customer Support Information
Remote Administration and Maintenance

Page A-22

To reduce the risk of unauthorized access through Remote Administration and
Maintenance, please observe the following procedures:
■

The System Administration and Maintenance capability of a Hybrid/PBX or
Key system is protected by a password.
— Change the default password immediately.
— Continue to change the password regularly.
— Give the password only to people who need it and impress upon them
the need to keep it secret.
— If anyone who knows the password leaves the company, change the
password immediately.

■

If you have a special telephone line connected to your Hybrid/PBX or Key
system for Remote Administration and Maintenance, you should do one of
the following:
— Unplug the line when it is not being used.
— Install a switch in the line to turn it off when it is not being used.
— Keep the Remote Administration and Maintenance telephone number
secret. Give it only to people who need to know it, and impress upon
them the need to keep it a secret. Do not write the telephone number on
the Hybrid/PBX or Key system, the connecting equipment, or anywhere
else in the system room.

If your Remote Administration and Maintenance feature requires that someone in
your office transfer the caller to the Remote Administration and Maintenance
extension, you should impress upon your employees the importance of
transferring only authorized individuals to that extension.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

B System Forms
Page B-1

B

System Forms

B

This appendix contains one copy of each system planning form. The forms are in
numerical order and organized according to planning purpose as shown in Table
B–1. You should make copies of these forms and use the copies, keeping the
originals for future use. Planning forms for data communications are contained in
Appendix C. The T1/PRI Planner is contained in Appendix D. The NI-1 BRI
Planner is contained in Appendix G. The Network Engineering forms are
contained in Appendix I.
Table B–1.

System Forms

Used for Planning

Form No.

Features and Calling
Privileges

N/A

Form Title
Employee Communication Survey

Control Unit Assembly
and Operating Conditions

1

System Planning

System Component
Numbering

2a

System Numbering: Extension Jacks

2b

System Numbering: Digital Adjuncts

2c

System Numbering: Line/Trunk Jacks

2d

System Numbering: Special Renumbers

3a

Incoming Trunks: Remote Access

3b

Incoming Trunks: DS1 Connectivity
(100D Module)

3c

Incoming Trunks: Tie

Incoming Line/Trunk
Connections

Continued on next page

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

B System Forms
Page B-2

Table B–1.

System Forms (Continued)

Used for Planning
Incoming Line/Trunk
Connections (Continued)

Form No. Form Title
3d

Incoming Trunks: DID

3e

Automatic Route Selection Worksheet

3f

Automatic Route Selection Tables

3g

Automatic Route Selection Default and
Special Numbers Tables

3h

LS-ID Delay

3i

Incoming Trunks: BRI Options

4a

Extension Copy: Analog Multiline
Telephone Template

4b

Analog Multiline Telephone

4c

Extension Copy: MLX Telephone Template

4d

MLX Telephone

4e

MFM Adjunct: MLX Telephone

4f

Tip/Ring Equipment

5a

Direct-Line Console (DLC): Analog

5b

Direct-Line Console (DLC): Digital

5c

MFM Adjunct: DLC

5d

Queued Call Console (QCC)

Features for Operators

6a

Optional Operator Features

Features for User Groups

6b

Optional Extension Features

6c

Principal User of Personal Line

6d

Message-Waiting Receivers

6e

Allowed Lists

Features for Systemwide Use

6f

Disallowed Lists

6g

Call Restriction Assignments and Lists

6h

Authorization Codes

6i

Pool Dial-Out Code Restrictions

7a

Call Pickup Groups

7b

Group Paging

7c

Group Coverage

7d

Group Calling

8a

System Features

9a

Night Service: Group Assignment

9b

Night Service: Outward Restriction

9c

Night Service: Time Set

10a

Label Form: Posted Message

10b

System Speed Dial

11

Service Observing: Group Assignment

MERLIN LEGEND® Communications System Release 6.1
Employee Communication Survey

Name _______________________________________ Room _______________ Extension ______________
Name of work group (Sales, Customer Service, etc.) _____________________________________________
Please answer each question below.
1. Do you regularly use any of the following outside lines? (Check any that apply)
❑ WATS
❑ FX (foreign exchange)
❑ Tie
❑ None of the above or donÕt know
2. Are your phone calls covered when youÕre away from your desk?
❑ No
❑ Yes
By whom?
_________________________________________________________________
_________________________________________________________________
3. Do you want your phone number to appear on another personÕs phone for screening, or covering calls, or
for any other reasons?
❑ No
❑ Yes
Please list these people:
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
4. Do you cover phone calls for co-workers when they are away from their desks?
❑ No
❑ Yes
For whom? ________________________________________________________________
________________________________________________________________
Which of those people should have a button on your phone used
exclusively for his or her calls?
________________________________________________________________
________________________________________________________________
When you are unable to cover calls, it is done by ____________________
________________________________________________________________

Form ECS-1

MERLIN LEGEND® Communications System Release 6.1
Employee Communication Survey

5. Is there a group of people with whom you share responsibilities such that is would be convenient if you
could answer each otherÕs calls?
❑ No
❑ Yes
With whom?
_______________________________________________________________
_______________________________________________________________
6. Would you say your phone use is
❑ Heavy
❑ Average
❑ Light
Do you need to handle more than two calls at time?
If yes, how many? ________________________
7. Do you have a data terminal or personal computer at your workstation?
❑ No
Do you expect to get one within the next year?
❑ No
❑ Yes
8. Do you use account codes for charge-back of calls?
❑ No
❑ Yes
Please list all the codes you use (attach another sheet if necessary):
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
9. Are there numbers that you and other people in your organization dial over and over every day?
❑ No
❑ Yes
Please list these numbers:
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
10. Do you want to be able to pick up other peopleÕs calls when you hear their phones ring?
❑ No
❑ Yes
Please list these people:
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________

Form ECS-2

MERLIN LEGEND® Communications System Release 6.1
Employee Communication Survey

11. Do you need to view incoming caller information?
❑ No
❑ Yes
For what purpose? ___________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________

Form ECS-3

MERLIN LEGEND® Communications System Release 6.1
Employee Communication Survey

Form ECS-4

MERLIN LEGEND® Communications System Release 6.1

Form 1
System Planning
Line/Trunk Capacity*
Module
Type

Trunks
Supported
by Module

Number of
Modules

400 LS/TTR¶

x

4

800

x

8

408

x

4

400 GS/LS/TTR

x

4

800 GS/LS

x

8

408 GS/LS

x

4

408 GS/LS-MLX

x

4

400EM

x

4

†

x

8

100D

x

24

800 GS/LS-ID

x

8

800 NI-BRI**

x

16

800 DID

Total Trunks
by Module
Type

System Totals
Extension Capacity*
Number of
Modules

Module
Type

Physical
Jacks per
Module

Physical
Jacks by
Module Type

Extensions
Assigned

008 MLX

x

8

x

2

008 ATL

x

8

x

1

¶

x

8

x

1

408 GS/LS

x

8

x

1

408 GS/LS-MLX

x

8

x

2

012

x

12

x

1

016

x

16

x

1

008 OPT

x

8

x

7

408

MERLIN LEGEND Mail

N /A

Total
Extensions
Assigned

+ (___x4)§
N /A

x

12††

System Totals
* System capacity for Personal Directories is decreased by one whenever an MLX-20L telephone is connected to an MLX port.
†
Hybrid/PBX mode only.
‡
The 100D module has one physical jack that supports 24 trunks.
§
The 008 OPT module is assigned 12 extension numbers although there are only 8 physical extension jacks.
¶
Although this MERLIN II module is supported, the 400 GS/LS/TTR, the 408 GS/LS, and the 408 GS/LS-MLX are the
recommended modules.
** The 800 NI-BRI module has 8 physical jacks that support 16 trunks. Up to five 800 NI-BRI modules (or any combination of
LINE/TRUNK modules up to the system maximum of 80 trunks) may be placed in the system. However, due to limitations in
the 391A, 391A1, and 391A2 power supplies, the number of 800 NI-BRI modules plus 100D modules cannot exceed 3 per carrier.
††
The MERLIN LEGEND Mail module has 7 dedicated internal ports, but assigns 12 total extensions.

Form 1-1

MERLIN LEGEND® Communications System Release 6.1

Form 1 (Continued)
System Planning
Control Unit Diagram
Unit Load Total________________

00

01

02 03

04 05

BASIC CARRIER

Unit Load Total________________

Ring Generator†

Power
Supply

Ring Generator†

Processor

Power
Supply

Ring Generator†

Power
Supply

Unit Load Total________________

06 07 08 09 10 11
EXPANSION CARRIER

12 13 14 15 16 17
EXPANSION CARRIER

System Operating Conditions
Language Selection
Backup
Programming Equipment
❑ Automatic
❑ System Programming Console System:
Weekly at ____________
Logical ID _____ Ext. No. _____ ❑ English ✦ ❑ French ❑ Spanish
Daily at ____________
SMDR:
❑ PC with SPM software
❑ English ✦ ❑ French ❑ Spanish ❑ Manual
❑ PCMCIA Memory Card
System Mode
❑ Key ✦

Printer:
❑ English ✦ ❑ French ❑ Spanish

❑ Hybrid/PBX*

Automatic Maintenance Busy
❑ Enable

❑ Behind Switch
Host Dial Codes:
❑ Transfer
____________
❑ Conference ____________
❑ Drop
____________
❑ Permanent Key

System Consoles
❑ QCC (s)
____ ____ ____ ____
❑ DLC (s)

❑ Disable ✦

____ ____ ____ ____

Set System Date
❑ Yes

____ ____ ____ ____
Second Dial Tone Timer
__________ (0✦ – 5000 ms)

✦ Factory Setting for system software
* Factory Setting for hardware
†
Older versions of the 012 and 008 OPT module require a Ring Generator on the carrier power supply module. Current versions of
the 012 and 008 OPT modules, and the 016 module do not require a Ring Generator. Both types can reside together in the
system.

Form 1-2

MERLIN LEGEND® Communications System Release 6.1

Form 1 (Continued)
Applications*
❑

Lucent Technologies Attendant†
Notes:

❑

Automated Document Delivery System (ADDS)
Notes:

❑

Call Accounting System (CAS) for Plus V3**
Notes:

❑

Call Accounting System for Windows
Notes:

❑

Call Accounting Terminal (CAT)
❑ Business
❑ Hospitality
Notes:

❑

Call Management System (CMS)†
Notes:

❑

Centrex
Notes:

❑

CONVERSANT®
Notes:

❑

MERLIN Identifier†
Notes:

❑

MERLIN LEGEND Mail/MERLIN MAIL™ Voice Messaging System†
Notes:

❑

MERLIN PFC™ Telephone‡
Notes:

❑

MERLIN LEGEND Reporter
Notes:

* CAUTION: General information about these applications is in the Feature Reference. But to ensure proper operation, you must
review the documentation provided with the applications.
†
Not orderable.
** Orderable only as an upgrade to existing CAS installations.
Form 1-3
‡
Refurbished only.

MERLIN LEGEND® Communications System Release 6.1

Form 1 (Continued)

❑

Group IV Fax
❑ Primary Rate Interface (PRI)
Notes:

❑

Basic Rate Interface (BRI)

❑

System Programming and Maintenance (SPM)
Notes:

❑

Video Conferencing
Notes:

❑

IS II*
❑ IVP/Auto Attendant
❑ AUDIX Voice Power
❑ CAS
❑ SPM
Notes: __________________________________________________________________________________

❑

IS III*
❑ IVP/Auto Attendant
❑ AUDIX Voice Power
❑ CAS
❑ SPM
❑ FAX Attendant System™
Notes: __________________________________________________________________________________

❑

PassageWay Direct Connect Solution
Notes: __________________________________________________________________________________

❑

Computer Telephony Integration
❑ NetWare
❑ Windows NT
Telephony Application: ___________________________________________________________________
Notes: __________________________________________________________________________________

❑

Messaging 2000
Notes: __________________________________________________________________________________

❑

Enhanced Service Center (ESC)
Notes: __________________________________________________________________________________

❑

Intuity
❑
❑
❑
Notes:

AUDIX
❑ CAS
❑ SPM
Lotus Notes
❑ Internet Messaging
Fax Messages
❑ Message Manager
__________________________________________________________________________________

Other
❑
❑
❑
❑
Notes:

______________________
______________________
______________________
______________________
__________________________________________________________________________________

❑

Form 1-4

* Not Orderable

Renumber System*
❑ 2-Digit ✦ ❑ Selected Extension Numbers

❑ 3-Digit

❑ Set Up Space

100

7100

11

101

7101

3

12

102

7102

4

13

103

7103

5

14

104

7104

6

15

105

7105

7

16

106

7106

8

17

107

7107

9

18

108

7108

10

19

109

7109

11

20

110

7110

12

21

111

7111

13

22

112

7112

14

23

113

7113

15

24

114

7114

16

25

115

7115

17

26

116

7116

18

27

117

7117

19

28

118

7118

20

29

119

7119

21

30

120

7120

22

31

121

7121

23

32

122

7122

24

33

123

7123

Form 2a-1

Shaded lines indicate possible operator positions.
✦ Factory Setting
* The system capacity for Personal Directories is decreased by one whenever an MLX-20L telephone is connected to an MLX port.
†
Use Form 2b for adjuncts connected via MFM .
‡
Ringing Frequency is programmable on the 016 T/R module only.
# The maximum number of VMI ports is 24.
** The maximum number of CTI links is 1.

N/A

N/A

N/A

N/A

N/A

N/A

MERLIN LEGEND® Communications System Release 6.1

10

2

CTI
Old Wire Person, Location, Ring
or Function
Ext. No. No.
Freq.‡ Appl.# Link**

System Numbering: Extension Jacks

1

Label

Centralized Voice Messaging
❑ No
❑ Yes

Form 2a

2-Dig. 3-Dig.
Mod. Log. Jack Type
Ext.
Ext. Set Up Renumber
to
Type ID A D† B Equipment No.✦ No. Space

Networked Switch
❑ No
❑ Yes

126

7126

28

37

127

7127

29

38

128

7128

30

39

129

7129

31

40

130

7130

32

41

131

7131

33

42

132

7132

34

43

133

7133

35

44

134

7134

36

45

135

7135

37

46

136

7136

38

47

137

7137

39

48

138

7138

40

49

139

7139

41

50

140

7140

42

51

141

7141

43

52

142

7142

44

53

143

7143

45

54

144

7144

46

55

145

7145

47

56

146

7146

48

57

147

7147

Shaded lines indicate possible operator positions.
✦ Factory Setting
* The system capacity for Personal Directories is decreased by one whenever an MLX-20L telephone is connected to an MLX port.
†
Use Form 2b for adjuncts connected via MFM.
‡
Ringing Frequency is programmable on the 016 T/R module only.
# The maximum number of VMI ports is 24.
** The maximum number of CTI links is 1.

N/A

N/A

N/A

N/A

N/A

N/A

MERLIN LEGEND® Communications System Release 6.1

36

CTI
Old Wire Person, Location, Ring
Freq.‡ Appl.# Link**
or Function
Ext. No. No.

System Numbering: Extension Jacks

27

Label

Form 2a (Continued)

Form 2a-2

2-Dig. 3-Dig.
Mod. Log. Jack Type
Ext. Ext. Set Up Renumber
to
Type ID A D* B Equipment No.✦ No. Space
34
7124
25
124
35
7125
26
125

149

7149

60

150

7150

52

61

151

7151

53

62

152

7152

54

63

153

7153

55

64

154

7154

56

65

155

7155

57

66

156

7156

58

6700

157

7157

59

6701

158

7158

60

6702

159

7159

61

6703

160

7160

62

6704

161

7161

63

6705

162

7162

64

6706

163

7163

65

6707

164

7164

66

6708

165

7165

67

6709

166

7166

68

6710

167

7167

69

6711

168

7168

70

6712

169

7169

71

6713

170

7170

72

6714

171

7171

Form 2a-3

Shaded lines indicate possible operator positions.
✦ Factory Setting
* The system capacity for Personal Directories is decreased by one whenever an MLX-20L telephone is connected to an MLX port.
†
Use Form 2b for adjuncts connected via MFM.
‡
Ringing Frequency is programmable on the 016 T/R module only.
# The maximum number of VMI ports is 24.
** The maximum number of CTI links is 1.

N/A

N/A

N/A

N/A

N/A

N/A

System Numbering: Extension Jacks

59

51

CTI
Old Wire Person, Location, Ring
Freq.‡ Appl.# Link**
or Function
Ext. No. No.

MERLIN LEGEND® Communications System Release 6.1

50

Label

Form 2a (Continued)

2-Dig. 3-Dig.
Mod. Log. Jack Type
Ext. Ext. Set Up Renumber
to
Type ID A D* B Equipment No.✦ No. Space
49
7148
58 148

175

7175

77

6719

176

7176

78

6720

177

7177

79

6721

178

7178

80

6722

179

7179

81

6723

180

7180

82

6724

181

7181

83

6725

182

7182

84

6726

183

7183

85

6727

184

7184

86

6728

185

7185

87

6729

186

7186

88

6730

187

7187

89

6731

188

7188

90

6732

189

7189

91

6733

190

7190

92

6734

191

7191

93

6735

192

7192

94

6736

193

7193

95

6737

194

7194

96

6738

195

7195

Shaded lines indicate possible operator positions.
✦ Factory Setting
* The system capacity for Personal Directories is decreased by one whenever an MLX-20L telephone is connected to an MLX port.
†
Use Form 2b for adjuncts connected via MFM.
‡
Ringing Frequency is programmable on the 016 T/R module only.
# The maximum number of VMI ports is 24.
** The maximum number of CTI links is 1.

N/A

N/A

N/A

N/A

N/A

N/A

MERLIN LEGEND® Communications System Release 6.1

6718

CTI
Old Wire Person, Location, Ring
Freq.‡ Appl.# Link**
or Function
Ext. No. No.

System Numbering: Extension Jacks

76

Label

Form 2a (Continued)

Form 2a-4

2-Dig. 3-Dig.
Mod. Log. Jack Type
Ext. Ext. Set Up Renumber
to
Type ID A D* B Equipment No.✦ No. Space
73
7172
6715 172
74
7173
6716 173
75
7174
6717 174

7197

203
204

7203

107

205
206

7205

6749

108

6750

207

7207

109

6751

208

7208

110

6752

209

7209

111

6753

210

7210

112

6754

211

7211

113

6755

212

7212

114

6756

213

7213

115

6757

214

7214

116

6758

215

7215

117

6759

216

7216

118

6760

217

7217

119

6761

218

7218

120

6762

219

7219

6741

100

6742

101

6743

102

6744

103

6745

104

6746

105

6747

106

6748

N/A

7198
7199
7200

N/A

7201
7202
7204

N/A

7206

Form 2a-5

Shaded lines indicate possible operator positions.
✦ Factory Setting
* The system capacity for Personal Directories is decreased by one whenever an MLX-20L telephone is connected to an MLX port.
†
Use Form 2b for adjuncts connected via MFM.
‡
Ringing Frequency is programmable on the 016 T/R module only.
# The maximum number of VMI ports is 24.
** The maximum number of CTI links is 1.

N/A

N/A

N/A

System Numbering: Extension Jacks

6740

99

CTI
Old Wire Person, Location, Ring
Freq.‡ Appl.# Link**
or Function
Ext. No. No.

MERLIN LEGEND® Communications System Release 6.1

197
198
199
200
201
202

98

Label

Form 2a (Continued)

2-Dig. 3-Dig.
Mod. Log. Jack Type
Ext. Ext. Set Up Renumber
to
Type ID A D* B Equipment No.✦ No. Space
7196
6739 196
97

221

7221

123

6765

222

7222

124

6766

223

7223

125

6767

224

7224

126

6768

225

7225

127

6769

226

7226

128

6770

227

7227

129

6771

228

7228

130

6772

229

7229

131

6773

230

7230

132

6774

231

7231

133

6775

232

7232

134

6776

233

7233

135

6777

234

7234

136

6778

235

7235

137

6779

236

7236

138

6780

237

7237

139

6781

238

7238

140

6782

239

7239

141

6783

240

7240

142

6784

241

7241

143

6785

242

7242

144

6786

243

7243

Shaded lines indicate possible operator positions.
✦ Factory Setting
* The system capacity for Personal Directories is decreased by one whenever an MLX-20L telephone is connected to an MLX port.
†
Use Form 2b for adjuncts connected via MFM.
‡
Ringing Frequency is programmable on the 016 T/R module only.
# The maximum number of VMI ports is 24.
** The maximum number of CTI links is 1.

N/A

N/A

N/A

N/A

N/A

N/A

MERLIN LEGEND® Communications System Release 6.1

6764

CTI
Old Wire Person, Location, Ring
Freq.‡ Appl.# Link**
or Function
Ext. No. No.

System Numbering: Extension Jacks

122

Label

Form 2a (Continued)

Form 2a-6

2-Dig. 3-Dig.
Mod. Log. Jack Type
Ext. Ext. Set Up Renumber
to
Type ID A D* B Equipment No.✦ No. Space
6763 220
7220
121

148

6790

149

6791

150

6792

151

6793

152
153

7246

6794

246
247
248
249
250
251

6795

252

7252

154

6796
6797

253
254

7253

155
156

6798

255

7255

157

6799

256

7256

158

6800

257

7257

159

6801

258

7258

160

6802

259

7259

161

6803

260

7260

162

6804

261

7261

163

6805

262

7262

164

6806

263

7263

165

6807

264

7264

166

6808

265

7265

167

6809

266

7266

168

6810

267

7267

N/A

7247
7248

N/A

7249
7250
7251
N/A

7254

Form 2a-7

Shaded lines indicate possible operator positions.
✦ Factory Setting
* The system capacity for Personal Directories is decreased by one whenever an MLX-20L telephone is connected to an MLX port.
†
Use Form 2b for adjuncts connected via MFM.
‡
Ringing Frequency is programmable on the 016 T/R module only.
# The maximum number of VMI ports is 24.
** The maximum number of CTI links is 1.

N/A

N/A

N/A

MERLIN LEGEND® Communications System Release 6.1

6789

CTI
Old Wire Person, Location, Ring
Freq.‡ Appl.# Link**
or Function
Ext. No. No.

System Numbering: Extension Jacks

147

Label

Form 2a (Continued)

2-Dig. 3-Dig.
Mod. Log. Jack Type
Ext. Ext. Set Up Renumber
to
Type ID A D* B Equipment No.✦ No. Space
145
7244
6787 244
146
7245
6788 245

268

7268

170

6812

269

7269

171

6813

270

7270

172

6814

271

7271

173

6815

272

7272

174

6816

273

7273

175

6817

274

7274

176

6818

275

7275

177

6819

276

7276

178

6820

277

7277

179

6821

278

7278

180

6822

279

7279

181

6823

280

7280

182

6824

281

7281

183

6825

282

7282

184

6826

283

7283

185

6827

284

7284

186

6828

285

7285

187

6829

286

7286

188

6830

287

7287

189

6831

288

7288

190

6832

289

7289

191

6833

290

7290

192

6834

291

7291

Shaded lines indicate possible operator positions.
✦ Factory Setting
* The system capacity for Personal Directories is decreased by one whenever an MLX-20L telephone is connected to an MLX port.
†
Use Form 2b for adjuncts connected via MFM.
‡
Ringing Frequency is programmable on the 016 T/R module only.
# The maximum number of VMI ports is 24.
** The maximum number of CTI links is 1.

N/A

N/A

N/A

N/A

N/A

N/A

MERLIN LEGEND® Communications System Release 6.1

6811

CTI
Old Wire Person, Location, Ring
Freq.‡ Appl.# Link**
or Function
Ext. No. No.

System Numbering: Extension Jacks

169

Label

Form 2a (Continued)

Form 2a-8

2-Dig. 3-Dig.
Mod. Log. Jack Type
Ext. Ext. Set Up Renumber
to
Type ID A D* B Equipment No.✦ No. Space

196

6838

197

6839

198

6840

198

6841

200

6842

294
295
296

7294

297
298
299

7297

N/A

7295
7296
7298
7299

Shaded lines indicate possible operator positions.
✦ Factory Setting
* The system capacity for Personal Directories is decreased by one whenever an MLX-20L telephone is connected to an MLX port.
†
Use Form 2b for adjuncts connected via MFM.
‡
Ringing Frequency is programmable on the 016 T/R module only.
# The maximum number of VMI ports is 24.
** The maximum number of CTI links is 1.

N/A

MERLIN LEGEND® Communications System Release 6.1

6837

CTI
Old Wire Person, Location, Ring
Freq.‡ Appl.# Link**
or Function
Ext. No. No.

System Numbering: Extension Jacks

195

Label

Form 2a (Continued)

2-Dig. 3-Dig.
Mod. Log. Jack Type
Ext. Ext. Set Up Renumber
to
Type ID A D* B Equipment No.✦ No. Space
7292
193
6835 292
7293
194
6836 293

Form 2a-9

MERLIN LEGEND® Communications System Release 6.1

MERLIN LEGEND® Communications System Release 6.1

Form 2b
System Numbering: Digital Adjuncts
(Make additional copies of this form as needed.)
Maximum: 127 Adjuncts
Factory-Set
Log.
ID
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

Set Up

2-digit 3-digit Space

710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749

300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339

Networked Switch
❑ No
❑ Yes

MLX
Telephone
Person, Location,
Renumber to Adjuncts 2B Ext. No. Function, and Equipment Type

7300
7301
7302
7303
7304
7305
7306
7307
7308
7309
7310
7311
7312
7313
7314
7315
7316
7317
7318
7319
7320
7321
7322
7323
7324
7325
7326
7327
7328
7329
7330
7331
7332
7333
7334
7335
7336
7337
7338
7339

Form 2b-1

MERLIN LEGEND® Communications System Release 6.1

Form 2b (Continued)
System Numbering: Digital Adjuncts
(Make additional copies of this form as needed.)
Maximum: 127 Adjuncts
Factory-Set
Log.
ID
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80

Set Up

2-digit 3-digit Space

750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
6850
6851
6852
6853
6854
6855
6856
6857
6858
6859
6860
6861
6862
6863
6864
6865
6866
6867
6868
6869
6870
6871
6872

Form 2b-2

340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379

7340
7341
7342
7343
7344
7345
7346
7347
7348
7349
7350
7351
7352
7353
7354
7355
7356
7357
7358
7359
7360
7361
7362
7363
7364
7365
7366
7367
7368
7369
7370
7371
7372
7373
7374
7375
7376
7377
7378
7379

MLX
Telephone
Person, Location,
Renumber to Adjuncts 2B Ext. No. Function, and Equipment Type

MERLIN LEGEND® Communications System Release 6.1

Form 2b (Continued)
System Numbering: Digital Adjuncts
(Make additional copies of this form as needed.)
Maximum: 127 Adjuncts
Factory-Set
Log.
ID
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120

Set Up

2-digit 3-digit Space

6873
6874
6875
6876
6877
6878
6879
6880
6881
6882
6883
6884
6885
6886
6887
6888
6889
6890
6891
6892
6893
6894
6895
6896
6897
6898
6899
6900
6901
6902
6903
6904
6905
6906
6907
6908
6909
6910
6911
6912

380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419

MLX
Telephone
Person, Location,
Renumber to Adjuncts 2B Ext. No. Function, and Equipment Type

7380
7381
7382
7383
7384
7385
7386
7387
7388
7389
7390
7391
7392
7393
7394
7395
7396
7397
7398
7399
7400
7401
7402
7403
7404
7405
7406
7407
7408
7409
7410
7411
7412
7413
7414
7415
7416
7417
7418
7419

Form 2b-3

MERLIN LEGEND® Communications System Release 6.1

Form 2b (Continued)
System Numbering: Digital Adjuncts
(Make additional copies of this form as needed.)
Maximum: 127 Adjuncts
Factory-Set
Log.
ID
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
156
157
158
159

Set Up

2-digit 3-digit Space

6913
6914
6915
6916
6917
6918
6919
6920
6921
6922
6923
6924
6925
6926
6927
6928
6929
6930
6931
6932
6933
6934
6935
6936
6937
6938
6939
6940
6941
6942
6943
6944
6945
6946
6947
6948
6949
6950
6951
6952

Form 2b-4

420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459

7420
7421
7422
7423
7424
7425
7426
7427
7428
7429
7430
7431
7432
7433
7434
7435
7436
7437
7438
7439
7440
7441
7442
7443
7444
7445
7446
7447
7448
7449
7450
7451
7452
7453
7454
7455
7456
7457
7458
7459

MLX
Telephone
Person, Location,
Renumber to Adjuncts 2B Ext. No. Function, and Equipment Type

MERLIN LEGEND® Communications System Release 6.1

Form 2b (Continued)
System Numbering: Digital Adjuncts
(Make additional copies of this form as needed.)
Maximum: 127 Adjuncts
Factory-Set
Log.
ID
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200

Set Up

2-digit 3-digit Space

6953
6954
6955
6956
6957
6958
6959
6960
6961
6962
6963
6964
6965
6966
6967
6968
6969
6970
6971
6972
6973
6974
6975
6976
6977
6978
6979
6980
6981
6982
6983
6984
6985
6986
6987
6988
6989
6990
6991
6992
6993

460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500

MLX
Telephone
Person, Location,
Renumber to Adjuncts 2B Ext. No. Function, and Equipment Type

7460
7461
7462
7463
7464
7465
7466
7467
7468
7469
7470
7471
7472
7473
7474
7475
7476
7477
7478
7479
7480
7481
7482
7483
7484
7485
7486
7487
7488
7489
7490
7491
7492
7493
7494
7495
7496
7497
7498
7499
7500

Form 2b-5

MERLIN LEGEND® Communications System Release 6.1

Loudspeaker Page, Line/Trunk No(s). _____________________

Loop-Start Reliable Disconnect*
■ No ✦
■ Yes

Jack Type
(LS, GS,
Log. DID, Tie,
etc.)
ID

Line/
Trunk
No.

Form 2c-1

1

801

2

802

3

803

4

804

5

805

6

806

7

807

8

808

9

809

10

810

11

811

12

812

13

813

14

814

15

815

16

816

17

817

18

818

19

819

20

820

Pool
DialOut
Code†‡

✦ Factory Setting
* If the system has AUDIX Voice Power/FAX Attendant System™, Integrated
Administration will automatically set Loop-Start Reliable Disconnect to Yes.
† Hybrid/PBX mode only.

Label

QCC
Operator
Toll Type
to
Outmode Prefix Req’d Hold Disc.
Receive
for
LD
Signaling
Interval
Calls†
TT✦ R Yes✦ No Short Long ✦ (No ✦)

QCC
Queue
Priority
Level†
(4 ✦)

‡ Maximum: 11 pools with up to 80 trunks per pool.
Factory settings: 70 (main), 891 (dial-in tie), 892 (automatic-in tie).

Function

System Numbering: Line/Trunk Jacks

Module
Type
and Slot
No.

Incoming
Line/Trunk
Type (Main
No., Personal Telephone
Number
ReLine, WATS,
or
number FX, NI-BRI,
Equipment
to
etc.)

MERLIN LEGEND® Communications System Release 6.1

Maintenance Alarm, Line/Trunk No. ____________________

Form 2c

Music On Hold, Line/Trunk No. __________ Source __________

21

821

22

822

23

823

24

824

25

825

26

826

27

827

28

828

29

829

30

830

31

831

32

832

33

833

34

834

35

835

36

836

37

837

38

838

39

839

40

840

✦ Factory Setting
† Hybrid/PBX mode only.

Pool
DialOut
Code†‡

Label

‡ Maximum: 11 pools with up to 80 trunks per pool.
Factory settings: 70 (main), 891 (dial-in tie), 892 (automatic-in tie).

Function

MERLIN LEGEND® Communications System Release 6.1

Line/
Trunk
No.

System Numbering: Line/Trunk Jacks

Jack Type
(LS, GS,
Log. DID, Tie,
etc.)
ID

QCC
Operator QCC
Toll Type
Queue
to
Outmode Prefix Req’d Hold Disc.
Receive Priority
Signaling
for LD
Interval
Calls† Level†
(4 ✦)
TT✦ R Yes✦ No Short Long ✦ (No ✦)

Form 2c (Continued)

Form 2c-2
Module
Type
and Slot
No.

Incoming
Line/Trunk
Type (Main
No., Personal Telephone
Number
ReLine, WATS,
or
number FX, NI-BRI,
Equipment
to
etc.)

41

841

42

842

43

843

44

844

45

845

46

846

47

847

48

848

49

849

50

850

51

851

52

852

53

853

54

854

55

855

56

856

57

857

58

858

59

859

60

860

Form 2c-3

✦ Factory Setting
† Hybrid/PBX mode only.

Pool
DialOut
Code†‡

Telephone
Number
or
Equipment

Label

‡ Maximum: 11 pools with up to 80 trunks per pool.
Factory settings: 70 (main), 891 (dial-in tie), 892 (automatic-in tie).

Function

MERLIN LEGEND® Communications System Release 6.1

Line/
Trunk
No.

Form 2c (Continued)

Jack Type
(LS, GS,
Log. DID, Tie,
etc.)
ID

QCC
Operator QCC
Toll Type
to
Queue
Outmode Prefix Req’d
Hold Disc.
Receive Priority
Signaling
for LD
Interval
Calls†
Level†
(4 ✦)
TT✦ R Yes✦ No Short Long ✦ (No ✦)

System Numbering: Line/Trunk Jacks

Module
Type
and Slot
No.

Incoming
Line/Trunk
Type (Main
No., Personal
ReLine, WATS,
number FX, NI-BRI,
to
etc.)

61

861

62

862

63

863

64

864

65

865

66

866

67

867

68

868

69

869

70

870

71

871

72

872

73

873

74

874

75

875

76

876

77

877

78

878

79

879

80

880

✦ Factory Setting
† Hybrid/PBX mode only.

Pool
DialOut
Code†‡

Label

‡ Maximum: 11 pools with up to 80 trunks per pool.
Factory settings: 70 (main), 891 (dial-in tie), 892 (automatic-in tie).

Function

MERLIN LEGEND® Communications System Release 6.1

Line/
Trunk
No.

System Numbering: Line/Trunk Jacks

Jack Type
(LS, GS,
Log. DID, Tie,
etc.)
ID

QCC
Operator QCC
Toll Type
Queue
to
Outmode Prefix Req’d Hold Disc.
Priority
Receive
Signaling
for LD
Interval
Calls† Level†
(4 ✦)
TT✦ R Yes✦ No Short Long ✦ (No ✦)

Form 2c (Continued)

Form 2c-4
Module
Type
and Slot
No.

Incoming
Line/Trunk
Type (Main
No., Personal Telephone
Number
ReLine, WATS,
or
number FX, NI-BRI,
Equipment
to
etc.)

MERLIN LEGEND® Communications System Release 6.1

Form 2d
System Numbering: Special Renumbers
Pools*
(Form 2c)
Description

Factory-Set
Number

Renumber
to

Group Calling
(Form 7d)
Group ID
Label

Factory-Set
Number

Renumber
to

793
794
795
796
797
798
799
Park Zone
(Form 6a)
Description

Factory-Set
Number

Renumber
to

881
882
883
884
885
886
887
888

Listed Directory
Number*
(QCC Queue)

DSS Page Buttons

Default

Factory-Set
Number

Renumber
to

800

PAGE 1 Beginning extension for range
PAGE 2 Beginning extension for range
PAGE 3 Beginning extension for range
ARS Dial-Out
†
Code

Renumber
to

770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
7920
7921
7922
7923
7924‡
7925‡
7926‡
7927‡
‡
7928
7929‡

70
890
891
892
893
894
895
896
897
898
899
Group Paging
(Form 7b)
Group ID

Factory-Set
Number

Remote Access
Code (Form 3a)

Factory-Set
Number
889

Renumber
to

Renumber
to

9
* Hybrid/PBX mode only.
† ARS Dial-Out Code is Idle Line Preference Code in Key mode.
‡ Reserved for AUDIX Voice Power/FAX Attendant System.

Form 2d-1

MERLIN LEGEND® Communications System Release 6.1

MERLIN LEGEND® Communications System Release 6.1

Form 3a
Incoming Trunks: Remote Access
DID and Private Network Tie Trunks
❑ Remote Access Code: 889

Barrier Codes Required for Private Network Tie Trunks
❑ Yes ✦

❑ Renumber to _______________

❑ No

Automatic Callback
❑ Enable

Barrier Codes Required for Non-Tie Trunks
❑ Yes ✦

❑ Disable ✦

❑ No
Number of Digits in Barrier Codes
❑ 4–11 (7✦)

Logical
ID

Trunk
No.

DID or Priv.
Net. Tie
Trunk

Non-Tie
Trunk

Trunk Type and
Description

Dedicated

Shared

✦ Factory Setting

Form 3a-1

MERLIN LEGEND® Communications System Release 6.1

Form 3a (Continued)
Incoming Trunks: Remote Access
Logical
ID

Form 3a-2

Trunk
No.

DID or Priv.
Net. Tie
Trunk

Non-Tie
Trunk

Trunk Type and
Description

Dedicated

Shared

MERLIN LEGEND® Communications System Release 6.1

Form 3a (Continued)
Class of Restriction without Barrier Codes
DID* and Private Network Tie Trunks

Non-Tie Trunks

Network Calls
❑ None

Network Calls
❑ None

❑ Tandem

❑ Tandem

❑ ARS

❑ ARS

Restriction
❑ Unrestricted

Restriction
❑ Unrestricted

❑ Outward Restrict ✦

❑ Outward Restrict ✦

❑ Toll Restrict

❑ Toll Restrict

ARS Restriction Level*
❑ 0
❑ 4

ARS Restriction Level*
❑ 0
❑ 4

❑ 1

❑ 5

❑ 1

❑ 5

❑ 2

❑ 6

❑ 2

❑ 6

❑ 3✦

❑ 3✦

Disallowed List Access
❑ List Numbers (0–7)
______ ______ ______ ______
______ ______ ______ ______

Disallowed List Access
❑ List Numbers (0–7)
______ ______ ______ ______
______ ______ ______ ______

✦ Factory Setting
* Hybrid/PBX mode only

Form 3a-3

MERLIN LEGEND® Communications System Release 6.1

Form 3a (Continued)
Class of Restriction with Barrier Codes
Maximum: 16 barrier codes. (Make copies if more than 4 are assigned.)
Barrier Code
Number ____________________
Digits _____________ (0–9, plus ✳)

Barrier Code
Number ____________________
Digits _____________ (0–9, plus ✳)

Restriction
❑ Unrestricted
❑ Outward Restrict ✦
❑ Toll Restrict

Restriction
❑ Unrestricted
❑ Outward Restrict ✦
❑ Toll Restrict

ARS Restriction Level*
❑ 0
❑ 4
❑ 1
❑ 5
❑ 2
❑ 6
❑ 3✦

ARS Restriction Level*
❑ 0
❑ 4
❑ 1
❑ 5
❑ 2
❑ 6
❑ 3✦

Disallowed List Access
❑ List Numbers (0–7)
______ ______ ______ ______
______ ______ ______ ______

Disallowed List Access
❑ List Numbers (0–7)
______ ______ ______ ______
______ ______ ______ ______

Barrier Code
Number ____________________
Digits _____________ (0–9, plus ✳)

Barrier Code
Number ____________________
Digits _____________ (0–9, plus ✳)

Restriction
❑ Unrestricted
❑ Outward Restrict ✦
❑ Toll Restrict

Restriction
❑ Unrestricted
❑ Outward Restrict ✦
❑ Toll Restrict

ARS Restriction Level*
❑ 0
❑ 4
❑ 1
❑ 5
❑ 2
❑ 6
❑ 3✦

ARS Restriction Level*
❑ 0
❑ 4
❑ 1
❑ 5
❑ 2
❑ 6
❑ 3✦

Disallowed List Access
❑ List Numbers (0–7)
______ ______ ______ ______
______ ______ ______ ______

Disallowed List Access
❑ List Numbers (0–7)
______ ______ ______ ______
______ ______ ______ ______

✦ Factory Setting
* Hybrid/PBX mode only

Form 3a-4

MERLIN LEGEND® Communications System Release 6.1

Form 3b
Incoming Trunks: DS1 Connectivity (100D Module)
Module 1 Slot No. __________
Type of Service Switch Type
❑ T1 ✦*
❑ 4ESS✦*‡
†‡
❑ PRI
❑ 5ESS‡
❑ DMS-100
❑ DMS-250
T1 Trunks
Trunk Type
Ground-Start
Loop-Start
Tie
Unequipped
All GroundStart
All Loop-Start
All Tie
All Unequipped
DID
All DID
S56 Data
All S56 Data

(PRI Service Only)
❑ DEX600E
❑ Legend-PBX
❑ Legend-NTWK

For Tie/All Tie
Channel
Number(s) Tie-PBX Toll
S56

Frame Format
❑ D4 Compatible ✦

Clock Synchronization
Priority

❑ Extended Superframe (ESF)

❑ Primary ✦

Suppression (Line Code)
❑ AMI-ZCS ✦

❑ Secondary

❑ B8ZS

❑ Tertiary
❑ None

Signaling Mode
❑ Robbed-Bit Signaling
(RBS) ✦

Source

❑ Common-Channel
Signaling (CCS)

❑ Local

Line Compensation
__________ Cable Feet
❑ 1 (-.6 dB) ✦

❑ Loop ✦
Activation
❑ Active ✦
❑ Not Active

❑ 2 (-1.2 dB)

Channel Service Unit
❑ Foreign Exchange ✦

❑ 3 (-1.8 dB)

❑ Special Access

❑ 4 (-2.4 dB)
❑ 5 (-3.0 dB)

Module 2 Slot No. __________
Type of Service Switch Type
❑ T1 ✦*
❑ 4ESS✦*‡
†‡
❑ PRI
❑ 5ESS‡
❑ DMS-100
❑ DMS-250
T1 Trunks
Trunk Type
Ground-Start
Loop-Start
Tie
Unequipped
All GroundStart
All Loop-Start
All Tie
All Unequipped
DID
All DID
S56 Data
All S56 Data

(PRI Service Only)
❑ DEX600E
❑ Legend-PBX
❑ Legend-NTWK

For Tie/All Tie
Channel
Number(s) Tie-PBX Toll
S56

Frame Format
❑ D4 Compatible ✦

Clock Synchronization
Priority

❑ Extended Superframe (ESF)

❑ Primary ✦

Suppression (Line Code)
❑ AMI-ZCS ✦

❑ Secondary

❑ B8ZS

❑ Tertiary
❑ None

Signaling Mode
❑ Robbed-Bit Signaling
(RBS) ✦

Source

❑ Common-Channel
Signaling (CCS)

❑ Local

Line Compensation
__________ Cable Feet
❑ 1 (-.6 dB) ✦

❑ Loop ✦
Activation
❑ Active ✦
❑ Not Active

❑ 2 (-1.2 dB)

Channel Service Unit
❑ Foreign Exchange ✦

❑ 3 (-1.8 dB)

❑ Special Access

❑ 4 (-2.4 dB)
❑ 5 (-3.0 dB)

NOTE: Do not configure 100D modules to do trunk-to-trunk transfers between DS1 and LS lines/trunks.
✦ Factory Setting
* The factory setting of T1 is not automatically selected if you enter nothing; it must be entered.
† PRI must be selected as the Type of DS1 connectivity before PRI options are entered.
‡ AT&T Toll and 5ESS local PRI service for Release 2.0 and later requires service provider switching equipment to be either
4ESS Generic 13 through Generic 16, 5ESS Generic 6, or a 5ESS serving the FTS2000 network. PRI service on Release 1.0
or 1.1 requires a DS1 facility from a 4ESS Generic 13 through Generic 16 or 4ESS Generic 16 switch.

Form 3b-1

MERLIN LEGEND® Communications System Release 6.1

Form 3b (Continued)

Module 3 Slot No. __________
Type of Service Switch Type
❑ T1 ✦*
❑ 4ESS✦*‡
†‡
❑ PRI
❑ 5ESS‡
❑ DMS-100
❑ DMS-250
T1 Trunks
Trunk Type
Ground-Start
Loop-Start
Tie
Unequipped
All GroundStart
All Loop-Start
All Tie
All Unequipped
DID
All DID
S56 Data
All S56 Data

(PRI Service Only)
❑ DEX600E
❑ Legend-PBX
❑ Legend-NTWK

For Tie/All Tie
Channel
Number(s) Tie-PBX Toll
S56

Frame Format
❑ D4 Compatible ✦

Clock Synchronization
Priority

❑ Extended Superframe (ESF)

❑ Primary ✦

Suppression (Line Code)
❑ AMI-ZCS ✦

❑ Secondary
❑ Tertiary

❑ B8ZS

❑ None

Signaling Mode
❑ Robbed-Bit Signaling
(RBS) ✦

Source

❑ Common-Channel
Signaling (CCS)

❑ Local

Line Compensation
__________ Cable Feet
❑ 1 (-.6 dB) ✦

❑ Loop ✦
Activation
❑ Active ✦
❑ Not Active

❑ 2 (-1.2 dB)

Channel Service Unit
❑ Foreign Exchange ✦

❑ 3 (-1.8 dB)

❑ Special Access

❑ 4 (-2.4 dB)
❑ 5 (-3.0 dB)

NOTE: Do not configure 100D modules to do trunk-to-trunk transfers between DS1 and LS lines/trunks.
✦ Factory Setting
* The factory setting of T1 is not automatically selected if you enter nothing; it must be entered.
† PRI must be selected as the Type of DS1 connectivity before PRI options are entered.
‡ AT&T Toll and 5ESS local PRI service for Release 2.0 and later requires service provider switching equipment to be either
4ESS Generic 13 through Generic 16, 5ESS Generic 6, or a 5ESS serving the FTS2000 network. PRI service on Release 1.0
or 1.1 requires a DS1 facility from a 4ESS Generic 13 through Generic 16 or 4ESS Generic 16 switch.

Form 3b-2

MERLIN LEGEND® Communications System Release 6.1

Form 3b (Continued)
PRI Options*
B-Channel Groups
Maximum: 80 groups with up to 23 channels per group.
B-Channel
Group No.

B-Channel
Slot and Port No.

Trunk No.

B-Channel
Group No.

B-Channel
Slot and Port No.

Trunk No.

* PRI must be selected as the Type of DS1 connectivity before PRI options are entered.
NOTE: To ensure optimal performance of the PRI facility, the B-channels must be assigned to the B-channel groups in the
order opposite that of the sequence that the inbound calls are delivered by the network service provider.

Form 3b-3

MERLIN LEGEND® Communications System Release 6.1

Form 3b (Continued)
PRI Services
Maximum: 3 Modules. (Make copies of this page for additional modules.)
Module Slot No. _______________
B-Channel
Group No.

Outgoing Services*

Incoming Services*

Incoming Routing
Line
Dial Plan
Routing†‡ Appearance§

* Services:
AT&T Toll: Megacom WATS, Megacom 800, ACCUNET® SDS, Software Defined Network (SDN), MultiQuest, Long Distance.
5ESS Local: OUTWATS, 56/64 Digital, Virtual Private Network, INWATS.
MCI Toll: MCI PRISM, MCI Vnet, MCI 800, MCI 900
DMS-100 Local: DMS Private, DMS INWATS, DMS OUTWATS, DMS Foreign Exchange (FX), DMS Tie Trunk.
Other: Call-by-Call, Other.
† Hybrid/PBX mode only.
‡ If you select Dial Plan Routing, complete "Dial Plan Routing" information on Form 3b-6.
§ If you select Line Appearance, complete "Line Appearance Routing" information on Form 3b-5.

Form 3b-4

MERLIN LEGEND® Communications System Release 6.1

Form 3b (Continued)

Line Appearance Routing (Incoming Services)*
B-Channel Trunk
Group No. No.*

Telephone Number
(up to12 digits)

B-Channel Trunk
Group No. No.*

Telephone Number
(up to12 digits)

*Trunks must be administered to terminate on an internal endpoint, for example, an extension, a Calling Group, etc.

Form 3b-5

MERLIN LEGEND® Communications System Release 6.1

Form 3b (Continued)

Dial Plan Routing (Incoming Services)*
Maximum: 16 entries
Entry No.

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

Service†

Pattern to
Match‡
Total Digits in Dialed
Number
(0–14)
Delete Digits
(0–14)
Add Digits
(0–4)

Entry No.
Service†

Pattern to
Match‡
Total Digits in Dialed
Number
(0–14)
Delete Digits
(0–14)
Add Digits
(0–4)

* Hybrid/PBX mode only.
† Services:
AT&T Toll: Megacom WATS, Megacom 800, ACCUNET® SDS, Software Defined Network (SDN), MultiQuest, Long Distance.
5ESS Local: OUTWATS, 56/64 Digital, Virtual Private Network, INWATS.
MCI Toll: MCI PRISM, MCI Vnet, MCI 800, MCI 900
DMS-100 Local: DMS Private, DMS INWATS, DMS OUTWATS, DMS Foreign Exchange (FX), DMS Tie Trunk.
Other: Call-by-Call, Other.
‡ Pattern of up to 8 digits.

Form 3b-6

MERLIN LEGEND® Communications System Release 6.1

Form 3b (Continued)
Outgoing Tables (Outgoing Services)

Network Selection Table
Maximum: 4 entries
0✦

Entry No.

1✦

101

Dial Prefix*

***

2

3

10

***

Special Services Table
Maximum: 8 entries
0

1

2

3

4

5

Pattern to
Match†

011

010

01

00

0

1

Operator‡

none

OP

OP

P

OP

none

I

I

I

N

N

N

3

3

2

2

1

1

Entry No.

Type of No.

6

7

(N=Nat’l; I=Int’l)
Delete Digits
(0–4)

✦
*
†
‡

Defaults.
Dial Pattern can be up to 8 digits (* is a wildcard); must include at least one number; cannot begin with *.
Pattern can be up to 4 digits; no asterisks(*).
Operator: Local Operator (OP), Presubscribed Carrier (P), No operator (none).

Form 3b-7

MERLIN LEGEND® Communications System Release 6.1

Form 3b (Continued)

Call-By-Call Service Table
Maximum: 10 entries
Entry No.

0

1

2

3

4

5

6

7

8

9

Pattern to Match
(up to 10 entries)

Call Type
(Voice/Data/Both)
Service*
Delete Digits
(0–8)

Entry No.
Pattern to match
(up to 10 entries)

Call-Type
(Voice/Data/Both)
Service*
Delete Digits
(0–8)
* Services:
AT&T Toll: Megacom WATS, Megacom 800, ACCUNET® SDS, Software Defined Network (SDN), MultiQuest, Long Distance.
5ESS Local: OUTWATS, 56/64 Digital, Virtual Private Network, INWATS.
MCI Toll: MCI PRISM, MCI Vnet, MCI 800, MCI 900
DMS-100 Local: DMS Private, DMS INWATS, DMS OUTWATS, DMS Foreign Exchange (FX), DMS Tie Trunk.
Other: Call-by-Call, Other.

Form 3b-8

MERLIN LEGEND® Communications System Release 6.1

Form 3b (Continued)
Number to Send
❑ Extension Only
❑ Base Number with Extension ____________________ (up to 12 digits)
❑ Line Telephone Number:
(Maximum: 69 telephone numbers)

Trunk No.

Telephone Number to Send
(up to12 digits)

Trunk No.

Telephone Number to Send
(up to12 digits)

Form 3b-9

MERLIN LEGEND® Communications System Release 6.1

Form 3b (Continued)
Test Telephone Numbers
Module 1: _______________

Module 2: _______________

Module 3: _______________

PRI Protocol
Timers and Counters
Factory Setting
T200 Timer
T203 Timer
N200 Counter
N201 Counter
K Counter
T303 Timer
T305 Timer
T308 Timer
T309 Timer
T310 Timer
T313 Timer
T316 Timer

1 second
30 seconds
3 transmissions
260 octets
7 frames
4 seconds
4 seconds
4 seconds
90 seconds
60 seconds
4 seconds
120 seconds

Terminal Equipment Identifier (TEI)
❑ 0✦
❑ _____ (1–63)

✦ Factory Setting

Form 3b-10

Change to
(1000–3000 ms)
(1–60 seconds)
(1–5 transmissions)
(16–260 octets)
(1–15 frames)
(4–12 seconds)
(4–30 seconds)
(4–12 seconds)
(30–120 seconds)
(2–120 seconds)
(4–60 seconds)
(3–120 seconds)

MERLIN LEGEND® Communications System Release 6.1

Form 3b (Continued)
T1 Switched 56 Options*
Maximum:3 Modules (Make additional copies of this page as needed.)
Module Slot No. ________
Type
❑ Incoming

Channel No. ________
Dial Plan Routing Options

❑ Outgoing

Exptected Digits
❑ 1

❑ Two Way ✦

❑ 2

Incoming Signaling Type
❑ Wink ✦
❑ Auto
❑ Delay
Outgoing Signaling Type
❑ Wink ✦

❑ 3✦
❑ 4
Delete Digits
❑ 0✦
❑ 1
❑ 2

❑ Auto

❑ 3

❑ Delay

❑ 4

Incoming Signaling Mode
❑ Rotary

Add Digits
❑ 0 digits ✦

❑ Touch-tone ✦

❑ Add these digits _____________
(Any number from 1–9999)

Outgoing Signaling Mode
❑ Rotary
❑ Touch-tone ✦

✦ Factory Setting
* T1 must be selected as the Type of DS1 connectivity. The T1 Truck Type must be configured as S56 (not T1-tie)

Form 3b-11

MERLIN LEGEND® Communications System Release 6.1

Two Way ✦

Incoming

In

Out

In

Out

In

Out

E&M Signal

Automatic
In

Out 1S✦ 1C

5

Inmode

Outmode

Dial Tone

TouchTouchTone Rotary✦ Tone Rotary✦ Remote ✦

Local

Answer Supv.
Time
300✦

Other

Disconnect
Time
300✦

Other

Incoming Trunks: Tie

✦ Factory Setting

Outgoing

Immediate

MERLIN LEGEND® Communications System Release 6.1

Trunk
No.

Delay

Form 3c

Logical
ID

Wink ✦

(Make as many copies as needed.)

Signaling Type (Intype/Outtype)

Direction

Form 3c-1

Two Way ✦

Outgoing

Incoming

In

Out

Delay
In

Out

Immediate
In

Out

Automatic
In

Out 1S✦ 1C

5

Inmode

Outmode

Dial Tone

TouchTouchTone Rotary✦ Tone Rotary✦ Remote ✦

Local

Answer Supv.
Time
300✦

Other

Disconnect
Time
300✦

Other

Incoming Trunks: Tie

✦ Factory Setting

MERLIN LEGEND® Communications System Release 6.1

Wink ✦

Form 3c (Continued)

Form 3c-2

Trunk
No.

E&M Signal

Signaling Type (Intype/Outtype)

Direction
Logical
ID

MERLIN LEGEND® Communications System Release 6.1

Form 3d
Incoming Trunks: DID*
(Make copies for each block.)
Block Number (1 or 2) _______________
Type
❑ Immediate-Start

Add Digits
❑ 0 digits ✦

❑ Wink-Start ✦

❑ Add these digits _______________
(any number from 1–9999)

Expected Digits
❑ 1
❑ 2

Signaling
❑ Rotary ✦

❑ 3✦

❑ Touch-tone

❑ 4

Invalid Destination
❑ Send to backup position ✦

Delete Digits
❑ 0✦

❑ Return to fast busy

❑ 1
❑ 2
❑ 3
❑ 4
Trunks Included in Block
Logical
ID

Trunk
No.

Telephone
No.

Disconnect Time
500 ms✦

Other
(10 to
2550)

✦ Factory Setting
* Hybrid/PBX mode only

Form 3d-1

Telephone
Number

Disconnect Time
500 ms✦ Other
(10 to
2550)

Logical Trunk
Number
ID

Telephone
Number

Disconnect Time
500 ms✦ Other
(10 to
2550)

Incoming Trunks: DID*

✦ Factory Setting
* Hybrid/PBX mode only

MERLIN LEGEND® Communications System Release 6.1

Logical Trunk
Number
ID

Form 3d (Continued)

Form 3d-2

Trunks Included in Block

MERLIN LEGEND® Communications System Release 6.1

MERLIN LEGEND® Communications System Release 6.1

Form 3e
Automatic Route Selection Worksheet*
Number of exchanges in the calling area ____________________

Trunk Pool No.

Trunk Type

Type of Dial
Toll
Local Network

Number of Area Codes, Exchanges,
or Network Destinations for which
Trunk Pool Is Used

Preferred Trunk Pools
For toll calls (Table 17) _______________
For local calls (Table 18) _______________
* Hybrid/PBX mode only

Form 3e-1

MERLIN LEGEND® Communications System Release 6.1

Form 3f
Automatic Route Selection Tables*
Maximum: 16 Tables. (Make a copy for each table.)
Table No. __________
Type of Table
❑ 6-Digit
❑ Area Code
❑ Exchange
❑ 1 + 7, dialing from
❑ within area code
❑ not within area code ✦
Area Code/Exchanges
001 __________
021 __________

041 __________

061 __________

081 __________

002 __________

022 __________

042 __________

062 __________

082 __________

003 __________

023 __________

043 __________

063 __________

083 __________

004 __________

024 __________

044 __________

064 __________

084 __________

005 __________

025 __________

045 __________

065 __________

085 __________

006 __________

026 __________

046 __________

066 __________

086 __________

007 __________

027 __________

047 __________

067 __________

087 __________

008 __________

028 __________

048 __________

068 __________

088 __________

009 __________

029 __________

049 __________

069 __________

089 __________

010 __________

030 __________

050 __________

070 __________

090 __________

011 __________

031 __________

051 __________

071 __________

091 __________

012 __________

032 __________

052 __________

072 __________

092 __________

013 __________

033 __________

053 __________

073 __________

093 __________

014 __________

034 __________

054 __________

074 __________

094 __________

015 __________

035 __________

055 __________

075 __________

095 __________

016 __________

036 __________

056 __________

076 __________

096 __________

017 __________

037 __________

057 __________

077 __________

097 __________

018 __________

038 __________

058 __________

078 __________

098 __________

019 __________

039 __________

059 __________

079 __________

099 __________

020 __________

040 __________

060 __________

080 __________

100 __________

Subpattern A Time of Day
_________________

Subpattern B Time of Day
_________________
Absorb
1 _______
2 _______

Call Type†
(Both ✦)
_____
_____

FRL
Pool
(3 ✦)‡
1 _____ ______
2 _____ ______

Other
Digits
_______
_______

Absorb
1 _______
2 _______

Call Type†
(Both ✦)
_____
_____

_______

3 _______

_____

3 _____ ______

_______

3 _______

_____

_______

4 _______

_____

4 _____ ______

_______

4 _______

_____

5 _____ ______

_______

5 _______

_____

5 _____ ______

_______

5 _______

_____

6 _____ ______

_______

6 _______

_____

6 _____ ______

_______

6 _______

_____

FRL
Pool
(3 ✦)‡
1 _____ ______
2 _____ ______

Other
Digits
_______
_______

3 _____ ______
4 _____ ______

✦ Factory Setting
* Hybrid/PBX mode only

† Select Voice only, Data only, or Both.
‡ Local tables default FRL is 2.

Form 3f-1

MERLIN LEGEND® Communications System Release 6.1

Form 3f (Continued)
Table No. __________
Type of Table
❑ 6-Digit
❑ Area Code
❑ Exchange
❑ 1 + 7, dialing from
❑ within area code
❑ not within area code ✦
Area Code/Exchanges
001 __________
021 __________

041 __________

061 __________

081 __________

002 __________

022 __________

042 __________

062 __________

082 __________

003 __________

023 __________

043 __________

063 __________

083 __________

004 __________

024 __________

044 __________

064 __________

084 __________

005 __________

025 __________

045 __________

065 __________

085 __________

006 __________

026 __________

046 __________

066 __________

086 __________

007 __________

027 __________

047 __________

067 __________

087 __________

008 __________

028 __________

048 __________

068 __________

088 __________

009 __________

029 __________

049 __________

069 __________

089 __________

010 __________

030 __________

050 __________

070 __________

090 __________

011 __________

031 __________

051 __________

071 __________

091 __________

012 __________

032 __________

052 __________

072 __________

092 __________

013 __________

033 __________

053 __________

073 __________

093 __________

014 __________

034 __________

054 __________

074 __________

094 __________

015 __________

035 __________

055 __________

075 __________

095 __________

016 __________

036 __________

056 __________

076 __________

096 __________

017 __________

037 __________

057 __________

077 __________

097 __________

018 __________

038 __________

058 __________

078 __________

098 __________

019 __________

039 __________

059 __________

079 __________

099 __________

020 __________

040 __________

060 __________

080 __________

100 __________

Subpattern A Time of Day
_________________

Subpattern B Time of Day
_________________
Absorb
1 _______
2 _______

Call Type†
(Both ✦)
_____
_____

FRL
Pool
(3 ✦)‡
1 _____ ______
2 _____ ______

Other
Digits
_______
_______

Absorb
1 _______
2 _______

Call Type†
(Both ✦)
_____
_____

_______

3 _______

_____

3 _____ ______

_______

3 _______

_____

4 _____ ______

_______

4 _______

_____

4 _____ ______

_______

4 _______

_____

5 _____ ______

_______

5 _______

_____

5 _____ ______

_______

5 _______

_____

6 _____ ______

_______

6 _______

_____

6 _____ ______

_______

6 _______

_____

FRL
Pool
(3 ✦)‡
1 _____ ______
2 _____ ______

Other
Digits
_______
_______

3 _____ ______

✦ Factory Setting
* Select Voice only, Data only, or Both.
‡ Local tables default FRL is 2.

Form 3f-2

MERLIN LEGEND® Communications System Release 6.1

Form 3g
Automatic Route Selection Default and Special Numbers Tables*
Table 17: Default Toll Table
Subpattern A Time of Day
_________________

Subpattern B Time of Day
_________________
Absorb
1 _______
2 _______

Call Type†
(Both ✦)
_____
_____

FRL
Pool
(3 ✦)
1 _____ ______
2 _____ ______

Other
Digits
_______
_______

Absorb
1 _______
2 _______

Call Type†
(Both ✦)
_____
_____

_______

3 _______

_____

3 _____ ______

_______

3 _______

_____

_______

4 _______

_____

4 _____ ______

_______

4 _______

_____

5 _____ ______

_______

5 _______

_____

5 _____ ______

_______

5 _______

_____

6 _____ ______

_______

6 _______

_____

6 _____ ______

_______

6 _______

_____

FRL
Pool
(3 ✦)
1 _____ ______
2 _____ ______

Other
Digits
_______
_______

3 _____ ______
4 _____ ______

Table 18: Default Local Table
Subpattern A Time of Day
_________________

Subpattern B Time of Day
_________________

FRL
Pool
(2 ✦)
1 _____ ______
2 _____ ______

Other
Digits
_______
_______

Absorb
1 _______
2 _______

Call Type†
(Both ✦)
_____
_____

FRL
Pool
(2 ✦)
1 _____ ______
2 _____ ______

Other
Digits
_______
_______

Absorb
1 _______
2 _______

Call Type†
(Both ✦)
_____
_____

3 _____ ______

_______

3 _______

_____

3 _____ ______

_______

3 _______

_____

4 _____ ______

_______

4 _______

_____

4 _____ ______

_______

4 _______

_____

5 _____ ______

_______

5 _______

_____

5 _____ ______

_______

5 _______

_____

6 _____ ______

_______

6 _______

_____

6 _____ ______

_______

6 _______

_____

Table 19: Dial 0

✦
*
†
‡

Table 20: Special Number (411, 611, 811, 911)

Pool

FRL (3 ✦)

Other Digits

Pool‡

FRL (3 ✦)

Other Digits

1 _____

________

_____________________

1 _70__

________

_____________________

Factory Setting
Hybrid/PBX mode only
Select Voice only, Data only, or Both.
Always set to the first pool in the system; cannot be changed.

Form 3g-1

MERLIN LEGEND® Communications System Release 6.1

Form 3g

MERLIN LEGEND® Communications System Release 6.1

Form 3h
LS-ID Delay
Note: Only for lines attached to 800 GS/LS-ID module.

Line

Yes

No✦

Line

Yes

No✦

Line

1

31

61

2

32

62

3

33

63

4

34

64

5

35

65

6

36

66

7

37

67

8

38

68

9

39

69

10

40

70

11

41

71

12

42

72

13

43

73

14

44

74

15

45

75

16

46

76

17

47

77

18

48

78

19

49

79

20

50

80

21

51

22

52

23

53

24

54

25

55

26

56

27

57

28

58

29

59

30

60

Yes

No✦

✦ Factory Setting

Form 3h-1

MERLIN LEGEND® Communications System Release 6.1

Service Configuration Hunt Pattern
CPN/BN
Series
IOC “S” MLHG Comp Linear Circular

MERLIN LEGEND® Communications System Release 6.1

CPN/BN = Calling Party Number/Billing Number
MLHG = Multi-Line Hunt Group

Service Profile
Identifier

Form 3i

Directory
Number

Incoming Trunks: BRI Options (800 NI-BRI Module)

Logical Line
ID
Number

Form 3i-1

MERLIN LEGEND® Communications System Release 6.1

Form 3i (Continued)

Clock Synchronization—100D or BRI Modules*
Primary Clock
Synchronization

Secondary Clock
Synchronization

Tertiary Clock
Synchronization

Slot No. ________

Slot No. ________

Slot No. ________

DSL No. ________ (BRI
only)

DSL No. ________ (BRI
only)

DSL No. ________ (BRI
only)

Source

Source

Source

❑

Loop

❑

Loop ✦

❑

Loop ✦

❑

Local (100D only)

❑

Local (100D only)

❑

Local (100D only)

Timers
T200 Timer

T305 Timer

❑

1,000 ms. ✦

❑

30 seconds ✦

❑

_____ ms. (500 to 5,000 ms.
in increments of 500 ms)

❑

_____ seconds (2 to 60 seconds
in increments of 1 second)

T203 Timer

T308 Timer

❑

33 seconds ✦

❑

4 seconds ✦

❑

_____ seconds (10 to 255 seconds
in increments of 1 second)

❑

_____ seconds (2 to 10 seconds
in increments of 1 second)

T303 Timer
❑

4 seconds ✦

❑

_____ seconds (2 to 10 seconds
in increments of 1 second)

✦ Factory Setting
* If the system includes both 800 NI-BRI modules and 100D modules, sychronization planning should be completed at the
same time. Refer to Form 3b while completing this form.

Form 3i-2

MERLIN LEGEND® Communications System Release 6.1

Form 4a
Extension Copy: Analog Multiline Telephone Template
(Make a copy of this form for each Master Extension.)
Master Extension (Template Extension)
Master Ext. No.

Person/Location

Extensions Copied to

Form 4a-1

MERLIN LEGEND® Communications System Release 6.1

Form 4a (Continued)
Button Diagram

34 BUTTON
22 BUTTON
10 BUTTON
5 BUTTON

5

10

11

23

4

9

12

24

SA
Orig Only

3

8

13

25

SA Icom
Voice

2

7

14

26

SA Icom
Ring

1

6

15

27

16

28

17

29

18

30

19

31

20

32

21

33

22

34

Note: Lines 1 through 8 only default on a
telephone when the system is in Key mode.

Form 4a-2

MERLIN LEGEND® Communications System Release 6.1

Form 4b
Analog Multiline Telephone
(Make a copy of this form for each telephone.)
Logical ID _______________ Extension No. _______________ Person or Location _________________
❑ Copied from Master Ext. No. _________________

Extension Jack Pair
❑ Voice Announce to Busy (voice/voice)
❑ Simultaneous Voice and Data (voice/data)
Even-numbered jack
Logical ID ________ Ext. No. _________
Telephone Model
❑ MLC-5
❑ BIS-22D
❑ BIS-10

❑ BIS-34

❑ BIS- 22

❑ BIS-34D

❑ Other _____________________________
Adjuncts
❑ General Purpose Adapter
❑ FAX machine
❑ Answering machine
❑ Data terminal
❑ Other __________________________
❑ Supplemental Alert Adapter
Alert device type ___________________
❑ Headset
❑ Headset adapter
❑ Hands-free unit
❑ Hearing-impaired handset
❑ Noisy environment
❑ Off Premises
❑ Other _____________________________
Personal Lines
______ ______ ______ ______
______ ______ ______ ______

Shared Extension No. ________
❑ Ring
❑ No Ring
Auto Line Selection
______ ______ ______ ______
______ ______ ______ ______
Optional Features
Abbreviated Ring
❑ Off
❑ On ✦
Auto Callback
❑ Off ✦
❑ On
Call Waiting
❑ Off ✦
❑ On
Voice-Announced Calls
❑ On ✦
❑ Off
Coverage Inside
❑ Off
❑ On ✦
Computer Telephony Integrated Client PC
❑ Yes
❑ No ✦
Cover Ring Delay
Primary Cover Ring Delay
❑ 2 Rings ✦
❑ ____rings (1–6)
Secondary Cover Ring Delay
❑ 2 Rings ✦
❑ ____rings (1–6)
Group Coverage Ring Delay
❑ 3 Rings ✦
❑ ____rings (1–9)

✦ Factory Setting

Form 4b-1

MERLIN LEGEND® Communications System Release 6.1

Form 4b (Continued)

Button Diagram
❑ See Master Extension

34 BUTTON
22 BUTTON
10 BUTTON
5 BUTTON

5

10

11

23

4

9

12

24

SA
Orig Only

3

8

13

25

SA Icom
Voice

2

7

14

26

SA Icom
Ring

1

6

15

27

16

28

17

29

18

30

19

31

20

32

21

33

22

34

Note: Lines 1 through 8 only default on a
telephone when the system is in Key mode.

Form 4b-2

MERLIN LEGEND® Communications System Release 6.1

Form 4c
Extension Copy: MLX Telephone Template
(Make a copy of this form for each Master Extension.)
Master Extension (Template Extension)
Master Ext. No.

Person/Location

Extensions Copied to

Form 4c-1

26

28

21

23

25

27

10

15

20

9

14

19

8

13

18

7

12

17

6

11

16

5

3

8

4

2
3

2

1

SA
Orig. Only 1
SA Icom
Voice
SA Icom
Ring

6
5
4

10

Note: Lines 1 through 8 only
default on a telephone when
the system is in Key mode.

28

7

20

20

MERLIN LEGEND® Communications System Release 6.1

24

Form 4c (Continued)

Button Diagram

Form 4c-2
22

MERLIN LEGEND® Communications System Release 6.1

Form 4c (Continued)

13

16

12

15

11

14

5

10

4

9

3

8

2

Icom
Voice

7

1

Icom
Ring

6

Key Mode:
Up to 8 personal line
buttons are assigned
beginning at button 3.

Behind Switch Mode:
One prime line button
is assigned to button 3.

5

10

4

9

3

8

2

Icom
Voice

7

1

Icom
Ring

6

5
10

Behind Switch Mode:
One prime line is assigned
to button 3

Form 4c-3

MERLIN LEGEND® Communications System Release 6.1

MERLIN LEGEND® Communications System Release 6.1

Form 4d
MLX Telephone
(Make a copy of this form for each telephone.)
Logical ID _______________ Extension No. _______________ Person or Location _________________________
❑ Copied from Master Ext. No. _________________
❑ Wall Mount
Telephone Model
❑ MLX-20L™*

Optional Features

❑ MLX-28D™

Abbreviated Ring
❑ Off

❑ MLX-16DP™

❑ On ✦

❑ MLX-10D™
❑ MLX-10DP™†

Auto Callback
❑ Off ✦

❑ MLX-10™

❑ On

❑ MLX-5D™
❑ MLX-5™
Adjuncts
❑ Headset

Call Waiting
❑ Off ✦
❑ On

❑ Hearing-impaired handset

Voice-Announced Calls
❑ On ✦

❑ Noisy environment

❑ Off

❑ Multi-Function Module (MFM) (Not supported on
the MLX-5 and MLX-5D) Extension No. _____
❑ FAX machine
❑ Answering machine
❑ Data terminal
❑ Alert device, type _________________________
❑ Other ___________________________________
❑ Off Premises
❑ Passageway
Personal Lines
______ ______ ______ ______
______ ______ ______ ______
Shared Extension No. ________
❑ Ring
❑ No Ring
Auto Line Selection
______ ______ ______ ______

Coverage Inside
❑ Off
❑ On ✦
Cover Ring Delay
Primary Cover Ring Delay
❑ 2 Rings ✦
❑ ____rings (1–6)
Secondary Cover Ring Delay
❑ 2 Rings ✦
❑ ____rings (1–6)
Group Coverage Ring Delay
❑ 3 Rings ✦
❑ ____rings (1–9)
Computer Telephony Integrated Client PC
❑ Yes
❑ No ✦

______ ______ ______ ______
Centralized Programming Requirements**
❑ Assign Service Observing Button
✦ Factory Setting
* The system capacity for Personal Directories is decreased by one whenever an MLX-20L telephone is connected to an MLX port.
† This telephone is the same as the MLX-10D except it has an adjunct plug in the back for connection to a PC when programming
telephone features using the PassageWay™ Direct Connect Solution software application. This telephone is available with Release
2.1 and later.
** Refer to form 11 to assign as a Service Observer.

Form 4d-1

28

21

23

25

27

5

10

15

20

9

14

19

8

13

18

7

12

17

6

11

16

3

8

4

2
3

2

1

SA
Orig. Only 1
SA Icom
Voice
SA Icom
Ring

6
5
4

10

Note: Lines 1 through 8 only
default on a telephone when
the system is in Key mode.

28

7

20

20

MERLIN LEGEND® Communications System Release 6.1

26

Form 4d (Continued)

24

Button Diagram
❑ See Master Extension

Form 4d-2
22

MERLIN LEGEND® Communications System Release 6.1

Form 4d (Continued)
Button Diagram
❑ See Master Extension
13

16

12

15

11

14

5

10

4

9

3

SA
Orig. Only

8

2

SA Icom
Voice

7

1

SA Icom
Ring

6

Button Diagram for MLX-16DP Telephone

Form 4d-3

MERLIN LEGEND® Communications System Release 6.1

MERLIN LEGEND® Communications System Release 6.1

Form 4e
MFM Adjunct: MLX Telephone
Extension No. ____________________ Person or Location __________________________________________
Connected to MLX extension No.____________
Copied from Master Extension No.____________
Adjuncts
❑ FAX machine
❑ Answering machine
❑ Used as delay announcement
device for calling groups
Ext. No.
______ ______ ______ ______
______ ______ ______ ______

❑ Enable Ringing/Idle Line Preference
❑ Change Automatic Line Selection order to:
(1) System Access Ring, (2) System Access
Originate Only, (3) outside trunks assigned to
buttons 3 through 10
❑ Set Ringing Option to No Ring for each
personal line on which calls are not received

❑ Data terminal
❑ Alert device, type ______________
❑ Used as Calls-in-Queue Alarm
device for calling groups
Ext. No. ___________________

Auto Line Selection
______ ______ ______ ______
______ ______ ______ ______

❑ Other ________________________

Optional Features

Button Diagram
❑ See Master Extension
Line 3

5

Auto Callback
❑ Off ✦
Line 8

10

Line 2

4

Line 7

9

Line 1

3

Line 6

8

SA
Orig. Only

Centralized Programming Requirements
❑ Disable Voice Announce – change button 2
assignment to System Access Originate Only
and remove button 3 assignment

❑ On
Call Waiting
❑ Off ✦
❑ On
Coverage Inside
❑ Off
❑ On ✦

SA Icom
Voice

2

SA Icom
Ring

1

Line 5

7

Cover Ring Delay
Primary Cover Ring Delay
❑ 2 Rings ✦

Line 4

Note: Lines 1 through 8 only
default on a telephone when
the system is in Key mode.

6

❑ ____rings (1–6)
Secondary Cover Ring Delay
❑ 2 Rings ✦
❑ ____rings (1–6)
Group Coverage Ring Delay
❑ 3 Rings ✦
❑ ____rings (1–9)

✦ Factory Setting

Form 4e-1

MERLIN LEGEND® Communications System Release 6.1

MERLIN LEGEND® Communications System Release 6.1

Form 4f
Tip/Ring Equipment
(Make a copy of this form for each device.)
Logical ID _______________ Extension No. _______________ Person or Location _____________________
Type
❑ Single-line telephone

Optional Features
Auto Callback
❑ Off ✦

❑ Answering machine
❑ Used as delay announcement
device for calling groups
Ext. No.
______ ______ ______ ______
______ ______ ______ ______

❑ On
Call Waiting
❑ Off ✦
❑ On

❑ FAX machine
❑ Other ________________________

Coverage Inside
❑ Off

Adjuncts
❑ Speakerphone

❑ On ✦
HotLine
❑ Off ✦

❑ Hearing-impaired handset
❑ Noisy environment

❑ On
Tel. No. or Ext. No. ________________

❑ Off Premises

Cover Ring Delay

Auto Line Selection
______ ______ ______ ______
______ ______ ______ ______

Primary Cover Ring Delay
❑ 2 Rings ✦

Button Diagram

❑ ____rings (1–6)

Line 3

5

Line 8

10

Secondary Cover Ring Delay
❑ 2 Rings ✦
❑ ____rings (1–6)

Line 2

4

Line 7

9

Group Coverage Ring Delay
❑ 3 Rings ✦
❑ ____rings (1–9)

Line 1

3

Line 6

8

SA Icom
Ring

2

Line 5

7

SA Icom
Ring

1

Line 4

6

SA
Orig. Only

Centralized Programming Requirements
❑ Remove all but one SA button to disable
features such as Transfer and Conference.

✦ Factory Setting

Form 4f-1

MERLIN LEGEND® Communications System Release 6.1

MERLIN LEGEND® Communications System Release 6.1

Form 5a
Direct-Line Console (DLC): Analog
(Make a copy of this form for each telephone.)
Logical ID _______________ Extension No. _______________ Person or Location _____________________
❑ Copied from Master Ext. No. _________________
Extension Jack Pair
❑ Voice Announce to Busy (voice/voice)

Personal Lines
______ ______ ______ ______

❑ Simultaneous Voice and Data (voice/data)

______ ______ ______ ______

Even-numbered jack

Auto Line Selection
______ ______ ______ ______

Logical ID _________ Ext. No. __________
Console Model
❑ MERLIN II System Display Console
❑ BIS-34D

______ ______ ______ ______
Optional Features

❑ BIS-34

Abbreviated Ring
❑ Off

❑ BIS-22D

❑ On ✦

❑ BIS-22
Adjuncts
❑ General Purpose Adapter
❑ FAX machine
❑ Answering machine
❑ Data terminal
❑ Other __________________________

Auto Callback
❑ Off ✦
❑ On
Call Waiting
❑ Off ✦
❑ On

❑ Supplemental Station Alert Adapter
Alert Device type ___________________

Voice-Announced Calls
❑ On ✦

❑ Headset

❑ Off

❑ Headset adapter
❑ Hearing-impaired handset

Coverage Inside
❑ Off

❑ Noisy environment

❑ On ✦

❑ CTI PC (DLC must be a BIS set)
❑ Other _____________________________

Cover Ring Delay
Primary Cover Ring Delay
❑ 2 Rings ✦
❑ ____rings (1–6)
Secondary Cover Ring Delay
❑ 2 Rings ✦
❑ ____rings (1–6)
Group Coverage Ring Delay
❑ 3 Rings ✦
❑ ____rings (1–9)

✦ Factory Setting

Form 5a-1

DISPLAY CONSOLE WITH DSS
34 BUTTON
22 BUTTON

5

10

11

23

10

20

30

40

4

9

12

24

11

21

31

41

3

8

13

25

12

22

32

42

SA Icom
Voice

2

7

14

26

13

23

33

43

SA Icom
Ring

1

6

15

27

14

24

34

44

16

28

15

25

35

45

17

29

16

26

36

46

18

30

17

27

37

47

31

18

28

38

48

32

19

29

39

49

19

Alarm
20
21

Night
Serv

33

22

Send/
Remove
Msg

34

Trnsfr

Recall

Conf

Drop

Shift 1

Shift 2

Shift 3

Msg
Stat

Note: Alarm, Night Service, and Send/Remove Msg will be replaced
with Lines 30, 31, and 32 if the system has that many lines.

Assignment of outside trunks to console buttons begins with button number 3.

MERLIN LEGEND® Communications System Release 6.1

Form 5a (Continued)

Form 5a-2

Button Diagram
❑ See Master Extension

MERLIN LEGEND® Communications System Release 6.1

Form 5b
Direct-Line Console (DLC): Digital
(Make a copy of this form for each console.)
Logical ID _______________ Extension No. _______________ Person or Location _______________________
❑ Copied from Master Ext. No. ________________
Console Model
❑ MLX-20L™

Voice-Announced Calls
❑ On ✦

❑ MLX-28D™

❑ Off

Adjuncts
❑ Direct Station Selector
Number (1 or 2) ____________

Coverage Inside
❑ Off

❑ Multi-Function Module (MFM) Extension No.
_____
❑ FAX machine
❑ Answering machine
❑ Data terminal
❑ Alert device
type ____________________
❑ Other ___________________
❑ Headset
❑ Hearing-impaired handset
❑ Noisy environment
❑ CTI PC
Personal Lines
______ ______ ______ ______
______ ______ ______ ______

❑ On ✦
Cover Ring Delay
Primary Cover Ring Delay
❑ 2 Rings ✦
❑ ____rings (1–6)
Secondary Cover Ring Delay
❑ 2 Rings ✦
❑ ____rings (1–6)
Group Coverage Ring Delay
❑ 3 Rings ✦
❑ ____rings (1–9)
Centralized Programming Requirements*
❑ Assign Service Observing Button

Auto Line Selection
______ ______ ______ ______
______ ______ ______ ______
Optional Features
Abbreviated Ring
❑ Off
❑ On ✦
Auto Callback
❑ Off ✦
❑ On
Call Waiting
❑ Off ✦
❑ On

✦ Factory Setting
* Refer to Form 11 to assign as a Service Observer.

Form 5b-1

MERLIN LEGEND® Communications System Release 6.1

Form 5b (Continued)

16

14
4

11

9

10
5

12

SA Icom
Voice

SA Icom
Ring
1

3

2

1

6

7
2

Assignment of outside trunks to console buttons begins with number 3.

Form 5b-2

15

17

18

16
13

11

12

18
4

3

8

14

13

17

20
15

1
5

19

27
25

2
21

28
26

2
22

20

28

Button Diagram
❑ See Master Extension

MERLIN LEGEND® Communications System Release 6.1

Form 5c
MFM Adjunct: DLC
Extension No. ____________________ Person or Location ___________________________________________
Connected to MLX extension No. ___________
Copied from Master Extension No. ___________
Adjuncts
❑ FAX machine
❑ Answering machine
❑ Used as delay announcement
device for calling groups
Ext. No.
______ ______ ______ ______
______ ______ ______ ______
❑ Data terminal
❑ Alert device, type ______________
❑ Use as Calls-in-Queue Alarm
device for calling groups
Ext. No. ___________________
❑ Other ________________________
Button Diagram
❑ See Master Extnsions
Line 3

Centralized Programming Requirements
❑ Disable Voice Announce – change button 2
assignment to System Access Originate Only
and remove button 3 assignment
❑ Enable Ringing/Idle Line Preference
❑ Change Automatic Line Selection order to:
(1) System Access Ring, (2) System Access
Originate Only, (3) outside trunks assigned to
buttons 3 through 10
❑ Set Ringing Option to No Ring for each
personal line on which calls are not received
Auto Line Selection
______ ______ ______ ______
______ ______ ______ ______
Optional Features

Line 8

Auto Callback
❑ Off ✦
❑ On

Line 2

Line 7

Call Waiting
❑ Off ✦
❑ On

Line 1

SA
Orig. Only

Line 6

Coverage Inside
❑ Off
❑ On ✦

SA Icom
Voice

Line 5

SA Icom
Ring

Line 4

Note: Lines 1 through 8 only
default on a telephone when
the system is in Key mode.

Cover Ring Delay
Primary Cover Ring Delay
❑ 2 Rings ✦
❑ ____rings (1–6)
Secondary Cover Ring Delay
❑ 2 Rings ✦
❑ ____rings (1–6)
Group Coverage Ring Delay
❑ 3 Rings ✦
❑ ____rings (1–9)

✦ Factory Setting

Form 5c-1

MERLIN LEGEND® Communications System Release 6.1

MERLIN LEGEND® Communications System Release 6.1

Form 5d
Queued Call Console (QCC)*
(Make a copy of this form for each console.)
Logical ID _______________ Extension No. _______________ Person or Location ______________________

Adjuncts
❑ Direct Station Selector

Button Diagram

❑ Number (1 or 2) ____________
16

17

18

19

❑ Hearing-impaired handset

20

❑ Headset

Z
Y

11
6

12
7

CALL 1

1

W

X

START

SOURCE
T

CALL 2

S

2

CALL 3

RELEASE

DESTINATION
U

Q

13
8
HEADSET
MUTE

P
O

3

CANCEL

JOIN
V

R

HEADSET
AUTO ANSWER
HEADSET
STATUS

POOL STATUS

N

14
SEND/REMOVE
MSG
CALL 4

9
L
K

4

CALL 5/VA

5

G

H

POSITION
BUSY

10

15

I

M

ALARM

J

❑ Yes

NIGHT
SERVICE

Message Center Operator
❑ No

FORCED
RELEASE

❑ Noisy environment

* Hybrid/PBX mode only.

Form 5d-1

MERLIN LEGEND® Communications System Release 6.1

MERLIN LEGEND® Communications System Release 6.1

Form 6a
Optional Operator Features
Direct-Line Console
Operator Hold Timer
❑ 60 seconds ✦

DLC Automatic Hold
❑ Disable ✦

❑ _____ seconds (10–255)

❑ Enable
Queued Call Console*

Hold Return
❑ Remain on hold ✦

Message Center
❑ No

❑ Return to queue

❑ Yes, Operator Extension No. ______

Automatic Hold or Release
❑ Automatic Release ✦

Extended Call Completion
❑ Automatic completion ✦

❑ Automatic Hold

❑ Manual completion

Calls-in-Queue Alert
❑ Disable ✦

Return Ring
❑ 4 rings ✦

❑ Enable, Operator Extension No(s).
______ ______ ______ ______

❑ ______ rings (1–15)

Queue Over Threshold
❑ 0 calls ✦ (operators not
notified when calls are in queue)
❑ ______ calls (1–99)

Position Busy Backup
❑ No ✦
❑ Yes, Extension no. of calling
group backup __________
Operator Hold Timer
❑ 60 seconds ✦

Elevate Priority
❑ 0 seconds ✦ (calls are not
automatically reprioritized)

❑ ______ seconds (10–255)
Voice Announce
❑ Disable ✦

❑ ______ seconds (5–30)

❑ Enable
Direct Station Selector
Page Buttons
Page Button
Beginning extension for range

1

2

3

Enter first extension number for range of 50 (1 DSS) or 100 (2 DSSs) extensions for each Page button.

Call Park Codes (See Form 2d)
Factory-Set
Extension No.
881
882
883
884

Renumber to

Factory-Set
Extension No.

Renumber to

885
886
887
888

✦ Factory Setting
* Hybrid/PBX mode only

Form 6a-1

MERLIN LEGEND® Communications System Release 6.1

Form 6a (Continued)
Call Types*

Call Types

QCC Operator to Receive Calls

Dial 0
Call Follow/Forward
Unassigned DID
Listed Directory Number
QCC Extension
Returning

QCC Queue
Priority Level
(4✦)

N/A

N/A

Group Coverage Calls
Group QCC Operator to Receive
No.
Calls
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

✦ Factory Setting
* Hybrid/PBX mode only

Form 6a-2

QCC Queue
Priority Level Group
No.
(4✦)
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

QCC Operator to Receive
Calls

QCC Queue
Priority Level
(4✦)

MERLIN LEGEND® Communications System Release 6.1

Form 6b
Optional Extension Features
Forced
Account
Extension Code Entry
Number
No✦

Microphone*

Yes Enable✦ Disable

✦ Factory Setting
* MLX telephones only

Remote Call
Forwarding

Language*

Not
Delay
French Spanish
Allowed✦ Allowed 0✦-9 English✦

Trunk-to-Trunk
Transfer†
No✦

Yes

† Single-line telephones are restricted from completing a trunk-to-trunk transfer.

Form 6b-1

MERLIN LEGEND® Communications System Release 6.1

MERLIN LEGEND® Communications System Release 6.1

Form 6c
Principal User of Personal Line
Factory-Set
Trunk No.

Extension
No.

Factory-Set
Trunk No.

Extension
No.

Factory-Set
Trunk No.

Extension
No.

Factory-Set
Trunk No.

801

821

841

861

802

822

842

862

803

823

843

863

804

824

844

864

805

825

845

865

806

826

846

866

807

827

847

867

808

828

848

868

809

829

849

869

810

830

850

870

811

831

851

871

812

832

852

872

813

833

853

873

814

834

854

874

815

835

855

875

816

836

856

876

817

837

857

877

818

838

858

878

819

839

859

879

820

840

860

880

Extension
No.

Note: Lines must be assigned to the principal user’s extension before the principal users
can be programmed.
See Form 2c, page1 for telephone numbers and extension numbers assigned to trunks.

Form 6c-1

MERLIN LEGEND® Communications System Release 6.1

MERLIN LEGEND® Communications System Release 6.1

Form 6d
Message-Waiting Receivers
System Notification Threshold (0-30 seconds)_____________
(factory setting is 10 seconds)
Receivers
Fax Machine Extension No.

Ext. No.

Ext. No.

Ext. No.

Ext. No.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

Form 6d-1

MERLIN LEGEND® Communications System Release 6.1

MERLIN LEGEND® Communications System Release 6.1

Form 6e
Allowed Lists

List 0 ____________

List 1 ____________

List 2 ____________

List 3 ____________

0
1
2
3
4
5
6
7
8
9

0
1
2
3
4
5
6
7
8
9

0
1
2
3
4
5
6
7
8
9

0
1
2
3
4
5
6
7
8
9

Allow to
Ext. Nos.

Allow to
Ext. Nos.

Allow to
Ext. Nos.

Allow to
Ext. Nos.

Form 6e-1

MERLIN LEGEND® Communications System Release 6.1

Form 6e (Continued)

List 4 ____________
0
1
2
3
4
5
6
7
8
9

List 5 ____________
0
1
2
3
4
5
6
7
8
9

List 6 ____________
0
1
2
3
4
5
6
7
8
9

List 7 ____________
0
1
2
3
4
5
6
7
8
9

Allow to
Ext. Nos.

Allow to
Ext. Nos.

Allow to
Ext. Nos.

Allow to
Ext. Nos.

Form 6e-2

MERLIN LEGEND® Communications System Release 6.1

Form 6f
Disallowed Lists
List 0 ____________
0
1
2
3
4
5
6
7
8
9

List 1 ____________
0
1
2
3
4
5
6
7
8
9

Disallow to
Ext. Nos.

List 2 ____________
0
1
2
3
4
5
6
7
8
9

Disallow to
Ext. Nos.

Disallow to
Ext. Nos.

Form 6f-1

MERLIN LEGEND® Communications System Release 6.1

Form 6f (Continued)

List 3 ____________
0
1
2
3
4
5
6
7
8
9

0
1
2
3
4
5
6
7
8
9

Disallow to
Ext. Nos.

Form 6f-2

List 4 ____________

List 5 ____________
0
1
2
3
4
5
6
7
8
9

Disallow to
Ext. Nos.

Disallow to
Ext. Nos.

MERLIN LEGEND® Communications System Release 6.1

Form 6f (Continued)
List 7 ____________
List 6 ____________
0
1
2
3
4
5
6
7
8
9

List 7 ____________

Default Entries✦
0 0
1 1 0
2 1 1
3 1 8 0 9
4 1 7 0 0
5 1 9 0 0
6 9 7 6
7 1 P P P 9 7 6
8
9

*

Disallow to
Ext. Nos.

Disallow to
Ext. Nos.

✦ Factory Setting

Form 6f-3

MERLIN LEGEND® Communications System Release 6.1

MERLIN LEGEND® Communications System Release 6.1

Form 6g
Call Restriction Assignments and Lists
Ext
No.

Copy
From

Restriction Type
Out.

Toll

Unrest.

Allowed
List No.

Disallowed
List No.

ARS
Restriction Levels
(FRL)*

* Hybrid/PBX mode only.

Form 6g-1

MERLIN LEGEND® Communications System Release 6.1

Form 6g (Continued)

Ext
No.

Copy
From

* Hybrid/PBX mode only.

Form 6g-2

Restriction Type
Out.

Toll

Unrest.

Allowed
List No.

Disallowed
List No.

ARS
Restriction Levels
(FRL)*

MERLIN LEGEND® Communications System Release 6.1

Form 6h
Authorization Codes
Note: Keep this form in a secure place.
Option for SMDR Account Code Field: ❑ Authorization Code
❑ Home Extension ✦
Extension
Number

Authorization
Code

Extension
Number

Authorization
Code

✦ Factory Setting

Form 6h-1

MERLIN LEGEND® Communications System Release 6.1

Form 6h (Continued)
Authorization Codes
Note: Keep this form in a secure place.
Option for SMDR Account Code Field: ❑ Authorization Code
❑ Home Extension ✦
Extension
Number

✦ Factory Setting

Form 6h-2

Authorization
Code

Extension
Number

Authorization
Code

MERLIN LEGEND® Communications System Release 6.1

Form 6i
Pool Dial-Out Code Restrictions
Pool Dial-Out Codes
Extension
Number

70

890

891

892

893

894

895

896

897

898

899 Factory Set
Renumber
To

Factory Setting: Restricted for all codes. Enter unrestricted codes on this form.
Hybrid/PBX mode only.

Form 6i-1

MERLIN LEGEND® Communications System Release 6.1

MERLIN LEGEND® Communications System Release 6.1

Form 7a
Call Pickup Groups
Maximum: 30 groups. (Make additional copies if more than 8 groups are assigned.)
Group Number __________

Group Number __________

Group ID ____________________

Group ID ____________________

Ext. No.

Person or Location

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

Ext. No.

Person or Location

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

Group Number __________

Group Number __________

Group ID ____________________

Group ID ____________________

Ext. No.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

Person or Location

Ext. No.

Person or Location

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

Form 7a-1

MERLIN LEGEND® Communications System Release 6.1

Form 7a (Continued)

Group Number __________

Group Number __________

Group ID ____________________

Group ID ____________________

Ext. No.

Person or Location

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

Ext. No.

Person or Location

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

Group Number __________

Group Number __________

Group ID ____________________

Group ID ____________________

Ext. No.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

Form 7a-2

Person or Location

Ext. No.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

Person or Location

MERLIN LEGEND® Communications System Release 6.1

Form 7b
Group Paging
(See Form 2d)
Group No. 1

Group ID ________________

Factory-Set Ext. No. 793 Renumber to _____
Ext. No.

Group ID ________________

Factory-Set Ext. No. 794 Renumber to _____

Person or Location

1
2
3
4
5
6
7
8
9
10

Ext. No.

Person or Location

1
2
3
4
5
6
7
8
9
10

Group No. 3

Group ID ________________

Factory-Set Ext. No. 795 Renumber to _____
Ext. No.
1
2
3
4
5
6
7
8
9
10

Group No. 2

Group No. 4

Group ID ________________

Factory-Set Ext. No. 796 Renumber to _____

Person or Location

Ext. No.

Person or Location

1
2
3
4
5
6
7
8
9
10

Form 7b-1

MERLIN LEGEND® Communications System Release 6.1

Form 7b (Continued)

Group No. 5

Group No. 6

Group ID ________________

Ext. No.

Group ID ________________

Factory-Set Ext. No. 798 Renumber to _____

Factory-Set Ext. No. 797 Renumber to _____
Person or Location

Ext. No.

1
2
3
4
5
6
7
8
9
10

1
2
3
4
5
6
7
8
9
10

Group No. 7

Page All

Factory-Set Ext. No. 799 Renumber to _____

Form 7b-2

Person or Location

MERLIN LEGEND® Communications System Release 6.1

Form 7c
Group Coverage
Maximum: 32 groups. Make additional copies if more than 8 groups are assigned.
Group No.* ______
Senders
Extension Nos.

Group No.* ______
Senders
Extension Nos.

Group No.* ______
Senders
Extension Nos.

Group No.* ______
Senders
Extension Nos.

➞

➞

➞

➞

Receivers†

Receivers†

Receivers†

Receivers†

❑ Calling Group
or
❑ QCC queue‡
1
2
3
4
5
6
7
8

❑ Calling Group
or
❑ QCC queue‡
1
2
3
4
5
6
7
8

❑ Calling Group
or
❑ QCC queue‡
1
2
3
4
5
6
7
8

❑ Calling Group
or
❑ QCC queue‡
1
2
3
4
5
6
7
8

* If a group is the coverage group for AUDIX Voice Power/FAX Attendant System (the default is Group No. 30 but can be
changed), write “AUDIX/FA” by the group number and list the extensions of AUDIX Voice Power/FAX Attendant System
subscribers (see Form 2a).
† A maximum of 8 multiline telephones can be used as receivers.The QCC queue can also be a receiver for Hybrid/PBX mode
only, but it is not counted in the 8 receiver maximum. If a calling group is the receiver, it must be the only receiver for a
coverage group. If the system has AUDIX Voice Power/FAX Attendant System, you do not need to fill in receivers here.
‡ Hybrid/PBX mode only.

Form 7c-1

MERLIN LEGEND® Communications System Release 6.1

Form 7c (Continued)

Group No.* ______
Senders
Extension Nos.

Group No.* ______
Senders
Extension Nos.

Group No.* ______
Senders
Extension Nos.

Group No.* ______
Senders
Extension Nos.

➞

➞

➞

➞

Receivers†

Receivers†

Receivers†

Receivers†

❑ Calling Group
or
❑ QCC queue‡
1
2
3
4
5
6
7
8

❑ Calling Group
or
❑ QCC queue‡
1
2
3
4
5
6
7
8

❑ Calling Group
or
❑ QCC queue‡
1
2
3
4
5
6
7
8

❑ Calling Group
or
❑ QCC queue‡
1
2
3
4
5
6
7
8

* If a group is the coverage group for AUDIX Voice Power/FAX Attendant System (the default is Group No. 30 but can be
changed), write “AUDIX/FA” by the group number and list the extensions of AUDIX Voice Power/FAX Attendant System
subscribers (see Form 2a).
‡ A maximum of 8 multiline telephones can be used as receivers. The QCC queue can also be a receiver for Hybrid/PBX
mode only, but it is not counted in the 8 receiver maximum. If a calling group is the receiver, it must be the only receiver for
a coverage group.
‡ Hybrid/PBX mode only.

Form 7c-2

MERLIN LEGEND® Communications System Release 6.1

Form 7d
Group Calling*
Maximum: 32 groups. (Make a copy of this form for each group.)
Group Number (1–32)† _______________________
Factory-Set Ext. No. __________________________

Group ID†__________________________________
Renumber to _________________________
(See Form 2d)
Provide coverage for Coverage Group Numbers __________________________________________________

Extensions
Ext.
No.

Person or
Location

1
2
3
4
5

Ext.
No.
6
7
8
9
10

Person or
Location

Ext.
No.
11
12
13
14
15

Person or
Location

Ext.
No.

Person or
Location

16
17
18
19
20

Trunks/Pools

* Before adding to a calling group when programming, you must first remove trunks from the QCC.
† If the system has AUDIX Voice Power/FAX Attendant System, fill in only the Group Number and Group Name here, then fill in the
rest of the Group Calling information on Forms B & C of the AUDIX Voice Power planning forms.

Form 7d-1

MERLIN LEGEND® Communications System Release 6.1

Form 7d (Continued)
Group Number _________________________________
Group ID _______________________________________
Ext. No. ________________________________________
Calling Group Options*
Hunt Type
❑ Circular ✦

Overflow Coverage
❑ No ✦

❑ Linear

❑ Yes, Calling Group No. __________

❑ Most-Idle

❑ Yes, QCC LDN (queue) Extension No.
__________

Primary Delay Announcements
❑ No ✦

Overflow Threshold
❑ 1 call ✦

❑ Yes, Extension No. _____

❑ _____ calls (2–99)

_____ _____ _____ _____
_____ _____ _____ _____

Overflow Threshold Time
❑ 0 seconds ✦

Secondary Delay Announcement
❑ No ✦

❑ _____ seconds (1–900)

❑ Yes, Extension No. __________
Delay Interval _____(0✦-900 sec.)

Group Type
❑ Auto Login

❑ Disabled ✦

❑ Auto Logout ✦

❑ Enabled

❑ Integrated VMI†
❑ Generic VMI†

Message-Waiting Receiver
❑ No ✦

Prompt-Based Overflow
❑ Disabled ✦

❑ Yes, Extension No. __________

❑ Enabled

First Calls-in-Queue Alarm Threshold
❑ 1 call ✦

Queue Control
❑ 99 calls ✦

❑ _____ calls (2–99)

❑ _____ calls (0–98)

Second Calls-in-Queue Alarm Threshold
❑ 1 call ✦
❑ _____ calls (2–99)
Third Calls-in-Queue Alarm Threshold
❑ 1 call ✦
❑ _____ calls (2–99)
External Alert for Calls-in-Queue Alarm
❑ No ✦
❑ Yes, Extension No. __________

Form 7d-2

* If the system has AUDIX Voice Power/FAX Attendant
System, you do not need to fill in this information.
Settings will be automatically set by Integrated
Administration to defaults assumed by the AUDIX
Voice Power system (and not necessarily those
listed on this form). Changing the assumed defaults
could affect how the AUDIX Voice Power system
works. If you change them, DO SO WITH CAUTION,
and record the settings on this form. For more
information, see the AUDIX Voice Power
documentation.
†

Any port programmed as a VMI port is, by default,
restricted from making outgoing calls.

MERLIN LEGEND® Communications System Release 6.1

Form 8a
System Features
Transfer Options**

SMDR Options

Return Time Interval
❑ 4 rings ✦

Call Report Format
❑ Basic ✦

Call Length‡
❑ 40 seconds ✦

❑ 0 rings

❑ ISDN

❑ _____ seconds (0–255)

❑ _____ rings (1–9)

Calls Reported (non-UDP)
❑ Incoming and outgoing ✦

Calls Reported (UDP)
❑ Incoming and outgoing ✦

❑ Outgoing only

❑ None

†

One -Touch Call Handling
❑ One-Touch Transfer ✦
❑ Manual Completion
❑ Automatic Completion ✦
❑ One-Touch-Hold
Transfer Audible
❑ Music On Hold ✦
❑ Ringback
Type of Transfer
❑ Voice button
❑ Ring button ✦
Camp-On Return Time
❑ 90 seconds ✦
❑ _____ seconds (30–300)
Call Park Return Time
❑ 180 seconds ✦
❑ _____ seconds (30–300)
Automatic Callback Interval
❑ 3 rings ✦

Talk Time
❑ Enabled
❑ Disabled ✦
Inside Dial Tone
❑ Inside ✦
❑ Outside
Reminder Service Cancel
❑ No
❑ Yes, _____ time of day
Calls to Unassigned Extensions
❑ QCC Queue _________§
❑ Extension ✦, No. __________ (default is the
primary operator extension)
❑ Calling Group, Extension No. __________
Recall Timer
❑ 350 ms
❑ 450 ms ✦

❑ _____ rings (1–6)

❑ 650 ms

Extension Status
❑ Hotel

❑ 1 sec

❑ Assign to operator positions
______ ______ ______ ______
______ ______ ______ ______

Rotary
❑ Delay ✦
❑ No Delay

❑ Group Calling/CMS ✦

Note:

✦
*
†
‡
**
§

If you use equipment that rebroadcasts music or other copyrighted material, you may be required to obtain a copyright
license from, and pay license fees to, a third party such as the American Society of Composers, Artists, and Producers
(ASCAP) or Broadcast Music Incorporated (BMI). Or you can purchase a Magic-on-Hold system, which does not
require you to obtain such a license, from Lucent Technologies or an authorized representative.
Factory Setting
Beginning with Release 2.1; calls received on personal lines with Do Not Disturb on will go immediately to Coverage instead
of waiting for the Cover Delay Interval.
If the system has AUDIX Voice Power/FAX Attendant System, Integrated Administration will automatically set the Return Time
Interval to “6.”
For systems where the majority of lines are PRI, the SMDR Call Length should be one second.
Transfer features (and any feature that requires more than one SA button) can be disabled on single-line telephones by
removing all but one SA button via Centralized Programming.
Hybrid/PBX mode only

Form 8a-1

MERLIN LEGEND® Communications System Release 6.1

MERLIN LEGEND® Communications System Release 6.1

Form 9a
Night Service: Group Assignment*
Operator Ext. No. _____
User or
Ext. No.
Calling Calling Group
Name
Group No.
or Trunk
No.

Operator Ext. No. _____
Ext. No.
User or
Calling Calling Group
Group No.
Name
or Trunk
No.

Operator Ext. No. _____
Ext. No.
User or
Calling Calling Group
Group No.
Name
or Trunk
No.

Operator Ext. No. _____
Ext. No.
User or
Calling Calling Group
Group No.
Name
or Trunk
No.

* If the system has AUDIX Voice Power/FAX Attendant System, for each operator that will use Night Service with that system, fill
in the operator’s extension number and the calling group number for Automated Attendant. The information will be
programmed using Integrated Administration.

Form 9a-1

MERLIN LEGEND® Communications System Release 6.1

Form 9a (Continued)

Operator Ext. No. _____
User or
Ext. No.
Calling Calling Group
Name
Group No.
or Trunk
No.

Form 9a-2

Operator Ext. No. _____
Ext. No.
User or
Calling Calling Group
Group No.
Name
or Trunk
No.

Operator Ext. No. _____
Ext. No.
User or
Calling Calling Group
Group No.
Name
or Trunk
No.

Operator Ext. No. _____
Ext. No.
User or
Calling Calling Group
Group No.
Name
or Trunk
No.

MERLIN LEGEND® Communications System Release 6.1

Form 9b
Night Service: Outward Restriction

Password _______________________ (To keep the password private, do not fill in the blank.)
Emergency Allowed List
Item No.

Telephone No. (12 digits maximum)

0
1
2
3
4

Item No.

Telephone No. (12 digits maximum)

5
6
7
8
9

Exclusion List (Telephones not restricted during Night Service)*
Ext. No.

Name

Ext. No.

Name

Ext. No.

Name

* All AUDIX Voice Power/FAX Attendant System ports are automatically included in the Exclusion
List by Integrated Administration. However, to keep a record of these, you may choose to review
Form 2a and, for all extensions listed as ports, copy the extension number to this list.

Form 9b-1

MERLIN LEGEND® Communications System Release 6.1

Form 9b (Continued)
Exclusion List (Telephones not restricted during Night Service)
Ext. No.

Form 9b-2

Name

Ext. No.

Name

Ext. No.

Name

MERLIN LEGEND® Communications System Release 6.1

Form 9c
Night Service: Options
Day

Start Time*

Stop Time*

Sunday (0)
Monday (1)
Tuesday (2)
Wednesday (3)
Thursday (4)
Friday (5)
Saturday (6)
* Hours and minutes in 24-hour (military) time
Note:

Start time is the END of your business day.
Stop time is the BEGINNING of your business day.

Coverage Control
❑ Enable
❑ Disable ✦

✦ Factory Setting

Form 9c-1

MERLIN LEGEND® Communications System Release 6.1

MERLIN LEGEND® Communications System Release 6.1

Form 10a
Label Form: Posted Message

Message No.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

Default Label
DO NOT DISTURB
OUT TO LUNCH
AT HOME
OUT SICK
IN A MEETING
IN CONFERENCE
WITH A CLIENT
WITH A CUSTOMER
AWAY FROM DESK
OUT ALL DAY
CUSTM MSG11
CUSTM MSG12
CUSTM MSG13
CUSTM MSG14
CUSTM MSG15
CUSTM MSG16
CUSTM MSG17
CUSTM MSG18
CUSTM MSG19
CUSTM MSG20

Revised Message
(16 characters maximum)
(Cannot be changed)

Form 10a-1

MERLIN LEGEND® Communications System Release 6.1

Display
Telephone Number (40 digits maximum)

Yes ✦ No*

#600
#601
#602
#603
#604
#605
#606
#607

#609
#610
#611
#612
#613
#614
#615
#616
#617
#618
#619

Form 10b-1

#620
#621
✦ Factory Setting
* If you select “No” display, this indicates a Marked System Speed Dial number which can override calling restrictions.

System Speed Dial

#608

MERLIN LEGEND® Communications System Release 6.1

Form 10b

Name
Dial
Code (11 characters maximum)

#622
#623
#624
#625
#626
#627
#628
#629
#630
#631
#632
#633
#634
#635
#636
#637
#638
#639
#640
#641
#642
#643
✦ Factory Setting
* If you select “No” display, this indicates a Marked System Speed Dial number which can override calling restrictions.

Yes ✦ No*

MERLIN LEGEND® Communications System Release 6.1

Display
Telephone Number (40 digits maximum)

Form 10b (Continued)

Form 10b-2

Name
Dial
Code (11 characters maximum)

Display
Telephone Number (40 digits maximum)

Yes ✦ No*

#644
#645
#646
#647
#648
#649
#650

#652
#653
#654
#655
#656
#657
#658
#659
#660
#661
#662
#663

Form 10b-3

#664
#665
✦ Factory Setting
* If you select “No” display, this indicates a Marked System Speed Dial number which can override calling restrictions.

System Speed Dial

#651

MERLIN LEGEND® Communications System Release 6.1

Form 10b (Continued)

Name
Dial
Code (11 characters maximum)

#666
#667
#668
#669
#670
#671
#672
#673
#674
#675
#676
#677
#678
#679
#680
#681
#682
#683
#684
#685
#686
#687
✦ Factory Setting
* If you select “No” display, this indicates a Marked System Speed Dial number which can override calling restrictions.

Yes ✦ No*

MERLIN LEGEND® Communications System Release 6.1

Display
Telephone Number (40 digits maximum)

Form 10b (Continued)

Form 10b-4

Name
Dial
Code (11 characters maximum)

Display
Telephone Number (40 digits maximum)

Yes ✦ No*

#688
#689
#690
#691
#692
#693
#694
#695

#697
#698
#699
#700
#701
#702
#703
#704
#705
#706
#707

Form 10b-5

#708
#709
✦ Factory Setting
* If you select “No” display, this indicates a Marked System Speed Dial number which can override calling restrictions.

System Speed Dial

#696

MERLIN LEGEND® Communications System Release 6.1

Form 10b (Continued)

Name
Dial
Code (11 characters maximum)

#710
#711
#712
#713
#714
#715
#716
#717
#718
#719
#720
#721
#722
#723
#724
#725
#726
#727
#728
#729

✦ Factory Setting
* If you select “No” display, this indicates a Marked System Speed Dial number which can override calling restrictions.

Yes ✦ No*

MERLIN LEGEND® Communications System Release 6.1

Display
Telephone Number (40 digits maximum)

Form 10b (Continued)

Form 10b-6

Name
Dial
Code (11 characters maximum)

MERLIN LEGEND® Communications System Release 6.1

Form 11
Service Observing: Group Assignment
(Make additional copies of this form as needed.)
Maximum: 16 Service Observing Groups
Group No. _____

Group No. _____

Group No. _____

Group No. _____

Observer Ext. No.* _____ Observer Ext. No.* _____ Observer Ext. No.* _____ Observer Ext. No.* _____
Warning Tone: ❑ Yes✦ Warning Tone: ❑ Yes✦ Warning Tone: ❑ Yes✦
❑ No
❑ No
❑ No

Warning Tone: ❑ Yes✦

Member
Ext. No.†

Member
Ext. No.†

Member
Name

Member
Ext. No.†

Member
Name

Member
Ext. No.†

Member
Name

❑ No
Member
Name

* Observer extension must be an MLX telephone but cannot be a QCC or CTI Link. The Service Observing button on the
Observers telephone must be programmed via Centralized Telephone Programming.
† Member extensions may be any telephone type but cannot be a QCC or CTI Link. The number of members in a Service
Observing Group may equal the maximum number of system extensions.
✦ Factory Setting

Form 11-1

MERLIN LEGEND® Communications System Release 6.1

Form 11
Service Observing: Group Assignment
(Make additional copies of this form as needed.)
Maximum: 16 Service Observing Groups
Group No. _____

Group No. _____

Group No. _____

Group No. _____

Observer Ext. No.* _____ Observer Ext. No.* _____ Observer Ext. No.* _____ Observer Ext. No.* _____
Warning Tone: ❑ Yes✦ Warning Tone: ❑ Yes✦ Warning Tone: ❑ Yes✦
❑ No
❑ No
❑ No

Warning Tone: ❑ Yes✦

Member
Ext. No.†

Member
Ext. No.†

Member
Name

Member
Ext. No.†

Member
Name

Member
Ext. No.†

Member
Name

❑ No
Member
Name

* Observer extension must be an MLX telephone but cannot be a QCC or CTI Link. The Service Observing button on the
Observers telephone must be programmed via Centralized Telephone Programming.
† Member extensions may be any telephone type but cannot be a QCC or CTI Link. The number of members in a Service
Observing Group may equal the maximum number of system extensions.
✦ Factory Setting

Form 11-2

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

C Data Forms
Page C-1

C

Data Forms

C

This appendix contains one copy of each data form. The forms are listed in Table
C–1. You should make copies of these forms and use the copies, keeping the
originals for future use. The system planning forms are contained in Appendix B.
The T1/PRI Planner is contained in Appendix D. The NI-1 BRI Planner is
contained in Appendix G. The Network Engineering forms are contained in
Appendix I.
Table C–1.

Data Forms

Form No.
1a

Form Title
Modem Data Station

1b

ISDN Terminal Adapter Data Station

2

Data Hunt Groups

3

Digital Data/Video Station

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

C Data Forms
Page C-2

Page ______of______

MERLIN LEGEND® Communications System Release 6.1
Data Form 1a

Modem Data Station
Logical ID ________________ Extension No. ________________ Person or Location ________________________
Data Station Use
❑ Individual use

Call Restriction
❑ Unrestricted ✦

❑ Local host computer

❑ Outward Restrict

❑ LAN workstation

❑ Toll Restrict

Modem Pool Member
❑ No

❑ Allow List(s)
______ ______ ______ ______
______ ______ ______ ______

❑ Yes, Pool Number __________

❑ Disallowed List(s)
______ ______ ______ ______
______ ______ ______ ______

Assigned to Data Hunt Group
❑ No
❑ Yes, DHG Extension __________

Forced Account Code Entry
❑ No ✦

Optional Features
Pool Dial-Out Code Restriction
❑ Unrestricted from following codes 
______ ______ ______ ______
______ ______ ______ ______
❑ Restricted from following codes*
______ ______ ______ ______
______ ______ ______ ______

❑ Yes
Facility Restriction Level
❑ 3✦
❑ __________ (0 - 6)
Button Diagram
Hybrid/PBX Mode

Key Mode

SAO-O
Icom R

SA R à†

Icom R

SA R

Ringing Options
Idle Line
Preference
✦
*
 

Factory Setting
Factory setting is restricted for all codes.
Pool dial-out code access must be programmed.

Idle Line
Preference
à

Only one SA Ring button assigned on 008 MLX or
408 GS/LS-MLX module.

Form 1a-1

MERLIN LEGEND® Communications System Release 6.1
Data Form 1a

Page ______of______

Page ______of______

MERLIN LEGEND® Communications System Release 6.1
Data Form 1b

ISDN Terminal Adapter Data Station
Logical ID ________________ Extension No. ________________ Person or Location ________________________
Data Station Use
❑ Individual use

Call Restriction
❑ Unrestricted ✦

❑ Local host computer

❑ Outward Restrict

❑ LAN workstation

❑ Toll Restrict

Modem Pool Member
❑ No

❑ Allow List(s)
______ ______ ______ ______
______ ______ ______ ______

❑ Yes, Pool Number __________

❑ Disallowed List(s)
______ ______ ______ ______
______ ______ ______ ______

Assigned to Data Hunt Group
❑ No
❑ Yes, DHG Extension __________

Forced Account Code Entry
❑ No ✦

Optional Features
Pool Dial-Out Code Restriction
❑ Unrestricted from following codes 
______ ______ ______ ______
______ ______ ______ ______
❑ Restricted from following codes*
______ ______ ______ ______
______ ______ ______ ______

❑ Yes
Facility Restriction Level
❑ 3✦
❑ __________ (0 - 6)
Button Diagram
Key Mode

Hybrid/PBX Mode

SAO-O
Icom R

SA R à†

Icom R

SA V

Ringing Options
Idle Line
Preference
✦
*
 

Factory Setting
Factory setting is restricted for all codes.
Pool dial-out code access must be programmed.

Idle Line
Preference
à

Only one SA Ring button assigned on 008 MLX or
408 GS/LS-MLX module.

Form 1b-1

MERLIN LEGEND® Communications System Release 6.1
Data Form 1b

Page______of_______

MERLIN LEGEND Communications System Release 6.1
Data Form 2

Data Hunt Groups
(Make a copy for each group.)
Purpose of Group
Group Number (1 -32) _________ Factory-Set Ext. No. ___________
_____________________________
Group ID _____________________ Renumber To _________________
_____________________________
_____________________________
_____________________________
(example: Local Host Computer
Access Workstation or LAN
Access, etc.)
Stations
Ext.
No.

Person or
Location

1
2
3
4
5

Ext.
No.

Person or
Location

Ext.
No.

Person or
Location

11
12
13
14
15

6
7
8
9
10

Ext.
No.

Person or
Location

16
17
18
19
20

Trunks or Pools
Logical ID
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

Trunk
or Pool

Logical ID
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

Trunk
or Pool

Logical ID
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Trunk
or Pool

Logical ID

Trunk
or Pool

61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80

Form 2-1

MERLIN LEGEND Communications System Release 6.1
Data Form 2 (Continued)

Page______of_______

Group Number _________________________________
Group ID _______________________________________
Ext. No. ________________________________________
Calling Group Options
Hunt Type
❑ Circular ✦

Overflow Coverage
❑ No ✦

❑ Linear

❑ Yes, Calling Group No. __________

Delay Announcement
❑ No ✦
❑ Yes, Extension No. __________
Message-Waiting Receiver
❑ No ✦
❑ Yes, Extension No. __________
Calls-in-Queue Alarm Threshold
❑ 1 call ✦
❑ _____ calls (2Ð99)
External Alert for Calls-in-Queue Alarm
❑ No ✦
❑ Yes, Extension No. __________

Form 2-2

❑ Yes, QCC LDN (queue) Extension No.
__________
Overflow Threshold
❑ 1 call ✦
❑ _____ calls (2Ð99)
Group Type
❑ Auto Login
❑ Auto Logout ✦
❑ Integrated VMI
❑ Generic VMI
Coverage Group Receiver
❑ No
❑ Yes, Group No. ____________
(See Form 6d.)

MERLIN LEGEND Communications System Release 6.1
Data Form 3

Page______of_______

Digital Data/Video Station

Logical
ID

Extension

Data/Video
Type
1B
2B

Digital
Facilities
In
Out

Equipment
Person
Location

Form 3-1

MERLIN LEGEND Communications System Release 6.1
Data Form 3

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

D T1/PRI Planner
Page D-1

D

T1/PRI Planner

D

To ensure compatibility with the system, all local offerings of DS1 configurations
must be reviewed by Lucent Technologies Sales and Design Support Center
(SDSC) personnel. This review begins when SDSC receives the “T1/PRI Planner”
form. This appendix contains instructions for completing the planner, including a
blank form. You should make copies of the form pages and use the copies,
keeping the originals for future use.
NOTE:
In Release 6.0 and later systems, T1 trunks are ordered for private
networks. The MERLIN LEGEND System programs the T1 trunks as PRI
trunks between the switches. See the Network Reference for more
information on configuring a system in a private network.
The MERLIN LEGEND Communications System (Release 4.2 and later) are
capable supporting the services listed below for each type of central office switch:
■

AT&T Toll Services for 4ESS or 5ESS. Megacom WATS, Megacom 800,
ACCUNET SDS, Software Defined Network (SDN), MultiQuest, and Long
Distance.

■

5ESS Local. OUTWATS, 56/64 Digital, Virtual Private Network, and
INWATS.

■

MCI Toll Services for DMS-250 or DEX600E. MCI Prism, MCI VNet, MCI
800, MCI 900.

■

Local Exchange Carrier Services for DMS-100. DMS Private Network,
DMS INWATS (Inward Wide Area Telephone Service), DMS OUTWATS
(Outward Wide Area Telephone Service), DMS FX (foreign exchange),
DMS Tie Trunk.

■

Miscellaneous. Call-by-Call, other.

For more information on the particular services see the Feature Reference.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

D T1/PRI Planner
Page D-2

Form Needed

D

T1/PRI Planner

Planning Form Instructions
1.

On page 1, fill in the customer name, telephone number, and address.
NOTE:
Reference Number is filled in by SDSC.

2.

Fill in the Order Number.

3.

Identify the personnel handling the account:
a.

Account Executive’s name and telephone number.

b.

System Consultant’s name and telephone number.

4.

Identify the DS1 facility vendor by writing the vendor’s name under the
T1/PRI Vendor heading, along with the contact person’s name and
telephone number.

5.

Under the Installation heading:

6.

7.

8.

a.

Write the “Due Date” on which the installation is scheduled to be
complete.

b.

Write the date the equipment is scheduled for delivery to the
customer in the Materials-on-Job Date space.

Under the Installation Contacts heading, list the names and telephone
numbers of the personnel responsible for the equipment order and its
installation:
a.

(Order) Implementor

b.

SDSC Manager

c.

National Technical Service Center (NTSC) Engineer

d.

Data Services Organization (DSO) Manager

Under the question about whether the order has been placed:
■

If the order has been placed, check the Yes box and fill in the date.

■

If the order has not been placed, check the No box.

On page 2, complete one box for each 100D module by transferring the
options information for each module from the corresponding box on
Form 3b (page 1):
a.

Service Ordered or Planned (Type of Service)

b.

Frame Format

c.

Switch Type

d.

Line Coding (Suppression)

e.

Line Signaling Mode

f.

Synchronization Timing (Clock Synchronization: Source)

D

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

D T1/PRI Planner
Page D-3

9.

To ensure that the synchronization integrity of the DS1 network  both
this communications system and its far-end connections  is protected,
prepare the DS1 Planning Map on page 4 for review by SDSC. Describe
the entire network of DS1 facilities by summarizing the following for each
100D module:
a.

Fill in the control unit slot number(s) of the 100D modules connected
to the CSU(s).

b.

Write the approximate number of cable feet between each module
and its CSU or far-end connection (refer to the Line Compensation
entry on Form 3b, Page 1).

c.

For the model number(s) of the CSU(s), do one of the following:

d.

e.

10.

■

If the CSU is the ACCULINK 3150, check the box for the
ACCULINK 3150.

■

If the CSU is not the ACCULINK 3150, check the Other box
and write the manufacturer’s name and model number in the
space provided at the bottom of the page.

■

If no CSU is needed, check None.

In the connection block(s), describe the DS1’s far-end connection by
doing one of the following:
■

If connected to the telephone company central office, check
CO.

■

If connected to another communications system, check PBX.

■

If connected to the PRI network, check PRI.

■

If the facility’s type of service is T1, check the type(s) of
emulated trunks. Also, check the Services box if the facility
includes services such as MultiQuest with DNIS.

Describe the clock synchronization sources according to the key at
the lower left of the map.
i.

Draw a circle and line from the clock source to the
appropriate 100D module.

ii.

Label the circle P for primary, S for secondary, or T for tertiary.

Make a copy of the T1/PRI Planner for your records and forward the
original to SDSC.

As an example, the system described in Figure D–1 shows a processor module
system with two 100D modules.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

D T1/PRI Planner
Page D-4

The communications system in Figure D–1 is configured as follows:
■

Module 1 in slot 04 is connected to an ACCULINK 3150 CSU that is
approximately 100 cable feet from the control unit. (The DS1 facility is
connected to the PRI network.)

■

Module 2 in slot 05 is connected to an ACCULINK 3150 CSU that is
approximately 160 cable feet from the control unit. (The far end is another
communications system.)

■

The primary clock synchronization source is the PRI network connected to
Module 1. Its path is shown by a line and the letter P.

■

The secondary clock synchronization path, shown by a line and the letter
S, is the system internal clock.

DS1 Planning Map

CONTROL UNIT
Clock

S
100D
MODULE 1

100D
MODULE 2

100D
MODULE 3

SLOT:____
04

SLOT:____
05

SLOT:____

Approximate
Distance_____
100 ft

Approximate
Distance_____
160 ft

CSU

CSU

Acculink 3150
Other*
None

Acculink 3150
Other*
None

Approximate
Distance_____
CSU

Acculink 3150
Other*
None

P
Connection 1
CO
PBX
PRI**
T1 Emulated Trunks
Tie
LS
GS
DID
S56 Data
Services

Connection 2
CO
PBX
PRI**
T1 Emulated Trunks
Tie
LS
GS
DID
S56 Data
Services

Connection 3
CO
PBX
PRI**
T1 Emulated Trunks
Tie
LS
GS
DID
S56 Data
Services

Key:
Digital Transmission
Facility

* Other model numbers

Primary Synchronization
Source
P
Secondary Synchronization
Source

S

Tertiary Synchronization
Source
T

Figure D–1. Sample DS1 Planning Map

** The switching equipment
of the service provider
must be 4ESS Generic 13 or later
or 5ESS G6 or later.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

D T1/PRI Planner
Page D-5

SDSC also evaluates the complexity of the facility configuration requested.
Examples of complex configurations are connections into PBX networking
applications, connections to multiplexing arrangements, or applications that
involve customer engineering or design. SDSC then does one of the following:
■

If an order is considered complex, SDSC directs you to the Business
Communications System (BCS) National Engineering Center (NEC).

■

If SDSC notifies you that the order’s configuration is not complex, Tier Ill
General Business System (GBS) National Technical Service Center
(NTSC) is authorized to approve the configuration.

The NTSC group’s preauthorization review is based, in part, on information you
provide to them. Specifically, you must send them the following:
■

A copy of the planner

■

A completed “Non-Complex Configuration” sheet (pages 5 through 10 of
the Planner) for each 100D module you plan to install

Complete one Non-Complex Configuration page (pages 5 through 10) for each
100D module. Label the top right corner of the copies “Page 1 of _ ” (1, 2, or 3).
On each page:
1.

Write the module number (1, 2, or 3). Indicate the total number of 100D
modules (maximum of 3 for each system).

2.

Fill in the control unit slot number (refer to page 1 of Form 3b).

3.

In the Services section:
a.

Check the box next to each emulated trunk or service that will be
connected. Check only those services allowed on the type of service
(T1, AT&T Toll, MCI Toll, or DMS Local) selected for the module.

b.

Circle the channel(s) to which each emulated trunk or service will be
assigned.
NOTE:
No channel should show more than one trunk or service, and the
24th channel cannot be used if the signaling type is common
channel.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

D T1/PRI Planner
Page D-6

4.

If the type of service is PRI, complete the PRI Identification Service section
by doing one of the following:
■

If you are not planning to use the number identification service,
check the No box and proceed to Step 5.

■

If you are planning to use the identification services, check the Yes
box and check the service planned:
— For incoming calls, check one of the following boxes: ANI,
SID, or Both. If both automatic and extension identification
service are planned, indicate the order in which the information should be displayed (ANI then SID or SID then ANI).
— For outgoing calls, check either ANI, SID/ANI Privacy,
SID — Extension Based, or SID — Line Based to indicate
the service planned.
NOTE:
The availability of the caller identification information may be limited
by local-serving (caller’s) jurisdiction, availability, or central office
equipment.

5.

In the Channel Service Unit section:
a.

Check the box that describes the channel service unit used. If you
are not using the model listed, check the second box and write in the
manufacturer information that describes the unit.

b.

Forward all copies of this page along with a copy of the Planner to
Tier III, GBS NTSC.

MERLIN LEGEND Communications System Release 6.1

T1/PRI Planner (Continued)
For use with Form 3b, Incoming Trunks–DS1 Connectivity (100D Module)

Reference No. ___________________
Customer
*Name _________________________________________________________ Tel. No. ____________________
*Address __________________________________________________________________________________

* Order Number _______________________________
Account Executive ______________________________________________ Tel. No. ____________________
Systems Consultant _____________________________________________ Tel. No. ____________________

T1/PRI Vendor
*Name __________________________________________________________
Contact ________________________________________________________Tel. No. ____________________

Installation
Due Date ________________________________________________________
Materials-on-Job Date ____________________________________________

Installation Contacts
Implementor ___________________________________________________ Tel. No. ____________________
SDSC Manager ________________________________________________ Tel. No. ____________________
NTSC Engineer ________________________________________________ Tel. No. ____________________
DSO Manager _________________________________________________ Tel. No. ____________________
Has order been placed with the network provider for this service?
❑

Yes, Date _______________

❑

No

* Required fields for presale.

1

MERLIN LEGEND Communications System Release 6.1

T1/PRI Planner (Continued)
*Module 1
Service Ordered or Planned
❑ PRI

Line Coding (Suppression)
❑ B8ZS (Preferred)

❑ T1

❑ AMI-ZCS

Frame Format
❑ ESF (Preferred)

Line Signaling Mode
❑ Common Channel (Required for PRI)

❑ D4 (May be used if required by local
telephone company)

❑ Local

Switch Type (PRI Service Only)

Synchronization Timing
❑ Loop (Default)

❑ 4ESS

❑ Legend-NTWK

❑ Local

❑ 5ESS

❑ Legend-PBX

❑ DMS-250
❑ DMS-100
❑ DXE600

*Module 2
Service Ordered or Planned
❑ PRI

Line Coding (Suppression)
❑ B8ZS (Preferred)

❑ T1

❑ AMI-ZCS

Frame Format
❑ ESF (Preferred)

Line Signaling Mode
❑ Common Channel (Required for PRI)

❑ D4 (May be used if required by local
telephone company)

❑ Local

Switch Type (PRI Service Only)

Synchronization Timing
❑ Loop (Default)

❑ 4ESS

❑ Legend-NTWK

❑ Local

❑ 5ESS

❑ Legend-PBX

❑ DMS-250
❑ DMS-100
❑ DXE600

* All fields required for presale

2

MERLIN LEGEND Communications System Release 6.1

T1/PRI Planner (Continued)

*Module 3
Service Ordered or Planned
❑ PRI

Line Coding (Suppression)
❑ B8ZS (Preferred)

❑ T1

❑ AMI-ZCS

Frame Format
❑ ESF (Preferred)

Line Signaling Mode
❑ Common Channel (Required for PRI)

❑ D4 (May be used if required by local
telephone company)

❑ Local

Switch Type (PRI Service Only)

Synchronization Timing
❑ Loop (Default)

❑ 4ESS

❑ Legend-NTWK

❑ Local

❑ 5ESS

❑ Legend-PBX

❑ DMS-250
❑ DMS-100
❑ DXE600

3

MERLIN LEGEND Communications System Release 6.1

T1/PRI Planner (Continued)
DS1 Planning Map

CONTROL UNIT
Clock
100D
MODULE 1

100D
MODULE 2

100D
MODULE 3

SLOT:____

SLOT:____

SLOT:____

Approximate
Distance_____

Approximate
Distance_____
CSU

CSU

Acculink 3150
Other*
None

Connection 1
CO
PBX
PRI**
T1 Emulated Trunks
Tie
LS
GS
DID
S56 Data
Services

Acculink 3150
Other*
None

Connection 2
CO
PBX
PRI**
T1 Emulated Trunks
Tie
LS
GS
DID
S56 Data
Services

Approximate
Distance_____
CSU

Acculink 3150
Other*
None

Connection 3
CO
PBX
PRI**
T1 Emulated Trunks
Tie
LS
GS
DID
S56 Data
Services

Key:
Digital Transmission
Facility

* Other model numbers

Primary Synchronization
Source
P
Secondary Synchronization
Source

S

Tertiary Synchronization
Source
T

4

** The switching equipment
of the service provider
must be 4ESS Generic 13 or later
or 5ESS G6 or later.

MERLIN LEGEND Communications System Release 6.1

Page______of_______

T1/PRI Planner (Continued)
Non-Complex Configuration
Module _____ of ______ Slot No. __________
Services*
Subscribed To:

Channels Assigned to Service

❑ Ground-start
(T1 only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Loop-start
(T1 only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Tie Trunk
(T1 only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ MultiQuest 900 (w/wo DNIS)
(T1 or AT&T Toll)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Megacom†
(T1 or AT&T Toll)

❑ OUTWATS‡

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Megacom 800
(w/wo DNIS)†
(T1 or AT&T Toll)

❑ INWATS‡

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Megacom/
Megacom 800†
(T1 or AT&T Toll)

❑ OUTWATS/
INWATS‡

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ SDN†
(T1 or AT&T Toll)

❑ VPN†

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ ACCUNET Switched
❑ 56/64 Digital‡
Digital Service (AT&T Toll only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ ACCUNET Switched 56
Digital Data Service (T1 only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ DID
(T1 only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Call-by-Call Service Selection
(AT&T Toll only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ MCI PRISM††
(MCI Toll)

❑ MCI Vnet††

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ MCI 800††
(MCI Toll)

❑ MCI 900††

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ DMS Private#
(DMS Local)

❑ DMS INWATS#

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ DMS OUTWATS#
(DMS Local)

❑ DMS FX#

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ DMS Tie Trunk#
Digital Service (PRI only)

* Required fields for presale
† 4ESS
‡ 5ESS
†† DMS-250 or DEX600
# DMS-100

5

MERLIN LEGEND Communications System Release 6.1

Page______of_______

T1/PRI Planner (Continued)
Non-Complex Configuration
Module _____ of ______ Slot No. __________

PRI Identification Service
*Will SID/ANI be used?
Incoming calls
Outgoing calls

❑ ANI
❑ ANI

❑

No

❑

❑ SID
❑ SID/ANI Privacy

Yes
❑ Both . . . Prefer _____ then _____
❑ SID – Extension Based ❑ SID – Line Based

Channel Service Unit
Mfr
Model
REG#

❑
AT&T Paradyne
3150
AW2USA-74673-DD-E

❑§
____________________
____________________
____________________
____________________

§ If a CSU other than the one listed AT&T models is used, AT&T will not accept the responsibility for its installation, connection,
or testing.

* Required fields for presale

6

MERLIN LEGEND Communications System Release 6.1

Page______of_______

T1/PRI Planner (Continued)
Non-Complex Configuration
Module _____ of ______ Slot No. __________
Services*
Subscribed To:

Channels Assigned to Service

❑ Ground-start
(T1 only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Loop-start
(T1 only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Tie Trunk
(T1 only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ MultiQuest 900 (w/wo DNIS)
(T1 or AT&T Toll)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Megacom†
(T1 or AT&T Toll)

❑ OUTWATS‡

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Megacom 800
(w/wo DNIS)†
(T1 or AT&T Toll)

❑ INWATS‡

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Megacom/
Megacom 800†
(T1 or AT&T Toll)

❑ OUTWATS/
INWATS‡

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ SDN†
(T1 or AT&T Toll)

❑ VPN†

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ ACCUNET Switched
❑ 56/64 Digital‡
Digital Service (AT&T Toll only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ ACCUNET Switched 56
Digital Data Service (T1 only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ DID
(T1 only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Call-by-Call Service Selection
(AT&T Toll only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ MCI PRISM††
(MCI Toll)

❑ MCI Vnet††

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ MCI 800††
(MCI Toll)

❑ MCI 900††

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ DMS Private#
(DMS Local)

❑ DMS INWATS#

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ DMS OUTWATS#
(DMS Local)

❑ DMS FX#

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ DMS Tie Trunk#
Digital Service (PRI only)

* Required fields for presale
† 4ESS
‡ 5ESS
†† DMS-250 or DEX600
# DMS-100

7

MERLIN LEGEND Communications System Release 6.1

T1/PRI Planner (Continued)

Page______of_______

Non-Complex Configuration
Module _____ of ______ Slot No. __________

PRI Identification Service
*Will SID/ANI be used?
Incoming calls
Outgoing calls

❑ ANI
❑ ANI

❑

No

❑

❑ SID
❑ SID/ANI Privacy

Yes
❑ Both . . . Prefer _____ then _____
❑ SID – Extension Based ❑ SID – Line Based

Channel Service Unit
Mfr
Model
REG#

❑
AT&T Paradyne
3150
AW2USA-74673-DD-E

❑§
____________________
____________________
____________________
____________________

§ If a CSU other than the one listed AT&T models is used, AT&T will not accept the responsibility for its installation, connection,
or testing.

* Required fields for presale

8

MERLIN LEGEND Communications System Release 6.1

Page______of_______

T1/PRI Planner (Continued)
Non-Complex Configuration
Module _____ of ______ Slot No. __________
Services*
Subscribed To:

Channels Assigned to Service

❑ Ground-start
(T1 only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Loop-start
(T1 only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Tie Trunk
(T1 only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ MultiQuest 900 (w/wo DNIS)
(T1 or AT&T Toll)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Megacom†
(T1 or AT&T Toll)

❑ OUTWATS‡

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Megacom 800
(w/wo DNIS)†
(T1 or AT&T Toll)

❑ INWATS‡

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Megacom/
Megacom 800†
(T1 or AT&T Toll)

❑ OUTWATS/
INWATS‡

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ SDN†
(T1 or AT&T Toll)

❑ VPN†

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ ACCUNET Switched
❑ 56/64 Digital‡
Digital Service (AT&T Toll only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ ACCUNET Switched 56
Digital Data Service (T1 only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ DID
(T1 only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ Call-by-Call Service Selection
(AT&T Toll only)

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ MCI PRISM††
(MCI Toll)

❑ MCI Vnet††

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ MCI 800††
(MCI Toll)

❑ MCI 900††

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ DMS Private#
(DMS Local)

❑ DMS INWATS#

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ DMS OUTWATS#
(DMS Local)

❑ DMS FX#

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

1
13

2
14

3
15

4
16

5
17

6
18

7
19

8
20

9
21

10
22

11
23

12
24

❑ DMS Tie Trunk#
Digital Service (PRI only)

* Required fields for presale
† 4ESS
‡ 5ESS
†† DMS-250 or DEX600
# DMS-100

9

MERLIN LEGEND Communications System Release 6.1

T1/PRI Planner (Continued)

Page______of_______

Non-Complex Configuration
Module _____ of ______ Slot No. __________

PRI Identification Service
*Will SID/ANI be used?
Incoming calls
Outgoing calls

❑ ANI
❑ ANI

❑

No

❑

❑ SID
❑ SID/ANI Privacy

Yes
❑ Both . . . Prefer _____ then _____
❑ SID – Extension Based ❑ SID – Line Based

Channel Service Unit
Mfr
Model
REG#

❑
AT&T Paradyne
3150
AW2USA-74673-DD-E

❑§
____________________
____________________
____________________
____________________

§ If a CSU other than the one listed AT&T models is used, AT&T will not accept the responsibility for its installation, connection,
or testing.

* Required fields for presale

10

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

E DS1 Connectivity Ordering
Page E-1

E

DS1 Connectivity Ordering

E

After the contract is signed, the sales representative or authorized dealer contacts
the DS1 connectivity vendor to discuss the T1/PRI service order. The vendor
needs information about the communications system as well as customer
identification. Table E–1 describes the kind of information the vendor requires.
This table should be reviewed with the customer’s network representative or
dealer so the information will be available when needed.
Table E–1.

Guide to DS1 Connectivity Ordering

Communications System
Manufacturer
Model
Type (Mode)
Jack Type
Facility Interface Code

AT&T
MERLIN LEGEND
digital PBX
RJ48C or RJ48X
Digital D4 Framing
Digital ESF Framing
Digital ESF and B8ZS

Digital PBX
o Has the EIA standard CISA transmission path
o Is senderized
o Is the equipment that must be timed
o Has an internal stratum clock level of 4
o Provides automatic call distribution through Group Calling feature
o Provides loopback (keep signal alive) through CSU

E

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

E DS1 Connectivity Ordering
Page E-2

Channel Service Unit (CSU)
Manufacturer
Model
Reg. Number

AT&T
3150
AW2USA-74673-DD-E

Other _____
__________
__________

Facility Interface Codes:
Digital D4 Framing
Digital ESF Framing
Digital ESF and B8ZS
Standard CSU jacks and test point provided

Audible Ringing Source
o Digital PBX

o Channel Service

Testing Service
o AT&T

o ___

If a CSU other than those listed above is used, Lucent Technologies will not accept
the responsibility for its installation, connection, or testing.

Echo Control Device
not used

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

F Unit Load Calculation
Page F-1

F

Unit Load Calculation

F

A unit load is a measure of power (1.9 watts) used to determine the electrical load
that the following components have on each carrier’s power supply:
■

Telephones and Adjuncts. Only the telephones and adjuncts that connect
to the analog and digital ports on the control unit require unit load
calculation. Do not include any equipment with its own power supply in the
unit load calculation.

■

Direct Inward Dial (DID) modules

Unit load and power requirements for a new system are computed automatically
when the equipment for the system is initially ordered. These calculations are
based on the assumption that each module is fully utilized, that is, all jacks are
used.
It may be useful to obtain more accurate calculations, for example, if the modules
are not fully utilized, if there is a change in the equipment, or if you suspect that a
particular carrier has more unit loads than the power supply can handle. You can
calculate the actual unit load using the worksheet and instructions in this
appendix.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

F Unit Load Calculation
Unit Load Rules

Unit Load Rules

Page F-2

F

A general rule to follow is that if you can distribute the DID modules and telephone
modules equally across the carriers, you will prevent unnecessary drain on any
one carrier.
Also, depending on the system’s mode, the rules vary. This section provides the
rules for calculating unit loads for the different modes.

Unit Loads for the Hybrid/PBX Mode

F

The 391A1 and 391A2 power supplies have a maximum rating of 54 unit loads
and generally can support six modules of any type in a system in Hybrid/PBX
mode  without exceeding the 54-unit maximum. If, however, both of the
following conditions are true, the unit loads on a carrier might exceed the 54-unit
maximum:
■

All six carrier slots are occupied by MLX or analog multiline telephone
modules

■

The carrier has a total of more than 45 MLX-20L telephones or 34-button
analog multiline telephones installed

The 391C1 and 391A3 power supplies have a maximum rating of 75 unit loads. If
your system contains a 391A1 or 391A2 power supply module, and the unit loads
for that carrier will exceed 54, a 391C1 power supply should be installed in the
system.

Unit Loads for Key or Behind Switch Mode

F

In a Key or Behind Switch system with four or fewer modules, no calculation is
needed. The power supply generally supports four modules of any type in Key or
Behind Switch mode.

Calculating Unit Loads

F

Use the worksheet and instructions in the remainder of this appendix to calculate
unit loads for each carrier. Make a copy of all pages of the worksheet for each
carrier.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

F Unit Load Calculation
Unit Load Worksheet

Unit Load Worksheet
1.

Page F-3

F

Number of modules in carrier (excluding power supply
and processor):
__________________
■

If fewer than 5, no further calculation is required.

■

If 5 or 6, continue to Step 2.

2.

Key or Behind Switch mode only:
Indicate the configuration of lines; then go to Step 5.

 Key
 Modified

3.

Hybrid/PBX mode only:
Do all modules in the carrier have MLX and/or
analog multiline telephone jacks?

 Yes
 No

4.

■

If no, no further calculation is required.

■

If yes, continue to Step 4.

Hybrid/PBX mode only:
Calculate the total number of MLX and analog
multiline telephones.
Number of MLX-20L telephones connected to
modules in the carrier:

__________________

Number of MLX-28D telephones connected to
modules in the carrier:

__________________

Number of 34-button analog multiline telephones
connected to modules in the carrier:

__________________

Total of MLX-20L, MLX-28D, and 34-button analog
telephones
■

If the total is less than 45, no further calculation is
required.

■

If the total is 45 or more, continue to Step 5.

__________________

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

F Unit Load Calculation
Unit Load Worksheet

5.

Page F-4

Calculate the estimated unit loads.

Module

Qty

x

Unit
Load

008

12.0

008 MLX

13.25

008 OPT

8.0

012 T/R

8.4

016 T/R

12.8

100D

0.0

400 LS

0.0

400 EM

8.0

400 GS/LS/TTR

0.0

408

12.0

408 GS/LS

12.0

408 GS/LS-MLX

13.5

800

0.0

800 GS/LS

0.0

800 DID

8.0

800 GS/LS-ID

8.0

MERLIN LEGEND Mail

0.0

= Total

Total Estimated Unit Load

6.

■

If the total is less than 75 (for the 391C1 or 391A3 power supplies) or 54 (for
the 391A1 or 391A2 power supplies), no further calculation is required.

■

If the total is 75 (391C1 or 391A3 power supplies) or 54 (391A1 or 391A2
power supplies) or more, continue to Step 6.

Calculate the actual carrier unit load using the table on the next page.
■

If the total actual unit load is less than or equal to 75 (391C1 or 391A3
power supplies) or less than or equal to 54 (391A1 or 391A2 power
supplies), no further calculation is required.

■

If the total actual unit load is more than 75 (391C1 or 391A3 power supplies)
or more than 54 (391A1 or 391A2 power supplies), continue to Step 7.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

F Unit Load Calculation
Unit Load Worksheet

Module
Equipment
Network Access Lines*
DID
DS1
NI-1 BRI
GS/LS
Tie
Telephones
MLX-5
MLX-5D
MLX-10
MLX-10D
MLX-10DP
MLX-16DP
MLX-28D
MLX-20L
BIS-10
BIS-22
BIS-22D
BIS-34
BIS-34D
MLC-5
MDC 9000
MDW 9000
10-Button Basic
10-Button HFAI
34-Button Basic
34-Button DLX
34-Button BIS
34-Button BIS/DIS
Single-Line Telephone
Optional Equipment†
Direct Station Selector‡
General-Purpose Adapter
Hands-Free Unit
Headset Adapter
EICON board

Page F-5

Qty x

Unit Load
Hybrid/PBX
or Modified

= Total
Key

1.0
0.0
0.0
0.0
1.4

0.0
0.0
0.0
0.0
1.4

0.9
0.9
0.9
0.9
0.9
1.5
1.2
1.1
0.9
1.0
1.0
1.1
1.1
0.0
0.0
0.0
0.9
1.0
0.9
1.2
1.2
1.2
0.6

1.2
1.2
1.2
1.2
1.2
1.5
1.7
1.6
1.1
1.3
1.3
1.5
1.5
0.0
0.0
0.0
1.1
1.2
1.1
1.7
1.4
1.4
0.7

0.7
0.8
0.8
0.8
0.0
Total Actual Unit Load

0.9
1.0
1.0
1.0
0.0

* Unit loads are computed for each trunk for trunk-type network access lines.
† The MFM has its own wall power unit located at the telephone and therefore is not added to the
unit load calculation.
‡ Up to two DSSs (one DSS for each MLX-28D or MLX-20L) can be powered from each control
unit carrier. For example, a three-carrier system can have six system operator positions, each
with one DSS powered from the control unit.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

F Unit Load Calculation
Unit Load Worksheet

7.

Try to exchange modules between carriers to reduce the unit loads to 75 (if a
391C1 or 391A3 power supply is installed) or 54 (if a 391A1 or 391A2 power
supply is installed). (Remember that the 100D, 800 NI-BRI, 400 LS, 400 GS/LS,
800, and 800 GS/LS modules have unit loads of 0.0.) Repeat Steps 1 through 6
to recalculate unit loads for the new configuration.
NOTES:
Empty slots are not permitted between modules.

8.

■

If the exchange reduces the unit load to below the rated maximum for your
power supply module, no further calculation is required.

■

If your system has a 391A1 or 391A2 power supply and the exchange does
not reduce the unit load to 54, replace the 391A1 or 391A2 power supply
with a 391C1 power supply. If your system has a 391C1 or 391A3 power
supply and the exchange does not reduce the unit load to 75, continue to
Step 8.

Calculate the unit load for slots 5 and 6 of the carrier using the table on the
next page.
■

If the unit load for slots 5 and 6 is less than or equal to 27, power is
sufficient for the carrier.

■

If the unit load for slots 5 and 6 is more than 27, continue to Step 9.

Page F-6

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

F Unit Load Calculation
Unit Load Worksheet

Module
Equipment
Network Access Lines*
DID
DS1
NI-1 BRI
GS/LS
Tie
Telephones
MLX-10
MLX-10D
MLX-10DP
MLX-28D
MLX-20L
BIS-10
BIS-22
BIS-22D
BIS-34
BIS-34D
MLC-5
MDC 9000
MDW 9000
10-Button Basic
10-Button HFAI
34-Button Basic
34-Button DLX
34-Button BIS
34-Button BIS/DIS
Single-Line Telephone
Optional Equipment†
Direct Station Selector‡
General-Purpose Adapter
Hands-Free Unit
Headset Adapter

Page F-7

Qty x

Unit Load
Hybrid/PBX
or Modified

= Total
Key

1.0
0.0
0.0
0.0
1.4

0.0
0.0
0.0
0.0
1.4

0.9
0.9
0.9
1.2
1.1
0.9
1.0
1.0
1.1
1.1
0.0
0.0
0.0
0.9
1.0
0.9
1.2
1.2
1.2
0.6

1.2
1.2
1.2
1.7
1.6
1.1
1.3
1.3
1.5
1.5
0.0
0.0
0.0
1.1
1.2
1.1
1.7
1.4
1.4
0.7

0.7
0.9
0.8
1.0
0.8
1.0
0.8
1.0
Total Actual Unit Load

* Unit loads are computed for each trunk for trunk-type network access lines.
† The MFM has its own wall power unit located at the telephone and, therefore, is not added to
the unit load calculation.
‡ Up to two DSSs (one DSS for each MLX-28D or MLX-20L) can be powered from each control
unit carrier. For example, a three-carrier system can have six system operator positions, each
with one DSS powered from the control unit.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

F Unit Load Calculation
Unit Load Worksheet

9.

Try to exchange modules between carriers to reduce the unit loads for slots 5
and 6 through 27. (Remember that the 100D, 800 NI-BRI, 400 LS, 400 GS/LS,
800, and 800 GS/LS modules have unit loads of 0.0.) Repeat Steps 1 through 8
to recalculate unit loads for each new configuration.
NOTES:
Empty slots are not permitted between modules.
■

If the unit load for slots 5 and 6 is less than or equal to 27, power is
sufficient for the carrier.

■

If the exchange does not reduce the unit load for slots 5 and 6 to 27, install
wall power units for the appropriate number of telephones to reduce the unit
load to 27.

Page F-8

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

G NI-1 BRI Review
Page G-1

G

NI-1 BRI Review

G

This appendix contains instructions for completing the NI-1 BRI Planner Form. If
you have questions while completing the form prior to the sale, contact the Sales
and Design Support Center (SDSC) engineers. Once the contract has been
signed and the forms are completed, make a photocopy of the forms for your
records and forward the forms to the technician who will do the installation. The
technician will then fax a copy to the National Service Assistance Center (NSAC)
if any questions or problems occur at the customer site.
The NI-1 BRI Planner form should be used in conjunction with System Form 3i,
Incoming Trunks: BRI Options (800 NI-BRI Module).

Form Needed

G

NI-1 BRI Planner

Planning Form Instructions
NOTE:
Prior to completing any of the steps below, you should first verify that the
customer’s local service provider offers National ISDN-1 BRI service with
ISDN Ordering Code (IOC) standardized capability package “S” and a
separate Multi-Line Hunt (MLH) service, depending on the customer's
requirements. If the Central Office uses a Lucent Technologies 5ESS or
Siemens SSC EWSD switch, MLH is available through the Series
Completion feature. The Multiline Hunt Group (MLHG) feature on these CO
switches is not recommended for use with MERLIN LEGEND. The Northern
Telecom DMS-100 provides MLH service through the MLHG feature. A
customer may want to order several BRI lines, some assigned as IOC
package “S” and the others as MLH.

G

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

G NI-1 BRI Review
Page G-2

To properly order and program NI-1 BRI service, it may be necessary to
contact the local service provider to determine what services are available
and the type of switching equipment used. See Appendix H, “NI-1 BRI
Provisioning” for detailed information that the local service provider may
require in order to supply the necessary connections.
1.

On page 1, fill in the customer name, telephone number, and address.
NOTE:
Reference Number is filled in by SDSC.

2.

Fill in the Order Number.

3.

Identify the personnel handling the account:
a.

Account Executive’s name and telephone number.

b.

System Consultant’s name and telephone number.

4.

Identify the NI-1 BRI facility vendor by writing the vendor’s name under the
NI-1 BRI Vendor heading, along with the contact person’s name and
telephone number.

5.

Under the Installation heading:

6.

7.

a.

Write the “Due Date” on which the installation is scheduled to be
complete.

b.

Write the date the equipment is scheduled for delivery to the
customer in the Materials-on-Job Date space.

Under the Installation Contacts heading, list the names and telephone
numbers of the personnel responsible for the equipment order and its
installation:
a.

(Order) Implementor

b.

SDSC Manager

c.

National Technical Service Center (NTSC) Engineer

d.

Data Services Organization (DSO) Manager

Under the question about whether the order has been placed:
■

If the order has been placed, check the Yes box and fill in the
expected service turn on date.

■

If the order has not been placed, check the No box.

8.

On page 2, enter the type of BRI service to be ordered. Since MERLIN
LEGEND Release 4.0 supports only National ISDN-1 BRI (2B+D) service,
enter NI-1 BRI in the space provided under the Type of Service heading.

9.

Contact the local service provider and determine what type of CO switch
serves your area (such as, Lucent Technologies 5ESS, Northern Telecom
DMS-100, or Siemens SSC EWSD). Enter this information under the Type
of CO Switch heading on page 2 of the form.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

G NI-1 BRI Review
Page G-3

10.

Determine which type of configuration is best suited for your system. Some
guidelines for selecting the service configuration are shown below:
■

IOC capability package “S”
Each BRI line, also called a Digital Subscriber Line (DSL), consists
of two B-channels, both of which support voice and data calls. In
order to have two simultaneous voice or digital data calls, each DSL
must be assigned two Directory Numbers (DNs) and two Service
Profile Identifiers (SPIDs) by the CO. Basic call handling is
supported along with the Calling Party Number/Billing Number
(CPN/BN) identification feature. No packet data capabilities or
hunting features are provided.
NOTE:
On the Lucent Technologies 5ESS switch, the Calling Party
Number identification feature is assigned using the standard
BRCS preconstructed features /LICNDA and /CPCOFA. If it
is possible, request /CPCPFA for the Calling Number
Identification feature from your local service provider as it
provides a clearer display of the CPN information.
IOC package “S” supports a maximum of one call per
telephone number (DN) at any given time. If another call
comes in on that line, the caller gets a busy signal.
For Canada and those areas of the United States where IOC
package “S” is not available, the capability package that is
ordered must provide alternate voice/circuit-switched data on
both B-channels with no packet data capability or
supplementary voice features except for the CPN/BN feature
if available. See Appendix H, “NI-1 BRI Provisioning” for
detailed information.

■

Multiline Hunt (MLH)
This feature is not part of the IOC package “S” and must be
provisioned separately.
One or more BRI lines (and their associated DNs) are grouped
together with one (main) telephone number. When an incoming call
arrives at the main number, the CO searches through the DNs until
an available line is found.
NOTE:
Each DN in the MLH group can be dialed directly, but hunting
may not be initiated (depending on the CO switch).
For the Siemens SSD EWSD switch, each MLH group must be
assigned as either voice or data; alternate voice/data is not
supported as mixing the two types in one group could create call
interference. This constraint does not apply to the Lucent
Technologies 5ESS or the Northern Telecom DMS-100 switches.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

G NI-1 BRI Review
Page G-4

The programming for Multiline Hunt is CO switch dependent. The
Lucent Technologies 5ESS and Siemens SSC EWSD switches
provide hunting through the Series Completion feature. The
Northern Telecom DMS-100 switch provides hunting through the
Multiline Hunt Group (MLHG) feature. Contact the local service
provider to determine what type of switching equipment is in use
and check the appropriate box under the MLH subheading of the
Service Configurations section on page 2 of the form.
The MERLIN LEGEND has currently been tested with each switch
type in the following configurations:
— Lucent Technologies 5ESS in a linear hunt group
— Northern Telecom DMS-100 in a circular hunt group
— Siemens SSC EWSD in a circular hunt group
Other configurations are possible, but are not guaranteed to work.
Appendix H, “NI-1 BRI Provisioning” provides sample LEC
programming screens of the Series Completion and MLHG features.
These screens show the fields and parameters for the CO switch
and may be forwarded to the local service provider if necessary.
11.

Once you have determined your Service Configuration, do one of the
following:
■

If your Service Configuration will be IOC “S”, check the box beside
the IOC “S” selection under the Service Configuration heading, then
enter the number of BRI lines that will be provisioned using this
package.

■

If your Service Configuration will be MLH, check the box beside the
MLH selection under the Service Configurations heading.
— Check the box for MLHG (Northern Telecom DMS-100) or
Series Completion (Lucent Technologies 5ESS or Siemens
SSC EWSD).
— Enter the total number of BRI lines provisioned using MLH,
the number of BRI lines provisioned as voice only hunt
groups, the number of BRI lines provisioned as data only
hunt groups, and the number of BRI lines provisioned as
voice/data hunt groups in the spaces provided.
NOTE:
MERLIN LEGEND Release 4.0 does not support voice/data
hunt groups with the Siemens SSC EWSD CO switch.

12.

Specify the total number of BRI lines under the Number of BRI Lines
Ordered heading.

13.

If CPN/BN is available with the BRI lines ordered, check the CPN/BN box
under the Additional Features heading.

14.

Make a copy of the NI-1 BRI Planner for your records and forward the
original to the technician who will perform the installation.

MERLIN LEGEND Communications System Release 6.1

NI-1 BRI Planner (Continued)
For use with Form 3i, Incoming Trunks: BRI Options (800 NI-BRI Module)

Reference No. ___________________
Customer
*Name _________________________________________________________ Tel. No. ____________________
*Address __________________________________________________________________________________

* Order Number _______________________________
Account Executive ______________________________________________ Tel. No. ____________________
Systems Consultant _____________________________________________ Tel. No. ____________________

NI-1 BRI Vendor
*Name __________________________________________________________
Contact ________________________________________________________Tel. No. ____________________

Installation
Due Date ________________________________________________________
Materials-on-Job Date ____________________________________________

Installation Contacts
Implementor ___________________________________________________ Tel. No. ____________________
SDSC Manager ________________________________________________ Tel. No. ____________________
NTSC Engineer ________________________________________________ Tel. No. ____________________
DSO Manager _________________________________________________ Tel. No. ____________________
Has order been placed with the network provider for this service?
❑

Yes, Date _______________

❑

No

* Required fields for presale.

1

MERLIN LEGEND Communications System Release 6.1

NI-1 BRI Planner (Continued)

Type of Service*
❑ _______________________________________
Type of CO Switch
❑ _______________________________________
Service Configurations
❑ IOCÓSÓ
Number of BRI Lines Provisioned _______
❑ MLH:
Number
Number
Number
Number

❑ MLHG
❑ Series Completion
of BRI Lines Provisioned _______
of Voice Only Hunt Groups Provisioned _______
of Data Only Hunt Groups Provisioned _______
of Voice/Data Hunt Groups Provisioned  _______

Number of BRI Lines Ordered
❑ _______________________________________
Additional Features
❑ CPN/BN

* MERLIN LEGEND Release 4.0 supports only National ISDN-1 BRI (2B + D) service.
 
MERLIN LEGEND Release 4.0 does not support Voice/Data Hunt Groups with the Siemens SSC EWSD Central Office Switch.

2

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

H NI-1 BRI Provisioning
Page H-1

H

NI-1 BRI Provisioning

H

This appendix provides detailed information concerning the features and
translations that make up the ISDN Ordering Code (IOC) standardized capability
package “S”, as well as the Multiline Hunt (MLH) feature. The MLH feature is
provisioned using either the Multiline Hunt Group or the Series Completion
feature, depending on the CO switch type.
Specific translations are provided for the following switches:
■

Lucent Technologies 5ESS

■

Northern Telecom DMS-100

■

Siemens SSC EWSD

After determining that the local service provider offers National ISDN-1 service,
the information contained in this appendix should be given to the local service
provider if necessary.
NOTE:
The programming screens shown in this appendix are representative
samples only. The local service provider will need to enter applicable data
(such as the telephone numbers) where necessary. Also note that the
programming covered in this appendix does not take place on the MERLIN
LEGEND Communications System. All programming is performed by the
local service provider on the CO switch.

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Lucent Technologies 5ESS Switch Translations

Lucent Technologies 5ESS
Switch Translations

Page H-2

H

For the Lucent Technologies 5ESS switch, Capability Package “S” includes
alternate voice/circuit-switched data on two B-channels. It also supports Calling
Number Identification on data and voice connections. Please note that in order to
have simultaneous calls on the two B-channels, two Directory Numbers (DNs)
must be assigned with this package.
The Lucent Technologies 5ESS switch also allows alternate voice and data
hunting on one DN using the Series Completion feature.

H

ISDN Capability Package “S”

The information listed below provides the DN translations that define Capability
Package “S”, and the screens and fields that must be programmed.
The information provided shows the translations for one Digital Subscriber Line
(DSL) and two DNs. For multiple DSLs/DNs, the CO will duplicate these screens
and enter the applicable DSL and DN values as needed.

ISDN Ordering Code: Capability S

H

VIEW 23.2

H

DN1 Translations

H

Fields that must be programmed on Screens 1, 2, 3 and 4:
1.
9.
11.
14.
15.
16.
17.
18.
20.
21.
22.
23.
42.
43.
44.

DSL TN
ASSOC
OE
D ISCN
DSERV
B1SERV
B2SERV
NT1 TYPE
DSL CLS
RSTR MP
MDPKT
MTERM
USPID
MAXBCHL
ACT USER











<0>
<2>

<2>


MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

H NI-1 BRI Provisioning
Lucent Technologies 5ESS Switch Translations

Page H-3

Fields that must be populated on Screens 4, 5, and 6:
48.
49.
50.
55.
56.
60.
61.
63.
69.
70.
72.
126.
140.

CKT TN
CKT LCC
CKT RAX
TERMTYP
DISPLAY
CSV
CSV CHL
CSV LIMIT
CSD
CSD CHL
CSD LIMIT
CPN SCRN
PIC






<1>

<1>
<2>

<2>



The Calling Number Identification feature is assigned using the standard BRCS
preconstructed features /LICNDA and /CPCOFA. If it is possible, request
/CPCPFA for the Calling Number Identification feature, as it provides a clearer
display of the CPN information.
The Redirecting Number Delivery (RND) feature is assigned using the
preconstructed RND feature, /RND. These features are assigned to the user in
View 23.8, Field 109.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

H NI-1 BRI Provisioning
Lucent Technologies 5ESS Switch Translations

Page H-4

DN2 Translations (Note: DSL information was built with DN1)
Fields that must be populated on Screens 1, 2, 3 and 4:
1.
9.
11.
42.
43.
44.

DSL TN
ASSOC
OE
USPID
MAXBCHL
ACT USER





<2>


Fields that must be populated on Screens 4, 5, and 6:
48.
49.
50.
55.
56.
60.
61.
63.
69.
70.
72.
126.
140.

CKT TN
CKT LCC
CKT RAX
TERMTYP
DISPLAY
CSV
CSV CHL
CSV LIMIT
CSD
CSD CHL
CSD LIMIT
CPN SCRN
PIC






<1>

<1>
<2>

<2>



The Calling Number Identification feature is assigned using the standard BRCS
preconstructed features /LICNDA and /CPCOFA. If it is possible, request
/CPCPFA for the Calling Number Identification feature, as it provides a clearer
display of the CPN information.
The Redirecting Number Delivery (RND) feature is assigned using the
preconstructed RND feature, /RND. These features are assigned to the user in
View 23.8, Field 109.

H

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Lucent Technologies 5ESS Switch Translations

Series Completion Feature Translations

Page H-5

H

The sample screens shown below illustrate the translations for alternate voice and
data hunting on one main DSL and three DNs forming a linear series completion
group. Voice hunting is provided using Series Completion (Field 87, SERHLN).
Data hunting is provided with Call Forward Data Busy Line (/CFDBLAC).
The 5ESS limits the number of members of a series completion group to 16 DNs,
and the number of lines forwarded using /CFDBLAC to the value specified on
Screen 9, Field 176 (SIMINTRA). This value is currently set to 99 series
completion groups, but can be changed.
5ESS SWITCH LABNSC1
SCREEN 1 OF 14

(*)1.
(*)4.
(*)5.
(*)6.
(*)9.

RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT

DSL TN C 2228700
MLHG
____
TERM
____
DSL OE _ ________
ASSOC U
CKT

SERVICES AND FEATURES
-----------------------BRCS FEATURE LIST
BRCS FEATURE PARAMETERS
DELFEAT LIST
DPKT
DSL INFO
ODB
PPB1
PPB2
USER INFO

5ESS SWITCH LABNSC1
SCREEN 2 OF 14

>11.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.

OE I 00101209
D ISCN 007096
D SERV SX
B1 SERV DMD
B2 SERV DMD
NT1 TYPE AULC
PM GRP PMDEF
DSL CLS STD
RSTR MP N
ACSR INH Y
MDPKT 8
MTERM 2

RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (DSL INFO)
25. CUT DGTS
2228
26. ACSR GRP___________
27. DFLT SRV__________

SCREENS
------6
7 to 9
4 & 5
14
10
2
11
12
13
3

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Lucent Technologies 5ESS Switch Translations

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (USER INFO)

SCREEN 3 OF 14

>28.
29.
30.
31.
32.
33.

USPID
0122287000
MAXB CHL1
ACT USERY
PPB1 USRN
PPB2 USRN
AGI
_
5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (CKT)

SCREEN 4 OF 14

>34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.

CKT TN
CKT LCC
CKT RAX
CKT MLHG
CKT TERM
NEW TN
CONFIG GRP
TERMTYP
DISPLAY
EKTS
CA
CA QTY

2228700
DSL
1
____
____
____
NI17507B
TYPEA
Y
____
___
__

CIRCUIT VOICE (CSV)
46. CSV
1
47. CSV CHL
ANY
48. CSV ACO
49. CSV LIMIT
1
50. CSV NBLIMIT __
51. SP DNA
___
52. SP DNA QTY __
53. AU DNA
54. AU DNA QTY

TKSN
TAUTON
SHAREDN
SAUTON
PRIVACYN
ICPN
SUSON
SUSTN

CIRCUIT
55. CSD
56. CSD
57. CSD
58. CSD
59. CSD
60. K56
61. K56
62. K64
63. K64

DATA (CSD)
1
CHL
ANY
ACO
_____
LIMIT
1
NBLIMIT __
DNA
___
DNA QTY __
DNA
___
DNA QTY __

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (CKT)

SCREEN 5 OF 14

>64.
65.
66.
67.
68.
69.
70.
71.

Page H-6

72.
73.
74.
75.
76.
77.
78.
79.
80.
81.

SAR QTY__
SAR ORIGN
SAR TERMN
INCOMINGN
INTERCOMN
ORIG CWN
PPN
CA PREFI
AUTO HOLDN
ONE TOUCHN

82.
83.
84.
85.
86.
87.
88.
89.
90.
91.
92.
95.

BUSY MONITORN
ATT MLHG____
RBV TGN____
ERCO ASGNN
ERCO ACTN
SERHLN2228701
BCK LNKN
ACD POS NUM____
CIDIALALLOW
PIC____
PTC____
E911 PSAPN

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Lucent Technologies 5ESS Switch Translations

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT

SCREEN 6 OF 14

>106. BFGN
ROW FEATURE
1 /LIDLXA
2 /CPCPFA
3 /CFDBLAC
4 ________
5 ________
6 ________
7 ________
8 ________
9 ________

______ _
A
A P C R
FEATURE
Y _ N N 10 ______
Y _ N N 11 ______
Y _ N N 12 ______
_ _ _ _ 13 ______
_ _ _ _ 14 ______
_ _ _ _ 15 ______
_ _ _ _ 16 ______
_ _ _ _ 17 ______
_ _ _ _ 18 ______

TG:GRPID
MOH ALW
IDP NAME
DPAT CAT
ICR SFG
SC1NAME
SC1S
SC2NAME
SC2S
CPUO:SELQ1
CPUO:SELQ2
CPUT:TPREDQ

SCREEN 8 OF 14

0
_
________
0
0
________
_
________
_
0
0
0

146.
147.
148.
149.
150.
151.
152.
153.
154.
155.
156.
157.

FEATURE
________
________
________
________

(FL)
A
_
_
_
_
_
_
_
_
_

P
_
_
_
_
_
_
_
_
_

A
C
_
_
_
_
_
_
_
_
_

R
_
_
_
_
_
_
_
_
_

28
29
30
31
32
33
34
35
36

FEATURE
________
________
________
________
________
________
________
________
________

A
_
_
_
_
_
_
_
_
_

A
C
_
_
_
_
_
_
_
_
_

P
_
_
_
_
_
_
_
_
_

ACSR GRPNM
EDS:GRPNM
BCLID GRP
PFA:VGRPNM
PFA:DGRPNM
ATH:VGRPNM
ATH:DGRPNM
MDR:GRPNM
ACCT:GRPNM
ARS:VGRPNM
ARS:DGRPNM
FRL

________
________
________
________
________
________
________
________
________
________
________
___

158.
159.
160.
161.
162.
163.
164.
165.
166.
167.

QALWD
PRIORITY Q
ARSSI
DIALPLN
ALWMDR
ACSR PINREQ
DRING
DCW DRING
CWO DRING
MWY DRING

_
_
__
___
_
_
_
_
_
_

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (HIGH RUNNER FEATURE PARAMETERS)

>172. MESSAGE SERVICE (MSS)
ROW
1
2
3
4

109. FEATURE LIST
A
A P C R
FEATURE
_ _ _ _ 19 ______
_ _ _ _ 20 ______
_ _ _ _ 21 ______
_ _ _ _ 22 ______
_ _ _ _ 23 ______
_ _ _ _ 24 ______
_ _ _ _ 25 ______
_ _ _ _ 26 ______
_ _ _ _ 27 ______

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (HIGH RUNNER FEATURE PARAMETERS)

SCREEN 7 OF 14

>134.
135.
136.
137.
138.
139.
140.
141.
142.
143.
144.
145.

Page H-7

GRPNM
________
________
________
________

175. MW:DCNDN _______________

R
_
_
_
_
_
_
_
_
_

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Lucent Technologies 5ESS Switch Translations

SCREEN 9 OF 14

Page H-8

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (HIGH RUNNER FEATURE PARAMETERS)
>176. CALL FORWARDING FEATURE PARAMETERS (CF)

ROW
1
2
3
4
5
6

FEATURE
FWD TO DN
TIMEOUT BSRING
/CFDBLAC2228701
0
N
__________________________
0
_
__________________________
0
_
__________________________
0
_
__________________________
0
_
__________________________
0
_

DPKT TN
LCC
RAX
MLHG
TERM
LNR HNT TN
HUNT DEACT
CHL SEL
NEW TN

_______
____
_
____
____
_______
_
N
_______

ODB TN
LCC
RAX
MLHG
TERM
LNR HNT TN
HUNT DEACT
CHL SEL
ISCN1
ISCN2
BAND
ODB

192.
193.
194.
195.
196.
197.

IECP DNIC
PB GRP
NOTIF
ICP
HUNT NOTIF
TCID

____
___
NO
N
___
____

198.
199.
200.
201.
202.
203.
204.
205.
206.
207.
208.
209.

H PVC LCN
L IN LCN
H IN LCN
L 2W LCN
H 2W LCN
L OUT LCN
H OUT LCN
BUSY LIMIT
PMDR GRP
PMDR ACT
DNA
DNA QTY

__
__
__
__
_
__
__
___
________
_
___
_

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (ODB)

SCREEN 11 OF 14

>210.
211.
212.
213.
214.
215.
216.
217.
218.
219.
220.
221.

SIMINTRA
99
0
0
0
0
0

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (DPKT)

SCREEN 10 OF 14

>183.
184.
185.
186.
187.
188.
189.
190.
191.

SIMINTER
1
0
0
0
0
0

_______
___
0
____
____
_______
_
N
______
______
0
_

222. RATE
____
223. N2
__
224. T1
___
225. T3
__
226. WNDSZ
_
227. NEW TN
_______
228. IECP DNIC ____
229. PB GRP
___
230. NOTIF
____
231. T3XX
0
232. ICP
N
233. HUNT NOTIF ___

234.
235.
236.
237.
238.
239.
240.
241.
242.
243.
244.

L IN LCN
H IN LCN
L 2W LCN
H 2W LCN
L OUT LCN
H OUT LCN
BUSY LIMIT
PMDR GRP
PMDR ACT
DNA
DNA QTY

___
___
___
___
___
___
___
_______
_
___
_

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Lucent Technologies 5ESS Switch Translations

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (PPB1)

SCREEN 12 OF 14

>245.
246.
247.
248.
249.
250.
251.
252.
253.

PPB1 TN
LCC
RAX
MLHG
TERM
LNR HNT TN
HUNT DEACT
CHL SEL
ISCN

_______
___
0
____
____
_______
_
N
______

254.
255.
256.
257.
258.
259.
260.
261.
262.
263.

PPB2 TN
LCC
RAX
MLHG
TERM
LNR HNT TN
HUNT DEACT
CHL SEL
ISCN

SCREEN 14 OF 14

RATE
N2
T1
T3
WNDSZ
NEW TN
IECP DNIC
PB GRP
ICP
HUNT NOTIF

_____
___
____
___
__
_______
____
___
N
___

264.
265.
266.
267.
268.
269.
270.
271.
272.
273.

H PVC LCN
L IN LCN
H IN LCN
L 2W LCN
H 2W LCN
L OUT LCN
H OUT LCN
BUSY LIMIT
PMDR GRP
PMDR ACT

___
___
___
___
___
___
___
___
_______
_

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (PPB2)

SCREEN 13 OF 14

>274.
275.
276.
277.
278.
279.
280.
281.
282.

Page H-9

______
___
0
____
____
______
_
N
_____

283.
284.
285.
286.
287.
288.
289.
290.
291.
292.

RATE
N2
T1
T3
WNDSZ
NEW TN
IECP DNIC
PB GRP
ICP
HUNT NOTIF

_____
__
___
__
_
______
____
___
N
___

293.
294.
295.
296.
297.
298.
299.
300.
301.
302.

H PVC LCN
L IN LCN
H IN LCN
L 2W LCN
H 2W LCN
L OUT LCN
H OUT LCN
BUSY LIMIT
PMDR GRP
PMDR ACT

___
___
___
___
___
___
___
___
______
_

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT

WARNING: These fields delete features currently on the view or in a BFG.
Deletion of a feature in BFG may invoke BFG reselection.
303. DELFEAT
ROW
1
2
3

FEATURE
________
________
________

No Messages

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

H NI-1 BRI Provisioning
Lucent Technologies 5ESS Switch Translations

5ESS SWITCH LABNSC1
SCREEN 1 OF 14

(*)1.
(*)4.
(*)5.
(*)6.
(*)9.

>11.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.

OE I 00101209
D ISCN 007096
D SERV SX
B1 SERV DMD
B2 SERV DMD
NT1 TYPE AULC
PM GRP PMDEF
DSL CLS STD
RSTR MP N
ACSR INH Y
MDPKT 8
MTERM 2

SCREEN 3 OF 14

>28.
29.
30.
31.
32.
33.

RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT

DSL TN C 2228701SERVICES AND FEATURES SCREENS
MLHG ____
------------------------ ------TERM ____
BRCS FEATURE LIST
6
DSL OE _ __________BRCS FEATURE PARAMETERS
7 to 9
ASSOC U
CKT
4 & 5
DELFEAT LIST
14
DPKT
DSL INFO
2
ODB
PPB1
PPB2
USER INFO

5ESS SWITCH LABNSC1
SCREEN 2 OF 14

USPID0122287010
MAXB CHL1
ACT USERY
PPB1 USRN
PPB2 USRN
AGI_

Page H-10

RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (DSL INFO)
25. CUT DGTS2228
26. ACSR GRP___________
27. DFLT SRV__________

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (USER INFO)

10
11
12
13
3

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Lucent Technologies 5ESS Switch Translations

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (CKT)

SCREEN 4 OF 14

>34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.

CKT TN
CKT LCC
CKT RAX
CKT MLHG
CKT TERM
NEW TN
CONFIG GRP
TERMTYP
DISPLAY
EKTS
CA
CA QTY

2228701
DSL
1
____
____
_______
NI17507A
TYPEA
Y
_____
___
__

TKSN
TAUTON
SHAREDN
SAUTON
PRIVACYN
ICPN
SUSON
SUSTN

72.
73.
74.
75.
76.
77.
78.
79.
80.
81.

ROW FEATURE
1 /CPCPFA
2 /LIDLXA
3 /CFDBLAC
4 ________
5 ________
6 ________
7 ________
8 ________
9 ________

CIRCUIT VOICE (CSV)
CSV
1
CSV CHL
ANY
CSV ACO
_____
CSV LIMIT
1
CSV NBLIMIT __
SP DNA
___
SP DNA QTY __
AU DNA
___
AU DNA QTY __

55.
56.
57.
58.
59.
60.
61.
62.
63.

CIRCUIT DATA (CSD)
CSD
1
CSD CHL
ANY
CSD ACO
_____
CSD LIMIT
1
CSD NBLIMIT __
K56 DNA
___
K56 DNA QTY __
K64 DNA
___
K64 DNA QTY __

SAR QTY__
82. BUSY MONITORN
SAR ORIGN
83. ATT MLHG____
SAR TERMN
84. RBV TGN____
INCOMINGN
85. ERCO ASGNN
INTERCOMN
86. ERCO ACTN
ORIG CWN
87. SERHLN2228703
PPN
88. BCK LNKY
CA PREFI
89. ACD POS NUM____
AUTO HOLDN 90. CIDIALALLOW
ONE TOUCHN 91. PIC____
92. PTC____
95. E911 PSAPN

SCREEN 6 OF 14

>106. BFGN

46.
47.
48.
49.
50.
51.
52.
53.
54.

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (CKT)

SCREEN 5 OF 14

>64.
65.
66.
67.
68.
69.
70.
71.

Page H-11

______ _
A
A P C R
Y _ N N 10
Y _ N N 11
Y _ N N 12
_ _ _ _ 13
_ _ _ _ 14
_ _ _ _ 15
_ _ _ _ 16
_ _ _ _ 17
_ _ _ _ 18

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT
109. FEATURE LIST (FL)
A
A
FEATURE A P C R
FEATURE A P C R
_______ _ _ _ _ 19 ______ _ _ _ _ 28
_______ _ _ _ _ 20 ______ _ _ _ _ 29
_______ _ _ _ _ 21 ______ _ _ _ _ 30
_______ _ _ _ _ 22 ______ _ _ _ _ 31
_______ _ _ _ _ 23 ______ _ _ _ _ 32
_______ _ _ _ _ 24 ______ _ _ _ _ 33
_______ _ _ _ _ 25 ______ _ _ _ _ 34
_______ _ _ _ _ 26 ______ _ _ _ _ 35
_______ _ _ _ _ 27 ______ _ _ _ _ 36

FEATURE
_______
_______
_______
_______
_______
_______
_______
_______
_______

A
_
_
_
_
_
_
_
_
_

P
_
_
_
_
_
_
_
_
_

A
C
_
_
_
_
_
_
_
_
_

R
_
_
_
_
_
_
_
_
_

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Lucent Technologies 5ESS Switch Translations

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (HIGH RUNNER FEATURE PARAMETERS)

SCREEN 7 OF 14

>134.
135.
136.
137.
138.
139.
140.
141.
142.
143.
144.
145.

TG:GRPID
MOH ALW
IDP NAME
DPAT CAT
ICR SFG
SC1NAME
SC1S
SC2NAME
SC2S
CPUO:SELQ1
CPUO:SELQ2
CPUT:TPREDQ

SCREEN 8 OF 14

0
_
________
0
0
________
_
________
_
0
0
0

146.
147.
148.
149.
150.
151.
152.
153.
154.
155.
156.
157.

FEATURE
________
________
________
________

SCREEN 9 OF 14

ACSR GRPNM
EDS:GRPNM
BCLID GRP
PFA:VGRPNM
PFA:DGRPNM
ATH:VGRPNM
ATH:DGRPNM
MDR:GRPNM
ACCT:GRPNM
ARS:VGRPNM
ARS:DGRPNM
FRL

________
________
________
________
________
________
________
________
________
________
________
___

158.
159.
160.
161.
162.
163.
164.
165.
166.
167.

QALWD
PRIORITY Q
ARSSI
DIALPLN
ALWMDR
ACSR PINREQ
DRING
DCW DRING
CWO DRING
MWY DRING

_
_
__
___
_
_
_
_
_
_

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (HIGH RUNNER FEATURE PARAMETERS)

>172. MESSAGE SERVICE (MSS)
ROW
1
2
3
4

Page H-12

175. MW:DCNDN _______________

GRPNM
________
________
________
________

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (HIGH RUNNER FEATURE PARAMETERS)
>176. CALL FORWARDING FEATURE PARAMETERS (CF)

ROW
1
2
3
4
5
6

FEATURE
FWD TO DN
TIMEOUT BSRING
/CFDBLAC2228703
0
N
__________________________
0
_
__________________________
0
_
__________________________
0
_
__________________________
0
_
__________________________
0
_

SIMINTER
1
0
0
0
0
0

SIMINTRA
99
0
0
0
0
0

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Lucent Technologies 5ESS Switch Translations

5ESS SWITCH LABNSC1
SCREEN 1 OF 14

(*)1.
(*)4.
(*)5.
(*)6.
(*)9.

>11.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.

OE I 00101221
D ISCN 007105
D SERV SX
B1 SERV
DMD
B2 SERV
DMD
NT1 TYPE
TLC
PM GRP ________
DSL CLS
STD
RSTR MP
N
ACSR INH
Y
MDPKT 8
MTERM 2

SCREEN 3 OF 14

>28.
29.
30.
31.
32.
33.

RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT

DSL TN C 2228703SERVICES AND FEATURES SCREENS
MLHG ____
-----------------------TERM ____
BRCS FEATURE LIST
DSL OE _ __________BRCS FEATURE PARAMETERS
ASSOC U
CKT
DELFEAT LIST
DPKT
DSL INFO
ODB
PPB1
PPB2
USER INFO

5ESS SWITCH LABNSC1
SCREEN 2 OF 14

USPID0122287030
MAXB CHL1
ACT USERY
PPB1 USRN
PPB2 USRN
AGI_

Page H-13

------6
7 to 9
4 & 5
14
10
2
11
12
13
3

RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (DSL INFO)
25. CUT DGTS2228
26. ACSR GRP___________
27. DFLT SRV__________

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (USER INFO)

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Lucent Technologies 5ESS Switch Translations

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (CKT)

SCREEN 4 OF 14

>34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.

CKT TN
CKT LCC
CKT RAX
CKT MLHG
CKT TERM
NEW TN
CONFIG GRP
TERMTYP
DISPLAY
EKTS
CA
CA QTY

2228703
DSL
1
____
____
_______
________
TYPEA
Y
_____
___
__

46.
47.
48.
49.
50.
51.
52.
53.
54.

CIRCUIT VOICE (CSV)
CSV
1
CSV CHL
ANY
CSV ACO
_____
CSV LIMIT
1
CSV NBLIMIT __
SP DNA
___
SP DNA QTY __
AU DNA
___
AU DNA QTY __

TKSN
TAUTON
SHAREDN
SAUTON
PRIVACYN
ICPN
SUSON
SUSTN

72.
73.
74.
75.
76.
77.
78.
79.
80.
81.

SAR QTY__
SAR ORIGN
SAR TERMN
INCOMINGN
INTERCOMN
ORIG CWN
PPN
CA PREFI
AUTO HOLDN
ONE TOUCHN

SCREEN 6 OF 14

>106. BFGN
ROW FEATURE
1 /LIDLXA
2 /CPCPFA
3 /CFDBLAC
4 ________
5 ________
6 ________
7 ________
8 ________
9 ________

55.
56.
57.
58.
59.
60.
61.
62.
63.

CIRCUIT DATA (CSD)
CSD
1
CSD CHL
ANY
CSD ACO
_____
CSD LIMIT
1
CSD NBLIMIT __
K56 DNA
___
K56 DNA QTY __
K64 DNA
___
K64 DNA QTY __

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (CKT)

SCREEN 5 OF 14

>64.
65.
66.
67.
68.
69.
70.
71.

Page H-14

______ _
A
A P C R
Y _ N N 10
Y _ N N 11
Y _ N N 12
_ _ _ _ 13
_ _ _ _ 14
_ _ _ _ 15
_ _ _ _ 16
_ _ _ _ 17
_ _ _ _ 18

82.
83.
84.
85.
86.
87.
88.
89.
90.
91.
92.
95.

BUSY MONITORN
ATT MLHG____
RBV TGN____
ERCO ASGNN
ERCO ACTN
SERHLN2228704
BCK LNKY
ACD POS NUM____
CIDIALALLOW
PIC____
PTC____
E911 PSAPN
5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT

109. FEATURE LIST (FL)
A
FEATURE A P C R
FEATURE A P
_______ _ _ _ _ 19 ______ _ _
_______ _ _ _ _ 20 ______ _ _
_______ _ _ _ _ 21 ______ _ _
_______ _ _ _ _ 22 ______ _ _
_______ _ _ _ _ 23 ______ _ _
_______ _ _ _ _ 24 ______ _ _
_______ _ _ _ _ 25 ______ _ _
_______ _ _ _ _ 26 ______ _ _
_______ _ _ _ _ 27 ______ _ _

A
C
_
_
_
_
_
_
_
_
_

R
_
_
_
_
_
_
_
_
_

28
29
30
31
32
33
34
35
36

FEATURE
_______
_______
_______
_______
_______
_______
_______
_______
_______

A
_
_
_
_
_
_
_
_
_

P
_
_
_
_
_
_
_
_
_

A
C
_
_
_
_
_
_
_
_
_

R
_
_
_
_
_
_
_
_
_

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Lucent Technologies 5ESS Switch Translations

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (HIGH RUNNER FEATURE PARAMETERS)

SCREEN 7 OF 14

>134.
135.
136.
137.
138.
139.
140.
141.
142.
143.
144.
145.

TG:GRPID
MOH ALW
IDP NAME
DPAT CAT
ICR SFG
SC1NAME
SC1S
SC2NAME
SC2S
CPUO:SELQ1
CPUO:SELQ2
CPUT:TPREDQ

SCREEN 8 OF 14

0
_
________
0
0
________
_
________
_
0
0
0

146.
147.
148.
149.
150.
151.
152.
153.
154.
155.
156.
157.

FEATURE
________
________
________
________

SCREEN 9 OF 14

ACSR GRPNM
EDS:GRPNM
BCLID GRP
PFA:VGRPNM
PFA:DGRPNM
ATH:VGRPNM
ATH:DGRPNM
MDR:GRPNM
ACCT:GRPNM
ARS:VGRPNM
ARS:DGRPNM
FRL

________
________
________
________
________
________
________
________
________
________
________
___

158.
159.
160.
161.
162.
163.
164.
165.
166.
167.

QALWD
PRIORITY Q
ARSSI
DIALPLN
ALWMDR
ACSR PINREQ
DRING
DCW DRING
CWO DRING
MWY DRING

_
_
__
___
_
_
_
_
_
_

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (HIGH RUNNER FEATURE PARAMETERS)

>172. MESSAGE SERVICE (MSS)
ROW
1
2
3
4

Page H-15

175. MW:DCNDN _______________

GRPNM
________
________
________
________

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (HIGH RUNNER FEATURE PARAMETERS)
>176. CALL FORWARDING FEATURE PARAMETERS (CF)

ROW
1
2
3
4
5
6

FEATURE
FWD TO DN
TIMEOUT BSRING
/CFDBLAC2228704
0
Y
__________________________
0
_
__________________________
0
_
__________________________
0
_
__________________________
0
_
__________________________
0
_

SIMINTER
1
0
0
0
0
0

SIMINTRA
99
0
0
0
0
0

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Lucent Technologies 5ESS Switch Translations

5ESS SWITCH LABNSC1
SCREEN 1 OF 14

(*)1.
(*)4.
(*)5.
(*)6.
(*)9.

>11.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.

OE I 00101221
D ISCN 007105
D SERV SX
B1 SERV
DMD
B2 SERV
DMD
NT1 TYPE
TLC
PM GRP ________
DSL CLS
STD
RSTR MP
N
ACSR INH
Y
MDPKT 8
MTERM 2

SCREEN 3 OF 14

>28.
29.
30.
31.
32.
33.

RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT

DSL TN C 2228704SERVICES AND FEATURES
SCREENS
MLHG ____
-----------------------TERM ____
BRCS FEATURE LIST
6
DSL OE _ __________BRCS FEATURE PARAMETERS
ASSOC U
CKT
DELFEAT LIST
DPKT
DSL INFO
ODB
PPB1
PPB2
USER INFO

5ESS SWITCH LABNSC1
SCREEN 2 OF 14

USPID0122287040
MAXB CHL1
ACT USERY
PPB1 USRN
PPB2 USRN
AGI_

Page H-16

------7 to 9
4 & 5
14
10
2
11
12
13
3

RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (DSL INFO)
25. CUT DGTS2228
26. ACSR GRP___________
27. DFLT SRV__________

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (USER INFO)

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Lucent Technologies 5ESS Switch Translations

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (CKT)

SCREEN 4 OF 14

>34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.

CKT TN
CKT LCC
CKT RAX
CKT MLHG
CKT TERM
NEW TN
CONFIG GRP
TERMTYP
DISPLAY
EKTS
CA
CA QTY

2228704
DSL
1
____
____
_______
________
TYPEA
Y
_____
___
__

46.
47.
48.
49.
50.
51.
52.
53.
54.

CIRCUIT VOICE (CSV)
CSV
1
CSV CHL
ANY
CSV ACO
_____
CSV LIMIT
1
CSV NBLIMIT __
SP DNA
___
SP DNA QTY __
AU DNA
___
AU DNA QTY __

TKS
TAUTO
SHARED
SAUTO
PRIVACY
ICP
SUSO
SUST

N
N
N
N
N
N
N
N

SCREEN 6 OF 14

>106. BFGN
ROW FEATURE
1 /CPCPFA
2 /LIDLXA
3 ________
4 ________
5 ________
6 ________
7 ________
8 ________
9 ________

______ _
A
A P C R
Y _ N N 10
Y _ N N 11
_ _ _ _ 12
_ _ _ _ 13
_ _ _ _ 14
_ _ _ _ 15
_ _ _ _ 16
_ _ _ _ 17
_ _ _ _ 18

55.
56.
57.
58.
59.
60.
61.
62.
63.

CIRCUIT DATA (CSD)
CSD
1
CSD CHL
ANY
CSD ACO
_____
CSD LIMIT
1
CSD NBLIMIT __
K56 DNA
___
K56 DNA QTY __
K64 DNA
___
K64 DNA QTY __

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (CKT)

SCREEN 5 OF 14

>64.
65.
66.
67.
68.
69.
70.
71.

Page H-17

72.
73.
74.
75.
76.
77.
78.
79.
80.
81.

SAR QTY
SAR ORIG
SAR TERM
INCOMING
INTERCOM
ORIG CW
PP
CA PREF
AUTO HOLD
ONE TOUCH

__
N
N
N
N
N
N
I
N
N

82.
83.
84.
85.
86.
87.
88.
89.
90.
91.
92.
95.

BUSY MONITOR
ATT MLHG
RBV TGN
ERCO ASGN
ERCO ACT
SERHLN
BCK LNK
ACD POS NUM
CIDIAL
PIC
PTC
E911 PSAP

N
____
____
N
N
_______
Y
____
ALLOW
____
____
N

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT
109. FEATURE LIST (FL)
A
FEATURE A P C R
FEATURE A P
_______ _ _ _ _ 19 ______ _ _
_______ _ _ _ _ 20 ______ _ _
_______ _ _ _ _ 21 ______ _ _
_______ _ _ _ _ 22 ______ _ _
_______ _ _ _ _ 23 ______ _ _
_______ _ _ _ _ 24 ______ _ _
_______ _ _ _ _ 25 ______ _ _
_______ _ _ _ _ 26 ______ _ _
_______ _ _ _ _ 27 ______ _ _

A
C
_
_
_
_
_
_
_
_
_

R
_
_
_
_
_
_
_
_
_

28
29
30
31
32
33
34
35
36

FEATURE
_______
_______
_______
_______
_______
_______
_______
_______
_______

A
_
_
_
_
_
_
_
_
_

P
_
_
_
_
_
_
_
_
_

A
C
_
_
_
_
_
_
_
_
_

R
_
_
_
_
_
_
_
_
_

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Lucent Technologies 5ESS Switch Translations

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (HIGH RUNNER FEATURE PARAMETERS)

SCREEN 7 OF 14

>134.
135.
136.
137.
138.
139.
140.
141.
142.
143.
144.
145.

TG:GRPID
MOH ALW
IDP NAME
DPAT CAT
ICR SFG
SC1NAME
SC1S
SC2NAME
SC2S
CPUO:SELQ1
CPUO:SELQ2
CPUT:TPREDQ

SCREEN 8 OF 14

0
_
________
0
0
________
_
________
_
0
0
0

146.
147.
148.
149.
150.
151.
152.
153.
154.
155.
156.
157.

FEATURE
________
________
________
________

SCREEN 9 OF 14

ACSR GRPNM
EDS:GRPNM
BCLID GRP
PFA:VGRPNM
PFA:DGRPNM
ATH:VGRPNM
ATH:DGRPNM
MDR:GRPNM
ACCT:GRPNM
ARS:VGRPNM
ARS:DGRPNM
FRL

________
________
________
________
________
________
________
________
________
________
________
___

158.
159.
160.
161.
162.
163.
164.
165.
166.
167.

QALWD
PRIORITY Q
ARSSI
DIALPLN
ALWMDR
ACSR PINREQ
DRING
DCW DRING
CWO DRING
MWY DRING

_
_
__
___
_
_
_
_
_
_

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (HIGH RUNNER FEATURE PARAMETERS)

>172. MESSAGE SERVICE (MSS)
ROW
1
2
3
4

Page H-18

175. MW:DCNDN _______________

GRPNM
________
________
________
________

5ESS SWITCH LABNSC1
RECENT CHANGE 23.8
DSL/BRCS ASSIGNMENT (HIGH RUNNER FEATURE PARAMETERS)
>176. CALL FORWARDING FEATURE PARAMETERS (CF)

ROW
1
2
3
4
5
6

FEATURE
FWD TO DN
TIMEOUT BSRING
__________________________
0
_
__________________________
0
_
__________________________
0
_
__________________________
0
_
__________________________
0
_
__________________________
0
_

SIMINTER
0
0
0
0
0
0

SIMINTRA
0
0
0
0
0
0

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Northern Telecom DMS-100 Switch Translations

Northern Telecom DMS-100 Switch
Translations

Page H-19

H

For the Northern Telecom DMS-100 switch, Capability Package “S” includes
alternate voice/circuit-switched data on two B-channels. It also supports Calling
Number Identification on data and voice connections. Please note that the
assignment of two DNs is required for this package.
The DMS-100 switch also allows alternate voice and data hunting on one DN
through the Multiline Hunt Group feature.

ISDN Capability Package "S"

H

The information listed below provides the DN translations that define Capability
Package “S”, and the commands that must be executed.

ISDN Ordering Code: Capability S

H

Provision DN1 using the following translations

H

Define a new Logical Terminal Identifier (LTID) using the SLT command:
SONUMBER

< or $>

LTID



FUNCTION



LTCLASS



CS



PS



MAXKEYS

<64>

TEI_TYPE



ABS



ABS

<$>

EKTS



SPIDSFX option
SPID_SUFFIX 
PVC option
VERSION
ISSUE


<2>

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

H NI-1 BRI Provisioning
Northern Telecom DMS-100 Switch Translations

Page H-20

Associate new DN with LTID using the NEW command:
SONUMBER

< or $>

DN



LCC



GROUP



SUBGRP



NCOS



SNPA



KEY

<1>

RINGING



LATANAME



LTG



LEN_OR_LTID



DMS-100 normally delivers the Calling Party Number and the Redirecting
Number, if available.
Attach LTIDs to LEN using the SLT command:
SONUMBER

< or $>

LTID



FUNCTION



LEN



Provision DN2 using the following translations
Define a new Logical Terminal Identifier (LTID) using the SLT command:
SONUMBER< or $>
LTID



FUNCTION



LTCLASS



CS



PS



MAXKEYS

<64>

TEI_TYPE



ABS



ABS

<$>

EKTS



H

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

H NI-1 BRI Provisioning
Northern Telecom DMS-100 Switch Translations

Page H-21

SPIDSFX option
SPID_SUFFIX 

PVC option
VERSION
ISSUE


<2>

Associate new DN with LTID using the NEW command:
SONUMBER

< or $>

DN



LCC



GROUP



SUBGRP



NCOS



SNPA



KEY

<1>

RINGING



LATANAME



LTG



LEN_OR_LTID



DMS-100 normally delivers the Calling Party Number and the Redirecting
Number, if available.
Attach LTIDs to LEN using the SLT command:
SONUMBER

< or $>

LTID



FUNCTION



LEN



Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Northern Telecom DMS-100 Switch Translations

Page H-22

H

Multiline Hunt Group Feature Translations

The sample screens shown below illustrate the translations for alternate voice and
data hunting on three Digital Subscriber Lines (DSLs) and six Directory Numbers
(DNs) forming a circular hunt group. This hunting is provided using the Multiline
Hunt Group feature.
The screens shown in this section are examples, DNs shown on these screens
should be replaced with applicable data.
QDN 2257141
DN:
2257141
TYPE: PILOT OF DNH
SNPA: 201SIG: N/A
HUNT GROUP: 22
LTID: PSATS
141
LTCLASS: BRAFS
LINE CLASS CODE:
KEY: 1
CUSTGRP:
MDCSCA
OPTIONS:
SFC
6ROUP OPTIONS:
CIR RCVD
MEMBER INFO:
1
2257146
2
2257145
3
2257144
4
2257143
5
2257142

HUNT GROUP
LNATTIDX: N/A
HUNT MEMBER:

O

ISDNKSET
SUBGRP: O NCOS: O

RING: Y

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

H NI-1 BRI Provisioning
Northern Telecom DMS-100 Switch Translations

Page H-23

QLT PSATS 141
LTID: PSATS 141
SNPA: 201
DIRECTORY NUMBER:
2257141
LT GROUP NO: 13
LTCLASS: BRAFS
DEFAULT LOGICAL TERMINAL: N
EKTS: N
CACH: N
BEARER SERVICE RESTRICTIONS:
NOPMD
CS: Y PS: N
VERSION: FUNCTIONAL ISSUE: 2
SPID-SUFFIX:
01
LEN: HOST 01 1 10 01
TEI: DYNAMIC
CUSTGRP:
MDCSCA SUBGRP: O NCOS: ORING: Y
LINE CLASS CODE: ISDNKSET
MAXKEYS: 64
DN IS ASSIGNED AS A DNH HUNT PILOT.
HUNT GROUP: 22 HUNT MEMBER: O
OPTIONS:
SFC
KEY
--1

DN
-DN

KEY
---

FEATURE
------NONE

6ROUP OPTIONS:
CIR RCVD
MEMBER INFO:
1
2257146
2
2257145
3
2257144
4
2257143
5
2257142

2257141

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Northern Telecom DMS-100 Switch Translations

Page H-24

QLT PSATS 142
LTID: PSATS
142
SNPA: 201
DIRECTORY NUMBER:2257142
LT GROUP NO: 13
LTCLASS: BRAFS
DEFAULT LOGICAL TERMINAL: N
EKTS: N
CACH: N
BEARER SERVICE RESTRICTIONS:
NOPMD
CS: Y PS: N
VERSION: FUNCTIONAL ISSUE: 2
SPID-SUFFIX:
01
LEN: HOST 01 1 10 02
TEI: DYNAMIC
CUSTGRP:
MDCSCA SUBGRP: O NCOS: O RING: Y
LINE CLASS CODE: ISDNKSET
MAXKEYS: 64
DN IS ASSIGNED AS A DNH HUNT MEMBER (NOT PILOT).
HUNT GROUP: 22
HUNT MEMBER: 5
OPTIONS:
SFC
KEY
--1

DN
-DN

2257142

KEY FEATURE
--------NONE
PILOT DN: 2257141
GROUP OPTIONS:
CIR RCVD
DN:
2257143
TYPE: MEMBER OF DNH HUNT GROUP
SNPA: 201
SIG: N/A
LNATTIDX: N/A
HUNT GROUP: 22
HUNT MEMBER: 4
LTID: PSATS
143
LTCLASS: BRAFS
LINE CLASS CODE:
ISDNKSET
KEY: 1
CUSTGRP:
MDCSCA SUBGRP: O NCOS: O
OPTIONS:
SFC
PILOT DN: 2257141
GROUP OPTIONS:
CIR RCVD

RING: Y

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Northern Telecom DMS-100 Switch Translations

Page H-25

LTID: PSATS
143
SNPA: 201
DIRECTORY NUNBER:2257143
LT GROUP NO: 13
LTCLASS: BRAFS
DEFAULT LOGICAL TERMINAL: N
EKTS: N
CACH: N
BEARER SERVICE RESTRICTIONS:
NOPMD
CS: Y PS: N
VERSION: FUNCTIONAL ISSUE: 2
SPID-SUFFIX:
01
LEN: HOST 01 0 07 01
TEI: DYNAMIC
CUSTGRP:
MDCSCA SUBGRP: O NCOS: O RING: Y
LINE CLASS CODE: ISDNKSET
MAXKEYS: 64
DN IS ASSIGNED AS A DNH HUNT MEMBER (NOT PILOT).
HUNT GROUP: 22
HUNT MEMBER: 4
OPTIONS:
SFC
KEY
--1

DN
-DN

2257143

KEY FEATURE
--------NONE
PILOT DN: 2257141
GROUP OPTIONS:
CIR RCVD
QDN 2257144;QLT PSATS 144
DN:
2257144
TYPE: MEMBER OF DNH HUNT GROUP
SNPA: 201
SIG: N/A
LNATTIDX: N/A
HUNT GROUP: 22
HUNT MEMBER: 3
LTID: PSATS
144
LTCLASS: BRAFS
LINE CLASS CODE:
ISDNKSET
KEY: 1
CUSTGRP:
MDCSCA SUBGRP: O NCOS: O
OPTIONS:
SFC
PILOT DN: 2257141
GROUP OPTIONS:
CIR RCVD

RING: Y

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Northern Telecom DMS-100 Switch Translations

Page H-26

LTID: PSATS
144
SNPA: 201
DIRECTORY NUMBER:
2257144
LT GROUP NO: 13
LTCLASS: BRAFS
DEFAULT LOGICAL TERMINAL: N
EKTS: N
CACH: N
BEARER SERVICE RESTRICTIONS:
NOPMD
CS: Y PS: N
VERSION: FUNCTIONAL ISSUE: 2
SPID-SUFFIX:
01
LEN: HOST 01 1 10 01
TEI: DYNAMIC
CUSTGRP:
MDCSCA SUBGRP: O NCOS: O RING: Y
LINE CLASS CODE: ISDNKSET
MAXKEYS: 64
DN IS ASSIGNED AS A DNH HUNT MEMBER (NOT PILOT).
HUNT GROUP: 22
HUNT MEMBER: 3
OPTIONS:
SFC
KEY
--1

DN
-DN

2257144

KEY FEATURE
--------NONE
PILOT DN: 2257141
GROUP OPTIONS:
CIR RCVD
QDN 2257145;QLT PSATS 145
DN:
2257145
TYPE: MEMBER OF DNH HUNT GROUP
SNPA: 201
SIG: N/A
LNATTIDX: N/A
HUNT GROUP: 22
HUNT HENBER: 2
LTID: PSATS
145
LTCLASS: BRAFS
LINE CLASS CODE:
ISDNKSET
KEY: 1
CUSTGRP:
MDCSCA
SUBGRP: O NCOS: O
OPTIONS:
SFC
PILOT DN: 2257141
GROUP OPTIONS:
CIR RCVD

RING: Y

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Northern Telecom DMS-100 Switch Translations

Page H-27

LTID: PSATS
145
SNPA: 201
DIRECTORY NUMBER:2257145
LT GROUP NO: 13
LTCLASS: BRAFS
DEFAULT LOGICAL TERMINAL: N
EKTS: N
CACH: N
BEARER SERVICE RESTRICTIONS:
NOPMD
CS: Y PS: N
VERSION: FUNCTIONAL ISSUE: 2
SPID-SUFFIX:
01
LEN: HOST 01 1 10 02
TEI: DYNAMIC
CUSTGRP:
MDCSCA SUBGRP: O NCOS: O RING: Y
LINE CLASS CODE: ISDNKSET
MAXKEYS: 64
DN IS ASSIGNED AS A DNH HUNT MEMBER (NOT PILOT).
HUNT GROUP: 22
HUNT MEMBER: 2
OPTIONS:
SFC
KEY
--1

DN

KEY
---

-DN

2257145

FEATURE
------NONE

PILOT DN: 2257141
GROUP OPTIONS:
CIR RCVD
QDN 2257146;QLT PSATS 146
DN: 2257146
TYPE: MEMBER OF DNH HUNT GROUP
SNPA: 201
SIG: N/A
LNATTIDX: N/A
HUNT GROUP: 22
HUNT MEMBER: 1
LTID: PSATS
146
LTCLASS: BRAFS
LINE CLASS CODE:
ISDNKSET
KEY: 1
CUSTGRP:
MDCSCA SUBGRP: O NCOS: O
OPTIONS:
SFC
PILOT DN: 2257141
GROUP OPTIONS:
CIR RCVD

RING: Y

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Northern Telecom DMS-100 Switch Translations

Page H-28

LTID: PSATS 146
SNPA: 201
DIRECTORY NUMBER:2257146
LT GROUP NO: 13
LTCLASS: BRAFS
DEFAULT LOGICAL TERMINAL: N
EKTS: N
CACH: N
BEARER SERVICE RESTRICTIONS:
NOPMD
CS: Y PS: N
VERSION: FUNCTIONAL ISSUE: 2
SPID-SUFFIX:
01
LEN: HOST 01 0 07 01
TEI: DYNAMIC
CUSTGRP:
MDCSCA SUBGRP: O NCOS: O RING: Y
LINE CLASS CODE: ISDNKSET
MAXKEYS: 64
DN IS ASSIGNED AS A DNH HUNT MEMBER (NOT PILOT).
HUNT GROUP: 22
HUNT MEMBER: 1
OPTIONS:
SFC
KEY
--1

DN
-DN

2257146

KEY FEATURE
--------NONE
PILOT DN: 2257141
GROUP OPTIONS:
CIR RCVD
QLEN 1 1 10 1;QLEN 1 1 10 2;QLEN 1 0 7 1
LEN:
HOST 01 1 10 01
ISG: 0 DCH: 1 ISG BRA Channel: 21
CARCODE: BX27AA
PADGRP: NPDGP
PM NODE NUMBER : 32
PM TERMINAL NUMBER:
322
TEI
--DYNAMIC
DYNAMIC

LTID
CSPSBCH/ISG Bd
-------------PSATS
141
Y N PSATS
144
Y N -

--

----------

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Northern Telecom DMS-100 Switch Translations

Page H-29

LEN:
HOST 01 1 10 02
ISG: 0 DCH: 1 ISG BRA Channel: 21
CARCODE: BX27AA
PADGRP: NPDGP
PM NODE NUMBER : 32
PM TERMINAL NUMBER:
323
TEI
--DYNAMIC
DYNAMIC

LTID
CSPSBCH/ISG Bd
-------------PSATS
142
Y
PSATS
145
Y

-N
N

----------

-N
N

----------

LEN:
HOST 01 0 07 01
ISG: 0 DCH: 1 ISG BRA Channel: 24
CARCODE: BX27AA
PADGRP: NPDGP
PM NODE NUMBER : 31
PM TERMINAL NUMBER:
226
TEI
--DYNAMIC
DYNAMIC
STOP2

LTID
CSPSBCH/ISG Bd
-------------PSATS
143
Y
PSATS
146
Y

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

Siemens SSC EWSD Switch
Translations

Page H-30

H

For the Siemens SSC EWSD switch, Capability Package “S” includes alternate
voice/circuit-switched data on two B-channels. It also supports Calling Number
Identification on data and voice connections. Please note that the assignment of
two Directory Numbers (DNs) is required for this package.
The Siemens SSC EWSD switch allows either voice or data hunting on one DN
using the Series Completion feature. The same provisioning is used for either a
voice or data series completion group.

ISDN Capability Package “S”

H

The information listed below provides the DN translations that define Capability
Package “S”, and the screens and fields that must be populated.
The information provided shows the translations for one DSL and two DNs. For
multiple DSLs/DNs, the CO will duplicate these screens and enter the applicable
DSL and DN values as needed.

H

ISDN Ordering Code: Capability S
DISPACCESS:EQN=20-0-5-4;
ACCESS DATA

EXEC’D
MASKNO:04328
MASKNO:00000

EQN =20-0-5-4,
CLOSS = 0,
BCHEQN =2,
BCEQN = SP & AU3 & C56 & C64,
CPDDN = 2156855917-VI & 2156855917-CMD,
CPVDN2 = 2156855917,
COE = CLASS1,
LINKOPT = DYNNOPAL,
BAPROF = 0;

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

Page H-31

DISPSUB:DN=6855917;
NPA = 215 DN = 6855917 EQN = 20-0-5-4MASKNO:03800
CAT = IBA
MASKNO:03774
BCHDN = 2
MASKNO:03798
BCDN = SP &AU3 &C56 &C64 MASKNO:04535
CT = VI
MASKNO:04396
LCC = BVCE RAX = 1
MASKNO:03785
BCHCT = 2
MASKNO:06282
IBCHCT = 2
MASKNO:06288
OBCHCT = 2
MASKNO:06291
PIC = 0288-SP
MASKNO:04398
& 0288-AU3
CHRG = FRSA1
MASKNO:03775
COS = ICND & RND
MASKNO:03777
CRBLIM = 2
MASKNO:03798
CT = CMD
MASKNO:04396
LCC = BCMD RAX = 1
MASKNO:03785
BCHCT = 2
MASKNO:06282
IBCHCT = 2
MASKNO:06288
OBCHCT = 2
MASKNO:06291
PIC = 0288-C56
MASKNO:04398
& 0288-C64
CHRG = FRSA1
MASKNO:03775
COS = ICND &RND
MASKNO:03777
CRBLM = 2
MASKNO:03798
DISPTSP:TSPID=215685591701
EQN: 20-0-5-4
USID: 5
TSPID: 215685591701
TERMLIM: 1
DN: 6855917
CT: VI
DN: 6855917
CT: CMD

MASKNO:04383

MASKNO:04386
MASKNO:04382
MASKNO:04385
MASKNO:04382
MASKNO:04385

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

Page H-32

DISPSUB:DN=6855919;
NPA = 215 DN = 6855919 EQN = 20-0-5-4MASKNO:03800
CAT = IBA
MASKNO:03774
BCHDN = 2
MASKNO:03798
BCDN = SP &AU3 &C56 &C64 MASKNO:04535
CT = VI
MASKNO:04396
LCC =BVCE RAX = 1
MASKNO:03785
BCHCT = 2
MASKNO:06282
IBCHCT = 2
MASKNO:06288
OBCHCT = 2
MASKNO:06291
PIC = 0288-SP
MASKNO:04398
& 0288-AU3
CHRG = FRSA1
MASKNO:03775
COS = ICND & RND
MASKNO:03777
CRBLIM = 2
MASKNO:03798
CT = CMD
MASKNO:04396
LCC = BCMD RAX = 1
MASKNO:03785
BCHCT = 2
MASKNO:06282
IBCHCT = 2
MASKNO:06288
OBCHCT = 2
MASKNO:06291
PIC = 0288-C56
MASKNO:04398
& 0288-C64
CHRG = FRSA1
MASKNO:03775
COS = ICND &RND
MASKNO:03777
CRBLIM = 2
MASKNO:03798
DISPTSP:TSPID=215685591901;
EQN: 20-0-5-4
USID: 1
TSPID: 215685591901
TERMLIM: 1
DN: 6855919
CT: VI
DN: 6855919
CT: CMD

MASKNO:04383

MASKNO:04386
MASKNO:04382
MASKNO:04385
MASKNO:04382
MASKNO:04385

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

Series Completion Feature Translations

Page H-33

H

The information listed below provides the translation for either voice or data
hunting on three Digital Subscriber Lines (DSLs) and six Directory Numbers
(DNs) forming a circular series completion group.
The screens shown in this section are examples. DNs shown on these screens
should be replaced with applicable data.

M

NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
0959
OMT-00/LEONLY
2816/04328

96-01-18

16:22:05

DISPSDNDAT:EQN=20-0-0-1&20-0-5-0&40-0-2-4:

EXEC’D

ISDN ACCESS DATA

MASKNO:04328
MASKNO:00000

VIEW = EQN.
EQN = 20-0-00-01.
BCHEQN = 2.
BCEQN = SP.
BCEQN = AU3.
BCEQN = C56.
BCEQN = C64.
CPDDN = 2156851189-VI.
CPDDN = 2156851189-CMD.
COE = CLASS1.
LINKOPT = DYNNOPAL.
NCCSL = D1--4.
NCCSL = D2--4.
NPCSL = P1--0.
NPCSL = P2--0.
NSL = 10.
L2TIM = T200-10.
L2TIM = T201-10.
L2TIM = T203-3.
L2COUNT = N200-3.
L2COUNT = OIFDCC-1.
L2COUNT = OIFDPC-3.
CPVDN2 = 2156851189.
CPVDN2 = 2156851289:
INTERRUPTION TEXT JOB 0959

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

CONTINUATION TEXT 0001
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328

Page H-34

96-01-18

SUBSCRIBER

16:22:08

MASKNO:04328
MASKNO:00000

VIEW = DN.
NPA = 215.
DN = 6851189.
EQN = 20-0-00-01.
BCHDN = 2.
BCDN = SP.
BCDN = AU3.
BCDN = C56.
BCDN = C64.
BCHCT = 2-VI.
BCHCT = 2-CMD.
BCHCT = 0-PMD.
IBCHCT = 2-VI.
IBCHCT = 2-CMD.
IBCHCT = 0-PMD.
OBCHCT = 2-VI.
OBCHCT = 2-CMD.
OBCHCT = 0-PMD.
CT = VI.
C1 = CMD:
INTERRUPTION TEXT JOB 0959
CONTINUATION TEXT 0002
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
SUBSCRIBER

96-01-18
.

VIEW = DNCT.
NPA = 215.
DN = 6851189.
EQN = 20-0-00-01.
CT = VI.
CAT = IBA.
LCC = PKGSV.
RAX = 1.
COS = ICND.
COS = RND.
COSDAT = SERCOMP-6851289.
PIC = 222-SP.
PIC = 288-AU3.
CRBLIM = 1:
lNTERRUPTION TEXT JOB 0959

16:22:31

MASKNO:04328
MASKNO:00000

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

CONTINUATION TEXT 0003
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
SUBSCRIBER

Page H-35

96-01-18

16:22:15

MASKNO:04328
MASKNO:00000

VIEW = DNCT.
NPA = 215.
DN = 6851189.
EQN = 20-0-00-01.
CT = CMD.
CAT = IBA.
LCC = PKGSD.
RAX = 1.
COS = ICND.
COS = RND.
COSDAT = SERCOMP-6851289.
PIC = 222-C56.
PIC = 288-C64.
CRBLIM = 1:
INTERRUPTION TEXT JOB 0959
CONTINUATION TEXT 0004
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
SUBSCRIBER

VIEW = DN.
NPA = 215.
DN = 6851289.
EQN = 20-0-00-01.
BCHDN = 2.
BCDN = SP.
BCDN = AU3.
BCDN = C56.
BCDN = C64.
BCHCT = 2-VI.
BCHCT = 2-CMD.
BCHCT = 0-PMD.
IBCHCT = 2-VI.
IBCHCT = 2-CMD.
IBCHCT = 0-PMD.
OBCHCT = 2-VI.
OBCHCT = 2-CMD.
OBCHCT = 0-PMD.
CT = VI.
CT = CMD:
INTERRUPTION TEXT JOB 0959

96-01-18

16:22:19

MASKNO:04328
MASKNO:00000

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

CONTINUATION TEXT 0005
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
SUBSCRIBER

Page H-36

96-01-18

16:22:22

MASKNO:04328
MASKNO:00000

VIEW = DNCT.
NPA = 215.
DN = 6851289.
EQN = 20-0-00-01.
CT = VI.
CAT = IBA.
LCC = PKGSV.
RAX = 1.
COS = ICND.
COS = RND.
COSDAT = SERCOMP-6852199.
PIC = 222-SP.
PIC = 288-AU3.
CRBLIM = 1:
INTERRUPTION TEXT JOB 0959
CONTINUATION TEXT 0006
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
SUBSCRIBER
VIEW = DNCT.
NPA = 215.
DN = 6851289.
EQN = 20-0-00-01.
CT = CMD.
CAT = IBA.
LCC = PKGSD.
RAX = 1.
COS = ICND.
COS = RND.
COSDAT = SERCOMP-6852199.
PIC = 222-C56.
PIC = 288-C64.
CRBLIM = 1:
INTERRUPTION TEXT JOB 0959

96-01-18

16:22:26

MASKNO:04328
MASKNO:00000

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

CONTINUATION TEXT 0007
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328

Page H-37

96-01-18

16:22:29

TERMINAL SERVICE PROFILE DATAMASKNO:04328
MASKNO:00000
VIEW = TSP.
EQN = 20-0-00-01.
USID = 1.
TSPID = 2156851189.
TERMLIM = 1.
TSPCOS = CHDBCHR:
INTERRUPTION TEXT JOB 0959
CONTINUATION TEXT 0008
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
TERMINAL SERVICE PROFILE DATA

96-01-18

16:22:32

MASKNO:04328
MASKNO:00000

VIEW = TSPDNCT.
EQN = 20-0-00-01.
TSPID = 2156851189.
NPA = 215.
DN = 6851189.
CT= VI:
INTERRUPTION TEXT JOB 0959
CONTINUATION TEXT 0009
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
TERMINAL SERVICE PROFILE DATA
VIEW = TSPDNCT.
EQN = 20-0-00-01.
TSPID = 2156851189.
NPA = 215.
DN = 6851189.
CT= CMD:
INTERRUPTION TEXT JOB 0959

96-01-18

16:22:35

MASKNO:04328
MASKNO:00000

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

CONTINUATION TEXT 0010
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
TERMINAL SERVICE PROFILE DATA

Page H-38

96-01-18

16:22:38

MASKNO:04328
MASKNO:00000

VIEW = TSP.
EQN = 20-0-00-01.
USID = 2.
TSPID = 2156851289.
TERMLIM = 1.
TSPCOS = CHDBCHR:
INTERRUPTION TEXT JOB 0959
CONTINUATION TEXT 0011
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
ISDN ACCESS DATA
VIEW = EQN.
EQN = 20-0-05-01.
BCHEQN = 2.
BCEQN = SP.
BCEQN = AU3.
BCEQN = C56.
BCEQN = C64.
CPDDN = 2156852199-VI.
CPDDN = 2156852199-CMD.
COE = CLASS1.
LINKOPT = DYNNOPAL.
NCCSL = D1--4.
NCCSL = D2--4.
NPCSL = P1--0.
NPCSL = P2--0.
NSL = 10.
L2TIM = T200-10.
L2TIM = T201-10.
L2TIM = T203-3.
L2COUNT = N200-3.
L2COUNT = OIFDCC-1.
L2COUNT = OIFDPC-3.
CPVDN2 = 2156852199.
CPVDN2 = 2156852299:
INTERRUPTION TEXT JOB 0959

96-01-18

16:22:40

MASKNO:04328
MASKNO:00000

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

CONTINUATION TEXT 0012
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
SUBSCRIBER

Page H-39

96-01-18

16:22:44

MASKNO:04328
MASKNO:00000

VIEW = DN.
NPA = 215.
DN = 6852199.
EQN = 20-0-05-00.
BCHDN = 2.
BCDN = SP.
BCDN = AU3.
BCDN = C56.
BCDN = C64.
BCHCT = 2-VI.
BCHCT = 2-CMD.
BCHCT = 0-PMD.
IBCHCT = 2-VI.
IBCHCT = 2-CMD.
IBCHCT = 0-PMD.
OBCHCT = 2-VI.
OBCHCT = 2-CMD.
OBCHCT = 0-PMD.
CT = VI.
CT = CMD:
INTERRUPTION TEXT JOB 0959
CONTINUATION TEXT 0013
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
SUBSCRIBER
VIEW = DNCT.
NPA = 215.
DN = 6852199.
EQN = 20-0-05-00.
CT = VI.
CAT = IBA.
LCC = PKGSV.
RAX = 1.
COS = ICND.
COS = RND.
COSDAT = SERCOMP-6852299.
PIC = 222-SP.
PIC = 288-AU3.
CRBLIM = 1:
INTERRUPTION TEXT JOB 0959

96-01-18

16:22:48

MASKNO:04328
MASKNO:00000

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

CONTINUATION TEXT 0014
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
SUBSCRIBER

Page H-40

96-01-18

16:22:51

MASKNO:04328
MASKNO:00000

VIEW = DNCT.
NPA = 215.
DN = 6852199.
EQN = 20-0-05-00.
CT = CMD.
CAT = IBA.
LCC = PKGSD.
RAX = 1.
COS = ICND.
COS = RND.
COSDAT = SERCOMP-6852299.
PIC = 222-C56.
PIC = 288-C64.
CRBLIM = 1:
INTERRUPTION TEXT JOB 0959
CONTINUATION TEXT 0015
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
SUBSCRIBER
VIEW = DN.
NPA = 215.
DN = 6852299.
EQN = 20-0-05-00.
BCHDN = 2.
BCDN = SP.
BCDN = AU3.
BCDN = C56.
BCDN = C64.
BCHCT = 2-VI.
BCHCT = 2-CMD.
BCHCT = 0-PMD.
IBCHCT = 2-VI.
IBCHCT = 2-CMD.
IBCHCT = 0-PMD.
OBCHCT = 2-VI.
OBCHCT = 2-CMD.
OBCHCT = 0-PMD.
CT = VI.
CT = CMD:
INTERRUPTION TEXT JOB 0959

96-01-18

16:22:55

MASKNO:04328
MASKNO:00000

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

CONTINUATION TEXT 0016
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
SUBSCRIBER

Page H-41

96-01-18

16:22:58

MASKNO:04328
MASKNO:00000

VIEW = DNCT.
NPA = 215.
DN = 6852299.
EQN = 20-0-05-00.
CT = VI.
CAT = IBA.
LCC = PKGSV.
RAX = 1.
COS = ICND.
COS = RND.
COSDAT = SERCOMP-6853119.
PIC = 222-SP.
PIC = 288-AU3.
CRBLIM = 1:
INTERRUPTION TEXT JOB 0959
CONTINUATION TEXT 0017
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
SUBSCRIBER
VIEW = DNCT.
NPA = 215.
DN = 6852299.
EQN = 20-0-05-00.
CT = CMD.
CAT = IBA.
LCC = PKGSD.
RAX = 1.
COS = ICND.
COS = RND.
COSDAT = SERCOMP-6853119.
PIC = 222-C56.
PIC = 288-C64.
CRBLIM = 1:
INTERRUPTION TEXT JOB 0959

96-01-18

16:23:01

MASKNO:04328
MASKNO:00000

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

CONTINUATION TEXT 0018
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
TERMINAL SERVICE PROFILE DATA

Page H-42

96-01-18

16:23:05

MASKNO:04328
MASKNO:00000

VIEW = TSP.
EQN = 20-0-05-00.
USID = 1.
TSPID = 2156852199.
TERMLIM = 1.
TSPCOS = CHDBCHR:
INTERRUPTION TEXT JOB 0959
CONTINUATION TEXT 0019
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
TERMINAL SERVICE PROFILE DATA

96-01-18

16:23:07

MASKNO:04328
MASKNO:00000

VIEW = TSPDNCT.
EQN = 20-0-05-00.
TSPID = 2156852199.
NPA = 215.
DN = 6852199.
CT= VI:
INTERRUPTION TEXT JOB 0959
CONTINUATION TEXT 0020
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
TERMINAL SERVICE PROFILE DATA
VIEW = TSPDNCT.
EQN = 20-0-05-00.
TSPID = 2156852199.
NPA = 215.
DN = 6852199.
CT= CMD:
INTERRUPTION TEXT JOB 0959

96-01-18

16:23:11

MASKNO:04328
MASKNO:00000

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

CONTINUATION TEXT 0021
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328

Page H-43

96-01-18

TERMINAL SERVICE PROFILE DATA

16:23:13

MASKNO:04328
MASKNO:00000

VIEW = TSP.
EQN = 20-0-05-00.
USID = 2.
TSPID = 2156852299.
TERMLIM = 1.
TSPCOS = CHDBCHR:
INTERRUPTION TEXT JOB 0959
CONTINUATION TEXT 0022
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
ISDN ACCESS DATA
VIEW = EQN.
EQN = 40-0-02-04.
BCHEQN = 2.
BCEQN = SP.
BCEQN = AU3.
BCEQN = C56.
BCEQN = C64.
CPDDN = 2156853119-VI.
CPDDN = 2156853119-CMD.
COE = CLASS1.
LINKOPT = DYNNOPAL.
NCCSL = D1--4.
NCCSL = D2--4.
NPCSL = P1--0.
NPCSL = P2--0.
NSL = 10.
L2TIM = T200-10.
L2TIM = T201-10.
L2TIM = T203-3.
L2COUNT = N200-3.
L2COUNT = OIFDCC-1.
L2COUNT = OIFDPC-3.
CPVDN2 = 2156853119.
CPVDN2 = 2156853219:
INTERRUPTION TEXT JOB 0959

96-01-18

16:23:16
MASKNO:04328
MASKNO:00000

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

CONTINUATION TEXT 0023
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
SUBSCRIBER

Page H-44

96-01-18

16:23:20

MASKNO:04328
MASKNO:00000

VIEW = DN.
NPA = 215.
DN = 6853119.
EQN = 40-0-02-04.
BCHDN = 2.
BCDN = SP.
BCDN = AU3.
BCDN = C56.
BCDN = C64.
BCHCT = 2-VI.
BCHCT = 2-CMD.
BCHCT = 0-PMD.
IBCHCT = 2-VI.
IBCHCT = 2-CMD.
IBCHCT = 0-PMD.
OBCHCT = 2-VI.
OBCHCT = 2-CMD.
OBCHCT = 0-PMD.
CT = VI.
CT = CMD:
INTERRUPTION TEXT JOB 0959
CONTINUATION TEXT 0024
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
SUBSCRIBER
VIEW = DNCT.
NPA = 215.
DN = 6853119.
EQN = 40-0-02-04.
CT = VI.
CAT = IBA.
LCC = PKGSV.
RAX = 1.
COS = ICND.
COS = RND.
COSDAT = SERCOMP-6853219.
PIC = 222-SP.
PIC = 288-AU3.
CRBLIM = 1:
INTERRUPTION TEXT JOB 0959

96-01-18

16:23:23

MASKNO:04328
MASKNO:00000

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

CONTINUATION TEXT 0025
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
SUBSCRIBER

Page H-45

96-01-18

16:23:27

MASKNO:04328
MASKNO:00000

VIEW = DNCT.
NPA = 215.
DN = 6853119.
EQN = 40-0-02-04.
CT = CMD.
CAT = IBA.
LCC = PKGSD.
RAX = 1.
COS = ICND.
COS = RND.
COSDAT = SERCOMP-6853219.
PIC = 222-C56.
PIC = 288-C64.
CRBLIM = 1:
INTERRUPTION TEXT JOB 0959
CONTINUATION TEXT 0026
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
SUBSCRIBER
VIEW = DN.
NPA = 215.
DN = 6853219.
EQN = 40-0-02-04.
BCHDN = 2.
BCDN = SP.
BCDN = AU3.
BCDN = C56.
BCDN = C64.
BCHCT = 2-VI.
BCHCT = 2-CMD.
BCHCT = 0-PMD.
IBCHCT = 2-VI.
IBCHCT = 2-CMD.
IBCHCT = 0-PMD.
OBCHCT = 2-VI.
OBCHCT = 2-CMD.
OBCHCT = 0-PMD.
CT = VI.
CT = CMD:
INTERRUPTION TEXT JOB 0959

96-01-18

16:23:30

MASKNO:04328
MASKNO:00000

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

CONTINUATION TEXT 0027
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
SUBSCRIBER

Page H-46

96-01-18

16:23:34

MASKNO:04328
MASKNO:00000

VIEW = DNCT.
NPA = 215.
DN = 6853219.
EQN = 40-0-02-04.
CT = VI.
CAT = IBA.
LCC = PKGSV.
RAX = 1.
COS = ICND.
COS = RND.
COSDAT = SERCOMP-6851189.
PIC = 222-SP.
PIC = 288-AU3.
CRBLIM = 1:
INTERRUPTION TEXT JOB 0959
CONTINUATION TEXT 0028
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
SUBSCRIBER
VIEW = DNCT.
NPA = 215.
DN = 6853219.
EQN = 40-0-02-04.
CT = CMD.
CAT = IBA.
LCC = PKGSD.
RAX = 1.
COS = ICND.
COS = RND.
COSDAT = SERCOMP-6851189.
PIC = 222-C56.
PIC = 288-C64.
CRBLIM = 1:
INTERRUPTION TEXT JOB 0959

96-01-18

16:23:37

MASKNO:04328
MASKNO:00000

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

CONTINUATION TEXT 0029
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
TERMINAL SERVICE PROFILE DATA

Page H-47

96-01-18

16:23:40

MASKNO:04328
MASKNO:00000

VIEW = TSP.
EQN = 40-0-02-04.
USID = 1.
TSPID = 2156853119.
TERMLIM = 1.
TSPCOS = CHDBCHR:
INTERRUPTION TEXT JOB 0959
CONTINUATION TEXT 0030
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
TERMINAL SERVICE PROFILE DATA

96-01-18

16:23:43

MASKNO:04328
MASKNO:00000

VIEW = TSPDNCT.
EQN = 40-0-02-04.
TSPID = 2156853119.
NPA = 215.
DN = 6853119.
CT= VI:
INTERRUPTION TEXT JOB 0959
CONTINUATION TEXT 0031
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
TERMINAL SERVICE PROFILE DATA
VIEW = TSPDNCT.
EQN = 40-0-02-04.
TSPID = 2156853119.
NPA = 215.
DN = 6853119.
CT= CMD:
INTERRUPTION TEXT JOB 0959

96-01-18

16:23:46

MASKNO:04328
MASKNO:00000

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

H NI-1 BRI Provisioning
Siemens SSC EWSD Switch Translations

CONTINUATION TEXT 0032
NAVK1/BELLCORNJRB/APS 13.0 PS0071/000
M
0959
OMT-00/LEONLY2816/04328
TERMINAL SERVICE PROFILE DATA
VIEW = TSP.
EQN = 40-0-02-04.
USID = 2.
TSPID = 2156853219.
TERMLIM = 1.
TSPCOS = CHDBCHR:
END JOB 0959 EXEC’D

Page H-48

96-01-18

16:23:49

MASKNO:04328
MASKNO:00000

Issue 1
August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

I

Network Engineering Forms

Page I-1

I

Network Engineering Forms

I

This appendix contains one copy of each of the network planning forms used by
the Network Engineering Group to plan and configure a MERLIN LEGEND
Release 6.0 (or later) private network. The forms are listed in Table I–1. You
should make copies of these forms and use the copies, keeping the originals for
future use.
NOTE:
To contact the Network Engineering Group, call 1 888 297-4700.
The system planning forms are contained in Appendix B. Planning forms for data
communications are contained in Appendix C. The T1/PRI Planner is contained in
Appendix D. The NI-1 BRI Planner is contained in Appendix G.
Table I–1.

Network Forms

Used for ...
Requesting assistance from the Sales and
Design Support Center
Preliminary network planning

Form
No.

Form Title

E-1154

Request for Sales and Design
Support Center Services

N/A

MERLIN LEGEND R6 Design
Implementation Guide

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

I

Issue 1
August 1998

Network Engineering Forms

Page I-2

REQUEST FOR SALES AND DESIGN SUPPORT CENTER SERVICES (E-1154)
Check each service being requested and describe in Scope of Work below:

Technical Assurance

Installation Specifications

Floorplan

Other

(Check products)

DEFINITY
AUDIX / Intuity
MERLIN LEGEND Networking

Sys Mgmt / CAS
UPS / DC Power

CONVERSANT
CMS

GENERAL INFORMATION: (Complete all fields):

DESIGN CENTER FAX: 303-850-8932

CUSTOMER INFORMATION

ACCOUNT TEAM INFORMATION

Name:

Name:

Address

Address

City:

ST:

Title:

City:

Zip:

ST:

LDN:

Tel.No.:

IL:

e-mail id:

Zip:

FAX:

(if multiple ILs are involved, list others below in Scope of Work)

MBO Code to be Charged:

Cust. Contact Name:
Cust. Contact Tel. No.:

(if multiple MBO Codes are to be charged, list below in Scope of Work)

Mark if Customer Permission for Switch Access has been
granted.

Alternate Contact:

MBO Project No.:
Project Manager:
Tel. No.:

PRE CONTRACT OR

Title:

Tel. No.:

POST CONTRACT.

ATTOMS/DOSS Ref No’s

Please list model and version of ALL Products (Switches and Adjuncts), both existing and/or proposed. Also specify the
number of nodes in an existing and/or proposed network plus hardware connectivity (digital/analog) and attach diagram.
New

Add

Upgrade

RFP

Controlled Introduction

Scope of Work:

Requested Due Date for Technical Assurance:
Requested Due Date for Floorplans:
MOJ Date:

Cutover Date:

Written Response

Verbal Response

for Specifications, other Deliverables:

MERLIN LEGEND R6 DESIGN IMPLEMENTATION GUIDE
Network Map:
In the space provided below please provide a drawing of your network
configuration. For ease of discussion please identify each site by a Node Number.
(Usually, if a DEFINITY is part of the network, it will be identified as Node 1).
Please include type of system, facilities interconnecting the systems, facilities
connecting to the PSTN, extension numbers, etc.
Customer Name: _______________________________________________

Network Configuration

1

MERLIN LEGEND R6 DESIGN IMPLEMENTATION GUIDE (CONTINUED)
If providing information for more than one site, please complete separate Design
Implementation Guide pages 2 through 6 for each site. (Multiple Network Configuration
drawings are not required).
Site/Customer Information:
Node Number: _______
Name: _________________________________________
Address: _______________________________________
City: __________________ State: ____Zip: _________
LDN: __________________________________________
IL: ____________________________________________
Customer Contact Name: __________________________
Customer Contact Tel. No.: ________________________
System Setup: (Show all pack codes and designations, i.e. ls/gs, mlx, etc.)
CABINET 1
Slot Module
0 Processor (R6)
1
2
3
4
5

CABINET 2
Slot
6
7
8
9
10
11

Module

CABINET 3
Slot
12
13
14
15
16
17

Module

If Legend exists, list the current Timing/Synchronization (DS1 or BRI Pack Location)
Current Synchronization:
Primary: __________________________________
Secondary: __________________________________
Tertiary: __________________________________

2

MERLIN LEGEND R6 DESIGN IMPLEMENTATION GUIDE (CONTINUED)
Customer Name: __________________________________ Node: ________
Dial Plan information:
Dial plan numbers for extensions, adjuncts, lines and calling groups must be unique
across the network. Numbers will have to be changed if a conflict is encountered.
MERLIN LEGEND routes Non-Local UDP calls by matching number ranges entered
into the Non-Local UDP tables. These number ranges can consist of 2- to 4-digit
numbers. 4-digit dial plans are recommended for MERLIN LEGEND. If a
DEFINITY is in the network, and has a 5-digit dial plan, MERLIN LEGEND routes
the call on 4-digits, but will send 5 digits.
Pool numbers and line numbers will be made unique across the network. This will be
transparent to the customer.
- What extension range is desired for this location: ________________
(any additional extension ranges?)
________________
(does this range allow for growth?)
________________
________________
- What adjunct range is desired for this location:
(any additional extension ranges?)
(does this range allow for growth?)

________________
________________
________________

Automatic Route Selection (ARS):

• It is strongly recommended that each system in the network have at least 1 local CO
•

line for emergency use (i.e. 911 calls, power failure use, etc.).
Traffic must be considered when routing ARS calls across the network, to assure
that enough lines are available to handle call volume.
- ARS access code ____ The same ARS access code is recommended on all systems.
- Will ARS be used to access the facilities on another system on the network for
making local calls _______ ? long distance calls _______ ?
- Will other systems on the network being using this systems ARS for making
local calls _______ ? long distance calls _______ ?
- Have ARS tables been administered, or are only the default tables used?
Default only? _____ Other tables are used. _____

NOTE: There are additional engineering charges when Design Center engineers the
custom ARS tables (1–16), i.e. TEHO. Consult with the assigned engineer.

3

MERLIN LEGEND R6 DESIGN IMPLEMENTATION GUIDE (CONTINUED)
Customer Name: __________________________________ Node: ________
- Is Remote Access used, or planned to be used, in this system? __________
- Does this customer intend, when MERLIN LEGEND R6.1 becomes available
(target August, 1998), to install a Centralized Voice Messaging System on this
all Legend Network?
Yes ___ No___
If yes, which VMS is to be used:

INTUITY:
MERLIN LEGEND Mail:
Messaging 2000:
AUDIX Voice Power:

_______
_______
_______
_______

NOTE: Centralized Voice Mail within a DEFINITY to MERLIN LEGEND
network is not supported.
- Is customer planning to use Auto-Attendant to route calls across the network
(to non-local UDP stations)?
Yes ___ No___
- If yes, which Voice Mail or Automated Attendant system do you plan to use?
_________________________________________

4

MERLIN LEGEND R6 DESIGN IMPLEMENTATION GUIDE (CONTINUED)
Customer Name: __________________________________ Node: ________
Public Switched Telephone Network lines:
Loop Start/Ground Start
Trk IDs

Pool

Type

COMMENTS

DID - Are DIDs connected to this system routing calls to non-local extensions? Y / N.
If yes, Local DID number range _________________________ .
Non-Local DID number range _____________________ .
Are DIDs connected to another system routing calls to this system? Y / N.
If yes, on what Node are the DIDs connected _______________ .
Trk IDs

Block

Type

ExpDig

DelDig

AddDig

OutType

E&M Sig

COMMENTS

Tie Trunks (Analog) or (Digital)
Trk IDs

Pool

Dir

InType

InMode

OutMode

DialTone

NOTE: If analog E&M Tie Lines are used to interconnect systems, calls can only go
over two hops, due to call setup time and transmission issues.
100D - DS1 (T1 - PRI)
Slot

Type
T1/PRI

Format
D4/esf

Supp
zcs/b8zs

Signal
rbs/com

LnComp
1–5

ClkSync
p/s/t

Src
lp/loc

*SwType

* 4E=4ESS, 5E=5ESS, 100=DMS100, 250=DMS250, DEX=DEX600E,
LN=Legend-NTWK, LP=Legend-PBX
NOTE: When ordering point-to-point T1, parameters must be designated. We
recommend ESF framing and B8ZS zero code suppression.
5

MERLIN LEGEND R6.1 DESIGN IMPLEMENTATION GUIDE (CONTINUED)
Customer Name: __________________________________ Node: ________
100D - DS1 (T1 - PRI) (continued)
PRI - T1 Assignments
Slot

Channels

Trunk IDs

Pool

Notes

Provide Circuit Numbers of T1 - PRI circuits ____________________________
____________________________
____________________________
Who is the Service Provider? _________________________________________
Who is providing the CSU/MUX? _____________________________________
CSU/MUX Type? ______________________________________
NOTE: IF 3160 CSU/DSU IS USED, CHECK WITH ENGINEER ON
CHANNELIZATION AND TIMING (SYNCH) PRIOR TO SUBMITTING
FORMS TO DATA GROUP FOR CSU TRANSLATIONS.

6

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Glossary

Issue 1
August 1998
Page GL-1

LG

Glossary
Italics
The use of italics in the glossary denotes multiple usage of the italicized text throughout the
glossary.

Numerics
2B data

Digital information carried by two B-channels for better
performance and quality; the bit rate is twice that of one
B-channel used alone.

7500B data module

See ISDN 7500B Data Module.

account code

Code used to associate incoming and outgoing calls with
corresponding accounts, employees, projects, and clients.

ACCUNET

AT&T’s switched digital service for 56-kbps, 64-kbps
restricted, and 64-kbps clear circuit-switched data calls.

address

A coded representation of the destination of data or of the
data’s originating terminal, such as the dialed extension
number assigned to the data terminal. Multiple terminals on
one communications line must each have a unique
address.

ADDS

(Automated Document Delivery System) Computer-based
application that stores documents in a database and
automatically faxes them on request.

adjunct

Optional equipment used with the communications system,
such as an alerting device or modem that connects to a
multiline telephone or to an extension jack.

ALS

(Automatic Line Selection) Programmed order in which the
system makes outside lines available to a user.

ambiguous
numbering

Numbering of extension ranges, remote access codes, or
other system components that causes conflicts in network
operations. These numbers can be unique and still be
ambiguous. For example, Extension 441 is different from
Extension 4410. However, for UDP routing purposes, the
two numbers are ambiguous and a call intended for
Extension 4410 is misrouted on the first three digits sent, to
Extension 441. See also unambiguous numbering.

A

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-2

AMI

(alternate mark inversion) Line coding format in which a
binary one is represented by a positive or negative pulse, a
binary zero is represented by no line signal, and
subsequent binary ones must alternate in polarity;
otherwise, a bipolar violation occurs. AMI is used in the
DS1 interface.

Analog data
station

See modem data station.

analog multiline
telephone

Also known as the MERLIN multiline telephone. A
telephone that transmits and receives analog signals and
has a number of line buttons.

analog
transmission

Mode of transmission in which information is represented in
continuously variable physical quantities, such as
amplitude, frequency, phase, or resistance. See also
digital transmission.

ANI

(Automatic Number Identification) Process of automatically
identifying a caller’s billing number and transmitting that
number from the caller’s local central office to another point
on or off the public network.

application

Software and/or hardware that adds functional capabilities
to the system. For example, MERLIN Identifier is an
application that provides caller identification information (if
available in the local area or jurisdiction).

ARS

(Automatic Route Selection) System feature that routes
calls on outside facilities according to the number dialed
and line/trunk availability. To initiate ARS, the user dials a
dial-out code, also called an “ARS access code.”

ASCAP

(American Society of Composers, Artists, and Producers)

Ascend Pipeline
25PX/75PX

An ISDN-BRI bridge/router that enables high-speed
Internet access over a digital facility. It makes outgoing
calls only.

ASN

(AT&T Switched Network) AT&T telecommunications
services provided through an Integrated Digital Services
Network Primary Rate Interface (ISDN-PRI) trunk, Accunet
switched digital service, Megacom, Megacom 800,
Software Defined Network (SDN), Multiquest, and Shared
Access for Switch Services (SASS).

asynchronous
data transmission

A method of transmitting a short bitstream of digital data,
such as printable characters represented by a 7- or 8-bit
ASCII code. Each string of data bits is preceded by a start
bit and followed by a stop bit, thus permitting data to be
transmitted at irregular intervals. See also synchronous
data transmission.

AT&T Attendant

Application with equipment that connects to one or more
tip/ring extension jacks and automatically answers
incoming calls with a recorded announcement; directs calls
in response to touch tones.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-3

AT&T Switched
Network

See ASN.

AUDIX Voice
Power

A voice-processing application, part of IS II/III, that provides
Automated Attendant, Call Answer, Information Service,
Message Drop, Voice Mail, and, optionally, Fax Attendant
System for use with the system.

Automated
Attendant

IS II/III, MERLIN LEGEND Mail, and Lucent Technologies
Attendant application that automatically answers incoming
calls with a recorded announcement and directs callers to a
department, an extension, or the system operator.

Automated
Document Delivery
System

See ADDS.

automatic
immediate cycling

Process that occurs in private network when all available
routes for a call specify systems with matching switch
identifiers. The call is routed from the originating system to
the destination system and back to the originating system
in a continuous loop. Switch identifiers labelling systems
must be unique across a network.

Automatic Line
Selection

See ALS.

Automatic Number
Identification

See ANI.

automatic
ringdown tie-trunk

See automatic-start tie trunk.

Automatic Route
Selection

See ARS.

automatic-start tie
trunk

Tie trunk on which incoming calls are routed to an operator
or other designated destination without a start signal, as
soon as the trunk is seized; the destination is specified
during programming. Also called “automatic ringdown” or
“auto-in” tie trunk.

auxiliary power
unit

Device that provides additional power to the system.

B8ZS

(bipolar 8 zero substitution) Line-coding format that
encodes a string of eight zeros in a unique binary sequence
to detect bipolar violations.

backup

Procedure for saving a copy of system programming onto a
floppy disk or memory card. See also restore.

bandwidth

Difference, expressed in hertz, between the highest and
lowest frequencies in a range that determines channel
capacity.

B

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-4

barrier code

Password used to limit access to the Remote Access
feature of the system. In a private network, it is especially
important that barrier codes be required for all types of
remote access.

basic carrier

Hardware that holds and connects the processor module,
power supply module, and up to five other modules in the
system. See also expansion carrier.

baud rate

Strictly speaking, a measurement of transmission speed
equal to the number of signal level changes per second. In
practice, often used synonymously with bit rate and bps.

B-channel

(Bearer-channel) 64- or 56-kbps channel that carries a
variety of digital information streams, such as voice at
64 kbps, data at up to 64 kbps, wideband voice encoded at
64 kbps, and voice at less than 64 kbps, alone or
combined.

Basic Rate
Interface

See BRI.

Bearer-channel

See B-channel.

Behind Switch
mode

One of three modes of system operation, in which the
control unit is connected to (behind) another telephone
switching system, such as Centrex or DEFINITY, which
provides features and services to telephone users. See
also Hybrid/PBX mode and Key mode.

binary code

Electrical representation of quantities or symbols
expressed in the base-2 number system, which includes
zeros and ones.

bipolar 8 zero
substitution

See B8ZS.

bipolar signal

Digital signal in which pulses (ones) alternate between
positive and negative. See also AMI, B8ZS, and bipolar
violation.

bipolar violation

Condition occurring when two positive or two negative
pulses are received in succession. See also AMI and
B8ZS.

BIS

(Built-In Speakerphone) Part of the model name of some
analog multiline telephones.

bit

(binary digit) One unit of information in binary notation; it
can have one of two values, zero or one.

bit rate

Speed at which bits are transmitted, usually expressed in
bps. Also called “data rate.”

blocking

Condition in which end-to-end connections cannot be made
on calls because of a full load on all possible services and
facilities. See also glare.

BMI

(Broadcast Music Incorporated)

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-5

board

A module, for example, 100D or 408 MLX GS/LS, that
allows you to connect lines/trunks and extensions to the
communications system.

board assignment

System Programming and Maintenance (SPM) procedure
for assigning line/trunk and extension modules to slots on
the control unit.

board
renumbering

System programming procedure for renumbering boards
that have already been assigned to specific slots on the
control unit.

BRI

(Basic Rate Interface) A standard protocol for accessing
Integrated Service Digital Network (ISDN) services.

broadband

Transmission path having a bandwidth greater than a
voice-grade channel.

BTMI

(basic telephone modem interface)

bus

Multiconductor electrical path used to transfer information
over a common connection from any of several sources to
any of several destinations.

button

Key on the face of a telephone that is used to access a line,
activate a feature, or enter a code on a communications
system.

byte

Sequence of bits (usually eight) processed together. Also
called “octet.”

Call Accounting
System

See CAS.

Call Accounting
Terminal

See CAT.

Caller ID

A service provided by some local telephone companies (if
local regulations allow) that supplies the calling party
telephone number. In Release 3.0 and later, an 800
GS/LS-ID module on the system can capture this
information and display it on the screens of MLX
telephones. See also ANI.

Calling group

Team of individuals who answer the same types of calls.

Call Management
System

See CMS.

CAS

(Call Accounting System) DOS- or UNIX System-based
application that monitors and manages telecommunications
costs.

CAT

(Call Accounting Terminal) Standalone unit with a built-in
microprocessor and data buffer that provides simple call
accounting at a low cost.

C

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-6

CCITT

(International Telegraph and Telephone Consultative
Committee)

CCS

(common-channel signaling) Signaling in which one
channel of a group of channels carries signaling
information for each of the remaining channels, permitting
each of the remaining channels to be used to nearly full
capacity. In the system’s 100D module, channel 24 can be
designated as the signaling channel for channels 1–23.

centralized
telephone
programming

Programming of features on individual telephones;
performed at a central location by the system manager.
See also system programming and extension
programming.

Centralized Voice
Messaging

The sharing of a voice messaging system by two or more
directly connected MERLIN LEGEND systems in a private
network. Available beginning in Release 6.1.

central office

See CO.

Centrex

Set of system features to which a user can subscribe on
telephone trunks from the local telephone company.

channel

Telecommunications transmission path for voice and/or
data.

channel service
unit

See CSU.

checksum

Sum of ones in a sequence of ones and zeros used to
detect or correct errors in data transmission.

circuit-switched
data call

Data call made through an exclusively established and
maintained connection between data stations.

class of restriction

See COR.

clear data channel

Clear data channels (also called unrestricted data
channels) allow the transmission of occurrences of more
than seven contiguous zero bits. If a clear data channel is
requested and only restricted channels are available, the
call will be rejected. See also restricted data channel.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-7

clock
synchronization

When digital signals are transmitted over a
communications link, the receiving end must be
synchronized with the transmitting end to receive the digital
signals without errors using clock synchronization. A
system synchronizes itself by extracting a timing signal
from an incoming digital stream. All the digital facilities in a
network operate from a single common clock, preferably a
port connected to a digital PSTN facility on a hub system or
a system that connects two network systems. In this case,
all digital facilities specify a loop clock source. One system
in a network may be specified as a local clock source when
no functioning digital facility in the network is connected to
the PSTN. All other digital facilities then use this clock and
specify their clock sources as loop. Primary, secondary,
and tertiary clock sources are specified to allow backup
synchronization in the event that the primary source is out
of service.

CMS

(Call Management System) DOS-based application that
simulates the actions of a system operator by answering
and distributing calls. Also produces reports for call
analysis.

CO

(central office) Location of telephone switching equipment
that provides local telephone service and access to toll
facilities for long-distance calling.

coaxial cable

Cable consisting of one conductor, usually a small copper
tube or wire within and insulated from another conductor of
larger diameter, usually copper tubing or copper braid.

codec

(coder-decoder) Device used to convert analog signals
such as speech, music, or television to digital form for
transmission over a digital medium and back to the original
analog form.

collected digits

Digits that a caller dials in response to an integrated voice
response application’s menus (also called prompted digits);
collected digits may be used to initiate screen pop at a
system extension. See also CTI link.

combination
configuration

A private network arrangement that combines
characteristics of Virtual Private Network (VPN), a series
configuration, and a star configuration.

common channel
signaling

See CCS.

communications
system

Software-controlled processor complex that interprets
dialing pulses, tones, and/or keyboard characters and
makes the proper interconnections both inside and
outside. Consists of a computer, software, a storage
device, and carriers with special hardware to perform the
actual connections. Provides voice and/or data
communications services, including access to public and
private networks, for telephones and other equipment.
Also referred to in this guide as “system,” short for MERLIN
LEGEND Communications System.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-8

control unit

Processor module, power supply module, other modules,
carriers, and housing of the system.

console

Telephone and adjuncts (if any) at operator or system
programmer extension.

CONVERSANT

Entry-level voice response application that automatically
answers and routes calls and executes telephone
transactions.

conversion
resource

See modem pool.

coordinating
system manager

In a private network that includes more than two systems,
the system manager who acts as a clearinghouse for any
changes made on local systems, that effect the network,
assuring that all system managers work together and that
local system changes do not have undesirable effects on
the network as a whole.

COR

(class of restriction) Various types of restrictions that can
be assigned to remote access trunks or barrier codes.
These restrictions consist of calling restrictions, ARS
Facility Restriction Levels (FRLs), Allowed Lists,
Disallowed Lists, and Automatic Callback queuing.

Coverage

Set of system features that can determine how extensions’
calls are covered when the person at the extension is busy
or not available.

CRC

(cyclic redundancy check) An error-detection code used on
DS1 facilities with the extended superframe format (ESF).

CSU

(channel service unit) Equipment used on customer
premises to provide DS1 facility terminations and signaling
compatibility.

CTI link

(Computer Telephony Integration) link. A hardware/
software feature that is part of the PassageWay Telephony
Services application. It allows the use of Lucent
Technologies-certified software applications on a LAN
running Novell NetWare software in a Hybrid/PBX mode
system. These applications may provide special features
for client control of such calling activities as power dialing.
See also screen pop.

cyclic redundancy
check

See CRC.

D4 framing format

Framing format consisting of a sequence of individual
frames of 24 eight-bit slots and one signal bit (193 bits) in a
12-frame superframe. See also ESF.

Data-channel

See D-channel.

D

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-9

data
communications
equipment

See DCE.

data module

A type of ISDN terminal adapter that acts as the DCE at a
data workstation that communicates over high-speed digital
facilities.

data rate

See bps.

data station

Special type of extension where data communications take
place; includes DTE and DCE; sometimes a telephone is
also part of a data station.

data terminal

An input/output device (often a personal computer) that can
be connected to the control unit via an interface.

data terminal
equipment

See DTE and data terminal.

data workstation

Special type of extension where data communications take
place; includes DTE and DCE; sometimes a telephone is
also part of a data workstation.

DCE

(data communications equipment) Equipment such as
modems or ISDN terminal adapters used to establish,
maintain, and terminate a connection between the system
and data terminal equipment (DTE), such as printers,
personal computers, host computers, or network
workstations.

DCP

(Digital Communications Protocol) AT&T proprietary
protocol to transmit digitized voice and data over the same
communications link.

D-channel

(Data-channel) 16- or 64-kbps channel that carries
signaling information or data on a PRI or BRI.

dedicated feature
buttons

The imprinted feature buttons on a telephone: Conf or
Conference, Drop, Feature, HFAI (Hands Free Answer on
Intercom), Hold, Message, Mute or Microphone, Recall,
Speakerphone or Spkrphone, and Transfer.

delay-start tie
trunk

Tie trunk or tandem tie trunk on which the originating end of
the tie trunk transmits an off-hook signal to the receiving
end and waits for the receiving end to send an off-hook
signal followed by an on-hook signal. Also called
“dial-repeating tie trunk.”

desktop
videoconferencing
system

A system application that allows face-to-face,
simultaneous video and voice communications between
individuals and requires high-speed data transmission
facilities. See also group videoconferencing system.

DFT

(direct facility termination) See personal line.

DHG

(data hunt group) Group of analog or digital data stations
that share a common access code. Calls are connected in
a round-robin fashion to the first available data station in
the group.

dial access

See feature code.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-10

Dialed Number
Identification
Service

See DNIS.

dial-out code

Digit (usually a ) or digits dialed by telephone users to get
an outside line.

dial plan

Numbering scheme for system extensions, lines, and
trunks.

dial-repeating tie
trunk

Tie trunk on which the originating end of the tie trunk
transmits an off-hook signal to the receiving end and waits
for the receiving end to send an off-hook signal followed by
an on-hook signal. Also called “dial-repeating tie trunk.”

DID

(Direct Inward Dial) Service that transmits from the
telephone company central office and routes incoming calls
directly to the called extension, calling group, or outgoing
line/trunk pool, bypassing the system operator.

DID trunk

Incoming trunk that receives dialed digits from the local
exchange, allowing the system to connect directly to an
extension without assistance from the system operator.

digital

Representation of information in discrete elements such as
off and on or zero and one. See also analog transmission.

Digital
Communications
Protocol

See DCP.

digital data station

See ISDN terminal adapter data station.

Digital Signal 0

See DS0.

Digital Signal 1

See DS1.

digital subscriber
line

See DSL.

digital switch
element

See DSE.

digital
transmission

Mode of transmission in which the information to be
transmitted is first converted to digital form and then
transmitted as a serial stream of pulses. See also analog
transmission.

DIP switch

(dual in-line package) Switch on a 400EM module used to
select the signaling format for tie-line transmission. Also
used on other equipment for setting hardware options.

direct facility
termination

(DFT) See personal line.

Direct Inward Dial

See DID.

Direct-Line
Console

See DLC.

Direct Station
Selector

See DSS.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-11

display buttons

Buttons on an MLX display telephone used to access the
telephone’s display.

DLC

(Direct-Line Console) Telephone used by a system
operator to answer outside calls (not directed to an
individual or a group) and inside calls, transfer calls, make
outside calls for users with outward calling restrictions, set
up conference calls, and monitor system operation.

DNIS

(Dialed Number Identification Service) Service provided by
AT&T and MCI; it routes incoming 800 or 900 calls
according to customer-selected parameters, such as area
code, state, or time of call.

door answering
unit

Device connected to a basic telephone jack and used at an
unattended extension or front desk.

DOS

(disk operating system)

drop-and-insert
equipment

A device that can be installed between systems connected
by tandem PRI trunks or T1-emulated tandem tie trunks to
allow fractional use of the facility, that is, use of fewer than
23 of the PRI B-channels or fewer than 24 of the T1
channels. In a PRI facility, the equipment must never drop
Channel 24, the D-channel. All channels must still be
programmed and all count towards the system maximum of
80 lines.

DS0

(Digital Signal 0) Single 64-kbps voice or data channel.

DS1

(Digital Signal 1) Bit-oriented signaling interface that
multiplexes twenty-four 64-kbps channels into a single
1.544-Mbps stream.

DSL

(Digital Subscriber Line) A Digital Subscriber Line provides
full-duplex service on a single twisted metallic pair (2-wire)
at a rate sufficient to support ISDN Basic Rate Access.

DSS

(Direct Station Selector) 60-button adjunct that enhances
the call-handling capabilities of an MLX-20L or MLX-28D
telephone used as an operator console.

DTE

(data terminal equipment) Equipment that makes the
endpoints in a connection over a data connection; for
example, a data terminal, personal computer, host
computer, or printer.

DTMF signaling

(dual-tone multifrequency signaling) Touch-tone signaling
from telephones using the voice transmission path. DTMF
signaling provides 12 distinct signals, each representing a
dialed digit or character, and each composed of two
voiceband frequencies.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-12

E
E&M signaling

Trunk supervisory signaling, used between two
communications systems, in which signaling information is
transferred through two-state voltage conditions (on the Ear
and Mouth leads) for analog applications and through two
bits for digital applications. See also tie trunk.

EIA

(Electronic Industries Association)

EIA-232-D

Physical interface, specified by the EIA, that transmits and
receives asynchronous data at speeds of up to 19.2-kbps
over cable distances of 50 feet (15 m).

Electronic
Switching System

See ESS.

endpoint

Final destination in the path of an electrical or
telecommunications signal.

Enhanced Service
Center

An application that sends calls to available agents in a
calling group. The Enhanced Service Center places calls in
queue, plays announcements, tracks agent activity and
availability, and provides real-time reports.

ESF

(extended superframe format) PRI framing format
consisting of individual frames of 24 eight-bit slots and one
signal bit (193 bits) in a 24-frame extended superframe.

ESS

(Electronic Switching System) Class of central office (CO)
switching systems developed by Lucent Technologies in
which the control functions are performed principally by
electronic data processors operating under the direction of
a stored program.

expansion carrier

Carrier added to the control unit when the basic carrier
cannot house all of the required modules. Houses a power
supply module and up to six additional modules.

ExpressRoute
1000

Data communications device that allows connection
between an RS-232 DTE device and the control unit using
MLX extension jacks on the 008 MLX or 408 GS/LS-MLX
module.

extended
superframe format

See ESF.

extension

An endpoint on the internal side of the communications
system. An extension can be a telephone with or without an
adjunct. Also called “station.” See also data workstation.

extension jack

An analog, digital, or tip/ring physical interface on a module
in the control unit for connecting a telephone or other
device to the system. Also called “station jack.”

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-13

extension
programming

Programming performed at an extension to customize
telephones for personal needs; users can program features
on buttons, set the telephone ringing pattern, and so on.
See also centralized telephone programming and system
programming.

facility

Equipment (often a line/trunk) constituting a
telecommunications path between the system and the
telephone company central office (CO).

Facility Restriction
Level

See FRL.

factory setting

Default state of a device or feature when an optional setting
is not programmed by the user or system manager.

fax

(facsimile) Scanning and transmission of a graphic image
over a telecommunications facility, or the resulting
reproduced image, or the machine that does the scanning
and transmitting.

Fax Attendant
System

Fax handling and processing application available with
AUDIX Voice Power.

FCC

(Federal Communications Commission)

feature

Function or service provided by the system.

feature code

Code entered on a dialpad to activate a feature.

feature module

Prior to Release 3.0, a circuit pack inserted into the
processor module, used to provide system features and
replaced when the system is upgraded.

Feature screen

Display screen on MLX display telephones; provides quick
access to commonly used features.

ferrite core

Attachment to the AC power cord and ground wire of the
carrier power supply for compliance with FCC, part 15
requirements.

Flash ROM

Beginning with Release 3.0, a type of read-only memory
provided on the processor module, used to supply system
features.

foil shield

Copper foil sheet (for power units) used to prevent
excessive noise on the module.

forced idle

Condition of the system during certain programming or
maintenance procedures; system prevents initiation of new
calls.

foreign exchange

See FX.

Fractional-T1

A digital transmission facility consisting of at least one, and
fewer than 24 DS0 channels using robbed-bit signaling and
connecting a PBX and a central office or toll office.

F

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-14

frame

One of several segments of an analog or digital signal that
has a repetitive characteristic. For example, a DS1 frame
consists of a framing bit and 24 bytes, which equals 193
bits.

framing format

Pattern of frames used in transmissions.

frequency
generator

See ring generator.

FRL

(Facility Restriction Level) Calling restriction type that
restricts calls to certain specified ARS and UDP routes.

FX

(Foreign exchange) Central office (CO) other than the one
that is providing local access to the public telephone
network.

General Purpose
Adapter

See GPA.

glare

Condition that occurs when a user tries to call out on a
loop-start line at the same time that another call arrives on
the same line.

GPA

(General Purpose Adapter) Device that connects an analog
multiline telephone to optional equipment such as an
answering machine or a fax machine.

ground-start trunk

Trunk on which the communications system, after verifying
that the trunk is idle (no ground on tip lead), transmits a
request for service (puts ground on ring lead) to the
telephone company central office (CO).

Group IV (G4) fax
machine

A fax unit, offering 400 by 100 dots per inch (DPI) in fine
mode, that can operate at any speed for communication
with a Group III (G3) fax machine or another Group IV (G4)
fax machine.

group
videoconferencing
system

A system application that allows face-to-face,
simultaneous video and voice communications between
groups and requires high-speed data transmission facilities.
See also desktop videoconferencing system.

Hands-Free
Answer on
Intercom

See HFAI.

hands-free unit

See HFU.

headset

Lightweight earpiece and microphone used for hands-free
telephone operation.

G

H

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-15

HFAI

(Hands-Free Answer on Intercom) Feature that allows a
user to answer a voice-announced call.

HFU

(Hands-Free Unit) Unit for analog multiline telephones that
allows users to make and receive calls on the
speakerphone without using the handset.

Home screen

Display normally shown on an MLX display telephone;
shows time, date, and call information, and shows when
some features are in use.

host

Telephone company or other switch providing features and
services to the system users, usually when the system is
operating in Behind Switch mode.

hub system

In private network that is arranged in a star configuration,
the communications system through which all calls across
the network pass.

Hybrid/PBX mode

One of three modes of system operation, in which the
system uses line/trunk pools and ARS in addition to
personal lines. Provides a single interface (SA buttons) to
users for both internal and external calling. See also Behind
Switch mode and Key mode.

ICLID

(Incoming Call Line Identification) See Caller ID.

ICOM buttons

(intercom buttons) Telephone buttons that provide access
to inside system lines for calling other extensions or
receiving calls from them.

immediate-start
tie trunk

Tie trunk on which no start signal is necessary; dialing can
begin immediately after the trunk is seized.

in-band signaling

See robbed-bit signaling.

inside dial tone

A tone users hear when they are off-hook on an SA or
ICOM button.

Inspect screen

Display screen on an MLX display telephone that allows the
user to preview incoming calls and see a list of the features
programmed on line buttons.

Integrated
Administration

Capability of IS III that simplifies the programming of
common information for the system, AUDIX Voice Power,
and, if it is also installed, Fax Attendant System.

Integrated
Services Digital
Network

See ISDN.

Integrated
Solution II/III

See IS II/III.

Integrated Voice
Power Automated
Attendant

IS II application that automatically answers incoming calls
with a recorded announcement and directs callers to a
department, an extension, or the system operator.

I

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-16

intercom buttons

See ICOM buttons.

interface

Hardware and/or software that links systems, programs, or
devices.

intersystem calls

In a private network, calls between a local extension and a
local or non-local dial plan extension.

Intuity

A set of integrated applications that provides voice mail, fax
messaging, automated attendant, call accounting, and
system programming.

Intuity
CONVERSANT

Voice response application that automatically answers and
routes calls and executes telephone transactions.

I/O device

(input/output device) Equipment that can be attached to a
computer internally or externally for managing a computer
system’s input and output of information.

IROB protector

(In-Range Out-of-Building protector) Surge-protection
device for off-premises telephones at a location within 1000
feet (305 m) of cable distance from the control unit.

IS II/III

(Integrated Solution II or Integrated Solution III) Set of UNIX
System-based applications that augments and provides
additional services using the system. IS II and III are no
longer available.

ISDN

(Integrated Services Digital Network) Public or private
network that provides end-to-end digital connectivity for all
services to which users have access by a limited set of
standard multipurpose user and network interfaces;
provides digital circuit-switched or packet-switched
connections within the network and to other networks for
national and international digital connectivity.

ISDN 7500B Data
Module

Data communications device that allows connection
between an RS-232 DTE device and the control unit by
MLX extension jacks on the 008 MLX or 408 GS/LS-MLX
module.

ISDN terminal
adapter

(Integrated Services Digital Network terminal adapter) A
device that connects the communications system with data
terminal equipment (DTE).

ISDN terminal
adapter data
station

A type of data station that includes an ISDN terminal
adapter as its DCE. It may also include an MLX telephone
for simultaneous voice and data (ISDN terminal adapter
data-only station). These data stations connect to MLX
extension jack modules for digital transmission of data over
a DS1 facility.

jack

Physical connection point to the system for a telephone,
line/trunk, or other device. Also called “port.”

J

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-17

K
kbps

(kilobits per second)

Key mode

One of three modes of system operation, in which the
system uses personal lines on line buttons for outside calls,
with a separate interface (ICOM buttons) for inside calling.
See also Behind Switch mode and Hybrid/PBX mode.

LAN

(local area network) Arrangement of interconnected
personal computers or terminals, sometimes accessing a
host computer, sometimes sharing resources such as files
and printers.

LDN

(Listed Directory Number)

LED

(light-emitting diode) Semiconductor device that produces
light when voltage is applied; light on a telephone.

line

Connection between extensions within the
communications system; often, however, used
synonymously with trunk.

line and trunk
assignment

Assignment of lines and trunks connected to the system
control unit to specific buttons on each telephone.

line coding

Pattern that data assumes as it is transmitted over a
communications channel.

line compensation

Adjustment for the amount of cable loss in decibels (dB),
based on the length of cable between a 100D module and
a channel service unit (CSU) or other far-end connection
point.

line/trunk

Refers to inside system lines and outside lines/trunks in
general terms. See also line and trunk.

line/trunk jack

Physical interface on a module in the control unit for
connecting an outside line/trunk to the communications
system. Also called “trunk jack.”

line/trunk and
extension module

Module on which the jacks for connecting central office
lines/trunks and/or the jacks for connecting the extensions
are located.

local dial plan

In a system that is part of a private network, a list of
extension ranges that the local system refers to in order to
route local intersystem calls via UDP.

local extension

In a system that is part of a private network, an extension
that is listed in the system’s local dial plan.

local host
computer access

A method for connecting an extension jack to an on-site
computer for data-only calls through a modem or ISDN
terminal adapter.

L

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-18

local loop

The two-way connection between a customer’s premises
and the central office (CO).

local user

In a private network, a person whose extension is
connected to the local control unit.

logical ID

Unique numeric identifier for each extension and line/trunk
jack in the system control unit.

loop-start line

Line on which a closure between the tip and ring leads is
used to originate or answer a call. High-voltage 20-Hz AC
ringing current from the central office signals an incoming
call.

Lucent
Technologies
Attendant

Application with equipment that connects to one or more
tip/ring (T/R) extension jacks and automatically answers
incoming calls with a recorded announcement; directs calls
in response to touch tones. This application is no longer
available.

Magic on Hold

A Lucent Technologies Music On Hold enhancement that
promotes a company’s products or services.

Mbps

(megabits per second)

Megacom

The AT&T tariffed digital WATS offering for outward calling.

Megacom 800

The AT&T tariffed digital 800 offering for inward calling.

memory card

Storage medium, similar in function to a floppy disk, that
allows information to be added to or obtained from the
communications system through the PCMCIA interface
slot on the processor module.

MERLIN Identifier

Adjunct that allows users to receive, store, and use
information provided by Caller ID.

MERLIN LEGEND
Mail

A voice messaging system that provides automated
attendant, call answering, and voice-mail services. It is
housed in its own module.

MERLIN MAIL

A voice messaging system that provides automated
attendant, call answering, and voice-mail services. No
longer available.

Messaging 2000

A voice messaging system housed in a PC that connects to
tip/ring ports on the system’s modules. Messaging 2000
provides voice mail, automated attendant, call answering,
and fax messaging.

MFM

(Multi-Function Module) Adapter that has a tip/ring mode
for answering machines, modems, fax machines, and
tip/ring alerts, and an SAA mode for -48 VDC alerts. It is
installed inside an MLX telephone and is used to connect
optional equipment to the telephone. The optional
equipment and the telephone operate simultaneously and
independently.

M

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-19

MLX telephone

A multiline button telephone that transmits and receives
digital signals.

mode codes

Streams of touch-tone codes used by voice messaging
applications to communicate with the system’s control unit.

modem

Device that converts digital data signals to analog signals
for transmission over a telephone line, and analog signals
received on a telephone line to digital signals.

modem data
station

A type of data station that includes a modem as its DCE. It
may also include an MLX telephone for simultaneous voice
and data (MLX voice and modem data station), an analog
multiline telephone (analog voice and modem data
station), or a single-line telephone for dialing only (modem
data-only station). These data stations connect respectively
to MLX, analog, or tip/ring extension jack modules. They
provide analog transmission of data.

modem pool

Pair, or group of pairs, of modems and data modules with
interconnected RS-232 interfaces that converts digital
signals to analog, or analog signals to digital, thereby
allowing users with ISDN terminal adapter data stations to
communicate with users who have analog modem data
stations.

module

Circuit pack in the control unit that provides the physical
jacks for connection of telephones and/or outside
lines/trunks to the communications system. In the name of
a module, the first digit indicates the number of line/trunk
jacks it contains; the last digit indicates the number of
extension jacks it contains. If no letters appear after the
number, a line/trunk module provides loop-start lines or an
extension jack module provides analog or tip/ring jacks. For
example, a 408 GS/LS MLX module contains four line/trunk
jacks and eight digital (MLX) extension jacks, and provides
either loop-start (LS) or ground-start (GS)trunks.

monitored
extension

Extension for which one or more CTI applications is
receiving call information. The CTI application does not
have to be directly attached to the equipment at the
extension in order to monitor calls. The call information may
appear on the PC screen of another extension that has
been programmed to receive it. See also CTI link and
unmonitored extension.

Multi-Function
Module

See MFM.

multiline
telephone

An analog or digital (MLX) telephone that provides multiple
line buttons for making or receiving calls or programming
features.

multiplexing

The division of a transmission channel into two or more
independent channels, either by splitting the frequency
band into a number of narrower bands or by dividing the
channel into successive time slots.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-20

Music On Hold

Customer-provided music source or Magic on Hold
connected to the system through a loop-start jack.

network

Configuration of communications devices and software
connected for information interchange.

network interface

Hardware, software, or both that links two systems in an
interconnected group of systems, for example, between the
local telephone company and a PBX.

NI-1 BRI

(National Integrated Services Digital Network 1 Basic Rate
Interface) A type of digital facility that carries the equivalent
of three lines. Two are called B-channels and provide voice
and data communications services. A third D-channel
controls signaling and maintains operations on the
B-channels.

non-local
extension

In a system that is part of a private network, an extension
that is in the non-local dial plan.

non-local user

In a private network, a user who is connected to another
system in the network and not to the local system.

non-local dial plan

In a system that is part of a private network, a list of
extension ranges that the local system references in order
to route non-local intersystem calls via UDP.

non-satellite
system

In a private network, a communications system that is
directly connected to and located more than 200 miles from
the local system.

off-hook

Telephone is said to be off-hook when the user has lifted
the handset, pressed the Speakerphone button to turn on
the speakerphone, or used a headset to connect to the
communications system or the telephone network.

off-premises
telephone

See OPT.

ones density

Requirement for channelized DS1 service to the public
network that eight consecutive zeros cannot occur in a
digital data stream.

on-hook

Telephone is said to be on-hook when the handset is hung
up, the speakerphone is turned off, and the user is not
using a headset to connect to the communications system
or the telephone network.

N

O

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-21

OPT

(off-premises telephone) Single-line telephone or other
tip/ring device connected to the system via a 008 OPT
module in the control unit. Appears as an inside extension
to the system, but may be physically located away from the
system.

OPX

(off-premises extension)

out-of-band
signaling

Signaling that uses the same path as voice-frequency
transmission and in which the signaling is outside the band
used for voice frequencies.

parity

The addition of a bit to a bit string so that the total number
of ones is odd or even, used to detect and correct
transmission errors.

PassageWay
Direct Connection
Solution

Set of software applications that provides an interface
between a personal computer and an MLX telephone.

PBX

(private branch exchange) Local electronic telephone
switch that serves local stations (for example, extensions
within a business) and provides them with access to the
public network.

PC

personal computer

PCMCIA memory
card

(Personal Computer Memory Card International
Association memory card) See memory card.

peripheral system

In a private network, a system that does not connect to
more than one other system, sometimes called an “end
node.”

personal line

Central office line/trunk that terminates directly at one or
more extensions. In Hybrid/PBX mode, a personal line
cannot be part of a line/trunk pool. Also called “DFT” (direct
facility termination).

PFT

(Power Failure Transfer) Feature that provides continuity
of telephone service during a commercial power failure by
switching some of the system’s line/trunk connections to
telephones connected to specially designated extension
jacks.

phantom
extension

An extension that is not actually plugged into the system
but is used, for example, as a calling group member
covered by a voice messaging system.

pool

In Hybrid/PBX mode, a group of outside lines/trunks that
users can access with a Pool button or by dialing an
access code on an SA button. Also used by the ARS
feature when choosing the least expensive route for a call.

point-to-point
facility

In a private network, a line/trunk that passes through the
PSTN without using the switching capabilities of the PSTN.

P

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-22

port

See jack. Also, refers to extension or line/trunk jacks before
these are numbered according to the dial plan during
programming. The lowest jack on a module is always
Port 1.

Power Failure
Transfer

See PFT.

power supply
module

Device that directs electricity to modules and telephones on
the system. One power supply module is needed for each
carrier, and an auxiliary power unit is added if needed.

PRI

(Primary Rate Interface) Standard interface that specifies
the protocol used between two or more communications
systems. As used in North America, it provides
twenty-three 64-kbps B-channels for voice and/or data and
one 16-kbps D-channel, which carries multiplexed signaling
information for the other 23 channels.

primary system
operator position

First jack on the first MLX or analog multiline extension
module in the control unit, that is, the extension jack with
the lowest logical ID in the system.

prime line

Individual extension number assigned to a telephone in a
system operating in Behind Switch mode. Each telephone
user has his or her own prime line and is automatically
connected to that line when he or she lifts the handset.

private
communications
network or private
network

An interconnected group of communications systems,
which may consist of MERLIN LEGEND Communications
Systems, DEFINITY Enterprise Communications Servers
(ECS), and/or DEFINITY ProLogix Solutions.

private network
trunks

The facilities that connect communications systems in a
private network. See also tandem tie trunks and tandem
PRI trunks.

processor module

Module in the second slot of the control unit (Slot 0, to the
right of the power supply module). Includes the software
and memory that runs the system.

programming port
reassignment

Reassignment of the system programming jack position to
any of the first five extension jacks on the first MLX module
in the control unit.

protocol

Set of conventions governing the format and timing of
message exchanges between devices, such as an MLX
telephone and the control unit.

PSTN

Network that is commonly accessible for local or
long-distance calling. Also called “public network” or
“public switched network.”

PSTN trunk

In a private network, a facility that connects a networked
system to the public switched telephone network.

public switched
telephone network

See PSTN.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-23

Q
QCC

(Queued Call Console) MLX-20L telephone used by a
system operator in Hybrid/PBX mode only. Used to answer
outside calls (directed to a system operator position) and
inside calls, direct inside and outside calls to an extension
or an outside telephone number, serve as a message
center, make outside calls for users with outward calling
restrictions, set up conference calls, and monitor system
operation.

RAM

(random-access memory) Computer memory in which an
individual byte or range of bytes can be addressed and
read or changed without affecting other parts of memory.

read-only memory

See ROM.

Remote Access

System feature that allows an outside caller to gain access
to the system, almost as if at a system extension. In a
private network, remote access settings are used to control
calls routed via ARS or UDP routing across the network.

restore

Procedure whereby saved and archived system
programming is reinstated on the system, from a floppy
disk or memory card. See also backup.

restricted data
channel

Restricted data channels do not allow the transmission of
occurrences of more than seven contiguous zero bits. See
also unrestricted data channel.

ring generator

Circuit pack added to the power supply that generates a
high-voltage, 20–30 Hz signal to ring a telephone.

riser cable

Cable that runs between floors in a multistory building and
connects wiring closets.

RS-232

Physical interface, specified by the Electronics Industries
Association (EIA), that transmits and receives
asynchronous data at distances of up to 50 feet (15 m).

robbed-bit
signaling

Signaling in which the least significant bit of every sixth
frame per channel is used for signaling in that channel.

ROM

(read-only memory) Computer memory that can be read
but cannot be changed.

R

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-24

S
SAA

(Supplemental Alert Adapter) Device that permits alerting
equipment to be connected to an analog multiline
telephone jack so that people working in noisy or remote
areas of a building can be alerted to incoming calls.

SA buttons

Telephone buttons that provide access to both inside and
outside calls.

satellite system

In a private network, a communications system that is
directly connected to and located within 200 miles of the
local system.

screen pop

Refers to a computer-telephony software application that
takes caller information (for example, provided by Caller ID
service), queries a database, and displays a screen with
information about the caller onto a user’s PC screen.
Screen pop requires that an identifying number or code be
available to identify the calling party. See also CTI link.

SDN

(Software Defined Network) AT&T private networking
service created by specialized software within the public
network.

series
configuration

A private network arrangement where either two or four or
more communications systems are connected in a line,
with no particular system acting as the hub system. See
also star configuration.

Service Observing

A feature available in Release 6.1 and later systems that
allows one extension to listen in on (observe) calls that
arrive at another extension.

SID

[station (extension) identification]

signaling

Sending of information between devices to set up,
maintain, or cease a connection such as a telephone call.

simplex signaling

Transmission of signals in one direction only across a
telecommunications channel.

single-line
telephone

Industry-standard touch-tone or rotary-dial telephone that
handles one call at a time and is connected to the system
via an extension jack on a 012, 016 (T/R), or 008 OPT
module.

slot

Position in a carrier for a module; numbered from 0.

SMDR

(Station Message Detail Recording) Feature that captures
usage information on incoming and outgoing calls.

SMDR printer

Printer used to produce SMDR reports. Connected to the
system via an RS-232 jack on the processor module.

Software Defined
Network

See SDN.

special character

Pause, Stop, or End-of-Dialing signal in a programmed
dialing sequence such as a speed dial number.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-25

SPM

(System Programming and Maintenance) DOS-, UNIX-, or
Windows-based application for programming the system.

square key

Configuration in Key mode operation in which all outside
lines appear on all telephones.

star configuration

A private network arrangement where either three or more
communications systems are connected with one system
acting as the hub system. See also series configuration.

station

See extension.

station jack

See extension jack.

Station Message
Detail Recording

See SMDR.

Supplemental
Alert Adapter

See SAA.

switch

See communications system.

Switched 56
service

DS1 Switched 56 service is an end-to-end digital, 56-kbps,
full duplex, synchronous, circuit-switched service offering.
The service is offered by network service providers and by
some Local Exchange Carriers (LECs) as circuit-switched,
56-kbps service. T1-emulated tandem tie trunks in a private
network can be programmed for data.

switchhook flash

Momentary (320 ms to 1 second) on-hook signal used as a
control; may be directed to the control unit or to a host
switch outside the system. Also called “Recall” or “timed
flash.”

switch identifier

A number assigned to a tandem trunk in a private network.
It identifies the system connected to the far end of the
trunk. Switch identifiers are based on the type of system
and its distance from the system where the identifier is
assigned. See also satellite system and non-satellite
system.

synchronous data
transmission

Method of transmitting a continuous digital data stream in
which the transmission of each binary bit is synchronized
with a master clock. See also asynchronous data
transmission.

system
acceptance test

Test of all trunks, telephones, data terminals, and features
after installation to ensure that they are working correctly.

System Access
buttons

See SA buttons.

system date and
time

Date and time that appear on MLX display telephones and
SMDR reports.

system
programming

Programming of system functions and features that affect
most users, performed from an MLX-20L telephone or a
computer using SPM. See also extension programming
and centralized telephone programming.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-26

System
Programming and
Maintenance

See SPM.

system
renumbering

Procedure used to change the numbers assigned to
telephones, adjuncts, calling groups, paging groups, park
zones, Remote Access, and lines/trunks.

T1

Type of digital transmission facility that in North America
transmits at the DS1 rate of 1.544 Mbps.

T1-emulated data

A T1 tie trunk programmed for S56DATA for use by data
calls at speeds up to 56 kbps. These trunks may be used
for tandem and non-tandem operation.

T1-emulated voice

A T1 tie trunk programmed for Tie-PBX or Tie-Toll for use
by voice calls.

T1 Switched 56
service

T1 digital data transmission over the public network or over
a private network at 56 kbps. See Switched 56 service.

tandem switching

The capability of private network communications systems
that allows them to direct outside calls from one facility to
another facility, rather than just to an extension. Calls may
be sent, for example, from a PSTN facility to a tandem
trunk or vice versa.

tandem trunk

An private outside facility (as opposed to an inside system
line) that connects two communications systems in a
private network and can carry calls to another outside
facility through tandem switching. The trunk is not
connected to the PSTN.

tandem tie trunk

A tandem trunk that is an analog delay-start tie trunk,
providing a single line/trunk per facility and allowing analog
transmission of voice and low-speed data; or a T1 facility
offering 24 channels on emulated tie trunks and
programmed for voice or data.

tandem PRI trunk

(tandem Primary Rate Interface trunk) A private network
trunk.

TAPI

Telephony Application Programming Interface. An
application programming interface that allows computer
telephony applications to be used. TAPI is not yet
supported by the MERLIN LEGEND Communications
System. See also TSAPI and CTI.

telephone power
supply unit

Equipment that provides power to an individual telephone.

terminal adapter

See ISDN terminal adapter.

tie trunk

Private trunk directly connecting two telephone switches.

timed flash

See switchhook flash.

T

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-27

tip/ring

Contacts and associated conductors of a single-line
telephone plug or jack.

touch-tone
receiver

See TTR.

T/R

See tip/ring.

trunk

Telecommunications path between the communications
system and the telephone company central office (CO) or
another switch. Often used synonymously with line.

trunk jack

See line/trunk jack.

trunk pool

See pool.

TSAPI

Telephony Services Application Programming Interface.
An application programming interface that allows computer
telephony applications to be used. TSAPI is supported by
the MERLIN LEGEND Communications System Release
5.0. See also TAPI and CTI.

TTR

(touch-tone receiver) Device used to decode DTMF
touch-tones dialed from single-line or Remote Access
telephones.

UDP

(Uniform Dial Plan) Composed of the local dial plan and
non-local dial plan. A dial plan that allows a caller at any
extension in a private network to dial the same number of
digits to reach any other extension in the private network,
even if the originating extension is physically connected to
one communications system and the terminating extension
is physically connected to a different communications
system.

unambiguous
numbering

The practice of numbering of extension ranges, remote
access codes, or other system components to avoid routing
conflicts in network or local calling. For example, Extension
441 is unique when compared to Extension 4410.
However, it is ambiguous, because a system routes as
soon as it matches the digits sent for a call with the digits in
a local plan or in a non-local dial plan extension range.
When a caller dials , a system routes the call to
Extension 441 immediately, without considering the last
dialed digit.

Uniform Dial Plan

See UDP.

uninterruptible
power supply

See UPS.

unit load

Measure of the power load drain of a module, telephone, or
adjunct.

unmonitored
extension

An extension for which no CTI application is receiving call
information. See also CTI link and monitored extension.

U

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Glossary

Page GL-28

unrestricted data
channel

Unrestricted data channels (also called clear data
channels) allow the transmission of occurrences of more
than seven contiguous zero bits. If an unrestricted data
channel is requested and only restricted channels are
available, the call will be rejected. See also restricted data
channel.

UPS

(uninterruptible power supply) Device that connects to the
system to provide 117 VAC to the equipment when the
commercial power source fails.

VAC

(alternating-current voltage)

VDC

(direct-current voltage)

VMI

(voice messaging interface) An enhanced tip/ring port.

videoconferencing
system

System application that allows face-to-face meetings, with
voice and video, to occur between individuals or groups.
This application requires high-speed data transmission
facilities. See also desktop videoconferencing and group
videoconferencing.

virtual private
network

See VPN.

VPN

(virtual private network) A type of private network that uses
the switching capabilities of the PSTN, rather than tandem
switching, to direct calls between connected
communications systems. A VPN may constitute a part of a
private network.

voice-band
channel

A transmission channel, generally in the 300–3400-Hz
frequency band.

voice mail

Application that allows users to send messages to other
system extensions, forward messages received with
comments, and reply to messages.

voice messaging
interface

See VMI.

WATS

(Wide Area Telecommunications Service) Service that
allows calls to certain areas for a flat-rate charge based on
expected usage.

wink-start tie trunk

Tie trunk on which the originating end transmits an off-hook
signal and waits for the remote end to send back a signal (a
wink) that it is ready for transmission.

V

W

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Index

Page IN-1

NI

Index
IN
Numerics
008 MLX module, 2–3, 2–5
008 module, 6–3
008 OPT module, 2–30
AUDIX Voice Power, 2–30, 2–31
extension capacity, 2–3
MERLIN MAIL voice messaging system, 2–31
016 T/R module, 2–5, 2–30
ringing frequency, 2–30, 2–32
100D module, 3–3, 3–22
2-digit numbering plan, 2–34
3-digit numbering plan, 2–35
408 GS/LS MLX module, 6–3
jacks, 3–2
Power Failure Transfer (PFT) feature, 2–6
408 GS/LS-MLX module, 6–3
ports, 2–15
408 module, 6–3
4ESS, 3–23, D–1
5ESS, 3–23, D–1
5ESS Local, 3–34
800 NI-BRI module, 2–5, 3–3, 3–5

A
Absorb digits, 4–70
Account Code Entry, 5–35
ACCUNET Switched Digital Services, 3–3
ACCUNET Switched Digital Services (SDS), D–1
Adding to the system, 6–2
Adjuncts, system
assigning buttons, 3–56
features, 4–3
numbering , 2–26
Queued Call Console (QCC), 4–4
Alert
external, 4–36
Allowed Lists, 4–50
American Society of Composers, Artists, and Producers (ASCAP), 3–9
Analog multiline telephones
and Delay Announcement Units, 2–27
button assignments (Hybrid/PBX mode), 3–57
button assignments (Key/Behind Switch mode), 3–59
Extension Copy feature, 4–11
jacks, 2–27
trunk assignment, 3–50
Analog voice and modem data stations
lines/trunks, 5–8
Answer supervision time, 3–41

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Index

Page IN-2
Applications
AUDIX Voice Power/Fax Attendant, 2–30
CONVERSANT, 2–31
Enhanced Service Center (ESC), 2–31
Integrated Solution II (IS II), 2–32
Integrated Solution III (IS III), 2–32
Intuity AUDIX, 2–31
jacks, 2–30
Lucent Attendant, 2–31
MERLIN LEGEND Mail, 2–31
MERLIN MAIL voice messaging system, 2–31
Messaging 2000, 2–31
planning for, 2–12
AT&T Switched Network (ASN), 3–3
AT&T Toll, 3–34
AUDIX Voice Power/Fax Attendant System
008 OPT module, 2–15
coverage group , 4–31
ports, 2–30
renumbering , 2–33
reserved extensions, 4–32
Auto Answer All, 5–35
Autodial, 3–49
Automatic backup , 2–11
Automatic Callback, 3–18, 3–20, 4–44
Automatic Hold or Release, 4–20
Automatic Maintenance Busy, 2–10
Automatic Route Selection (ARS), 5–35
absorb digits setting , 4–72
area code/exchanges, 4–59
button assignments, 3–55
call types, 4–72
description, 4–59
Facility Restriction Levels (FRLs), 4–67
other digits setting , 4–72
pools, 4–70
preferred trunk pools, 4–59
slow dial tone and , 3–49
subpatterns, 4–66
tables, 4–63
type of dialing , 4–59
worksheet, 4–59
Auxiliary equipment, 6–4

B
Backing up the system, system programming , 2–11
Barrier codes, 3–18, 3–20
B-channel groups, 3–33
Behind Switch mode
button assignments, 3–57
features, 2–8
BRI line options
Service Profile Identifier (SPID)
planning form instructions, 3–45

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Index

Page IN-3
BRI line options planning , 3–44
clock synchronization
planning considerations, 3–46
Service Profile Identifier (SPID)
planning considerations, 3–45
timers
planning considerations, 3–48
planning form instructions, 3–48
Broadcast Music Incorporated (BMI), 3–9
Buttons
assigning , 3–55
assigning in Behind Switch mode, 3–57
assigning in Hybrid/PBX mode, 3–52
assigning in Key mode, 3–57
factory assignments, 3–57

C
Calculating unit loads, F–2
Call Management System (CMS), 2–23, 2–34
Call-by-Call Service Selection, 3–3, 3–36
Calling Groups
and dial-in trunks, 3–16, 4–34
and DID trunks, 3–42
and Incoming Call Line Identification (ICLID), 3–4
and Pools, 3–16
and Remote Access, 3–19
and Tie trunks, 3–40
interaction with Music on Hold and External Page Port trunks, 3–4
Calling groups
Calls-in-Queue alarm threshold , 4–35
extension number, 4–33
Extension Status, 4–32, 4–44
external alert for, 4–36
Hunt type, 4–35
MERLIN LEGEND Mail, 4–33
Message Waiting receiver, 4–35
names, 4–33
options, 4–35
overflow coverage, 4–39
overflow threshold , 4–36
overflow time threshold , 4–40
overview, 4–32
types, 4–40
Calling Restrictions, 5–37
Calling restrictions, 5–35, 5–37
overview, 4–5, 4–53
Calls-in-Queue alarm threshold , 4–35
Calls-in-Queue alert, 4–20
Camp-On, 4–43
Capacity
lines/trunks, 2–2
Centralized programming , 4–2
Centralized Voice Mail, 2–32
CentreVu Computer-Telephony Services for Windows NT, 2–26, 2–28
Centrex, 3–3
Channel service unit (CSU), 3–27

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Index

Page IN-4
Class of restriction (COR)
with barrier codes, 3–22
without barrier codes, 3–21
Clock synchronization
800 NI-BRI and 100D module interaction, 3–46
NI-1 BRI service, 3–46
planning considerations, 3–46
Primary Rate Interface (PRI), 3–32
T1 service, 3–26
Computer Telephony Integration (CTI) link, 1–6, 2–28
Consoles, system, 2–11
Control unit
configuration planning , 2–1, 2–36
diagram, 2–6
extension capacity, 2–3
line/trunk capacity, 2–2
module placement, 2–1, 2–4
operating conditions, 2–7
CONVERSANT, 2–31
Conversion
requirements for restore, 7–4
Cover Ring Delay, 4–14
Coverage, 2–16
AUDIX Voice Power/Fax Attendant System, 4–31
Cover button, 4–31
delay interval, 4–30
group , 4–30
Group Cover button, 4–31
Group Coverage calls, 4–31
Individual Coverage, 4–28
overview, 4–28
primary, 4–29
receivers, 4–28, 4–29
secondary, 4–29
senders, 4–28
Coverage delay interval, 4–30
Coverage VMS, 4–56

D
Data communications equipment, 5–3
Data forms, C–1
Data Hunt Group , 5–4
Data stations, 5–3
analog voice and modem data, 5–8
buttons in Hybrid/PBX mode, 5–31
calling restrictions, 5–35
extension jacks, 5–1
extension jacks for, 5–1
GPA, 5–7
ISDN terminal adapter data-only, 5–11
LAN host computer, 5–15, 5–25
LAN workstations, 5–15, 5–25
modem data-only, 5–9
Data Status, 5–35
Data Terminal, 5–3
Data Terminal Equipment (DTE), 5–3
Date, 2–10

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Index

Page IN-5
Delay Announcement Devices
connected to tip/ring jacks, 2–30
MLX telephone adjunct, 2–25
Delay announcement devices, 2–18
Delay Announcement Units
Connected to analog multiline telephones, 2–27
TTRs required , 2–20
Delay option, 3–49
Delay Ring interval, 4–30
DEX600, D–1
Dial plan routing , 3–33
Dial tone, 2–17, 3–41, 3–49
secondary dial tone timer, 2–12
Dialed Number Identification Service (DNIS), 3–3
Digital adjuncts
assigning trunks, 3–51
features, 4–3
jacks, 2–25
user information, 3–51
Digital Signal 1 (DS1)
configurations summary, 3–38
ground-start emulation, 3–3
T1, 6–3
Direct Inward Dial (DID) trunks, 5–28
blocks and , 3–43
dial one, 3–42
disconnect time, 3–44
expected digits, 3–43
invalid destination, 3–43
options, 3–42
planning , 3–42
remote access, 3–19, 3–42
signaling , 3–43
type, 3–43
Direct Station Selector (DSS)
buttons, 3–62
park zones, 4–25
ranges, 4–25
Directed call completion, 4–22
Direct-Line Console (DLC)
assigning trunks, 3–50
Automatic Hold , 4–18
button assignment, 3–62, 3–63
button assignments, 3–62
definition, 2–11
Extension Copy feature, 4–11
features, 4–18
MFM adjuncts, 3–50
primary operator position, 2–21
Disallowed Lists, 4–51
Disconnect signal, 3–12
Disconnect time, 3–41, 3–44
DMS FX services, D–1
DMS INWATS services, D–1
DMS OUTWATS services, D–1
DMS Private Network services, D–1
DMS Tie Trunk services, D–1
DMS-100 Local services, 3–34
DMS-100 services, D–1
DMS-250 services, D–1

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Index

Page IN-6

E
E&M signal, 3–40
Elevate priority, 4–21
Emergency Allowed List, 4–55
Enhanced Service Center, 2–30
Enhanced Service Center (ESC), 2–31
Extension Copy, 4–2
Extension jacks
data stations, 5–1
identifying , 2–14
LAN data stations, 5–15
numbers, 2–4, 4–27
pairs, 2–24
Extension Status, 4–32, 4–44
Extensions
adding , 6–2, 6–6
assigning numbers, 2–13
capacity, 2–3
identifying jacks, 2–14
jack pairs, 2–24
labels, 2–33
module types, 2–14
modules required , 6–2
numbering plans, 2–33

F
Facility Restriction Levels (FRLs), 4–67
Fax machines
features, 4–8
message threshold , 4–8
message-waiting receiver, 4–8
Features
adding , 6–2
group-assigned , 4–26
overview, 4–1
system, 4–41
telephone, 4–2
Federal Communications Commission (FCC)
Key mode registration, 3–6
system mode registration, 2–8
Forced Account Code Entry, 4–6
Forms
data, C–1
system planning , B–1
Forward Delay option, 4–7
Framing format, 3–25, 3–31
FTS2000 network, 3–23

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Index

Page IN-7

G
General-Purpose Adapter (GPA), 5–8
analog multiline telephone connection, 2–27
data stations, 5–7
feature assignment, 5–7
requirement, 6–3
Ground-start
emulation, 3–3
lines/trunks, 5–27
Ground-start trunks
emulation, 3–3
Group Calling
and dial-in trunks, 3–16, 4–34
and DID trunks, 3–42
and Incoming Call Line Identification (ICLID), 3–4
and Pools, 3–16
and Remote Access, 3–19
and Tie trunks, 3–40
assigning trunks, 3–4
Delay Announcement Device, 2–25
interaction with Music on Hold and External Page Port trunks, 3–4
options, 4–35
overview, 4–32
touch-tone receivers (TTRs) required , 2–18
Group channel assignments, 3–33
Group Cover button, 4–31
Group Coverage, 4–30
Group ID, 4–28
Group name, 4–28
Group number, 4–27
Group paging , 4–27
Group Videoconferencing , 5–17

H
Hold
disconnect interval, 3–14
return, 4–19
timer, 4–18
HotLine, 4–10
Hunt type, 4–35
Hybrid/PBX mode
Automatic Maintenance Busy, 2–10
buttons for data stations in, 5–31
calling restrictions, 5–35
setting up , 2–8

I
Idle Line Preference, 5–35
Integrated Solution II (IS II), 2–32
Integrated Solution III (IS III), 2–32

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Index

Page IN-8
Integrated Voice Power Automated Attendant, 2–32
Interdigit timers, 4–49
Intuity, GL–16
Intuity AUDIX, 2–30, 2–31
INWATS, D–1
ISDN Terminal Adapter, 5–3

J
Jacks
additional operator positions, 2–22
analog multiline telephones, 2–27
applications, 2–30
auxiliary equipment, 3–9
CTI applications, 2–28
data terminals, 2–25
identifying for extensions, 2–14
lines/trunks, 3–1
MLX, 2–24, 2–25
operator position maximum, 2–22
primary operator position, 2–21
system programming , 2–7
tip/ring (T/R) equipment, 2–30
type, 2–15

K
Key mode
data stations, 5–33
FCC registration, 3–6
permanent, 2–8
setting up , 2–8

L
Labeling
display telephones, 4–57
extensions, 2–33
Posted Messages, 4–57
System Speed Dial, 4–58
Language selection, 2–9
Line coding
Primary Rate Interface (PRI), 3–31
T1 service, 3–25
Line compensation
settings, 3–25, 3–32
T1, 3–25
Line options planning
BRI Line Options, 3–44
Service Profile Identifier (SPID), 3–45
clock synchronization, 3–46
timers, 3–48

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Index

Page IN-9
Lines/trunks
adding to the system, 6–4
assigning , 3–50
capacity, 2–2
connecting components with, 2–4
Direct Inward Dial (DID), 3–42
DS1 connectivity, 3–23
hold disconnect interval, 3–14
identifying jacks, 3–1
incoming types, 3–6
jacks, 3–2
labels, 3–7
loop-start disconnect, 3–12
modules and jack types, 3–2
NI-1 BRI connectivity, 3–44
options, 3–11
outmode signaling , 3–13
planning overview, 3–1
pools, 3–16
Primary Rate Interface (PRI), 3–23
QCC operator to receive calls, 3–15
QCC queue priority, 3–15
remote access, 3–18
required , 6–2
T1 service, 3–23, 3–24
T1 Switched 56 service, 3–28
tie, 3–39
toll type, 3–13
Voice Messaging System, 3–10
Local Area Networks (LANs)
host computer data stations, 5–15, 5–25
workstation data stations, 5–15, 5–25
Logical IDs, 2–4
Loop-Start
disconnect signal, 3–12
lines/trunks, 5–27
reliable disconnect, 3–12
trunk-to-trunk transfer, 3–12
Loudspeaker paging jacks, 3–9
LS-ID Delay, 3–4

M
Magic on Hold , 3–9
Maintenance Alarm jacks, 3–9
Marked System Speed Dial, 4–58
Marked system speed dial
and star codes, 2–12, 4–58
Master extensions, 4–14
MCI 800 services, D–1
MCI 900 services, D–1
MCI Prism services, D–1
MCI Toll services, 3–34
MCI VNet services, D–1
Megacom 800 services, 3–3, 3–24, D–1
Megacom WATS services, 3–3, D–1

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Index

Page IN-10
MERLIN LEGEND Mail, 2–31, 4–33
calling groups, 4–33
MERLIN MAIL voice messaging system, 2–31
Message center, 4–21
Message-waiting receiver, 4–35
Messaging 2000, 2–30, 2–31
Microphone operation, 4–6
MLX telephones
and Delay Announcement Devices, 2–25
as programming equipment (MLX-20L telephone), 2–7
assigning trunks, 3–50
button assignments in Hybrid/PBX mode, 3–57
button assignments in Key and Behind Switch mode, 3–57
Extension Copy feature, 4–11
jacks, 2–25
language, 2–9
MFM adjuncts, 4–3
microphone operation, 4–6
modules, 2–14
Multi-Function Module (MFM) adjuncts, 3–50
optional features, 4–2
Modem, 5–3
Modem Data Stations, 5–3
Modem data-only stations, 5–9
Modem/ISDN Terminal Adapter Pool, 5–4
Modes of operation, 2–8
Modifications to system
overview, 6–1
preparation, 6–2
Modules
adding to the system, 6–2
line/trunk jack types and , 3–2
placement in control unit, 2–1
touch-tone receivers (TTRs), 2–16
types, 2–1
Multi-Function Module (MFM)
adjuncts, 3–50
assigning buttons, 3–52, 3–56
Behind Switch mode and , 2–25
extension number, 2–25
MLX telephone, 2–27
MLX telephones, 3–50
MultiQuest, 3–3, D–1
Music On Hold , 3–9

N
Netware, 2–26
Network selection table, 3–36
NI-1 BRI, 5–29
connectivity, 3–44
Night Service
Emergency Allowed List, 4–55
Exclusion List, 4–55
group assignment, 4–54
outward restriction, 4–55
time set, 4–56

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Index

Page IN-11
Night Service Coverage Control, 4–56
Numbering line/trunk jacks, 3–2
Numbering plans, 2–33
Numbering the system, 2–13

O
One-Touch Call Handling , 4–42
Operation
modes, 2–8
Operator features, 4–18
Operator hold timer, 4–18, 4–23
Operator positions, 2–22
Outmode signaling , 3–13
OUTWATS, D–1
Overflow
Prompt-based , 4–40
threshold , 4–36
time threshold , 4–40
Overflow coverage, 4–36

P
Page buttons, 4–25
Park return time, 4–43
Park zones, 4–25
PassageWay Telephony Services for NetWare, 2–28
PassageWay Telephony Services for Netware, 2–26
PC with System Programming and Maintenance (SPM), 2–7
PCMCIA card , 2–11
Permanent Key mode, 2–8
Personal Line, 5–31
Personal Lines, 5–35
Personal lines, 4–7
Personal Speed Dial, 5–36
Personal Video Conferencing , 5–16
Pickup groups, 4–27
Planning forms, B–1
Pool, 5–31
Pool dial-out code, 3–17, 4–4
Pools, 3–16
Automatic Route Selection (ARS), 4–59, 4–70
Posted Messages, 4–57
Power Failure Transfer (PFT) telephones
jacks, 2–6
module placement, 2–6
Primary Cover Ring Delay, 4–14
Primary operator position, 2–21, 2–22
Primary Rate Interface (PRI), 3–3
B-channel groups, 3–33
Call-by-Call Service Selection, 3–36
clock synchronization, 3–32
Dial Plan Routing , 3–33
framing format, 3–31
incoming services, 3–33

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Index

Page IN-12
Primary Rate Interface (PRI), (continued)
line appearance routing , 3–33
line coding , 3–31
line compensation, 3–32
network selection table, 3–33, 3–36
number to send , 3–37
options, 3–33
outgoing services, 3–33
outgoing tables, 3–34
overview, 3–30
review by Lucent, 3–38
signaling mode, 3–31
Special Services Selection Table, 3–36
Terminal Equipment Identifier (TEI), 3–38
test telephone number, 3–38
timers and counters, 3–38
type of service, 3–30
Principal user, 4–7
Privacy, 5–36
Programming
centralized , 4–2
equipment, 2–7
Extension Copy feature, 4–11
system, 4–2
Prompt-Based Overflow setting , 2–18

Q
Queue over threshold , 4–20
Queued Call Console (QCC)
additional operator positions, 2–22
adjuncts, 4–4
call types, 4–24
Direct Station Selector (DSS), 4–19
features, 4–4, 4–19
identification information, 4–4
Message Center, 4–21
MFM adjunct features, 4–4
operator to receive calls, 3–15
optional features, 4–4
Position-Busy Backup , 4–23
primary operator position, 2–21
queue priority, 3–16, 4–20, 4–31
Voice Announce, 4–24

R
Release 1.0,
Release 1.1,
Release 2.0,
Release 3.1,
Release 4.0,
Release 4.1,
Release 4.2,
Release 5.0,

3–23
3–23
3–23
xxxv
xxxii
xxx, 3–23
xxvii, 3–23
xxii

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Index

Page IN-13
Release 6.0, xvii
Release 6.1, xiii
Remote Access
barrier codes, 3–18
dial-in tie trunks, 3–18
Direct Inward Dial (DID) trunks, 3–18, 3–42
modifying , 6–3
overview, 3–18
Private network tandem trunks, 3–18
shared access, 3–18
slow dial tone and , 3–49
Remote access
Direct Inward Dial (DID) trunks, 3–19
Remote Call Forward , 3–49, 4–7
forward delay option, 4–7
Renumbering
2-digit numbering plan, 2–34
3-digit numbering plan, 2–35
AUDIX Voice Power, 2–33
overview, 2–33
Set Up Space numbering plan, 2–35
Requirements
CTI Applications, 1–6
Return ring , 4–22
Ringing frequency
016 module, 2–30, 2–32

S
Sales and Design Support Center (SDSC), 3–38
Secondary Cover Ring Delay, 4–14
Secondary Dial Tone Timer, 2–12
Service Observing , 4–16
Service Profile Identifier (SPID)
planning considerations, 3–45
planning form instructions, 3–45
Set Up Space numbering plan, 2–35
Shared Access for Switched Services (SASS), 3–3
Signaling
Direct Inward Dial (DID) trunks, 3–43
Primary Rate Interface (PRI), 3–31
tie trunks, 3–39
Signaling mode
T1 service, 3–25
Simultaneous voice and data, 2–24
Slow dial tone, 3–49
Software Defined Network (SDN), 3–3
Speakerphone, 2–27
Special Services Table, 3–36
Specifications, environmental
CTI, 1–9
Speed Dial
marked system, 4–58
marked system and star codes, 2–12, 4–58
system, 4–58
Speed dial
marked system and star codes, 2–12

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Index

Page IN-14
Station Message Detail Recording (SMDR)
language, 2–9, 2–10
options, 4–45
Subpatterns, 4–66
Supplemental Alert Adapter (SAA), 2–26
Switchhook flash, 3–3
System
adding to, 6–2
adjuncts, 3–9, 3–10
consoles, 2–7, 2–11
date, 2–10
extension capacity, 2–3
lines/trunks capacity, 2–2
modifications, 6–2
operating conditions, 2–7, 2–24, 2–25
programming , 4–2
time, 2–10
System Access Ring , 5–31
System features
Automatic Callback interval, 4–44
Camp-On return time, 4–43
one-touch call handling , 4–42
overview, 4–41
Park return time, 4–43
transfer audible, 4–43
transfer options, 4–42, 4–43
System numbering
adjuncts, 2–26
extension jacks, 2–14
line/trunk jacks, 3–2
overview, 2–13
plans, 2–33
renumbering , 2–33
System planning form, B–1
System Programming and Maintenance (SPM)
console, 2–7
software, 2–7
System Programming and Maintenance (SPM) software
versions, 7–3, 7–4
System Speed Dial, 4–58, 5–36
labels, 4–58

T
T1 service
channel service unit (CSU), 3–27
clock synchronization, 3–26
common services, 3–3
digital data transmission, 3–24
DS1 connectivity, 6–3
framing format, 3–25
line coding , 3–25
line compensation, 3–25
overview, 3–24
signaling mode, 3–25
T1/PRI review, 3–38
type of service, 3–25

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Index

Page IN-15
T1 Switched 56 service, 3–3, 3–24
clock synchronization, 3–26
dial plan routing , 3–29
direction, 3–28
framing format, 3–25
incoming signaling mode, 3–28
incoming signaling type, 3–29
line appearance routing , 3–29
line coding , 3–25
line compensation, 3–25
outgoing signaling mode, 3–28
outgoing signaling type, 3–29
overview, 3–28
signaling mode, 3–25
type of service, 3–25
TAPI, GL–26
Telephone buttons
assigning , 3–52
Direct-Line Console (DLC), 3–62
Hybrid/PBX mode, 3–52
Key and Behind Switch mode, 3–57
Terminal adapters, 2–25, 2–26
Terminal Equipment Identifier (TEI), 3–38
Test telephone number, 3–33, 3–38
Tie trunks, 3–39, 5–28
barrier codes, 3–19
dial tone, 3–41
options, 3–39
overview, 3–39
remote access and , 3–21
signaling , 3–39
slow dial tone and , 3–49
Time, 2–10
Timers
planning considerations, 3–48
planning form instructions, 3–48
secondary dial tone, 2–12
Timers and counters, 3–38
Tip/ring (T/R) equipment, 6–3
assigning trunks, 3–50
Delay Announcement Devices, 2–30
features, 4–3
jacks, 2–30
MLX telephones, 2–26
optional features, 4–3
Toll abuse, 3–42
Toll type, 3–13
Touch-tone receivers (TTRs)
calculating number required , 2–20
modules with, 2–16
required by prompt-based overflow, 2–18
required by voice mail/auto attendant, 2–17
system requirements, 2–16
voice messaging system requirement, 2–16
Transfer audible, 4–43
Trunk-to-trunk transfer, 3–12, 4–9
TSAPI, GL–27

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112

Issue 1
August 1998

Index

Page IN-16

U
Unit load rules, F–2
Unit load worksheet, F–3
Unit loads
Key or Behind Switch Mode, F–2

V
Video endpoints, 2–3
Video System, 5–4
Virtual Private Network, D–1
Voice Announce to Busy, 2–24, 6–3
Voice Mail, Centralized , 2–32
Voice mail/auto attendant
fails to transfer calls, 2–16
touch-tone receivers (TTRs) required , 2–17
Voice Messaging System
functions, 3–10
services, 3–10
Voice messaging systems, 2–16

W
Windows NT, 2–26



File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.4
Linearized                      : No
Page Count                      : 588
Page Mode                       : UseOutlines
Page Layout                     : SinglePage
Producer                        : 
Keywords                        : 
Mod Date                        : 2002:01:09 08:32:03-06:00
Author                          : EZ Manuals
Creation Date                   : 0-01-01T00:00:00Z
Subject                         : 
Modify Date                     : 2002:01:09 08:32:03-06:00
Create Date                     : 0-01-01T00:00:00Z
Metadata Date                   : 2002:01:09 08:32:03-06:00
Title                           : 
Creator                         : EZ Manuals
Description                     :