Lucent Technologies MERLIN LEGEND User Manual

Download

MERLIN LEGEND

Communications System Release 6.1

System Planning

555-661-112 Comcode 108289489 Issue 1 August 1998

Notice

Every effort was made to ensur e th at the info rm ation in this book was complete and accurate at the time of printin g. How ever, information is

subject to change. See App end ix A, “Customer Support Information,” for important i nformation.

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 subs tantial additional charges for you r tele com m unications 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 th at ca n int roduce 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 inform ation regarding your system and toll fraud, see Appendix A, “Custome r 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 rea sonable protection agai nst ha rmful interference when the equipment is opera te d in a commercial envir onm ent. This equipment generates, use s , and can radiate radio frequency energy and, if not instal led and used in accordance with the instruction manual, may cause harmful interference t o radio communications. Operation of this equipment in a resid ent ial area is likely to cause harmful i n terference, in which case the user will be required to correct the interference at his own expense. For further FCC information, see Ap pe ndix A, “Customer Support Information.”

Canadian Department of Communications (DOC) Interference Information

This digital apparatus does no t ex ce ed the Class A limits for radio noise emissions set out i n the radio interference regulati ons of t he Canadian Department of Communications. Le Présent Appareil Numériqu e n’ émet pas de bruits radioélectriques dépassant les limites applicables aux appareil s num é riq ues de la classe A préscrites dans le règlement sur le brouillage radioélectrique édicté par le ministère des C om munications du Canada.

Trademarks

5ESS, AUDIX, DEFINITY, HackerTracker, CONVERSANT, Lucent Technologies Attendant, Fax Attendant System , MERLIN, ME RL IN LEGEND, MERLIN MAIL, MERL IN PF C, MLX-10, MLX-10D, MLX-10DP, MLX-16DP, MLX-20L, MLX-28D, Passa ge Way, PARTNER, and Voice Power are registere d tr ademarks and 4ESS, Intuity, Luc en t Te c hnologies, MLX-5, MLX-5D, and E xpressRoute 1000 are trademarks of Lucent Technologies in the U S a nd other countries. NetPROT ECT is a service mark of Lucent Te chnologies in the US and other co untries. Supra, StarSet, and Mirage are registered tradema rks of P lantronics, Inc. MEGACOM, ACCUNET, AT&T, Magic on Hold, and MultiQuest are registered trademarks of AT&T.

Pipeline is a tradem ark 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 regis tered trademark and DMS a trad emark of Northern Te lecom. 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

Write: BCS Publications Center

Order: Document No. 555-661-110

For more information abou t L uce nt Technologies docu m ent s, refe r to t he sect io n entitled ‘‘Related Docum ents’’ on page xlix

Support Telephone Number

In the continental US, Lucent Technologies provi des a tol l-f ree customer helpline 24 hours a da y. Call the Lucent Technologi es Helpline at 1 800 628-2888 or your Luce nt Te chnologies authorized dealer if you need assistance when install in g, programming, or using your system. Consultation charges may apply. Outside the conti nental US, contact your loc al Lucent Technologies a uth orized representative .

Lucent Technolo gies Fraud Intervent io n

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 cer tified to be Year 2000 comp liant. Additional inf ormation on this certif ication, and other issues regarding Year 2000 compliance, is available online at http://www.lucent.com/enterprise/sig/yr2000.

Warranty

Lucent Technologie s provides a limited warranty on this product. Refer to “Lim it ed Wa rranty and Limitation of Li ability” in Appendix A, “Customer Support Information. ”

Fax 1 800 457-1764 International Fax 317-322-6699

2855 North Franklin Road Indianapolis, IN 46219- 1385

Comcode: 108289000 Issue 1, August 1998

MERLIN LEGENDCommunications System Release 6.1 System Planning

555-661-112

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

Issue 1

August 1998

Page iii

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

1 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

August 1998

Contents

2 Control Unit Configuration 2–1

■ Planning Module Plac eme nt 2–2

■ Recording System Oper ati ng Cond iti ons 2–7

■ Numbering the System 2–13

3 Lines/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

Issue 1

Page iv

4 Features 4–1

■ Telephone and Extension Features 4–2

■ Operator Features 4–18

■ Group-Assigned Features 4–26

■ System Features 4–41

5 Data 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

August 1998

Contents

6 Modifications 6–1

■ Preparation 6–2

■ Adding to the System 6–2

7 Upgrading 7–1

■ Upgrading to Release 6.1 7–2

■ Release 6.1 Forms 7–5

A 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

Issue 1

Page v

B System Forms B–1

C Data Forms C–1

MERLIN LEGENDCommunications System Release 6.1 System Planning

Contents

555-661-112

August 1998

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

Issue 1

Page vi

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

Figures

555-661-112

Issue 1

August 1998

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

Figures

555-661-112

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

Issue 1

August 1998

Page viii

MERLIN LEGENDCommunications System Release 6.1 System Planning

Tables

555-661-112

Issue 1

