Lucent Technologies 555-670-116 User Manual

MERLIN LEGEND

Communications System Release 7.0

Pocket Reference

555-670-116 Comcode 108370305 Issue 1 April 1999

April 1999

Notice

Every effort has been made to ensure that the information in this guide is complete and accurate at the time of printing. Information,

however, is subject to change. See Appendix A, “Customer Support Information,” in

System Programming

, for important information.

Your Responsibility for Your System’s Security

Toll fraud is the unauthorized use of your telecommunications

system by an unauthorized party—for example, persons other than your company’s employees, agents, subcontractors, or persons working on your company’s behalf. Note that there may be a risk of toll fraud associated with your telecommunications system, and, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services.

You and your system manager are responsible for the security of your system, such as programming and configuring your equipment to prevent unauthorized use. The system manager is also responsible for reading all installation, instruction, and system administration documents provided with this product in order to fully understand the features that can introduce risk of toll fraud and the steps that can be taken to reduce that risk. Lucent Technologies does not warrant that this product is immune from or will prevent unauthorized use of common-carrier telecommunication services or facilities accessed through or connected to it. Lucent Technologies will not be responsible for any charges that result from such unauthorized use. For important information regarding your system and toll fraud, see Appendix A, “Customer Support Information,” in

System Programming

Federal Communications Commission Statement

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at their own expense. For further FCC information, see Appendix A, “Customer Support Information,” in

System Programming

Canadian Department of Communications (DOC) Interference Information

This digital apparatus does not exceed the Class A limits for radio noise emissions set out in the radio interference regulations of the Canadian Department of Communications.

Le Présent Appareil Numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la classe A préscrites dans le réglement sur le brouillage radioélectrique édicté par le ministère des Communications du Canada.

Year 2000 Compliance

The MERLIN LEGEND Communications System is certified to be Year 2000 compliant. Additional information on this certification, and other issues regarding Year 2000 compliance, is available online at http://www.lucent.com/ enterprise/sig/yr2000.

Trademarks

5ESS, AUDIX, CONVERSANT, CentreVu, DEFI NITY, Magic On Hold, MERLIN, MERLIN LEGEND, MERLIN Mail, PARTNER, PassageWay, MLX-10, MLX-10D, MLX-10DP, MLX-16DP, MLX20L, MLX-28D, MLS-6, MLS-12, MLS-12D, MLS-18D, MLS-34D, SYSTIMAX, TransTalk, and Voice Power are registered trademarks and 4ESS, Intuity, Lucent Technologies, and Prologix are trademarks of Lucent Technologies in the US and other countries.

Acculink, ACCUNET, MEGACOM, MulitiQuest, MLX-5, MLX-5D, and NetPROTECT are registered trademarks of AT&T.

Microsoft, Windows, Windows NT, and MS-DOS are registered trademarks of Microsoft Corporation.

ProComm and ProComm Plus are registered trademarks of DataStorm Technologies, Inc.

Supra, Supra NC, StarSet, and Mirage are registered trademarks of Plantronics, Inc.

UNIX is a registered trademark of UNIX System Laboratories, Inc. PagePac is a registered trademark and Powermate and Zonemate

are trademarks of DRACON, a division of Harris Corporation. Okidata is a registered trademark of Okidata Corporation. Pipeline is a trademark of Ascend Communications, Inc. Intel and Pentium are registered trademarks of Intel Corporation. Apple and Macintosh are registered trademarks of Apple

Computer, Inc. IBM is a registered trademark of International Business Machines,

Inc. Novell and NetWare are registered trademarks of Novell

Corporation. CLASS is a servicemark of Bellcore.

Ordering Information

Call: BCS Publications Center

Write: BCS Publications Center

Order: Document No. 555-670-140

For more information about Lucent Technologies documents, refer

to the section entitled, “Related Documents” in “About This Guide.”

Voice 1-800-457-1235 International Voice

317-322-6791

Fax 1-800-457-1764 International Fax

317-322-6699

2855 North Franklin Road Indianapolis, IN 46219-1385

Comcode: 108289513 Issue 1, April 1999

Support Telephone Number

In the continental US, Lucent Technologies provides a toll-free customer helpline 24 hours a day. Call the Lucent Technologies Helpline at 1-800-628-2888 or your Lucent Technologies authorized dealer if you need assistance when installing, programming, or using your system. Outside the continental US, contact your local Lucent Technologies authorized representative.

Network Engineering Group

For assistance in designing a private network, call the Network Engineering Group at 1-888-297-4700.

Lucent Technologies Corpora te Security

Whether or not immediate support is required, all toll fraud incidents involving Lucent Technologies products or services

