Prior Releases: Features and Enhancements. Lucent Technologies MERLIN LEGEND, MERLIN LEGEND Release 6.1

MERLIN LEGEND Communications System Release 6.1

Feature Reference 555-661-110

Prior Releases: Features and Enhancements

Release 6.0 Enhancements (February 1998)

Prior Releases: Features and

Enhancements

Issue 1

August 1998

Page xxv

Release 6.0 Enhancements

(February 1998)

0

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

Private Networks 0

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

®

Enterprise

Communications Server (ECS) and ProLogix

®

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

Available for Hybrid/PBX mode systems, the private network features of the

MERLIN LEGEND Communications System Release 6.0 provide the following advantages for geographically dispersed organizational sites:

■

Intersystem Calling. In a private network, users on one local system can call extensions on other systems in the network. Release 6.0 can support

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





Issue 1

August 1998

Page xxvi

■

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

Toll Savings. Private networked trunks allow you to realize significant cost savings on toll calls by performing tandem switching in the following two ways:

— Callers on a local system can reach the PSTN via outside trunks connected to other systems in a private network, avoiding toll charges or substantially decreasing the cost of toll calls. For example, if you are in

Cincinnati and another site in your company is in Dallas, you can make a call to a number in the Dallas local calling area over your private network, decreasing toll costs.

— In addition, organizations use private networked trunks to make calls between networked systems, which may be geographically distant from one another. Using the example above, from your office in Cincinnati you can dial an extension at a sister site in Dallas, just as you would dial an extension on your own local system, without a costly long-distance phone call. You simply dial the extension number.

Service Cost Savings. In addition to toll call savings, there are two other ways that organizations can save on service costs incurred from telecommunications providers that provide PSTN access:

— You order a point-to-point T1 circuit from a service provider, then use system programming to set it up for tandem PRI services. As necessary, a service provider provides amplification for PRI tandem trunks in cases where the distance between networked systems is great enough to distort signals, but the service provider does not supply switching services.

— You can tailor your use of PRI B-channels with drop-and-insert equipment that allows fractional use of T1 channels for non-MERLIN

LEGEND data/video communications between sites, while keeping the remaining T1 channels for PRI voice or data traffic.

NOTE:

The 24th T1 channel must not be dropped before reaching the

MERLIN LEGEND Communications System because MERLIN

LEGEND uses the 24th channel as the PRI D-channel or signalling channel.

— You can tailor your use of T1 channels to support a mix of T1-emulated tandem tie trunks for voice or data communications at 56 kbps per channel, allowing 2B data transfers at 112 kbps. The system also allows fractional use of point-to-point T1 tandem trunks with drop-and-insert equipment.





Issue 1

August 1998

Page xxvii

■ 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. Chapter 1 in Network Reference includes an example of this configuration.

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 calls in queue reaches the programmed maximum, subsequent callers receive a busy signal.

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

■ DID (Direct Inward Dialing)

■

■

■

PRI facilities programmed for dial-plan routing

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

Dial-in Tie

Queue control also applies to internal calls to a DGC group and calls to a calling group through the QCC.

Internal calls that dial a Listed Directory Number (LDN) or and are directed to a calling group administered as Position-Busy Backup are eligible for queue control. Calls that come in on a trunk assigned to the Queued Call Console (QCC) are not eligible for queue control if the call is directed to a calling group designated as Position-Busy Backup.

Remote-access calls to a calling group, coverage calls directed to a calling group, calls directed to calling group through QCC Position-Busy backup, and all other outside calls are not eligible for queue control.





Issue 1

August 1998

Page xxviii

Prompt-Based Overflow 0

System managers can activate the Prompt-Based Overflow option. This option allows callers waiting in queue and listening to a delay announcement to press the

# key in order to reach the overflow receiver for the group, which may be the QCC queue or another calling group (including a calling group assigned for a voice mail system).

All three overflow distribution options—based on the number of calls, the time a caller has waited, and according to the caller’s prompt—may be used at one time.

In this case, time-based and number-of-calls based options take precedence over overflow distribution based on the caller’s prompt.

When prompt-based overflow distribution is used, an extra TTR must be provided for each delay announcement device assigned to the associated calling group.