August 1998

Page ix

Ta bl e s 0

1 Before You Begin

1–1 Environmental Requir em ents 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 Syst em Requirements for Touc h-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

Tables

555-661-112

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

Issue 1

August 1998

Page x

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

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 inst ru cti on s.

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

Issue 1

August 1998

Page xi

■ 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 wal l out lets, as th is c an resu lt in the risk of fire o r elec tr ical

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

■ 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.

Issue 1

August 1998

Page xii

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

MERLIN LEGENDCommunications System Release 6.1 System Planning

New Features and Enhancements

555-661-112

New Features and Enhancements

Release 6.1 Enhancements (August, 1998) 0

Issue 1

August 1998

Page xiiiRelease 6.1 Enhancements (August,1998)

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

New Features and Enhancements

555-661-112

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

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.

for detailed information about Centralized Voice

Issue 1

August 1998

Page xivRelease 6.1 Enhancements (August, 1998)

■ 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 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 group. See the

Network Reference

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.

single

non-local member that is defined by the Uniform

for details.

only

member in the calling

■ 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

New Features and Enhancements

555-661-112

■ 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

Issue 1

August 1998

Page xvRelease 6.1 Enhancements (August, 1998)

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

New Features and Enhancements

555-661-112

PRI Switch Type Test 0

A new maintenance test, the PRI Switch Type Test, has been created to allow Lucent T echnologies 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.

Issue 1

August 1998

Page xviRelease 6.1 Enhancements (August, 1998)

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Prior Releases: Features and Enhancements

555-661-112

Prior Releases: Features and Enhancements

Release 6.0 Enhancements (February, 1998) 0

Issue 1

August 1998

Page xviiRelease 6.0 Enhancements (February,1998)

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 Communications Server (ECS) and ProLogix 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

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,

tandem trunks

to connect networked systems.

™

Enterprise

Communications Systems in

MERLIN LEGENDCommunications System Release 6.1 System Planning

Prior Releases: Features and Enhancements

555-661-112

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. Pri vat e net wor ked tr un ks may al low yo u to real iz e si gnifi cant

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.

Issue 1

August 1998

Page xviiiRelease 6.0 Enhancements (February, 1998)

— 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

Prior Releases: Features and Enhancements

555-661-112

■ 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.

Issue 1

August 1998

Page xixRelease 6.0 Enhancements (February, 1998)

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

Prior Releases: Features and Enhancements

555-661-112

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

Issue 1

August 1998

Page xxRelease 6.0 Enhancements (February, 1998)

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

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 and a Pause character may be required after the

 instead of a dial-out code,

. The Centrex service provider

determines whether the Pause is needed.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Prior Releases: Features and Enhancements

555-661-112

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

Page xxiRelease 6.0 Enhancements (February, 1998)

MERLIN LEGENDCommunications System Release 6.1 System Planning

Prior Releases: Features and Enhancements

555-661-112

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

Issue 1

August 1998

Page xxiiRelease 5.0 Enhancements (June, 1997)

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 T echnologies-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 vi ntag e firmwar e is suppo r ted.

Basic Call Control 0

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Prior Releases: Features and Enhancements

555-661-112

Screen Pop 0

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

Issue 1

August 1998

Page xxiiiRelease 5.0 Enhancements (June, 1997)

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Prior Releases: Features and Enhancements

555-661-112

HotLine Feature 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 extens i on, the tele pho ne auto mati c all y dia ls 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.

Issue 1

August 1998

Page xxivRelease 5.0 Enhancements (June, 1997)

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Prior Releases: Features and Enhancements

555-661-112

Most Idle Hunt Type 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.

Issue 1

August 1998

Page xxvRelease 5.0 Enhancements (June, 1997)

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Prior Releases: Features and Enhancements

555-661-112

Enhanced Calls-in-Queue Alarm Thresholds 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.

Issue 1

August 1998

Page xxviRelease 5.0 Enhancements (June,1997)

■ 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

Prior Releases: Features and Enhancements

555-661-112

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 services):

■ NORTEL

■ 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:

switch types that carry for AT&T Switched Network

DMS™-100 BCS 36 for local exchange carrier services

Issue 1

August 1998

Page xxviiRelease 4.2 Enhancements (June, 1997)

■ 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 OUTWAT S (Outwar d Wi de 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)

MERLIN LEGENDCommunications System Release 6.1 System Planning

Prior Releases: Features and Enhancements

555-661-112

Improvements to Station Message Detail Recording (SMDR) and Support for MERLIN LEGEND Reporter Application 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 Fiel d. 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.

Issue 1

August 1998

Page xxviiiRelease 4.2 Enhancements (June, 1997)

■ 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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Prior Releases: Features and Enhancements

555-661-112

MERLIN LEGEND Reporter 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

Issue 1

August 1998

Page xxixRelease 4.2 Enhancements (June, 1997)

■ 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 i s 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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Prior Releases: Features and Enhancements

555-661-112

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.

Issue 1

August 1998

