Cisco Unified CallManager Features and Services Guide, Release 4.2(3)
Barge, Privacy, and Privacy on Hold
Downloads: This chapterpdf (PDF - 271.0KB) The complete bookPDF (PDF - 5.71MB) | Feedback

Barge, Privacy, and Privacy on Hold

Table Of Contents

Barge, Privacy, and Privacy on Hold

Introducing Barge, Privacy, and Privacy on Hold

Barge

Barge Using Built-In Conference—Barge Softkey

Barge Using Shared Conference—cBarge Softkey

Privacy

Privacy on Hold

System Requirements for Barge, Privacy, and Privacy on Hold

Interactions and Restrictions

Interactions

Barge and cBarge

Upgrading to Cisco Unified CallManager Release 4.0 or Later

Barge and Call Park

Barge and Join

Restrictions

Installing and Activating Barge, Privacy, and Privacy on Hold

Activating Barge with Built-In Conference Bridge

Activating cBarge with Shared Conference Bridge

Activating Privacy

Activating Privacy on Hold

Configuring Barge, Privacy, and Privacy on Hold

Barge Configuration Checklist

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

System Requirements for Barge, Privacy, and Privacy on Hold

Interactions and Restrictions

Installing and Activating Barge, Privacy, and Privacy on Hold

Configuring Barge, Privacy, and Privacy on Hold

Setting the Service Parameters for Barge, Privacy, and Privacy on Hold

Troubleshooting Barge and Privacy

Where to Find More Information

Introducing Barge, Privacy, and Privacy on Hold

The following sections describe Barge and Privacy.

Barge

Privacy

Privacy on Hold

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:

Built-in conference bridge at the target device (the phone that is being barged). This mode uses the Barge softkey.

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 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.

Table 8-1 Built-In and Shared Conference Bridge Differences 

Action
Using Barge Softkey (Built-In Conference Bridge at Target Device)
Using cBarge Softkey (Shared Conference Bridge)

The standard softkey template includes the softkey.

Yes

No

A media break occurs during barge setup.

No

Yes

User receives a barge setup tone, if configured.

Yes

Yes

To Conference displays as the name at the barge initiator phone.

To Barge XXX

To Conference

To Conference displays as the name at the target phone.

To/From Other

To Conference

To Conference displays as the name at the other phones.

To/From Target

To Conference

A spinning circle displays on the right side of prompt status message at the target device.

Yes

No

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.


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 Unified CallManager failure occurs, the barge call gets preserved (like all active calls).

Some Cisco Unified IP Phones (such as Model 7940 and 7960) have the built-in conference bridge capability, which barge uses.


Note Cisco Unified IP Phone models 7940 and 7960 cannot support two media stream encryptions or SRTP streams simultaneously. To prevent instability due to this condition, the system automatically disables the built-in bridge for Cisco Unified IP Phone models 7940 and 7960 when the device security mode is set to encrypted. For more information, refer to the Cisco Unified CallManager Security Guide.


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. Choosing default uses the setting of the 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.


For more information, refer to the "Configuring Barge, Privacy, and Privacy on Hold" section.

Related Topics

Configuring Service Parameters for a Service on a Server, Cisco Unified CallManager Administration Guide

Configuring Cisco Unified IP Phones, Cisco Unified CallManager Administration Guide

Softkey Template Configuration, Cisco Unified CallManager Administration Guide

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

Softkey Template Configuration, Cisco Unified CallManager Administration Guide

Configuring Cisco Unified IP Phones, Cisco Unified CallManager Administration Guide

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:

Set a service parameter.

Set the phone privacy setting to On.

Add Privacy button to phone button template.

Add the phone button template that has Privacy button to each device.

When the device that is configured for privacy registers with Cisco Unified 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 When a Cisco Unified CallManager database that contains the BargeEnabled parameter is upgraded from Cisco CallManager Release 3.3 to Release 4.0 or later, the system resets the privacy settings opposite the BargeEnabled setting.


Related Topics

Privacy and Privacy on Hold Configuration Checklist

Configuring Service Parameters for a Service on a Server, Cisco Unified CallManager Administration Guide