The delay announcement informs the caller of the # key option to exit the queue and leave rather than waiting for an agent. If no TTR is available when a calling group call arrives, the call is not sent to a delay announcement extension.

Centrex Transfer via Remote Call Forwarding 0

Centrex Transfer via Remote Call Forwarding can be used in all system modes of operation to send outside calls to a remote telephone number or another Centrex station. In this context, the term outside refers to calls that arrive on an analog

Centrex loop-start line at the 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. Refer to “Centrex Operation” on page 129

for details on applicable considerations and rules.

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




Release 5.0 Enhancements (June 1997)

Issue 1

August 1998

Page xxix

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

Release 5.0 Enhancements (June 1997)

0


Computer Telephony Integration (CTI) 0

Beginning with Release 5.0, a PassageWay

®

Telephony Services CTI link from the MERLIN LEGEND Communications System to a LAN server running Novell

®

NetWare

®

software allows Lucent Technologies-certified telephony applications to control and monitor MLX and analog multiline telephone (BIS only) operations.

The physical connection for the CTI link is an MLX port on a 008 MLX or 408 MLX module on the MERLIN LEGEND Communications System control unit and ISDN link interface card plugged into the customer’s server. The feature is available for

Hybrid/PBX mode systems only.

NOTE:

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

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

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

Issue 1

August 1998

Page xxx

NOTE:

Transfer and 3-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 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

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

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





Issue 1

August 1998

Page xxxi 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.

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 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 onetime opportunity. Once the Personal Speed Dial number is programmed, any changes to it or any other extension programming must be performed using centralized telephone programming.

Any type of inside or outside line that is normally available to a single-line telephone can be assigned to a HotLine extension. Generally, the HotLine telephone does not receive calls, and its lines should be set to No Ring.

!

SECURITY l 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 0

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





Issue 1

August 1998

Page xxxii

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.

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.

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





Issue 1

August 1998

Page xxxiii

Calls-in-Queue Alarm button indicates the severity of the alarm conditions in the following ways:

■ If the number of waiting calls is less than the value programmed for

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

■

■

■

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

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

If the number of waiting calls is greater than or equal to the highest value,

Threshold 3, the LED lights steadily.

NOTE:

A DSS (Direct Station Selector) button that is used as a

Calls-in-Queue Alarm button can only indicate two threshold levels, either by flashing or by lighting steadily. If a calling group must use this type of Calls-in-Queue Alarm button, only two threshold levels should be programmed.

If all three thresholds are set to the same value, the result is one threshold only with LED state either off or on (steady). If two values are the same, then the result is two alarm levels (flash, steady). The factory setting is one call for all three thresholds with LED states of off and steady.

An external alert only signals when the number of calls in the queue meets or exceeds the programmed Threshold 3 value.

MLX-5 and MLX-5D Telephones 0

The MLX-5 nondisplay and MLX-5D display telephones are compatible with all system releases. The display telephone includes a 2-line by 24-character display, and both telephones come with 5 line buttons. In systems prior to Release 5.0, the

MLX-5 and MLX-5D telephones are treated as MLX-10 and MLX-10D telephones respectively. As of Release 5.0, the system recognizes the MLX-5 and MLX-5D telephones as 5-button telephones.

If these telephones are connected to communications system releases prior to 5.0 they are recognized by the communications system as 10 button telephones.





Issue 1

August 1998

Page xxxiv


0

Release 4.2 includes all Release 4.1 functionality, plus the enhancements listed below. There are no hardware changes for Release 4.2.

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

Release 4.2 of the system supports connectivity to MCI

®

or local exchange carrier

(LEC) PRI services and to the following central office switch types (in addition to the 4ESS™ and 5ESS

®

switch types that carry for AT&T Switched Network services):

■ NORTEL

®

DMS™-100 BCS 36 for local exchange carrier services

■

■

NORTEL DMS-250 generic MCI07 serving the MCI network

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

Beginning with Release 4.2, the following MCI PRI and PRI local exchange carrier

(LEC) services (along with AT&T Switched Network Services) can be provided to users of the MERLIN LEGEND Communications System:

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

