Barge Overview
Barge allows a user to be added to a remotely active call that is on a shared line. Remotely active calls for a line are the active (connected) calls that are made to or from another device that shares a directory number with the line.
If you configure party entrance tone, a tone plays on the phone when a basic call changes to a barged call or cbarged call. In addition, a different tone plays when a party leaves the multiparty call.
Phones support Barge in the following conference modes:
-
Built-in conference bridge at the phone that is barged—This mode uses the Barge softkey. Most Cisco Unified IP Phones include the built-in conference bridge capability.
-
Shared conference bridge—This mode uses the cBarge softkey.
By pressing the Barge or cBarge softkey in the remote-in-use call state, the user is added to the call with all parties, and all parties receive a barge beep tone (if configured). If Barge fails, the original call remains active. If no conference bridge is available (built-in or shared), the barge request gets rejected, and a message displays on the Barge initiator device. When network or Unified Communications Manager failure occurs, the Barge call is preserved.
Note |
To display the softkey option for both Barge and cBarge, disable the Privacy option in Unified Communications Manager user interface for those devices that have shared line appearances. |
For a list of Cisco Unified IP Phones that support Barge, log in to Cisco Unified Reporting and run the Unified CM Phone Feature List report. Make sure to select Built In Bridge as the feature. For details, see Generate a Phone Feature List.
Single-Button Barge and Single-Button cBarge
The Single-Button Barge and Single-Button cBarge features allow a user to press the shared-line button of the remotely active call, to be added to the call. All parties receive a barge beep tone (if configured). If barge fails, the original call remains active.
Phones support Single-Button Barge and Single-Button cBarge in two conference modes:
-
Built-in conference bridge at the phone that is barged—This mode uses the Single-Button Barge feature.
-
Shared conference bridge—This mode uses the Single-Button cBarge feature.
By pressing the shared-line button of the remote-in-use call, the user is added to the call with all parties, and all parties receive a barge beep tone (if configured). If barge fails, the original call remains active. If no conference bridge is available (built-in or shared), the barge request gets rejected, and a message is displayed at the Barge initiator device.
Built-In Conference
When the user presses the Barge softkey or a shared-line button, a Barge call is set up by using the built-in conference bridge, if available. A built-in conference bridge is advantageous because neither a media interruption nor display changes to the original call occur when the Barge is being set up.
Shared Conference
When the user presses the cBarge softkey, or a shared-line button, a barge call is set up by using the shared conference bridge, if available. The original call is split and then joined at the conference bridge, which causes a brief media interruption. The call information for all parties changes to "Barge". The barged call becomes a conference call with the barge target device as the conference controller. It can add more parties to the conference or can drop any party. When any party releases the call, the remaining two parties experience a brief interruption and then get reconnected as a point-to-point call, which releases the shared conference resource.
Built-In and Shared Conference Differences
Feature |
Barge with Built-In Conference |
Barge with Shared Conference |
||
---|---|---|---|---|
|
Yes |
No |
||
A media break occurs during barge setup. |
No |
Yes |
||
If configured, a user receives a barge setup tone. |
Yes |
Yes |
||
Text displays at the barge initiator phone. |
To barge XXX |
To Conference |
||
Text displays at the target phone. |
To/From Other |
To Conference |
||
Text displays at the other phones. |
To/From Target |
To Conference |
||
Bridge supports a second barge setup to an already barged call. |
No |
Yes |
||
Initiator releases the call. |
No media interruption occurs for the two original parties. |
Media break occurs to release the shared conference bridge when only two parties remain and to reconnect the remaining parties as a point-to-point call. |
||
Target releases the call. |
Media break occurs to reconnect initiator with the other party as a point-to-point call. |
Media break occurs to release the shared conference bridge when only two parties remain and to reconnect the remaining parties as a point-to-point call. |
||
Other party releases the call. |
All three parties get released. |
Media break occurs to release the shared conference bridge when only two parties remain and to reconnect the remaining parties as a point-to-point call. |
||
Target puts call on hold and performs Direct Transfer, Join, or Call Park. |
Initiator gets released. |
Initiator and the other party remain connected. |