Lucent Technologies MERLIN LEGEND Release 5.0 System Programming Manual page 65

Communications system
Hide thumbs Also See for MERLIN LEGEND Release 5.0:
Table of Contents

Advertisement

MERLIN LEGEND Communications System Release 5.0
System Programming 555-650-111
1
Programming Basics
Product Enhancements
Release 2.1 Enhancements
Refer to Release 2.1 Notes for detailed descriptions of Release 2.1
enhancements. Release 2.1 includes all Release 2.0 functionality plus the
enhancements listed below.
Operational
System operational enhancements include the following:
When a call is forwarded to a multiline telephone that has an Auto Dial or
DSS button programmed for the forwarding telephone, the green light next
to the Auto Dial or DSS button for the forwarding telephone does not flash.
People answering calls received on Cover buttons are allowed to generate
touch tones if their telephones are not outward- or toll-restricted.
Calls received on personal lines with Do Not Disturb on go immediately to
coverage instead of waiting for the coverage delay interval.
A call put on hold at a Cover button can be added to a conference by
someone who has a personal line for the call.
A call put on hold at a Cover button can be picked up by any person who
has a personal line for the call.
Calls that have been put on hold at a Cover, SA, Shared SA, or Pool
button can be picked up by a person who has a personal line button for the
call.
An inside call on hold at an SA button can be picked up and transferred by
any person with a Shared SA button corresponding to the button with the
held call.
Calls that are on hold awaiting transfer can be picked up by any user who
has a personal line for the call.
Beginning with Integrated Solution III Version 1.2, the automatic
reconciliation program that was run automatically at 3:00 a.m. is disabled
and can be invoked manually from the User Maintenance menu.
If a telephone is programmed for Forced Account Code Entry, account
codes do not have to be entered when using a programmed Loudspeaker
Paging button. In addition, an SMDR record is not generated for calls made
to paging ports.
When an MLX telephone, other than an MLX-20L, is plugged into an MLX
port and the Personal Directory does not contain any entries, the allocation
of the Personal Directory resource is released. If there are any entries in
the Personal Directory, the Personal Directory allocation and the entries in
the Personal Directory are saved in the MLX port.
SMDR call records for calls made on PRI facilities are more accurate than
SMDR call records for calls made on non-PRI facilities. Outgoing calls
made on PRI facilities receive "answer supervision." Consequently, SMDR
timing for calls made on PRI facilities begins when the call is answered.
1
1
Issue 1
June 1997
Page 1-51

Advertisement

Table of Contents
loading

Table of Contents