With legacy PABX, it was possible to a phone user that have the needed priviledges (attendant/assistant for example) , to join an ongoing call in order to tell one of the call peers that he should hang up because of an emergency waiting call for example.
Is this option available in CUCM 6.1 ? if yes how to configure it ?
This is the closest feature. Barge adds a user to a call that is in progress. Pressing a softkey automatically adds the user (initiator) to the shared-line call (target), and the users currently on the call receive a tone (if configured). Barge supports built-in conference and shared conference bridges.
Barge and cBarge can only be used with "Shared Lines" on IP Phones. Here is the related info;
Barge Using Built-In Conference-Barge Softkey
You can use the Barge softkey only in the remote-in-use call state. A built-in conference bridge proves advantageous because neither a media interruption nor display changes to the original call occur when the barge is being set up. A spinning circle displays at the right side of the prompt status message window at the target device.
When the barge initiator releases the call, the barge call gets released between the barge initiator and target. The original call between the target device and the other party remains active. A barge disconnect tone (beep beep) plays to all remaining parties.
When the target device releases the call, the media between the barge initiator and the other party gets dropped briefly and then reconnects as a point-to-point call. The display changes at the barge initiator device to reflect the connected party.
When the other party releases the call, both the original call and the barge call get released.
When the barge initiator puts the call on hold, both the target device and the other party remain in the call.
When the target device puts the call on hold or in a conference or transfers it, the barge initiator gets released from the barge call while the original call also gets put on hold, in a conference, or transferred. The barge initiator can barge into a call again after the media gets reestablished at the target.
When the other party puts the call on hold or in a conference or transfers it, both the target device and the barge initiator remain in the call.
When network or Cisco CallManager failure occurs, the barge call gets preserved (like all active calls).
Some Cisco IP Phones (such as Model 7940 and 7960) have the built-in conference bridge capability, which barge uses.
The following settings activate or deactivate the built-in conference bridge:
â¢Enable or disable the built-in bridge by setting the Cisco CallManager clusterwide service parameter, Built-in Bridge Enable, to On or Off.
â¢Enable or disable the built-in bridge for each device by using the Built In Bridge drop-down list box in the Phone Configuration window (choose on, off, or default). On or off override the Built-in Bridge Enable service parameter.
Note To use barge with a built-in bridge, ensure the preceding items are enabled, Privacy is disabled, and the Barge softkey is assigned to each device. Otherwise, to use shared conference bridge, assign the cBarge softkey to each device.
Barge with Built-In Conference Bridge Configuration Checklist
Assign the Standard User or Standard Feature softkey template (both contain the Barge softkey) to each device that accesses Barge by using the built-in conference bridge.
Set the following optional Cisco CallManager service parameters:
â¢To enable Barge for all users, set the Built-In Bridge Enable clusterwide service parameter to On
Note If this parameter is set to Off, configure Barge for each phone by setting the Built in Bridge field in Phone Configuration
â¢Set the Party Entrance Tone clusterwide service parameter to True (required for tones)
In the User Configuration window for each user that is allowed to access the Barge with built-in conference bridge feature, associate the device that has the Barge softkey template that is assigned to it.
You can use the cBarge softkey only in the remote-in-use call state. No standard softkey template includes the cBarge softkey. To access the cBarge softkey, the administrator adds it to a softkey template and then assigns the softkey template to a device.
When cBarge gets pressed, a barge call gets set up by using the shared conference bridge, if available. The original call gets split and then joined at the conference bridge, which causes a brief media interruption. The call information for all parties gets changed to Barge.
Barge with Shared Conference Bridge (cBarge) Configuration Checklist
Assign the Standard User or Standard Feature softkey template (you configure cBarge to either template) to each device that accesses Barge by using the shared conference bridge.
Set the optional clusterwide service parameter Party Entrance Tone to True (required for tones).
In the User Configuration window for each user that is allowed to access the cBarge with shared conference bridge feature, associate the device that has the cBarge softkey template that is assigned to it.
Notify users that the cBarge feature is available.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...