should be reported

1-800-821-8235. In addition to recording the incident, Lucent Technologies Corporate Security is available for consultation on security issues, investigation support, referral to law enforcement agencies, and educational programs.

to Lucent Technologies Corporate Security at

Lucent Technologies Fraud Intervention

If you

suspect you are being victimized

technical support or assistance, call BCS National Service Assistance Center at 1-800-628-2888.

by toll fraud and you need

Warranty

Lucent Technologies provides a limited warranty on this product. Refer to “Limited Warranty and Limitation of Liability” in Appendix A, “Customer Support Information,” in

System Programming

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Contents

Release 7.0 Enhancements (April 1999) 1 Release 6.1 Enhancements (August 1998) 4 Release 6.0 Enhancements (February 1998) 7 Release 5.0 Enhancements (June 1997) 11 Release 4.2 Enhancements (June 1997) 15 Release 4.1 Enhancements (June 1997) 17 Release 4.0 Enhancements (March 1996) 18 Release 3.1 Enhancements (March 1996) 21 Release 3.0 Enhancements (August 1994) 23 Release 2.1 Enhancements (August 1994) 26 Release 2.0 Enhancements (October 1992) 29 Release 1.1 Enhancements (October 1992) 31

Issue 1

April 1999

Design Benefits 32 Environmental Specifications 33 Power and Grounding 35 Control Unit Interfaces 37 Network Interface Requirements 38 FCC Registration 38 DOC Registration 38 Hardware and Software Capacities 39 Constraining Factors 42

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

Contents

555-670-116

Ordering Codes 45

Control Unit Modules 70 Adjunct Summary 80

Power Supply Unit Load Requirements 90

Unit Load Calculation Rules 90 Unit Load Rating of System Modules 91 Unit Load Rating of System Trunks,

Telephones, and Adjuncts 92 System Feature Availability by Operating Mode

Telephone and Operator Console Features 96 Reference Documents 110

Maintenance Error Codes 111 Technical Addendum 111 Module/Component History 126 Telephone LEDs 138 Wiring Constraints 141 PC Connections 141 Technical Support Telephone Numbers 144

Issue 1

April 1999

Feedback Form 147

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 7.0 Enhancements (April 1999)

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

■ MLS and Enhanced Tip/Ring (ETR) Telephone

Support

One of the most important new capabilities of MERLIN LEGEND Release 7.0 is its support for MLS and ETR telephones, allowing existing customers with either telephones the ability to migrate to a MERLIN LEGEND Communications System. The MLS telephones include the MLS-6

MLS-12D include the ETR-6, ETR-18, ETR-18D, and ETR-34D. The

Business Cordless 905 telephone and the TransTalk™ 9000

, MLS-18D®, and MLS-34D®. The ETR telephones

Digital Wireless System are also supported. The MLS, ETR, and Business Cordless 905 telephones, as well

as the TransTalk 9000 Digital Wireless System, require ET R station ports. To provide support for these telephones and for the TransTalk 9000 system, two new modules have been designed:

— 412 LS-ID-ETR Module. The 412 LS-ID-ETR module is not

available. To connect ETR and MLS telephones to a MERLIN LEGEND Communications System, use the 016 ETR module.

— 016 ETR Module. The 016 ETR module provides 16 ETR

station ports, including 6 with T/R functionality and 4 TTRs. On the 016 ETR module, the first 10 ports are ETR ports

only—these ports do not have T/R functionality. The remaining 6 ports (ports 11 through 16) can be programmed to support either T/R or ETR, but not both simultaneously.

■ Expanded Digital Endpoint Connectivity

Release 7.0 increases the maximum number of digital telephones supported from 127 to 200 by introducing a new 016 MLX module. In addition, each of the 200 ports can support an MFM adjunct which increases the current 255 station endpoints to 400.

— 016 MLX Module. Each 016 MLX module provides 16 digital

station ports and has an additional 32K of dual port RAM.

— Processor Module. The 016 MLX module can only be

utilized with the CKE4 or later processor module with upgrade to R7.0 software. The CKE4 processor module provides the lead to access the additional 32K of RAM on the 016 MLX module.

■ Voice Announce on Idle Only Option on MLX Telephones

Prior to Release 7.0, no options were available for disabling intercom voice announcements at an MLX telephone when

busy. In Release 7.0, a new option—Voice Announce on IDLE ONLY—is available with the existing Voice Announce feature. This new option allows a user to receive intercom voice announcements only when they are not active on another call.

, MLS-12®,

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 7.0 Enhancements (April 1999)

■ Priority Call Queuing

Priority call queuing provides the ability to:

— Place some callers ahead of others who are waiting for the