Adding Phone Button Templates, Cisco Unified CallManager Administration Guide

Configuring Cisco Unified IP Phones, Cisco Unified CallManager Administration Guide

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:

Set the Enforce Privacy Setting on Held Calls service parameter to True.

Set a Privacy service parameter.

Set the phone privacy setting to On.

Add Privacy button to phone button template.

Add the phone button template that has Privacy button to each device.

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

Privacy and Privacy on Hold Configuration Checklist

Configuring Service Parameters for a Service on a Server, Cisco Unified CallManager Administration Guide

Adding Phone Button Templates, Cisco Unified CallManager Administration Guide

Configuring Cisco Unified IP Phones, Cisco Unified CallManager Administration Guide

System Requirements for Barge, Privacy, and Privacy on Hold

Barge and privacy require the following software component to operate:

Cisco Unified CallManager 4.0 or later

Privacy on hold requires the following software component to operate:

Cisco Unified CallManager 4.2 or later

The following phones support barge by using the Barge or cBarge softkey in any Cisco Unified CallManager softkey template:

Cisco Unified IP Phone Models 7905, 7912, 7920, 7940, 7960, 7970


Note Cisco Unified IP Phone Models 7905 and 7912 support cBarge only.


The following phones support privacy with the Privacy button on the phone button template:

Cisco Unified IP Phone Models 7905, 7912, 7940, 7960, 7970

The following phones support the built-in conference bridge capability:

Cisco Unified IP Phone Models 7940, 7960, 7970


Note If the phone does not support a Privacy button, by default, the privacy for that phone remains Off (all devices sharing a line with that phone will display the phone information).


Interactions and Restrictions

The following sections describe the interactions and restrictions for barge, privacy, and privacy on hold:

Interactions

Restrictions

Interactions

The following sections describe how barge and privacy interact with Cisco Unified CallManager applications and call processing:

Barge and cBarge

Upgrading to Cisco Unified CallManager Release 4.0 or Later

Barge and Call Park

Barge and Join

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 Unified CallManager Release 4.0 or Later

When a Cisco Unified 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:

To enhance performance, disable built-in bridge or turn on privacy for those devices that do not have shared-line appearances or do not use barge.

CTI does not support barge through APIs that TAPI/JTAPI applications invoke. CTI generates events for barge when it is invoked manually from an IP phone by using the Barge or cBarge softkey.

Cisco recommends that you do not configure cBarge for a user who has barge configured. Choose only one barge method for each user.

The original call requires G.711 codec. If G.711 is not available, use cBarge instead.

You can assign a softkey template, containing the Barge softkey, to any IP phone that uses softkeys; however, some IP phone models do not support the barge feature (Cisco Unified IP Phone Model 7905 and Model 7912 support cBarge only).

A Cisco Unified IP Phone 7970 user cannot barge into an encrypted call if the Cisco Unified IP Phone 7970 that is used to barge is not configured for encryption. When barge fails in this case, a busy tone plays on the phone where the user initiated the 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 Unified 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 You can configure cbarge if you want barge functionality, but Cisco Unified CallManager automatically classifies the call as nonsecure.


If you configure encryption for Cisco Unified IP Phone models 7960 and 7940, those encrypted devices cannot accept a barge request when they are participating in an encrypted call. When the call is encrypted, the barge attempt fails. A tone plays on the phone to indicate that the barge failed.

A message displays in Cisco Unified CallManager Administration when you attempt the following configuration:

In the Phone Configuration window, you choose Encrypted for the Device Security Mode (or System Default equals Encrypted), On for the Built In Bridge setting (or default setting equals On), and you click Insert or Update after you create this specific configuration.

In the Enterprise Parameter window, you update the Device Security Mode parameter.

In the Service Parameter window, you update the Built In Bridge Enable parameter.

The following restrictions apply to privacy:

To enhance performance, disable built-in bridge or turn on privacy for those devices that do not have shared-line appearances or do not use barge.

CTI does not support privacy through APIs that TAPI/JTAPI applications invoke. CTI generates events when privacy gets enabled or disabled from an IP phone by using the Privacy feature button.

