Lucent Technologies MERLIN LEGEND Release 6.1 Technical manual

555-661-112
Comcode 108289489
Issue 1
August 1998
MERLIN LEGEND®
Communications System
Release 6.1
System Planning

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 unau-
thorized 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
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.”
Call: BCS Publications Center
Voice 1 800 457-1235 International Voice 317-322-6791
Fax [phone] International Fax [phone]
Write: BCS Publications Center
2855 North Franklin Road
Indianapolis, IN 46219-1385
Order: Document No. 555-661-110
Comcode: 108289000
Issue 1, August 1998

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112
Issue 1
August 1998
Contents
Page iii
Contents
New Features and Enhancements xiii
■Release 6.1 Enhancements (August, 1998) xiii
Prior Releases: Features and Enhancements 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 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
1Before 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
2Control Unit Configuration 2–1
■Planning Module Placement 2–2
■Recording System Operating Conditions 2–7
■Numbering the System 2–13
3Lines/Trunks 3–1
■Identifying Line/Trunk Jacks 3–2
■Selecting Line/Trunk Options 3–11
■Assigning Lines/Trunks 3–50
■Assigning Telephone Buttons 3–52
4Features 4–1
■Telephone and Extension Features 4–2
■Operator Features 4–18
■Group-Assigned Features 4–26
■System Features 4–41
5Data Communications 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
6Modifications 6–1
■Preparation 6–2
■Adding to the System 6–2
7Upgrading 7–1
■Upgrading to Release 6.17–2
■Release 6.1 Forms 7–5
ACustomer 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
BSystem 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
DT1/PRI Planner D–1
EDS1 Connectivity Ordering E–1
FUnit Load Calculation F–1
■Unit Load Rules F–2
■Calculating Unit Loads F–2
■Unit Load Worksheet F–3
GNI-1 BRI Review G–1
HNI-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
INetwork 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
Figures 0
1 Before You Begin
1–1 System Configuration for Support of CTI Applications 1–7
1–2 Sample Floor Plan 1–14
2 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
3 Lines/Trunks
3–1 Partially Completed System Form 2c 3–8
3–2 Factory-Set Assignment, MLX Telephones
(Hybrid/PBX Mode) 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
4 Features
4–1 Completed ARS Worksheet Automatic Route
Selection Tables 4–62
4–2 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 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
D 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
Tabl es 0
1 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
2 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
3 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
4 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 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
6 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
7 Upgrading
7–1 Programming Compatibility 7–3
7–2 Planning Forms 7–5
B System Forms
B–1 System Forms B–1
C Data Forms
C–1 Data Forms C–1
E DS1 Connectivity Ordering
E–1 Guide to DS1 Connectivity Ordering E–1
I 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
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.
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.

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

New Features and Enhancements
Page xiiiRelease 6.1 Enhancements (August, 1998)
MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112 Issue 1 August 1998
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

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112 Issue 1 August 1998
New Features and Enhancements
Page xivRelease 6.1 Enhancements (August, 1998)
Centralized Voice Messaging 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.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112 Issue 1 August 1998
New Features and Enhancements
Page xvRelease 6.1 Enhancements (August, 1998)
■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.
SMDR 0
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.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112 Issue 1 August 1998
New Features and Enhancements
Page xviRelease 6.1 Enhancements (August, 1998)
PRI Switch Type Test 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.

Prior Releases: Features and Enhancements
Page xviiRelease 6.0 Enhancements (February, 1998)
MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112 Issue 1 August 1998
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 Issue 1 August 1998
Prior Releases: Features and Enhancements
Page xviiiRelease 6.0 Enhancements (February, 1998)
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.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112 Issue 1 August 1998
Prior Releases: Features and Enhancements
Page xixRelease 6.0 Enhancements (February, 1998)
■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.
Queue Control 0
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.

MERLIN LEGENDCommunications System Release 6.1
System Planning 555-661-112 Issue 1 August 1998
Prior Releases: Features and Enhancements
Page xxRelease 6.0 Enhancements (February, 1998)
Prompt-Based Overflow 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 a ll
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.