same agent group.

— Give key clients priority over others. — Automatically increase the number of agents answering calls

during busy times, while continuing to offer callers the choice to leave a message instead of waiting.

— Keep costs down by handling toll free calls (calls arriving on

800 and 888 lines) before processing calls on local lines.

Priority call queuing is accomplished in Release 7.0 by allowing you to define a supportive relationship between calling groups. Calls that arrive in one calling group can be processed by another calling group when no one from the first calling group is available to answer the call. Through system programming, a calling group can be assigned a priority level between 1 (highest priority) and 32 (lowest priority) and then designated as a support group for another group.

■ Calling Party Name on Caller ID

Release 7.0 continues to support Calling Party Number and adds a new functionality for Calling Party Name. By programming a button on the telephone or with a feature code through centralized programming, users are able to toggle

between displaying the caller’s telephone number or the caller’s name. In order to use this feature, users must subscribe to caller identification from their local exchange carrier (LEC).

Calling Party Name can be 15 characters in length for MLX telephones as well as for ETR and MLS telephones. Calling Party Name is not recorded on SMDR reports. In addition, neither Calling Party Name nor Calling Party Number are displayed on analog multilin e telep hon es.

This feature requires loop-start (LS) trunks. The existing LS-ID delay feature must be programmed for each line, as well. This prevents Calling Party Number and Name information from being lost when a call is answered too quickly.

Release 7.0 software also supports the Caller ID capability of the 408 GS/LS-ID-MLX module. Although previously orderable, the Caller ID capability of this module could not be used until Release 7.0 software became available.

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 7.0 Enhancements (April 1999)

■ MLX Headset Operation

Headset operation in Release 7.0 has been enhanced so that MLX headset operation more closely mimics the handset operation in the following ways:

— When a person is on a call using a headset and the headset

auto-answer is turned on, the user hears a short ring when another call is coming in. In previous releases, this ring was not provided.

— When a person receives a voice-announced call and handles

the call by using a headset and turning off the speakerphone, the associated LEDs (the DSS button and the inside Auto Dial button) for that extension at other telephones are lit. In previous releases, the LEDs for that extension did not light at the other telephones.

— When a reliable disconnect occurs on a headset-handled

call, the associated LEDs (the DSS button and the inside Auto Dial button) for that extension at other telephones are turned off. In previous releases, the LEDs for that extension remained lit at the other telephones unless the user pressed the Headset Hangup button.

■ Touch-Tone or Rotary Signaling

Beginning in Release 7.0, you can program tip/ring ports to use rotary signaling. You can program any tip/ring port on an individual basis (including ports on the 412 LS-ID-ETR and 016 ETR modules that are programmed for tip/ring operation). The factory setting is that rotary signaling is disabled.

Whenever the system receives a rotary digit on a port, it determines if the port is programmed as rotary-enabled. If the port is rotary-enabled, the system processes the digit. If the port is not rotary-enabled, the digit is rejected. Touch-tone digits are always accepted by the port, regardless if it is rotary-enabled or not.

■ Abandoned Call Information Reported to

MERLIN LEGEND Reporter

For abandoned calls, you are now able to identify the queue or the agent where the call was aband one d. Th e MER LIN LEGEND Release 7.0 software has been modified so that either of the following occurs:

— If the caller hangs up while the call is in queue, the Auto

— If the caller hangs up while the call is ringing at a group

member’s extension, that group member’s extension number is entered into the SMDR record.

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 6.1 Enhancements (August 1998)

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

■ Private Networking

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

■ Centralized Voice Messaging

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 the VMS is called Voice Messaging includes the functions of voice mail, Automated Attendant, and fax messaging. See the

Reference

Centralized Voice Messaging

for detailed information about Centralized Voice

Messaging. Centralized Voice Messaging offers the following benefits:

— Private-networked MERLIN LEGEND Systems do not need a

local VMS. Having systems use a centralized VMS instead of separate VMSs is more economical .

— Users who travel between sites can dial the same digits

anywhere in the privat e network to access the voice messaging system. For example, a salesperson headquartered in Cincinnati can dial the same four digits at

the company’s Los Angeles office to retrieve voice messages.

— Productivity is enhanced because messages can be

forwarded and broadcast 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 ef fi ci ency saves time bec ause a us er on ly ha s to look at his or her telephone to determine if he or she has a message.

hub

. This sharing of . Centralized

Network

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 6.1 Enhancements (August 1998)

■ Group Calling Enhancements

single

A calling group can have a defined by the Uniform Dial Plan and exists on another MERLIN

non-local member that is

LEGEND Communications System connected by a tandem trunk to the local system. If a calling group contains a non-local

