-
Cisco Unified CallManager Features and Services Guide, Release 4.2(1)
-
Index
-
Preface
-
Cisco CallManager Extension Mobility
-
Cisco IP Manager Assistant With Proxy Line Support
-
Cisco IP Manager Assistant With Shared Line Support
-
Cisco Call Back
-
Client Matter Codes and Forced Authorization Codes
-
Music On Hold
-
Cisco CallManager AutoAttendant
-
Barge, Privacy, and Privacy on Hold
-
Call Park and Directed Call Park
-
Immediate Divert
-
Malicious Call Identification
-
Multilevel Precedence and Preemption
-
Custom Phone Rings
-
Cisco WebDialer
-
Cisco CallManager Attendant Console
-
Call Display Restrictions
-
Quality Report Tool
-
External Call Transfer Restrictions
-
Cisco CallManager Device Mobility
-
Troubleshooting Features and Services
-
Feedback
Table Of Contents
Barge, Privacy, and Privacy on Hold
Introducing Barge, Privacy, and Privacy on Hold
Barge Using Built-In Conference—Barge Softkey
Barge Using Shared Conference—cBarge Softkey
System Requirements for Barge, Privacy, and Privacy on Hold
Upgrading to Cisco CallManager Release 4.0 or Later
Installing and Activating Barge, Privacy, and Privacy on Hold
Activating Barge with Built-In Conference Bridge
Activating cBarge with Shared Conference Bridge
Configuring Barge, Privacy, and Privacy on Hold
Privacy and Privacy on Hold Configuration Checklist
Setting the Service Parameters for Barge, Privacy, and Privacy on Hold
Troubleshooting Barge and Privacy
Where to Find More Information
Barge, Privacy, and Privacy on Hold
The Barge, Privacy, and Privacy on Hold features work with each other. These features work with only shared lines.
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.
The administrator enables or disables privacy and privacy on hold features. Privacy must be enabled for a device to activate privacy on hold. Users toggle the privacy feature on or off.
When privacy is enabled, the system removes the call information from all phones that share lines and blocks other shared lines from barging in on its calls. When privacy is disabled, the system displays call information on all phones that have shared line appearances and allows other shared lines to barge in on its calls.
The privacy on hold feature preserves privacy when a private call on a shared line is put on hold. When privacy on hold is enabled, the calling name and number that are blocked when privacy is enabled remain blocked when the call is put on hold, and the system blocks other shared lines from resuming the held call. When privacy on hold is disabled and a private call is put on hold, the system displays calling name and number on all phones that have shared line appearances and allows other shared lines to resume the held call.
If privacy on hold is enabled, users can activate the feature while the call is on hold by toggling privacy on; likewise, users can deactivate privacy on hold by toggling privacy off while the call is on hold. If privacy on hold is disabled, toggling privacy on or off does not affect the held call.
If a private call is put on hold, retrieved at the same phone, and privacy is then toggled off, the system displays the call information on all phones that have shared line appearances but does not allow another phone to resume or barge the held call.
Administrators can configure privacy for all devices or for each device. Administrators configure privacy on hold for the cluster.
This chapter provides the following information about barge and privacy:
•
Introducing Barge, Privacy, and Privacy on Hold
•
•
•
•
•
•
•
Introducing Barge, Privacy, and Privacy on Hold
The following sections describe Barge and Privacy.
Barge
Barge allows a user to get added to a remotely active call that is on a shared line. Remotely active calls for a line comprise active (connected) calls that are made to or from another device that shares a directory number with the line. Barge supports this type of remote-in-use call.
Phones support barge in two conference modes:
•
•
By pressing the Barge or cBarge softkey in the remote in use call state, the user gets added to the call with all parties, and all parties receive a barge beep tone (if configured). If barge fails, the original call and status remain active.
If no conference bridge is available (built-in or shared), the barge request gets rejected, and a message displays at the barge initiator device.
Table 8-1 describes the differences between barge with built-in conference bridge and shared conference.
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.
Note
The following settings activate or deactivate the built-in conference bridge:
•
•
Note
For more information, refer to the "Configuring Barge, Privacy, and Privacy on Hold" section.
Related Topics
•
•
•
Barge Using Shared Conference—cBarge Softkey
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.
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 from the call, which leaves only two parties in the conference, the remaining two parties experience a brief interruption and then get reconnected as a point-to-point call, which releases the shared conference resource.
For more information, see the "Configuring Barge, Privacy, and Privacy on Hold" section.
Related Topics
•
•
Privacy
With privacy, administrators can enable or disable the capability of users with phones that share the same line (DN) to view call status and to barge the call. Administrators enable or disable privacy for each phone or for all phones in the cluster.
By default, the system enables Privacy for all phones in the cluster. To enable all phones with Privacy, ensure the clusterwide service parameter is set to True and the phone privacy setting is set to default.
To configure certain phones with access to privacy, administrators perform the following steps to enable or disable privacy:
•
•
•
•
When the device that is configured for privacy registers with Cisco CallManager, the feature button on the phone that is configured with privacy gets labeled, and the status shows through an icon. If the button has a lamp, it lights.
When the phone receives an incoming call, the user makes the call private (so the call information does not display on the shared line) by pressing the Privacy feature button. The Privacy feature button toggles between on and off.
Note
Related Topics
•
•
•
•
Privacy on Hold
With the privacy on hold feature, administrators can enable or disable the capability of users with phones that share the same line (DN) to view call status and retrieve calls on hold.
Administrators enable or disable privacy on hold for all phones in the cluster. To enable privacy on hold, the administrator must also enable the privacy feature for the phone or for all phones. Privacy on hold activates automatically on all private calls when privacy on hold is enabled.
By default, the system disables privacy on hold for all phones in the cluster. To enable all phones with privacy on hold, set the clusterwide Privacy service parameter to True, set the clusterwide Enforce Privacy Setting on Held Calls service parameter to True, and leave the phone privacy setting to default.
To configure certain phones with access to privacy on hold, administrators set the the Enforce Privacy Setting on Held Calls service parameter to True and set the Privacy setting for the phone to True:
•
•
•
•
•
To activate privacy on hold, users press the Hold softkey while on a private call. To return to the call, users press the Resume softkey. The phone that put the call on hold displays the status indicator for a held call; shared lines display the status indicators for a private and held call.
Related Topics
•
•
•
•
System Requirements for Barge, Privacy, and Privacy on Hold
Barge and privacy require the following software component to operate:
•
Privacy on hold requires the following software component to operate:
•
The following phones support barge by using the Barge or cBarge softkey in any Cisco CallManager softkey template:
•
Note
The following phones support privacy with the Privacy button on the phone button template:
•
The following phones support the built-in conference bridge capability:
•
Note
Interactions and Restrictions
The following sections describe the interactions and restrictions for barge, privacy, and privacy on hold:
Interactions
The following sections describe how barge and privacy interact with Cisco CallManager applications and call processing:
•
Barge and cBarge
Cisco recommends that you assign either the Barge or cBarge softkey to a softkey template. By having only one of these softkeys for each device, you can avoid confusion for users and potential performance issues.
Upgrading to Cisco CallManager Release 4.0 or Later
When a Cisco CallManager database that contains the BargeEnabled parameter is upgraded from Cisco CallManager Release 3.3 to Release 4.0 or later, the system configures the privacy settings opposite the BargeEnabled setting.
Barge and Call Park
When the target parks the call, the barge initiator gets released (if using the built-in bridge), or the barge initiator and the other party remain connected (if using the shared conference).
Barge and Join
When the target joins the call with another call, the barge initiator gets released (if using the built-in bridge), or the barge initiator and the other party remain connected (if using the shared conference).
Restrictions
The following restrictions apply to barge:
•
•
•
•
•
•
If the initiator phone is configured for encryption, the barge initiator can barge into an authenticated or nonsecure call from the encrypted phone. After the barge occurs, Cisco CallManager classifies the call as nonsecure.
If the initiator phone is configured for encryption, the barge initiator can barge into an encrypted call, and the phone indicates that the call state equals encrypted.
A user can barge into an authenticated call, even if the phone that is used to barge is nonsecure. The authentication icon continues to display on the authenticated devices in the call, even if the initiator phone does not support security.
Tip
•
A message displays in Cisco CallManager Administration when you attempt the following configuration:
–
–
–
The following restrictions apply to privacy:
•
•
The following restriction applies to built-in conference bridge:
•
•
The following restrictions apply to privacy on hold:
•
Installing and Activating Barge, Privacy, and Privacy on Hold
Barge, privacy, and privacy on hold system features come standard with Cisco CallManager software. The administrator activates the features after installation to make them available for system use. The following sections provide information about activating the features:
•
•
Activating Barge with Built-In Conference Bridge
To activate barge with built-in conference bridge, add the Barge softkey to a softkey template, assign the softkey template to a device, set the Built-in Bridge Enable service parameter to On, and set the party entrance tone to True. See the "Barge Configuration Checklist" section for details.
Note
Activating cBarge with Shared Conference Bridge
To activate barge with shared conference bridge, add the cBarge softkey to a softkey template, assign the softkey template to a device, and set the party entrance tone to True. See the "Barge Configuration Checklist" section for details.
Activating Privacy
The system automatically activates privacy in the Cisco CallManager cluster because the Privacy Setting service parameter is set to True and the phone has the Privacy setting at Default. The administrator must also add privacy to a phone button template and assign the phone button template to a device. See the "Privacy and Privacy on Hold Configuration Checklist" section for details.
Activating Privacy on Hold
The system automatically activates privacy on hold in the Cisco CallManager cluster when the Enforce Privacy Setting on Held Calls service parameter is set to True and the phone has the privacy feature configured. See the "Privacy and Privacy on Hold Configuration Checklist" section for details.
Configuring Barge, Privacy, and Privacy on Hold
This section contains the following information:
•
•
•
Barge Configuration Checklist
Table 8-2 provides a checklist to configure barge with built-in conference bridge.
Table 8-2 Barge with Built-In Conference Bridge Configuration Checklist
Step 1
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.
Configuring Cisco IP Phones, Cisco CallManager Administration Guide
Step 2
Set the following optional Cisco CallManager service parameters:
•
Note
•
Configuring Service Parameters for a Service on a Server, Cisco CallManager Administration Guide
Configuring Cisco IP Phones, Cisco CallManager Administration Guide
Step 3
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.
Adding a New User, Cisco CallManager Administration Guide
Step 4
Notify users that the barge feature is available.
Refer to the phone documentation for instructions on how users access barge on their Cisco IP Phone.
Table 8-3 provides a checklist to configure barge with shared conference bridge.
Table 8-3 Barge with Shared Conference Bridge (cBarge) Configuration Checklist
Step 1
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.
Configuring Cisco IP Phones, Cisco CallManager Administration Guide
Step 2
Set the optional clusterwide service parameter Party Entrance Tone to True (required for tones).
Configuring Service Parameters for a Service on a Server, Cisco CallManager Administration Guide
Step 3
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.
Adding a New User, Cisco CallManager Administration Guide
Step 4
Notify users that the cBarge feature is available.
Refer to the phone documentation for instructions on how users access cBarge on their Cisco IP Phone.
Privacy and Privacy on Hold Configuration Checklist
Table 8-4 provides a checklist to configure privacy.
Table 8-4 Privacy Configuration Checklist
Step 1
If all phones in the cluster need access to privacy, keep the setting of the Privacy Setting clusterwide service parameter to True (default) and keep the Privacy field in the Phone Configuration window to Default. Continue with the following steps.
If only certain phones in the cluster need access to privacy, set the Privacy Setting service parameter to False and set the Privacy field in the Phone Configuration window to On. Continue with the following steps.
Configuring Service Parameters for a Service on a Server, Cisco CallManager Administration Guide
Configuring Cisco IP Phones, Cisco CallManager Administration Guide
Step 2
For each phone button template that has privacy, add privacy to one of the feature buttons (some phone models use the Private button).
Phone Button Template Configuration, Cisco CallManager Administration Guide
Step 3
For each phone user that wants privacy, choose the phone button template that contains the Privacy feature button.
Configuring Cisco IP Phones, Cisco CallManager Administration Guide
Step 4
In the User Configuration window, for each user that does not want information about the shared-line appearances to display, associate the device that has the Privacy feature button that is assigned to it.
Adding a New User, Cisco CallManager Administration Guide
Step 5
To configure the optional privacy on hold feature, set the Enforce Privacy Setting on Held Calls service parameter to True.
Configuring Service Parameters for a Service on a Server, Cisco CallManager Administration Guide
Step 6
Notify users that the privacy feature and the privacy on hold feature (if configured) are available.
Refer to the phone documentation for instructions on how users access privacy on their Cisco IP Phone.
Setting the Service Parameters for Barge, Privacy, and Privacy on Hold
Cisco CallManager provides four clusterwide service parameters: Built In Bridge Enable for the built-in conference bridge capability, Privacy Setting for the Privacy feature, Enforce Privacy Setting on Held Calls setting for the privacy on hold feature, and Party Entrance Tone for the tones that are played during barge.
•
•
If the Privacy field in the Phone Configuration window is set to default, the phone uses the setting that is configured in the Privacy Setting service parameter.
•
•
Troubleshooting Barge and Privacy
For information about troubleshooting tools, messages, and how to recover from barge problems, refer to "Troubleshooting Features and Services."
Where to Find More Information
Related Topics
•
•
•
•
•
Additional Cisco Documentation
•
•
•