— MCI Prism

®

service for domestic outgoing long-distance and international voice calls; for domestic outgoing 56-kbps restricted,

64-kbps unrestricted, and 64-kbps restricted circuit-switched data calls

— MCI VNet

®

service for incoming and outgoing domestic and voice calls; for 56-kbps restricted, 64-kbps restricted, and 64-kbps unrestricted circuit-switched data calls

■

— MCI 800 for domestic, toll-free, incoming voice calls

— MCI 900 service numbers

LEC services for DMS-100 switch types:

— DMS Virtual Private Network service for calls between the MERLIN

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

— DMS INWATS (Inward Wide Area Telephone Service) for domestic toll-free incoming voice calls

— DMS OUTWATS (Outward Wide Area Telephone Service) for domestic outgoing long-distance voice calls

— DMS FX (foreign exchange) to provide local call rating for calls from the local exchange to the area serviced by the foreign exchange.





Issue 1

August 1998

Page xxxv

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

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 Field. For Auto Login and Auto Logout calling groups, the TALK field records the amount of time a calling group agent spends on a call.

■

■

DUR. (DURATION) Field. For Auto Login and Auto Logout calling groups, call timing begins when a call arrives at MERLIN LEGEND

Communications System and not after a preset number of seconds. Call timing ends when the call is disconnected; either the caller or the agent hangs up. This allows the system manager to determine how long a caller waited for an agent’s attention.

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

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

The call is answered by someone not a member of an Auto Login or

Auto Logout calling group.

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





Issue 1

August 1998

Page xxxvi

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 peakcall load. The SMDR Talk Time option sets up special call records used by

MERLIN LEGEND Reporter. The default is Off, in which case the Release 4.0

SMDR reports are available. If the option is set to On, the following new reports are provided:

■

■

Organization Detail Report

Organization Summary and Trends Report

■

■

■

■

Selection Detail Report

Account Code Report

Traffic Report

Extension Summary Report

■

■

■

■

■

Data Report

Talk and Queue Time Distribution Report

Time of Day Report

ICLID Call Distribution Report

Facility Grade of Service Report

Maintenance Enhancements 0

Change to Permanent Error Alarm 0

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

Installation, Programming, and Maintenance.

Enhanced Extension Information Report 0

Beginning with Release 4.2, the Extension Information Report includes the

Extension Status (ESS) and supervisory mode of each extension.





Issue 1

August 1998

Page xxxvii


0

Release 4.1 includes all Release 4.0 functionality, plus the enhancements listed below. There are no hardware changes in Release 4.1.

Coverage Timers Programmed for

Individual Extensions 0

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

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

■ The Primary Cover Ring Delay (1–6 rings) and Secondary Cover Ring

Delay (1–6 rings), programmed on individual extensions, replace the Delay

Ring Interval programmed systemwide in previous releases.

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

Night Service with Coverage Control 0

Beginning with Release 4.1, a system manager can enable the Night Service

Coverage Control option to automatically control the status of telephones programmed with Coverage VMS (voice messaging system) Off buttons, according to Night Service status.

When Coverage Control is enabled and the MERLIN LEGEND Communications

System is put into Night Service, all programmed Coverage VMS Off buttons are automatically turned off (LED is unlit) and all eligible outside calls are sent to the assigned voice messaging system calling group with normal ringing delay. When

Night Service is deactivated during the day, all programmed Coverage VMS Off buttons are automatically turned on (LED is lit) and voice mail coverage is disabled for outside calls.

Users can override the Coverage VMS Off button status at any time by pressing the programmed Coverage VMS Off button to turn the LED on or off.





Issue 1

August 1998

Page xxxviii

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.

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 (National Integrated Services Digital

Network-1 Basic Rate Interface) Provisioning Test Tool is enhanced to include testing for BRI facilities that are part of Multiline Hunt Groups (MLHGs).

The NI-1 BRI Provisioning Test Tool is used by Lucent Technologies maintenance personnel on MERLIN LEGEND Communications Systems that include a 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.




Release 4.0 Enhancements (March 1996)

Issue 1

August 1998

Page xxxix


(March 1996)

