Lucent Technologies MERLIN LEGEND Release 6.1 Feature Reference page 244

MERLIN LEGEND Communications System Release 6.1
Feature Reference 555-661-110
Features
CTI (Computer Telephony Integration) Link
You cannot program a CTI link port on an MLX module with firmware vintage 29.
Use an earlier or later vintage.
Because CTI link programming requires that you busy-out the control unit slot
where the MLX module with the CTI link is being added or removed, either you
must use SPM software to program the CTI link, or the link must be located on a
different module from the one where the system programming MLX-20L console
is connected. The busy-out programming procedure is available from the system's
Maintenance menu. For details about busying-out a slot in the control unit, see the
System Manager's Guide .
An extension programmed as a CTI link should not be used as a phantom
extension—an extension that does not serve equipment plugged into the system
but used for a special purpose, for example, coverage by a voice messaging
system.
In Release 6.0 and later systems, if a PassageWay Telephony Services client
extension with a call on an analog Centrex loop-start line attempts either to
conference or to transfer to an extension with Centrex Transfer via Remote Call
Forwarding activated, the call is immediately transferred without consultation,
regardless of the user's intentions. The originator is disconnected.
Private Network Operation (Release 6.0 and
Later Systems Only)
Operation for non-local extension calls in CTI-linked PassageWay Telephony
Services applications depends upon the application implementation as well as the
type of private networked trunk (PRI, analog tie, or T1 tie) that carries calls
between the systems, according to the following rules:
For an outgoing call, if the PassageWay Telephony Services application
uses the length of a destination telephone number in order to differentiate
PSTN calls from UDP calls, a PassageWay Telephony Services client
displays a non-local extension call in the same way as it does inside calls.
For an outgoing call, if the PassageWay Telephony Services application
uses receipt of the Network Reached event to differentiate PSTN calls from
inside calls, a PassageWay Telephony Services client displays a non-local
extension call or other UDP-routed call in the same way it does an outside
call made to the public switched telephone network.
For an incoming call, if the PassageWay Telephony Services application
uses the length of ANI information to differentiate PSTN calls from UDP
calls, a PassageWay Telephony Services client displays a non-local UDP
call as an inside call.
For an incoming call, if the PassageWay Telephony Services application
uses the presence of a trunk identifier in the delivered event to differentiate
PSTN calls from UDP calls, a PassageWay Telephony Services client
displays a non-local UDP call in the same way it does a PSTN call.
Issue 1
August 1998
Page 195