Lucent Technologies 5 User Manual
MERLIN LEGEND Communications System Release 5.0
System Manager’s Guide
System Manager’s Guide
555-650-118
Issue 1
June 1997
New Features and Enhancements
Page xvi
Release 5.0 Enhancements
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.
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.
NOTES:
1.
The NetWare server software version must be 3.12, 4.1, or 4.11.
2.
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.
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:
user’s analog multiline or MLX telephone’s SA buttons. Basic call control includes:
■
Answering calls arriving on an SA button
■
Making calls from an SA button
■
Hanging up calls
■
Hold and retrieving a call on hold at the user’s extension
NOTE:
Transfer and 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.
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.
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