Page xxxRelease 4.1 Enhancements (June, 1997)

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Prior Releases: Features and Enhancements

555-661-112

Forward on Busy 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 (Natio nal 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

Page xxxiRelease 4.1 Enhancements (June, 1997)

MERLIN LEGENDCommunications System Release 6.1 System Planning

Prior Releases: Features and Enhancements

555-661-112

Release 4.0 Enhancements (March, 1996) 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 ( 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.

bearer channels

Issue 1

August 1998

Page xxxiiRelease 4.0 Enhancements (March, 1996)

) on a BRI line can carry one

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Prior Releases: Features and Enhancements

555-661-112

Support for 2B Data Applications 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 Communications System or DEFINITY Enterprise Communications Server. The two communications systems can be co-located or at different sites.

G1.1

Issue 1

August 1998

Page xxxiiiRelease 4.0 Enhancements (March, 1996)

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Prior Releases: Features and Enhancements

555-661-112

Time-Based Option for Overflow on Calling Group 0

Issue 1

August 1998

Page xxxivRelease 4.0 Enhancements (March, 1996)

Release 4.0 has added a

number of calls

limit. If the Overflow Threshold Time option is set to a valid

time

limit for calls in queue in addition to the previous

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Prior Releases: Features and Enhancements

555-661-112

Release 3.1 Enhancements (March, 1996) 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.

Issue 1

August 1998

Page xxxvRelease 3.1 Enhancements (March, 1996)

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 messagi ng systems. The system manager ca n manual ly assign this list to other extensions.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Prior Releases: Features and Enhancements

555-661-112

Default Pool Dial-Out Code Restriction for All Extensions 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

Issue 1

August 1998

Page xxxviRelease 3.1 Enhancements (March, 1996)

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 low er in ord er t o rest rict callin g. No ad just ment t o the r oute F RL 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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

About This Book

555-661-112

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.

Issue 1

August 1998

Page xxxviiIntended Audience

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

About This Book

555-661-112

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

Page xxxviiiHow to Use This Book

MERLIN LEGENDCommunications System Release 6.1 System Planning

About This Book

555-661-112

Terms and Conventions Used 0

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

Lines, Trunks, and Facilities 0

Issue 1

August 1998

Page xxxixTerms and Conventions Used

Facility

telephone system and the telephone company central office. Technically, a connects a switch to a switch, for example, the MERLIN LEGEND Communications System to the central office. Technically, a 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 interchangeably. In this guide, we use facilities in general. Specifically, we refer to terms such as 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 line/trunk module trunk jack line/trunk jack station extension station jack extension jack analog data station modem data workstation 7500B data station ISDN terminal adapter data workstation analog voice and data station analog voice and modem data

digital voice and analog data station MLX voice and modem data workstation analog data-only station modem data-only workstation 7500B data-only station ISDN terminal adapter data-only

MLX voice and 7500B data station MLX voice and ISDN terminal adapter

is a general term that designates a communications path between a

line

is a loop-start

line

and

trunk

are often applied

lines/trunks

personal line, ground-start trunk, DID trunk

workstation

workstation data workst ation

and

line/trunk

digital facilities

to refer to

. We also use specific

, and so on. When you

trunk

MERLIN LEGENDCommunications System Release 6.1 System Planning

About This Book

555-661-112

Typographical Conventions 0

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

Example Purpose

very

It is steps. You before touching the connection.

The part of the headset that fits over one or both ears is called a

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.

Choose ([W3URJfrom the display screen.

To activate Call Waiting, dial

important that you follow these

must

attach the wristband

headpiece.

 Constant-width type in italics indicates

Italics indicate emphasis.

Italics also set off special terms.

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

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

characters you dial at the telephone or type at the PC.

Issue 1

August 1998

Page xlTerms and Conventions Used

Product Safety Advisories 0

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

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.

CAUTION

WARNING

MERLIN LEGENDCommunications System Release 6.1 System Planning

About This Book

555-661-112

Security 0

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

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.”

SECURITY ALERT

Issue 1

August 1998

Page xliSecurity

MERLIN LEGENDCommunications System Release 6.1 System Planning

About This Book

555-661-112

Page xliiRelated Documents

System

System Manager’s Guide, Feature

MERLIN LEGENDCommunications System Release 6.1 System Planning

About This Book

555-661-112

How to Comment on This Book 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 Manage r Lucent Techn ol ogi es 211 Mount Airy Road, Room 2W226 Basking Ridge, NJ 07920

Issue 1

August 1998

Page xliiiHow to Comment on This Book

MERLIN LEGENDCommunications System Release 6.1 System Planning

About This Book

555-661-112

Issue 1

August 1998

Page xlivHow to Comment on This Book

MERLIN LEGENDCommunications System Release 6.1 System Planning

Before You Begin

555-661-112

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

Issue 1

August 1998

Page 1-1Reviewing System Components

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Before You Begin

555-661-112

Confirming the Location of the Control Unit 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 requi remen t s 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)

Issue 1

August 1998

Page 1-2Confirming the Location of the Control Unit

Heat Dissipation

Power Basic carrier: 117 VAC 60 Hz ± 5% 160 W 5.4 amps

Temperature 40° through 104°F; 4° through 40°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

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)

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.

(optimal temperature 60°F; 16°C)

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

Before You Begin

555-661-112

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

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

Issue 1

August 1998

Page 1-3Confirming the Location of the Control Unit

. A newly designed pre-drille d,

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Before You Begin

555-661-112

Grounding Requirements 1

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

■ Lightning

■ Power su rges

■ 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:

Issue 1

August 1998

Page 1-4Confirming the Location of the Control Unit

■

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

MERLIN LEGENDCommunications System Release 6.1 System Planning

Before You Begin

555-661-112

Electrical Noise/Radio-Frequency Interference 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).