only

member, the non-local member must be the calling group. See the

A calling group containing a single non-local member can be used for the same purposes as a calling group containing local

Network Reference

member in th e

for details.

extensions, includi ng:

— Night Service. Night Service coverage can be provided

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

— Group Coverage. Group Coverage can be provided across

a private network to a VMS, a non-local calling group, a QCC queue, a DLC, or any individual extension on the remote system.

— 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

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 Se lector

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

■ Call Forwarding

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

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 6.1 Enhancements (August 1998)

■ SMDR

In addition to SMDR options for non-network calls placed to and from the local system, system managers now can program SMDR to log incoming and outgoing UDP calls, or they can choose to log no UDP calls. The factory setting is to record all UDP calls.

Customers who use a call accounting system may not want to fill the database with calls coming and going across the private network. These customers may choose not to log UDP calls.

■ Decrease in Call Setup Time

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

■ PRI Switch Type Test

A new maintenance test, the PRI Switch Type Test, has been created to allow Lucent T e chnologies technicians or authorized dealers to automatically determine if each end of the PRI tandem trunks has been programmed correctly. The test works for directly connected MERLIN LEGEND Systems, not for DEFINITY

systems.

For a PRI tandem trunk to operate correctly between two MERLIN LEGEND Systems, one system must have the PRI Switch Type set to Network, and the other system must have the PRI Switch Type set to PBX. If both ends of the PRI tand em trunk are programmed the same, problems occur in the communications between the two systems.

■ Service Observing

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 ob serving how a Customer Service representative handles calls.

The Service Observing group can listen to anywhere from one extension to all extensions in the system, including other Service Observers. Up to 16 Service Observing groups can be programmed. The Service Observer and the observed extension must be on the same system.

The observer activates Service Observing either by pressing a Service Observing button and then dialing an extension number, or by pressing a DSS or Auto Intercom button. The Service Observer must use an MLX telephone to observe an extension; the telephone at the observed extension can be of any type.

A warning tone that alerts the observer, the observed extension, and the caller that Service Observing is occurring can be set to on or off through System Programming. The factory setting is on.

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 6.0 Enhancements (February 1998)

■ WinSPM

The System Programming and Maintenance (SPM) software is now available in a Windows format called WinSPM. For R6.1 and later systems, WinSPM provides a graphical user interface (GUI) for those tasks most 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 WinSPM. Supported in Windows 95 backwards-compatible with previous DOS versions of SPM and is available on CD-ROM.

■ Windows NT Driver

, Windows NT, and Windows 98, WinSPM is also

The MERLIN LEGEND Windows NT PBX driver is available in R6.1. When coupled with the CentreVU Telephony Services application, the driver provides true server-based Computer T el epho ny In teg rati on (CT I). The new driv er re qui res a ME RLI N LEGEND System of Release 5.0 or later and servers and PCs that support the applications.

Release 6.0 Enhancements (February 1998)

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

■ Private Networks

In Hybrid/PBX mode systems only, MERLIN LEGEND Communications Systems can be networked with one another or with DEFINITY Enterprise Communications Server (ECS)

and ProLogix™ Communications Systems in private networks. In previous releases, this functionality is available using tie lines, but users handle calls between networked switches as outside calls. In this release, dialing the pool access code is not necessary for a call going from one networked switch to another. Also, delay-start tie trunks or T1 trunks administered as PRI can act as

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 up to 20 patterns, associated 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 telephones for incoming calls across PRI tandem trunks.

tandem trunks

to connect networked systems.

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 6.0 Enhancements (February 1998)

— Toll Savings. Private networked trunks may allow you to

realize significant cost savings on long-distance and toll calls by performing tandem switching in the following two ways:

— Callers on a local system, or individuals dialing in to

remote access at a local system, can reach the public switched telephone network (PSTN) via outside trunks connected to other systems in a private network, avoiding toll charges or decreasing the cost of toll calls. No special dialing is required. For example, an organization might have a main office in Boston and a subsidiary office in New Jersey connected by networked private tandem trunks between two systems. A user in the New Jersey office who wishes to make an outside call to the 617 area code (Bost o n) ca n d o so t hr o ugh a l i ne /t r un k co nn ec te d t o the system in Boston. For example, he or she might dial,

916175551211. The local ARS tables would route this call over the private networked trunks and use the ARS tables of the remote system in Boston to route this call. The system managers at each end of a private network set up ARS and Remote Access features to implement this functionality.

— In addition, local organizations or incoming DID calls use

private networked trunks to make intersystem calls between networked systems, which may be geographically distant from one another, also resulting in toll savings.

— Service Cost Savings. In addition to toll call savings, there

