/mcpC H A P T E R 40 Barge • Barge Overview, on page 517 • Barge Configuration Task Flow, on page 519 • Barge Interactions, on page 526 • Barge Restrictions, on page 527 • Barge Troubleshooting, on page 527 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. 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. Note 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, on page 5. Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 517