0


Support for Up to 200 Extensions 0

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

Support for National ISDN BRI Service 0

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

New Control Unit Modules 0

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

800 NI-BRI Module 0

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

016 Tip/Ring Module 0

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

Downloadable Firmware for the

016 and NI-BRI Modules 0

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





Issue 1

August 1998

Page xl

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-kpbs channels) or 128 kbps (using two

64-kbps B-channels). This feature is available for Hybrid/PBX and Key modes only.

Support for T1 Switched 56

Digital Data Transmission 0

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

Communications System with a Lucent Technologies DEFINITY

®

G1.1

Communications System or DEFINITY Enterprise Communications Server. The two communications systems can be co-located or at different sites.

Forwarding Delay Option 0

Each user can program a Forwarding Delay setting for the Forward, Remote Call

Forwarding, or Follow Me features. The forwarding delay is the number of times that a call rings at the forwarding extension before the call is sent to the receiver.

The delay period gives the original call recipient time to answer or to screen calls by checking the displayed calling number (if available). The delay can be set at 0 up to 9 rings. The factory setting for the forwarding delay is 0 rings (no delay).

Voice Announce on Queued Call Console 0

The system manager can enable the fifth Call button on a QCC console

(Hybrid/PBX mode only) to announce a call on another user’s speakerphone

(providing the destination telephone has a voice announce-capable SA button available). A QCC cannot receive voice-announced calls; they are received as ringing calls. The factory-set status for the fifth Call button is Voice Announce disabled.





Issue 1

August 1998

Page xli

Time-Based Option for

Overflow on Calling Group 0

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

Single-Line Telephone Enhancements 0

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

■

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

■

■

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

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

Seven-Digit Password for SPM 0

Release 4.0 has increased system security by requiring a 7-digit password for system managers or technicians who use SPM to perform programming or the

Trunk Test procedure. This password is for use in addition to a remote access barrier code.





Issue 1

August 1998

Page xlii


(March 1996)

0


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

*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 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 outside security measures that are implemented in Release

3.1 and later systems.





Issue 1

August 1998

Page xliii

Disallowed List Including Numbers Often

Associated with Toll Fraud 0

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

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.

!


Before removing restrictions, it is strongly recommended that you read

Appendix A, “Customer Support Information.”

Default Facility Restriction

Level (FRL) for VMI Ports 0

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

Default for the Default Local Table 0

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

New Maintenance Procedure for

Testing Outgoing Trunks 0

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





Issue 1

August 1998

Page xliv

!


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.

Prior Releases: Features and Enhancements. Lucent Technologies MERLIN LEGEND, MERLIN LEGEND Release 6.1

Prior Releases: Features and

Enhancements

Release 6.0 Enhancements

(February 1998)

Release 5.0 Enhancements (June 1997)

Release 4.2 Enhancements (June 1997)

Release 4.1 Enhancements (June 1997)

Release 4.0 Enhancements

(March 1996)

Release 3.1 Enhancements

(March 1996)

Related manuals

Table of contents

Prior Releases: Features and Enhancements. Lucent Technologies MERLIN LEGEND, MERLIN LEGEND Release 6.1

Prior Releases: Features and

Enhancements

Release 6.0 Enhancements

(February 1998)

Release 5.0 Enhancements (June 1997)

Release 4.2 Enhancements (June 1997)

Release 4.1 Enhancements (June 1997)

Release 4.0 Enhancements

(March 1996)

Release 3.1 Enhancements

(March 1996)

Related manuals

AT&T

MERLIN LEGEND Release 3.1

Lucent Technologies

555-670-116

Lucent Technologies

Marine Radio 6.1

Lucent Technologies

MERLIN LEGEND

AT&T

MERLIN LEGEND Release 3.1

AT&T

MERLIN LEGEND Release 3.0

Lucent Technologies

MERLIN LEGEND

AT&T

MERLIN LEGEND Release 3.1

Lucent Technologies

MERLIN LEGEND

AT&T

MERLIN LEGEND Release 3.0

AT&T

Merlin Legend BIS34D

Lucent Technologies

MERLIN LEGEND Release 5.0

Table of contents