Issue 1

August 1998

Page 1-5Confirming the Location of the Control Unit

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Before You Begin

555-661-112

Requirements for Supporting CTI Applications 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. 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.

Issue 1

August 1998

Page 1-6Requirements for Supporting CTI Applications

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

■ The A.E. should contact the SDSC (1 888 297-4700 select the

appropriat e promp ts to re ach th e MERLI N LEGEND split ) to disc uss 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.

3. 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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Before You Begin

555-661-112

4. 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.

5. 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

MERLIN LEGEND Release 5.0 or later

Telephony Server

LAN

August 1998

Client Desktop

Issue 1

Page 1-7Requirements for Supporting CTI Applications

CTI Link

Public

Network

Figure 1–1. System Configuration for Support of CTI Applications

MERLIN LEGENDCommunications System Release 6.1 System Planning

Before You Begin

555-661-112

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

■ One of the following configurati ons :

— Novell NetWare

Network Manager’s Guide

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

Issue 1

August 1998

Page 1-8Requirements for Supporting CTI Applications

form more information.

■ 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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Before You Begin

555-661-112

■ 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

Page 1-9Requirements for Supporting CTI Applications

MERLIN LEGENDCommunications System Release 6.1 System Planning

Before You Begin

555-661-112

Obtaining Telephone Company Information 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

Issue 1

August 1998

Page 1-10Obtaining Telephone Company Information

■ 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

MERLIN LEGENDCommunications System Release 6.1 System Planning

Before You Begin

555-661-112

Obtaining User Information 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?

Issue 1

August 1998

Page 1-11Obtaining User Information

■ 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

Before You Begin

555-661-112

Table 1–3. Employee Communications Survey: Description of Questions

Required Information Description

Issue 1

August 1998

Page 1-12Obtaining User Information

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

2. Calls covered by someone else (sender)

3. Shares lines/telephone numbers

4. Covers someone else’s

calls (receiver)

5. Shares incoming calls

6. Frequency of use

7. Data needs

8. Use of account codes

9. Frequently dialed numbers

10. Picks up calls

11. View incoming caller information

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.

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.

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

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

Identifies calling group needs. Identifies heavy and light telepho ne us ers. Heav y users

may benefit from additional System Access buttons and/or an additional System Access Originate Only button.

Identifies existing and potential data terminal and personal computer users.

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).

Identifies useful numbers for the System Speed Dial list. Identifies need for a Pickup group. 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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Before You Begin

555-661-112

Obtaining a Floor Plan 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

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 at 10-button MLX telephones, telephones,

BIS-34 at 34-button analog multiline telephones, and so on.

MLX-20L at 20-button MLX display

Issue 1

August 1998

Page 1-13Obtaining a Floor Plan

and the

MLX-10

4. Indicate the type of adjunct at each location. For example, write

ana. modem

the symbol.

5. Indicate any additional equipment, such as a Stati on Mes s age Deta il 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 Sele ctors (D SSs), or an I nteg rated S ervic es Dig ital Ne twork ( 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.

(analog modem), headset, or other type of adjunct beneath

FA X,

MERLIN LEGENDCommunications System Release 6.1 System Planning

Before You Begin

555-661-112

HORN

PLANT AREA

PRESIDENT'S

OFFICE

Issue 1

August 1998

Page 1-14Obtaining a Floor Plan

WAREHOUSE

SUPPLY

ROOM

PLANT MANAGER'S

OFFICE

ANS. MACH.

SALES

DEPARTMENT

ANS. MACH.

DRAFTING

DEPARTMENT

SHIPPING & RECEIVING

FAX

CONFERENCE

ROOM

PRESIDENT'S

SECRETARY

FAX

PRESIDENT'S

VICE

PRESIDENT'S

SECRETARY

VICE

OFFICE

RECEPTION

ACCOUNTING DEPARTMENT

FAX

DSS

MLX Telephone

Analog Multiline Telephone

Figure 1–2. Sample Floor Plan

Single-line Telephone

Operator Position

Computer or Data Terminal

Adjunct

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

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:

Issue 1

August 1998

Page 2-1

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Planning Module Placement 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.

Issue 1

August 1998

Page 2-2Planning Module Plac ement

Forms Needed 2

■ 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 2

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Capacity for Extensions 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.

Issue 1

August 1998

Page 2-3Planning Module Plac ement

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 2

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).

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