are two ways that organizations can save on service costs incurred from telecommunications providers that provide public switched telephone network access:

— Y ou 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 64 kbps per channel or 128 kbps for 2B data, while keeping the remaining Bchannels available for PRI voice traffic. The PRI D-channel must remain active.

— Y ou 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-andinsert equipment to provide fractional T1 use.

— Voice Mail and Auto Attendant. Networked systems (prior

to Release 6.1) should have their own local voice mail and/or auto attendant applications as well as their own external alerts and Music-On-Hold sources. A single Auto Attendant, however, 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.

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 6.0 Enhancements (February 1998)

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

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

■ Queue Control

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

Queue control applies to calls received on the following types of facilities:

— Direct Inward Dialing (DID) — PRI facilities programmed for dial-plan routing — All calls transferred from a voice messaging interface (VMI)

port

— Dial-in Tie

Queue control also applies to internal calls to a calling group and calls to a calling group through the Queued Call Console (QCC).

Internal calls that dial #0 or #800 and are directed to a calling group administered as P osition-Busy Backup are eligible for queue control. Calls that come in on a trunk assigned to the 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 a calling group through QCC Position-Busy Backup, and all other outside calls are not eligible for queue control.

■ Prompt-Based Overflow

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.

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 6.0 Enhancements (February 1998)

■ Centrex Transfer via Remote Call Forwarding

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 Centr ex 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 that are 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 MERLI N 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 facilities. Loop-start lines do not have to provide reliable

all

loop-start lines in the system must be Centrex

disconnect for use by the Centrex Transfer via the Remote Call Forwarding feature.

— T o transfer calls outside the Centrex system, the organization

must subscribe to a Centrex trunk-to-trunk transfer feature.

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

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, however, do apply.

■ Authorization Cod es an d

Remote CallForwarding

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. Th is i s e spec iall y us ef ul fo r a s ing le- lin e te leph one use r 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 (for example, from another switch in the network). No other features can be used by entering an authorization code in this fashion.

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 5.0 Enhancements (June 1997)

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

■ Computer Telephony Integration (CTI)

Beginning with Release 5.0, a PassageWay Services CTI link from the MERLIN LEGEND Communications System to a LAN server running Novell allows Lucent Technologies-certified telephony applications to control and monitor MLX and analog multiline telephone (BIS only) operations. The physical connection for the CTI link is an MLX port on a 008 MLX or 408 MLX module on the MERLIN LEGEND Communications System control unit and an ISDN

link interface card plugged into the customer’s server. The feature is available for Hybrid/PBX mode systems only.

NOTES:

•The NetWare server software version must be 3.12, 4.1, or 4.11.

•The 008 MLX and 408 MLX modules must have a firmware vintage other than 29. If the module has firmware 29, programming a CTI link on the module is prevented. An earlier or later vintage firmware is supported.

■ Basic Call Control

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

— Answering calls arriving on an SA button. — Making calls from an SA button. — Hanging up calls. — Holding 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.

■ Screen Pop

