Lucent Technologies Definity Enterprise Communication Server 8.2 User Manual
DEFINITY ECS Release 8.2
Administrator’s Guide
Administrator’s Guide
555-233-506
Issue 1
April 2000
Features and technical reference
1561
Transfer — Trunk-to-Trunk
20
To administer Trunk-to-Trunk Transfer system-wide, complete the
Feature-Related System Parameters screen. To restrict Trunk-to-Trunk Transfer
on a trunk-group basis, assign COR-to-COR calling-party restrictions on the Class
of Restriction (COR) screen. To allow individual users to control Trunk-to-Trunk
Transfers, assign capabilities on the Class of Service (COS) screen.
Feature-Related System Parameters screen. To restrict Trunk-to-Trunk Transfer
on a trunk-group basis, assign COR-to-COR calling-party restrictions on the Class
of Restriction (COR) screen. To allow individual users to control Trunk-to-Trunk
Transfers, assign capabilities on the Class of Service (COS) screen.
Considerations
■
Trunk-to-Trunk Transfer is particularly useful when a caller outside the
system calls a user or attendant and requests a transfer to another outside
number. For example, a worker, away on business, can call in and have the
call transferred elsewhere.
system calls a user or attendant and requests a transfer to another outside
number. For example, a worker, away on business, can call in and have the
call transferred elsewhere.
■
Transferred trunk calls can be administered to receive either music or
silence.
silence.
■
Some central office (CO) trunks do not signal the PBX when the CO user
disconnects from a call. The system ensures that incoming CO trunks
without Disconnect Supervision are not transferred to outgoing trunks or to
other incoming CO trunks without Disconnect Supervision.
disconnects from a call. The system ensures that incoming CO trunks
without Disconnect Supervision are not transferred to outgoing trunks or to
other incoming CO trunks without Disconnect Supervision.
■
An attendant-assisted call connecting an outgoing trunk or incoming trunk
without Disconnect Supervision to an outgoing trunk must be held on the
console. The system does not allow the attendant to release the call. The
attendant can, however, use the Forced Release button and disconnect all
parties associated with the call.
without Disconnect Supervision to an outgoing trunk must be held on the
console. The system does not allow the attendant to release the call. The
attendant can, however, use the Forced Release button and disconnect all
parties associated with the call.
■
If a user has connected two outgoing trunks or an outgoing call and an
incoming call without Disconnect Supervision, the user must remain on the
call. Otherwise, the call is dropped. An incoming trunk with Disconnect
Supervision can be connected to an outgoing trunk without the user
remaining on the call. An incoming trunk can also be connected to another
incoming trunk without the user remaining on the call if one of the
incoming trunks has Disconnect Supervision.
incoming call without Disconnect Supervision, the user must remain on the
call. Otherwise, the call is dropped. An incoming trunk with Disconnect
Supervision can be connected to an outgoing trunk without the user
remaining on the call. An incoming trunk can also be connected to another
incoming trunk without the user remaining on the call if one of the
incoming trunks has Disconnect Supervision.
Interactions
■
Attendant Lockout
Attendant Lockout does not function on Trunk-to-Trunk Transfer.
■
Call Vectoring
Station control of Trunk-to-Trunk Transfer does not affect routing of
incoming trunks to a VDN that ultimately routes to a destination off-net.
incoming trunks to a VDN that ultimately routes to a destination off-net.
A route to a number off the switch does not require you to enable
trunk-to-trunk transfer.
trunk-to-trunk transfer.