5. 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:

Issue 1

August 1998

Page 2-4Planning Module Plac ement

■ 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 2

NOTE:NOTE: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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

1. 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.

Issue 1

August 1998

Page 2-5Planning Module Plac ement

— 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 plu s 100D modu le s in a single carr i er 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

Network Reference

the

for additional information.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

2. For each line/trunk and extension jack of each module, write the type of

X = extension; and L/T = line/trunk) and the associated logical ID,

jack ( 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 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.

Issue 1

August 1998

Page 2-6Planning Module Plac ement

PFT in the modules. A PF T

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

800

408 GS/LS

Power Supply

Ring Generator

OO8 MLX

L/T4

L/T8

L/T3

L/T7

L/T2

L/T6

L/T1

L/T5

X16

X24 X7 X6 X5 X4 X3 X2

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17

BASIC CARRIER

X32

X15

X23

X14

X22

X30

X13

X21

X29

X12

X20

X28

X11

X19

X27

X10

X18

X26

X17

X25

Power Supply

L/T12

L/T11

L/T10

L/T9

X31

400 GS/LS/TTR

OO8 MLX

408

012

L/T16 L/T15 L/T14 L/T13

X44 X43 X42

X41

X40

X52

X39

X51

X38

X50

X37

X49

X36

X48

X35

Ring Generator

X47

X34

X46

X33

X45

EXPANSION CARRIER

L/T24 L/T23 L/T22

L/T21

L/T20

L/T19 L/T18 L/T17

L/T32 L/T31

L/T30

L/T29 L/T28 L/T27 L/T26 L/T25

Power Supply

Ring Generator

EXPANSION CARRIER

Figure 2–1. Sample Control Unit Diagram

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Recording System Operating Conditions 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

Forms Needed 2

Issue 1

August 1998

Page 2-7Recording System Operating Conditions

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 2

1. Under the Programming Equipment heading in the System Operating Conditions section on Form 1 (page 2), do

■ 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.

one

of the following:

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Issue 1

August 1998

Page 2-8Recording System Operating Conditions

2. 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.”

3. 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.

System Mode 2

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 2

Under the System Mode heading in the System Operating Conditions section of

one

Form 1 (page 2), check

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Language Selection 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.

Issue 1

August 1998

Page 2-9Recording System Operating Conditions

NOTE:NOTE: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: 2

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

one

1. To select a systemwide language, check factory setting), French, or Spanish.

2. To set a different language for SMDR, check (the factory setting), French, or Spanish.

3. To set a different language for printed reports, check English (the factory sett ing), French, or Spanish.

of the following: English (the

one

of the following: English

one

of the following:

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Automatic Maintenance Busy 2

The factory setting for Automatic Maintenance Busy is Disable, which means that

not

faulty lines/trunks are

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

Planning Form Instructions 2

Under the Automatic Maintenance Busy heading in the System Operating Conditions section of Form 1, page 2, do

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

■ To enable Automatic Maintenance Busy, check Enable.

one

Issue 1

August 1998

Page 2-10Recording System Operating Conditions

of the following:

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 2

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

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Backup 2

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:NOTE: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.

Planning Form Instructions 2

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.

Issue 1

August 1998

Page 2-11Recording System Operating Conditions

System Consoles 2

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

Planning Form Instructions 2

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).

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Second Dial Tone Timer 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 st ar codes, th en th e ap prop ria te n umb er of pa uses (eac h 1. 5 se cond s) must be programmed in the entry following each star code.

Issue 1

August 1998

Page 2-12Recording System Operating Conditions

Planning Form Instructions 2

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.

Applications 2

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 2

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Numbering the System 2

This section describes the assignment of numbers to extensions.

NOTE:NOTE: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.

Issue 1

August 1998

Page 2-13Numbering the System

■ 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

Referenc e

provides detailed information about system numbering and the three

Feature

numbering plans.

Forms Needed 2

■ Floor plan

■ Equipment List (if available)

■ Form 1, System Planning

■ Form 2a, System Numbering: Extension Jacks

■ Form 2b, System Numbering: Digital Adjuncts

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Identifying Extension Jacks 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 — A dd iti ona l oper ato r posit ion s — 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

Issue 1

August 1998

Page 2-14Numbering the System

Planning Form Instructions 2

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 types and the equipment that can be connected to these jacks.

lists the extension jack

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Table 2–1. Application Ports

Issue 1

August 1998

Page 2-15Numbering the System

Module

008

Ext. Jack Type

Analog 8

No. of Jacks Used to Connect

408 408 GS/LS

008 MLX

Digital 88MLX telephones with or without PassageWay

408 GS/LS-MLX

012 016

Basic Telephone

008 OPT 8

MERLIN

Analog 0