Screen pop occurs when the calling number, called number, or other user-defined identifier (such as an 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:

Telephony

NetWare® software

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 5.0 Enhancements (June 1997)

— Calling gr oup distribution. — ISDN PRI Routing by Dial Plan. — An extension on the MERLIN LEGEND Communications

System.

— Remote access.

NOTE:

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

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

unit.

— A transfer, redirection, or conference of a call that was

answered at a Direct-Line Console (DLC) or at a Queued Call Console (QCC).

NOTES:

•DLCs 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 is not using a CTI link extension, it is non-monitored.

•Calls to a QCC or a DLC not using a CTI application do not initia te screen pop at the operator position. However, 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.

•Calls transferred from Cover buttons on non-monitored DLCs do not initiate screen pop at the destination extension.

■ HotLine Feature

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 c onnected to an 008 OPT, 012, or 016 module as a HotLine. When a user lif ts the handset at the HotLine extension, the telephone automatically dials the inside extension or outside telephone number programmed as the first Personal Speed Dial number (code #01) for the extension. The system does not permit calls to be transferred, put on hold, or conferenced. (A user can press the telephone’s Hold button, if it has one, to put a call on local hold, but the call cannot be redirected in any way. Switchhook flashes are ignored.)

Personal Speed Dial codes can be programmed from the extension prior to HotLine assignment (a system programming function). Alternatively, a Personal Speed Dial code can be programmed from the single-line telephone after HotLine operation is assigned. However, because of security considerations, this is a one-time opportunity. Once the Personal Speed Dial number is programmed, any changes to it or any other extension programming must be performed using centralized telephone programming.

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 5.0 Enhancements (June 1997)

Any type of inside or outside line that is norm ally available to a single-li ne 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.

SECURITY ALERT:

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

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

■ Most Idle Hunt Type

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 appl ications, 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

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 Rel ease 4.2 and earlier systems. Furthermore, an additional secondary delay announcement device can be specified, for a total of ten primary device extensions and one secondary device extension per group.

A primary delay announcement device operates in the same fashion as a single delay announcement device, playing once, as soon as it is available, for the caller who has waited the longest for a calling group agent and has not heard a primary delay announcement. If a secondary announcement device is used, it can use the factory setting, which plays the announcement once, or it can be set to repeat the announcement after a certain amount of time. The system manager programs the ti me (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 “Calling Group Options” in Chapter 4 of

for guidelines on setting the delay.)

Planning

Issue 1

April 1999

System

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 5.0 Enhancements (June 1997)

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 programmed as

a secondary delay announcement device.

■ Enhanced Calls-in-Queue Alarm Thresholds

Three Calls-in-Queue Alarm thresholds can be set to more clearly indicate the real-time status of the calls waiting in the queue according to the behavior of programmed Calls-in-Queue Alarm buttons. In earlier releases, only one Calls-in-Queue Alarm Threshold setting is available to activate the LEDs at programmed Calls-in-Queue Alarm buttons for a calling group.

Using all three levels, the system manager sets Threshold 3 to the highest value, Threshold 2 to a middle value, and Threshold 1 to the lowest value. A Calls-in-Queue Alarm button indicates the severity of the alarm conditions in the following ways:

— If the number of waiting calls is less than the value

programmed for Threshold 1 or drops below that level, the LED is unlit.

— If the number of waiting calls is greater than or equal to the

Threshold 1 value but less than the Threshold 2 value, the LED flashes.

— If the number of waiting calls is greater than or equal to the

Threshold 2 value but less than the value for Threshold 3, the LED winks.

— If the number of waiting calls is greater than or equal to the

highest value, Threshold 3, the LED ligh ts stead ily.

NOTE:

A Direct Station Selector (DSS) 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 pr ogrammed.

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 signals only when the number of calls in the queue meets or exceeds the program m ed Threshold 3 value.

■ MLX-5 and MLX-5D Telephones

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 five 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 5button telephones.

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 4.2 Enhancements (June 1997)

If these telephones are connected to commu nicat ions system releases prior to 5.0, they are recognized by the communications system as 10-button telephones.

Release 4.2 Enhancements (June 1997)

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)

Release 4.2 of the system supports connectivity to MCI local exchange carrier (LEC) PRI services and to the following

central office switch types (in addition to the 4ESS™ and

switch types that carry AT&T Switched Network

5ESS

services):

services.

DMS™-100 BCS 36 for local exchange carrier

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

— MCI Toll Services for DMS-250 or DEX600E switch type:

— MCI Prism

and international voice calls; for domestic outgoing 56kbps restricted, 64-kbps unrestricted, and 64-kbps

service for domestic outgoing long-distance

restricted circuit-switched data calls.

— MCI VNet

and voice calls; for 56-kbps restricted, 64-kbps restricted,

service for incoming and outgoing domestic

and 64-kbps unrestricted circuit-switched data calls.

— MCI 800 for domestic, toll-free incoming voice calls. — MCI 900 service numbers.

— LEC services for DMS-100 switch types:

— DMS Virtual Private Network service for calls between the

MERLIN LEGEND Communications System and another communications system (such as another MERLIN LEGEND Communications System).

— DMS INWATS (Inward Wide Area Telephone Service) for

domestic toll-free incoming voice calls.

— DMS OUTWATS (Outward Wide Area Telephone Service)

for domestic outgoing long-distance voice calls.

— DMS FX (foreign exchange) to provide local call rating for

calls from the local exchange to the area serviced by the foreign exchange.

— DMS tie trunk service to provide private exchange call

rating for calls placed on a dedicated central office facility between the MERLIN LEGEND Communications System and another communications system.

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 4.2 Enhancements (June 1997)

■ Improvements to Station Message Detail

Recording (SMDR) and Support for MERLIN LEGEND Reporter Application

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 L EGEND Reporter features listed are administrable:

— TALK Field. For Auto Login and Auto Logout calling groups,

the TALK field records the amount of time a calling group agent spends on a call.

— DUR. (DURATION) Field. For Auto Login and Auto Logout

calling groups, call timing begins when a call arrives at the MERLIN LEGEND Communications preset number of seconds. Call timing ends when the call is

System and not after a

disconnected; either the caller or the agent hangs up. This allows the system manager to determine how long a caller

waited for an agent’s attention.

— Coding of Calls on Reports. An asterisk (*) appears in the

call record when:

— A call is not answered by an Auto Login or Auto Logout

calling group agent and is abandoned while waiting for an agent.

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

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 telephone 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 provid ed:

— Organization Detail Report — Organization Summary and Trends Report — Selection Detail Report — Account Code Report — Traffic Report — Extension Summary Report

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 4.1 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

■ Change to Permanent Error Alarm

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

Programming, and Maintenance.

■ Enhanced Exten sion Information Report

Beginning with Release 4.2, the Extension Information Report includes the Extension Status and supervisory mode of each

Installation,

extension.

Release 4.1 Enhancements (June 1997)

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

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 D elay (1–6 rings) and Se condary

Cover Ring Delay (1–6 rings), prog ra mm ed on in divi d ual 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’ callhandling requirements.

■ Night Service with Coverage Control

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.

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 4.0 Enhancements (March 1996)

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

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.

■ Forward on Busy

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 or ICOM buttons is forwarded immediately to the programmed destination, preventing the caller from hearing a busy sign al from the intended call

recipient’s extension.

■ Maintenance Testing for BRI Facilities that Are

Part of Multiline Hunt Groups (MLHGs)

Beginning with Release 4.1, the NI-1 BRI (National Integrated Services Digital Network-1 Basic Rate Interface) Provisioning Test Tool is enhanced to include testing for BRI facilities that are part of Multiline Hunt Groups (MLHGs).

The NI-1 BRI Provisioning Test To ol 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

April 1999

Release 4.0 Enhancements (March 1996)

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

■ Support for Up to 200 Extensions

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

■ Support for National ISDN BRI Service

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 di gital data, which is necessary for videoconferencing and other high-speed applications. Release 4.0 supports the

bearer channels

) on a BRI line can carry one

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 4.0 Enhancements (March 1996)