The following restriction applies to built-in conference bridge:

To enhance performance, disable built-in bridge or turn on privacy for those devices that do not have shared-line appearances or do not use barge.

The initiator cannot park a call, redirect a call, or use any feature that is using the CTI/JTAPI/TSP interface. The system supports only hold and unhold.

The following restrictions apply to privacy on hold:

CTI does not support privacy on hold through APIs that TAPI/JTAPI applications invoke. CTI generates events when a privacy-enabled call is put on hold and when privacy gets enabled or disabled on held calls from an IP phone by using the Privacy feature button.

Installing and Activating Barge, Privacy, and Privacy on Hold

Barge, privacy, and privacy on hold system features come standard with Cisco Unified 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

Activating cBarge with Shared Conference Bridge

Activating Privacy

Activating Privacy on Hold

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 To set barge with built-in conference bridge for all users, set the Built-in Bridge Enable service parameter to On. To set barge with built-in conference bridge for individual users, set the Built in Bridge field to On in the Phone Configuration window.


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 Unified 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 Unified 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

Privacy and Privacy on Hold Configuration Checklist

Setting the Service Parameters for Barge, Privacy, and Privacy on Hold

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 

Configuration Steps
Related Procedures and Topics

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 Unified IP Phones, Cisco Unified CallManager Administration Guide

Step 2 

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).

Configuring Service Parameters for a Service on a Server, Cisco Unified CallManager Administration Guide

Configuring Cisco Unified IP Phones, Cisco Unified 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 Unified 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 Unified 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 

Configuration Steps
Related Procedures and Topics

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 Unified IP Phones, Cisco Unified 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 Unified 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 Unified 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 Unified IP Phone.

Privacy and Privacy on Hold Configuration Checklist

Table 8-4 provides a checklist to configure privacy.

Table 8-4 Privacy Configuration Checklist 

Configuration Steps
Related Procedures and Topics

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 Unified CallManager Administration Guide

Configuring Cisco Unified IP Phones, Cisco Unified 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 Unified 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 Unified IP Phones, Cisco Unified 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 Unified 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 Unified 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 Unified IP Phone.

Setting the Service Parameters for Barge, Privacy, and Privacy on Hold

Cisco Unified 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.

Built In Bridge Enable—Default specifies Off. This parameter enables or disables the built-in conference bridge capability for phones that use the Barge softkey. Set this parameter for each server in a cluster that has the Cisco CallManager service and barge configured. If Built in Bridge is set to On in Phone Configuration, the service parameter setting gets overridden.

Privacy Setting—Default specifies True. This parameter enables or disables the privacy feature for phone users who do not want to display information on shared-line appearances. Set this parameter for each server in a cluster that has the Cisco CallManager service and privacy configured. If only certain phones need the privacy feature, set the service parameter to False and set the Privacy field to On in Phone Configuration.

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.

Enforce Privacy Setting on Held Calls—Default specifies False. This parameter enables or disables the privacy on hold feature for phone users who want to preserve privacy on held calls. Set this parameter for each server in a cluster that has the Cisco CallManager service and privacy configured.

Party Entrance Tone—Default specifies False. This parameter enables or disables the tones that play during barge. Set this parameter for each server in a cluster that has the Cisco CallManager service and barge (with tones) configured.

Troubleshooting Barge and Privacy

For information about troubleshooting tools, messages, and how to recover from barge problems, refer to the Troubleshooting Guide for Cisco Unified CallManager.

Where to Find More Information

Related Topics

Phone Button Template Configuration, Cisco Unified CallManager Administration Guide

Cisco Unified IP Phone Configuration, Cisco Unified CallManager Administration Guide

Softkey Template Configuration, Cisco Unified CallManager Administration Guide

Adding a New User, Cisco Unified CallManager Administration Guide

Cisco Unified IP Phones, Cisco Unified CallManager System Guide

Additional Cisco Documentation

Cisco Unified IP Phone administration documentation for Cisco Unified CallManager

Cisco Unified IP Phone user documentation and release notes

Cisco Unified CallManager Security Guide