LEGEND Mail

Analog multiline telephones

TransTalk Wireless telephones

Call Management System (CMS)*

Direct Connect Solution

CTI link

†

Desktop video endpoints

Group Video endpoints

and/or

†

Digital data devices, such as an ISDN terminal

†

adapter

1216Tip/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 Cente r Messaging 2000

Intuity™ AUDIX VS

MERLIN MAIL

AUDIX

‡

Tip/ring equipment in another building or off

Voice Power (IS II or III)*

Voice Messaging System*

premises

Off-Premises Range Extender

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 ID s for an 00 8 OP T mo dule, e ven tho ugh only eight wi ll have equipm ent

attached to them. Do not u se a n 00 8 OPT module for applications (such as MERLIN LEG EN D Ma il, 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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Planning Form Instructions 2

Refer to the completed Control Unit Diagram (Form 1) and Table 2–1 above to

mark the extension jack types on Fo rm 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 type of each extension jack next to its logical ID:

August 1998

Page 2-16Numbering the System

one

of the following to indicate the

Issue 1

■ 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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

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

Issue 1

August 1998

Page 2-17Numbering the System

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:NOTE:NOTE:

cannot

A VMS

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

11 21 32 42 63 84

18 8

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

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

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:NOTE: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

Issue 1

August 1998

Page 2-18Numbering the System

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

Control Unit Configuration

555-661-112

Table 2–5. TTRs Required for Primary Delay Announcement Devices

Number of Devices Number of TTRs Required

11 22 33 44 54 65 75

8 or more 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

Issue 1

August 1998

Page 2-19Numbering the System

Number of Devices Number of TTRs Required

11 21 31 42 52 62 73 83 93

10 or more 4

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

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

Issue 1

August 1998

Page 2-20Numbering the System

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-emu lat ed tande m tie tru nks. 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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Jack for Primary Operator Position 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 2

Mark jack assignments on Form 2a:

one

1. Do

of the following:

■ If the system uses a system programming console, proceed to

Step 2.

Issue 1

August 1998

Page 2-21Numbering the System

■ 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.

one

5. Do

of the following:

■ 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.

6. To indicate the primary QCC operator posi tio n:

■ Locate the first extension jack showing a D (digital) jack type and

QCC beside the preprinted logical ID number.

write

■ 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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

7. To indicate the primary DLC operator position:

■ Locate the first extension jack showing a jack type of D (digital) or A

(analog) and write

■ Write the name or location of the primary DLC operator in the

DLC beside the preprinted logical ID number.

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”.

Jacks for Additional Operator Positions 2

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”.

Issue 1

August 1998

Page 2-22Numbering the System

The maximum number of operato r positi on s is shown in Table 2–7

Table 2–7. Maximum Number of Operator Positions

Position Tel e ph on e Maximum

QCC MLX-20L 4 DLC MLX-20L

MLX-28D

DLC Analog multiline

telephones

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 2

NOTE:NOTE:NOTE:

For each CMS connected to the system, you must assign two analog DLC

not

positions. These two DLCs do

need to have the factory setting

extension numbers but do need to be on the same module.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

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.

one

3. Do

of the following:

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

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

4. 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.

Issue 1

August 1998

Page 2-23Numbering the System

5. 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.

6. 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”.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Extension Jack Pairs for Analog Telephones 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.

Issue 1

August 1998

Page 2-24Numbering the System

Planning Form Instructions 2

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

one

(even-numbered logical ID) number of each boxed pair, do 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”.

of the

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Jacks for MLX Telephones 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:NOTE: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.

Issue 1

August 1998

Page 2-25Numbering the System

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 Chapte r 5, “Data Commun ic ations ” .

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

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 2

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. On Form 2a, mark the extension jack assignments for the video stations and the remaining MLX telephones:

Issue 1

August 1998

Page 2-26Numbering the System

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.

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

one

a. Do

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

c. 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. If a digital data or video system is connected to the jack, enter the

extension number in the MLX Telephone Ext. No. column.

3. 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”.

Issue 1

August 1998

Page 2-27Numbering the System

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 butt on pro grammed.

■ 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:NOTE: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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

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

Planning Form Instructions 2

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.”

Issue 1

August 1998

Page 2-28Numbering the System

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.

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

Control Unit Configuration

555-661-112

Issue 1

August 1998

Page 2-29Numbering the System

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

monitored

unmonitored

extension, and the DLC transfers a call to a

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.

unmonitored, non-attendant

If an

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

not

2B data port, do

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 2

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

not

port. If you want to keep a port programmed as a 2B data port, do 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.

assign it as

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

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 Attendant 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.

Issue 1

August 1998

Page 2-30Numbering the System

, AUDIX Voice Power-Integrated

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.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Table 2–8. Application Ports

Application Ports TTRs Telephones

Issue 1

August 1998

Page 2-31Numbering the System

MERLIN LEGEND Mail 2

4 6

Messaging 2000 4

8 12 16

Intuity AUDIX 4

8 10 12

Enhanced Service Cente r (ESC ) 12

CONVERSANT (see Note 3 MERLIN MAIL

Lucent Technologies Atten dant * 1

AUDIX Voice Power* 2

1. No longer orderable.

NA 1 2

2 3

1 4

0 5

0 6

0 2

2 3

1 4

0 5

0 6

0 8

)

3 + 1 for the modem 2

2 + 1 for the modem 1

6 + 1 for programming 1

5 + 1 for programming 2

4 + 1 for programming 2

3 + 1 for programming 1

6 2

4 3

2 4

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 application s 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

Control Unit Configuration

555-661-112

Planning Form Instructions 2

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.

Issue 1

August 1998

Page 2-32Numbering the System

■ 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 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.

port

Proceed to the next section, “Labels”.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Labels 2

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.

Planning Form Instructions 2

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”.

Issue 1

August 1998

Page 2-33Numbering the System

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 informat ion.

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

Control Unit Configuration

555-661-112

For detailed information about the numbering plans (including considerations, constraints, and feature interactions that may affect selection), see the

Reference.

NOTE:NOTE: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 Operator Console (not flexible) 0 1 Extensions 10−19 2 Extensions 20−29 3 Extensions 30−39 4 Extensions 40−49 5 Extensions 50−59 6 Extensions 60−66 Extra

7 Main Pool70MFMs/

Terminal Adapters 710−766

8 800*Trunks 801−880 Park

9 ARS Access (Hybrid/PBX Mode) / Idle Line Access 9

Extensions 6700−6842

6843− 6849

767−

Calling Groups 770–791,7920−7929

769

881−888

Extra MFMs/ Terminal Adapters 6850−6992

Paging Groups 793−799

889

†

Pools 890−899

Issue 1

August 1998

Page 2-34Numbering the System

Feature

6993− 6999

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

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

0 Operator Console (not flexible) 0 1 Extensions 100−199 2 Extensions 200−299 3 MFMs/Terminal Adapters 300–399 4 MFMs/Terminal Adapters 400−499 5 500−599 6 600−699 7 Main Pool

8 800

9 ARS Access (Hybrid/PBX mode)/Idle Line Access

Listed Directory Number (QCC)

†

Remote Access

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

70 71−76

Trunks

801−880

Calling Groups

770−791, 7920−7929

Park

889

881−888

Issue 1

August 1998

Page 2-35Numbering the System

Paging

Groups

793−799

†

Pools

890−899

Figure 2–3. Extension Numbers for 3-Digit Numbering Plan

0 Operator Console (not flexible) 0 1 2 3 4 5 6 7 Main Pool70Extensions

8 800

9 ARS Access (Hybrid/PBX mode)/Idle Line Access 9

Listed Directory Number (QCC).

†

Remote Access

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

7100−−7299

Trunks 801−−880

MFMs/Terminal Adapters 7300−−7499

100−−199 200−−299 300−−399 400−−499 500−−599 600−−699

7500−−7699

Park 881−−888

Calling Group 770−−791, 7920−−7929

†

889

Figure 2–4. Extension Numbers for Set Up Space Numbering Plan

Paging Groups 793−−799

Pools 890−−899

MERLIN LEGENDCommunications System Release 6.1 System Planning

Control Unit Configuration

555-661-112

Planning Form Instructions 2

Use Figure 2–2 through Figure 2–4 as you record extens io n numbe r inf ormati on :

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

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.

one

3. Do

of the following:

Network Reference

Issue 1

August 1998

Page 2-36Numbering the System

■ 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’r e usin g .

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.

Selected Extension Numb ers 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.

Be sure to check

NOTE:NOTE:NOTE:

The remaining columns on Form 2a (Eqpt., Label, Old Ext. No., and Wire No.) are completed by the technici an during installation.

To complete the forms for lines/trunks, proceed to Chapter 3, “Lines/Trunks”.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Lines/Trunks

555-661-112

Planning for lines/trun ks consists of the following tasks:

Issue 1

August 1998

Page 3-1

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:NOTE: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

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.

for information.

MERLIN LEGENDCommunications System Release 6.1 System Planning

Lines/Trunks

555-661-112

Identifying Line/Trunk Jacks 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.

Forms Needed 3

■ Form 1, System Planning

■ Form 2c, System Numbering: Line/Trunk Jacks

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

Issue 1

August 1998

Page 3-2Identifying Line/Trunk Jacks

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

Lines/Trunks

555-661-112

Table 3–1. Line/Trunk Jack Types

Issue 1

August 1998

Page 3-3Identifying Line/Trunk Jacks

Module Type

400 800 408

Line/Trunk Jack Type

Loop-start (LS) 4

Number of Jacks 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 800 GS/LS 408 GS/LS 408 GS/LS-MLX 800 GS/LS-ID

Ground-start/ loop-start (GS/LS)

4 8

Line/Trunk Types: Basic,

Special Purpose (FX, WATS) 4 4 8

Auxiliary Equipment: Music On Hold,

Loudspeaker paging system,

Maintenance Alarm, MERLIN

Identifier

800 DID

DID 8 DID

(Hybrid/PBX) 800 NI-BRI NI-1 BRI 8 (16 channels) NI-1 BRI 400EM Tie 4 Tie 100D DS1 1 (24 channels) T1

T1 Switched 56 Data PRI

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 Megacom 800, Software Defined Network (SDN), and MultiQuest also supports Call-by-Call Service Selection and some ACCUNET

WATS,



. PRI



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

not

service with loop-start lines only. The system does

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).