ISDN Ordering Code (IOC) Package “S” (basic call handling) service configuration and Multiline Hunt service configuration on designated central office switches.

■ New Control Unit Modules

Release 4.0 supports a new NI-BRI line/trunk module and a higher-capacity tip/r ing mod ule.

■ 800 NI-BRI Module

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

■ 016 Tip/Ring Module

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

The Personal Compute r Memory Card Int ernat ional Assoc iatio n (PCMCIA) technology, introduced in Release 3.0, continues to support these two modules for installation and upgrade in Release 4.0. A Release 3.0 or later processor is required for PCMCIA technology.

■ Support for 2B Data Applications

A Lucent Technologies-certified group and desktop video application can use two B-channels to make video/data calls when connected to a sing le 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 Da ta Transmission

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

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 4.0 Enhancements (March 1996)

■ Forwarding Delay Option

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 from 0 to 9 rings. The factory setting for the forwarding delay is 0 rings (no delay).

■ Voice Announce on Queued Call Console

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.

■ Time-Based Option for

Overflow on Calling Group

time

Release 4.0 has added a to the previous

number of calls

limit for calls in queue in addition

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

■ Single-Line Telephone Enhancements

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 central office. 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 oth er usele ss messages. This operation is not programmable.

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 3.1 Enhancements (March 1996)

■ Seven-Digit Pas sword for SPM

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.

Release 3.1 Enhancements (March 1996)

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

■ Call Restriction Checking for Star Codes

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. For example, in many areas, a telephone user can dial *67 before a telephone number to disable central

office-supplied caller identification at the receiving party’s telephone. You must contract with your telephone service provider to have these codes activated.

When users dial star codes, the system’s calling restrictions determine whether the codes are allowed. If they are allowed, the system’s calling restrictions are reset, and the remaining digits that the users dial are checked against the calling restrictions.

■ Trunk-to-Trunk Transfer Set for Each Extension

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 Di al Tone Timer

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 central office 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 central office 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 central office is ready to receive more digits from the caller.

■ Security Enhancements

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

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 3.1 Enhancements (March 1996)

■ Disallowed List Including Numbers Often

Associated with Toll Fraud

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 voice messaging interface (VMI) ports used by voice messaging systems. The system manager can manually assign this list to other extensions.

■ Default Pool Dial-Out Code

Restriction for All Extensions

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

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.

SECURITY ALERT:

Before removing restrictions, it is strongly recommended that

you read Appendix A, ‘‘Customer Support Information,” in System Programming.

■ Default Facility Restriction

Level (FRL) for VMI Ports

The default Au tomat ic Rout e Se lect io n (AR S) F RL f or VMI p ort s is 0, restricting all outcalling.

■ Default for the Default Lo cal Table

