Conference Disconnect; Call Transfer During Conference - Nortel Meridian Meridian 1 Feature Description And Administration

Page 1674 of 1814

Conference disconnect

Call Transfer during Conference

Operating parameters
Feature interactions
553-2901-301 Standard 9.00 January 2002
ISDN BRI features
• the B-channel to which the Conference Controller is connected can be
used to complete the conference
• both calls are not conference calls
If the controller requests a disconnect signal, the network disconnects the
entire conference if:
• only one party will remain after the controller disconnects
• none of the calls that will remain has been answered
• only two parties remain and both are outgoing trunk calls
• more than two parties remain and all are trunk calls
Otherwise, only the controller is disconnected and the rest of the conferees
remain.
Using the Conference feature, a Call Transfer can be achieved in the
following way:
Ann makes a call to Bob. Bob answers the call and conferences Carl. After
Carl answers the call, Bob completes the conference. Then Bob can
disconnect himself from the conference, thus transferring Ann to Carl.
The same conditions that determine whether the remaining parties in a
conference should be dropped when one party disconnects from the
conference apply here. For example, Bob makes a call to Ann. Then Bob
conferences in Carl. If both Ann and Carl are on a remote node (that is, both
calls made by Bob to Ann and Carl are outgoing trunk calls), then as Bob
disconnects from the conference, both Ann and Carl will be dropped as well.
Call Transfer cannot be achieved in this scenario.
There are no operating parameters associated with this feature.
There are no feature interactions associated with this feature.