MERLIN LEGENDCommunications System Release 6.1 System Planning

Lines/Trunks

555-661-112

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

Issue 1

August 1998

Page 3-4Identifying Line/Trunk Jacks

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

Lines/Trunks

555-661-112

Planning Form Instructions 3

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

Issue 1

August 1998

Page 3-5Identifying Line/Trunk Jacks

Table 3–2. Codes for Line/Trunk Jacks

Jack Type Code Line/Trunk Type

LS Loop-start GS/LS Ground-start/loop-start DID DID Tie Tie T1-GS DS1 connectivity used to emulate GS T1-LS DS1 connectivity used to emulate LS T1-Tie

DS1 connectivity used to emulate tie or for digital data service T1-DID DS1 connectivity used to emulate DID T1-S56 DS1 connectivity used for digital data PRI DS1 connectivity used for PRI service BRI NI-1 BRI

1. T1 Switched 56 digi tal data is also availab le using T1 -Tie trunk s. See the “Tie Trunk s”

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, or write

■ If the module will connect services (such as, Megacom and

Megacom 800), write

T1 if the channels are not being used at this time.

PRI for all 24 logical IDs of PRI-type modules.

T1-LS, T1-TIE, or T1-S56),

)

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

MERLIN LEGENDCommunications System Release 6.1 System Planning