The default Automatic Route Selection (Hybrid/PBX mode onl y) FRL has changed to 2 for the Default Local table. System

managers can easily change an extension’s default FRL of 3 to 2 or lower to restrict calling. No adjustment to the route FRL is required.

■ New Maintenance Procedure for Testing

Outgoing Trunks

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

Issue 1

April 1999

SECURITY ALERT:

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 these upgrade notes and in the relevant system guides.

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 3.0 Enhancements (August 1994)

Release 3.0 includes all Release 2.1 functionality plus the enhancements listed below.

■ Equipment

New hardware includes a variety of components. Additional details are included elsewhere in this book.

— CPU modifications include:

— A processor running at 16 MHz with a 32-bit wide data

bus.

— 1.5 MB of non-volatile (battery-backed) RAM. — 4.0 MB of Flash ROM. — PCMCIA memory card interface. — A full-duplex 1200/2400 bps modem. — Error/Status code display for maintenance support.

— An 800 GS/LS-ID line/trunk module delivers the calling

party’s telephone number to the customer premises (MLX display telephones only) if the service is subscribed to by the customer and if it is supported by the caller’s telephone company.

— Support for:

— MDC 9000 (six-line, cordless). — MDW 9000 (six-line, cordless, wireless). — 8101 (single-line telephone, desk or wall-mount, data/fax

jack, selectable positive disconnect).

— 2500YMGL and 2500 MMGL (single-line desk telephones,

selectable positive disconnect).

— Picasso — Videophone 2500 single-line telephone with interactive

— Pre-fabricated and pre-drilled backboard.

■ Installation, Upgrade Administration, and Maintenance

These are the new MERLIN LEGEND Communications System capabilities:

— SPM (Release 3.18) conversion of translations from Release

1.0, 1.1, 2.0, and 2.1 to 3.0.

— Remote operation at 1200/2400bps. — Advice and feedback administration screens for new Release

3.0 functionality.

— PCMCIA Memory Card Interface (a Release 3.0 processor

board required) allowing:

— System software installation. — System software upgrade. — 800 GS/LS-ID port module firmware upgrade. — Integrated backup and restore of translations. — Automatic and manual options for backup and restore are

— Inter-digit dialing timer values are programmable.

™

still images).

Still-Image telephone (for interactive display of

video display

available on the system. Automatic backup can be

scheduled weekly or daily to fit the customer’s needs.

Issue 1

April 1999

MERLIN LEGEND Communications System Release 7.0 Pocket Reference

555-670-116

Release 3.0 Enhancements (August 1994)

— Inspection of Lines/Trunks displays only those lines and

trunks configured on system rather than all 80 facilities.

— Extensions and facilities in Maintenance Busy (both manual

and automatic) can be identified by the maintenance monitor.

■ User Features

— Security. The Remote Access feature allows people at

remote locations to enter the system by dialing the number of a line or trunk designated for remote access. The system can be programmed to require the remote user to dial a barrier code (a type of password) after reaching the system. In earlier versions, the systemwide barrier code length is fixed at four digits. Release 3.0 allows a systemwide barrier code length ranging from a minimum of four digits to a maximum of 11 digits, with a factory setting of seven digits. SMDR records are enhanced to provide information for remote access calls. If the remote access call is received on a facility providing Caller ID information (see below), the SMDR report can help trace the call.

— Caller ID. Caller information (telephone number) is furnished

to MLX display telephones by an 800 GS/LS-ID module using the LS (loop-start) option. This allows customers to screen calls before answering the telephone, as well as providing calling party information for use with various applications. This function is available only when the customer subscribes to caller identification service from the telephone company, if the telephone company supports that service.

— Shared System Access (SSA). A telephone may have up to

27 Shared SA buttons to expand extension coverage.

— Authorization Codes. The Authorization Code feature

allows you to make calls using your calling privileges when you are dialing from an extension other than your own. When you enter your authorization code (ranging from 2 to 11 characters and unique across the system), the privileges and restricti ons assigned to your home extension override the current restrictions at the host extension. This includes toll restriction, outward restriction, Facility Restriction Level (FRL), Allowed Lists, Disallowed Lists, Night Service Exclusion List, and Dial Access to Pools. All other functions on the telephone are those of the local telephone, not the home extension. Authorization codes can also be used for the purpose of call accounting through the SMDR printout. The SMDR account code field can hold either the authorization code extension number or the authorization code itself.

— Direct Voice Mail. If your company has voice mail, this

feature allows you to dial a co-worker’s voice mailbox directly without ringing that person’s extension. Direct Voice Mail is especially useful for transferring calls when a co-worker is not available.

Issue 1

April 1999

+ 123 hidden pages