Avaya Communication Manager, Руководство администратора, Страница: 1394 / 1854

Feature Reference
Bridged call appearance
1394 Administrator’s Guide for Avaya Communication Manager
November 2003
When the primary telephone user is active on a call, and no other bridging user is active on
the call, that call can be placed on hold by the primary telephone user utilizing normal
single-line conference procedures. Any attempt by a bridging user to bridge onto the call
during a successful conference attempt is denied.
A bridging user, alone on a bridged call, can conference the call utilizing the normal
multiappearance telephone conference procedures. Any attempt by the analog primary
telephone user to bridge onto the call during a successful conference attempt is ignored.
Any attempt by other bridging users is denied (standard denial response is returned to the
bridged appearance).
If a conference is not allowed because of the preceding limitations, the user can
accomplish a transfer by asking an internal nonbridged party in the connection to create
the conference, or asking the remaining bridging users and primary user to disconnect so
that the conference can be completed. At completion of the conference, the parties that left
the call can reenter the call if control of the conference remains with the primary
telephone. If control of the conference does not remain with the primary telephone, the
bridging user must conference the primary telephone and the bridging user back into the
call as required.
If the bridging user has no other available bridged appearances of the primary extension
(other than the one he or she is currently on), the bridging user, after pressing the
conference/transfer button, must select a call appearance to be used for the conference,
before dialing the number.
— Multiappearance telephones
Call Waiting Termination applies only to an active call on the primary telephone that has
no one else bridged on. If one or more bridging users are active on a call, Call Waiting
calls are denied whether or not the primary user is also off-hook on the call. A bridging
user cannot bridge onto a call with the primary user if there is also a call waiting.
Conferences can be set up on bridged appearances using the usual conference operations.
Either a primary extension button or a bridged appearance button can be used to make the
calls for adding to the conference.
You can administer the system to automatically select the first idle appearance if there is
no idle appearance with an extension matching the extension that is conferencing the call.
When the user presses the conference button (the second time) to connect the parties
together, the newly formed conference call appears on the primary or bridged appearance
to which the user was connected at the time of that last conference button depression. The
other appearance is disassociated from the conference call. Therefore, if the original call is
on a bridged appearance, and the conference is formed on an appearance of the bridged
user’s own primary extension, the bridged extension becomes disassociated from the
conference call and the principal user of that bridged extension can no longer bridge onto
the conference.
This disassociation of the conference from the bridged extension can be avoided by setting
up the conference in the opposite order. To do this, the user:
1
Presses the hold button to hold the original call on the bridged appearance
2
Selects a call appearance and calls the party to be added
3
Presses the conference or transfer button
4
Selects the held bridged appearance
5
Presses the conference button (again)