Lines/Trunks

555-661-112

Incoming Line/Trunk Type 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:NOTE: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 3

Issue 1

August 1998

Page 3-6Identifying Line/Trunk Jacks

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.

Lucent Technologies MERLIN LEGEND User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

IMPORTANT SAFETY INSTRUCTIONS 0

New Features and Enhancements

Private Networking 0

Centralized Voice Messaging 0

Group Calling Enhancements 0

Transfer Redirect 0

Direct Station Selector 0

Call Forwarding 0

SMDR 0

Decrease in Call Set-Up Time 0

PRI Switch Type Test 0

Service Observing 0

Win SPM

Windows NT Driver 0

Prior Releases: Features and Enhancements

Private Networks 0

Group Calling Enhancements 0

Queue Control 0

Prompt-Based Overflow 0

Centrex Transfer via Remote Call Forwarding 0

Computer Telephony Integration (CTI) 0

Basic Call Control 0

Screen Pop 0

HotLine Feature 0

Group Calling Enhancements 0

Most Idle Hunt Type 0

Delay Announcement Devices 0

Enhanced Calls-in-Queue Alarm Thresholds 0

MLX-5 and MLX-5D Telephones 0

Additional Network Switch and Services Options for ISDN Primary Rate Interface (PRI) 0

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

MERLIN LEGEND Reporter 0

Maintenance Enhancements 0

Change to Permanent Error Alarm 0

Enhanced Extension Information Report 0

Release 4.1 Enhancements (June, 1997) 0

Coverage Timers Programmed for Individual Extensions 0

Night Service with Coverage Control 0

Night Service Group Line Assignment 0

Forward on Busy 0

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

Support for Up to 200 Extensions 0

Support for National ISDN BRI Service 0

New Control Unit Modules 0

800 NI-BRI Module 0

016 Tip/Ring Module 0

Support for 2B Data Applications 0

Support for T1 Switched 56 Digital Data Transmission 0

Forwarding Delay Option 0

Voice Announce on Queued Call Console 0

Single-Line Telephone Enhancements 0

Seven-Digit Password for SPM 0

Call Restriction Checking for Star Codes 0

Trunk-to-Trunk Transfer Set for Each Extension 0

Programmable Second Dial Tone Timer 0

Security Enhancements 0

Disallowed List Including Numbers Often Associated with Toll Fraud 0

Default Pool Dial-Out Code Restriction for All Extensions 0

Default Outward Restrictions for VMI Ports 0

Default Facility Restriction Level (FRL) for VMI Ports 0

Default for the Default Local Table 0

New Maintenance Procedure for Testing Outgoing Trunks 0

About This Book

Page xxxviiIntended Audience

How to Use This Book 0

Lines, Trunks, and Facilities 0

Page xxxixTerms and Conventions Used

Typographical Conventions 0

Product Safety Advisories 0

Page xliSecurity

Page xliiRelated Documents

Page xliiiHow to Comment on This Book

Before You Begin

Page 1-1Reviewing System Components

Grounding Requirements 1

Electrical Noise/Radio-Frequency Interference 1