Barge and Privacy Best CCNP Training Institute in Gurgaon

Network Bulls
www.networkbulls.com
Best Institute for CCNA CCNP CCSP CCIP CCIE Training in India
M-44, Old Dlf, Sector-14 Gurgaon, Haryana, India
Call: +91-9654672192

CUCM considers a DN associated to more than one device in the same partition to be a
shared-line appearance. One example of a shared-line appearance is where a DN appears
on line 1 of a manager telephone and also on line 2 of an assistant telephone. Another
CUCM
A
C
IP
IP
1 C Calls A;
A is Busy
2 Sends Call-Back Notification to
C When A Is Available Again
424 Chapter 16: User Features
example of a shared line is a single incoming number that is set up to appear as line 2 on
every help desk telephone in an office. Figure 16-21 shows a DN that is associated with two
devices. Notice that the phone name in Figure 16-21 includes an SEP prefix followed by
the MAC addresses of the device. SEP is an acronym for Selsius Ethernet Phone. Selsius is
the company Cisco acquired that created the CallManager product. Cisco has been involved
in the development of CallManager since Version 2.0.
Figure 16-21 Shared-Line Appearance
These guidelines are helpful when using shared-line appearances with CUCM:
■ A shared-line appearance can be created by assigning the same DN and partition to
different lines on different devices.
■ If other devices share a line, the words “Shared Line” display in red next to the DN in
the Directory Number Configuration window in CUCM Administration.
■ If you change the CSS, call waiting, call forward, or call pickup settings on any device
that uses the shared line, the changes are applied to all the devices that use that shared
line.
■ To stop sharing a line appearance on a device, you can change the DN or partition
number for the line and update the device. (Deletion removes the DN on the current
device only. The deletion does not affect the other devices.)
■ Do not use shared-line appearances on any Cisco Unified IP Phone that will be used
with the Attendant Console.
■ Do not use shared-line appearances on any Cisco Unified IP Phone 7960 or 7961 that
requires the Auto Answer capability.
Barge and Privacy 425
The barge feature allows a manager or supervisor with the Barge softkey to enter into an
existing call on a shared line. Two types of barge are available in Cisco Unified Call-
Manager Release 4.0 and later:
■ Barge using built-in conference (Barge softkey): Barge uses the built-in conference
capability of the target IP phone. Barge also uses the Standard User or Standard Feature
softkey template (both contain the Barge softkey). When a barge is being set up,
no media interruption occurs, and the only display change to the original call is a spinning
circle displayed at the right side of the Prompt Status message window at the target
device. The Barge feature is supported only when the G.711 audio codec is in use.
The digital signal processor (DSP) of the target phone mixes the audio conversations.
When the initiator uses barge to join the call, it becomes a three-way call. When only
two parties are left in the conference, they experience a brief interruption while the
media streams are reconnected as a point-to-point call, releasing the shared conference
resources. If the target hangs up, the caller who used barge and the other party connect
in a point-to-point call. If the other party hangs up, the original call and the barged call
are released.
■ Barge using shared conference (cBarge softkey): Conference Barge (cBarge) uses a
shared conference bridge. No standard softkey template includes the cBarge softkey.
To enable users to access the cBarge softkey, the administrator must add it to a nonstandard
softkey template and then assign the softkey template to a device. When a user
presses the cBarge softkey, a barge call is set up by means of the shared conference
bridge, if it is 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. The conference controller can add more parties
to the conference or can drop any party.
Barge configuration involves the following configuration options:
■ Assign the Standard User or Standard Feature softkey template to each device that
accesses barge using the built-in bridge functionality.
■ To enable barge cluster-wide for all users, choose System > Service Parameters for
the Cisco CallManager service and set the Built-In Bridge Enable cluster-wide service
parameter to On. This is illustrated in Figure 16-22. Alternatively, configure the barge
feature for each telephone by setting the Built-In Bridge field in the Phone
Configuration window on the device.
■ Set the Party Entrance Tone setting to True if you desire the target phone to hear a tone
when the line is barged into.
426 Chapter 16: User Features
Figure 16-22 Cluster-Wide Barge Configuration
To configure the Barge feature with Shared Conference Bridge (cBarge), follow these steps:
Step 1 Assign the Standard User or Standard Feature softkey template
(configure cBarge to either template) to each device that accesses barge
by using the shared conference bridge.
Step 2 Set the optional cluster-wide service parameter Party Entrance Tone to
True (required for tones).
Step 3 Associate the devices to the cBarge softkey template.
Step 4 Notify users that the cBarge feature is available.
The privacy feature was introduced in CUCM Release 4.0. Administrators can enable or
disable the ability of users with telephones that share the same line to view call status and
to barge into the call if they click the Privacy button on their phone before selecting the
shared line. Administrators enable or disable privacy for each phone. The Privacy button
requires a phone button template with the Privacy button to be assigned to the phone.
To configure the privacy feature, follow these steps:
Step 1 Set the optional Privacy Setting cluster-wide service parameter to True if
a large number of devices will be using the privacy feature of shared
lines.
Step 2 Modify one or more phone button templates to include a phone button for
privacy.
Step 3 Each phone requiring privacy must have the Privacy option set to On in
the Privacy drop-down menu of the Cisco Unified IP Phone Configuration
window. If privacy is configured cluster-wide, the Privacy setting should
be left at Default or On to enable privacy. This is illustrated in Figure 16-23.
The Privacy Off setting will override the cluster-wide setting inheritance.
User Web Pages 427
Figure 16-23 Device-Level Barge Configuration
Step 4 Assign the phone button template that contains the Privacy feature button
to IP phones that require that feature.
When privacy is enabled, the Privacy button changes display; a black circle appears inside
the Privacy field. Now, when the other user on the shared line goes off-hook on the shared
line, the Barge softkey does not appear.