Barge is a feature that allows users of a shared octo-line directory number to join an active call by pressing a soft key on their phone. This effectively converts the call into an ad-hoc conference. This feature uses a hardware conference bridge configured in Cisco Unified CME. When the initiator barges into the call, an ad hoc conference is created between the barge initiator, the target party, and the other party that is already participating in the call. Connected parties hear the barge tone (single beep) after the conference is set up. When a party leaves the conference, a barge leave tone is played to the remaining parties.
NOTE: If a phone that is using the shared line has Privacy enabled, call information does not appear on the other phones that share the line and the call cannot be barged.
NOTE: CME version 7.0 or later is needed for SCCP support, CME version 7.1 needed for SIP support (Barge, cBarge, and Privacy)
Barge uses the built-in conference bridge on the target phone (the phone that is being barged) which limits the number of users allowed to barge. A barge conference supports up to three parties. If more users want to join a call on a SIP shared line, cBarge must be used. The SIP phone requires the built-in conference bridge to use Barge. Barge is supported for SIP shared-line directory numbers only.
cBarge Overview
The cBarge feature uses a shared conference resource which allows more that one person to barge into the call. A cBarge conference supports the maximum number of parties provisioned on the centralized conference resource. The centralized conference resource must be provisioned to use cBarge. cBarge is supported on SCCP shared octo-line directory numbers and SIP shared-line directory numbers.
When any party releases from the call, the call remains a conference call if at least three participants remain on the line. If only two parties remain in the conference, they are reconnected as a point-to-point call, which releases the conference bridge resources. When the target party parks the call or joins the call with another call, the barge initiator and the other parties remain connected.
Privacy
The privacy feature enables phone users to block other users who share a directory number from seeing call information, resuming a call, or barging into a call on the shared line. When a phone receives an incoming call on a shared line, the user can make the call private by pressing the Privacy feature button, which toggles between on and off to allow the user to alter the privacy setting on their phone. The privacy state is applied to all new calls and current calls owned by the phone user. Privacy is supported on SCCP octo-line directory numbers and SIP shared-line directory numbers.
Privacy is enabled for all phones in the system by default. You can disable privacy globally and enable it only for specific phones, either individually or through an phone template. You can also enable the privacy button on specific phones. After a phone with the privacy button enabled registers with Cisco Unified CME, the line feature button on the phone gets labeled "Privacy," a status icon displays, and if the button has a monitor lamp, it lights when privacy is active. For Extension Mobility phones, you can enable the privacy button in the user profile and logout profile.
The Privacy on Hold feature prevents other phone users from viewing call information or retrieving a call put on hold by another phone sharing the directory number. Privacy on Hold is disabled for all phones in the system by default. You can enable Privacy on Hold globally for all phones. To disable Privacy on Hold on individual phones, you must disable Privacy on those phones.
The Privacy feature applies to all shared lines on a phone. If a phone has multiple shared lines and Privacy is enabled, other phones cannot view or barge into calls on any of the shared lines.
SCCP Sample Configuration: cBarge Soft Key
Note: the cBarge softkey is enabled in its default state, however, use the following config to change the order of the soft ke displayed during the "remote-in-use" state.
ephone-template 1
softkeys remote-in-use CBarge Newcall
softkeys hold Resume Newcall Join
softkeys connected TrnsfVM Park Acct ConfList Confrn Endcall Trnsfer Hold
max-calls-per-button 3
busy-trigger-per-button 2
!
ephone 12
no phone-ui speeddial-fastdial
ephone-template 1
mac-address 000C.1234.5678
type 7960
button 1:8 2:4
SIP Sample Configuration: Barge and cBarge Softkeys
Note: the Barge and cBarge softkey is enabled in its default state, however, use the following config to change the order of the soft ke displayed during the "remote-in-use" state.
voice register template 1
softkeys hold Resume Newcall
softkeys connected Trnsfer Park Hold
softkeys remote-in-use cBarge Barge
!
voice register pool 120
id mac 000C.1234.5678
type 7962
number 1 dn 12
template 1
SCCP Sample Configuration: Turn on Privacy on Hold and Privacy
The following example disables privacy globally, but enables it on ephone 8.
telephony-service
no privacy
privacy-on-hold
max-ephones 80
max-dn 200
timeouts transfer-recall 60
voicemail 5999
max-conferences 8 gain -6
transfer-system full-consult
fac standard
!
ephone 8
privacy on
privacy-button
max-calls-per-button 3
busy-trigger-per-button 2
mac-address 000C.1234.5678
type 7960
button 1:4 2:8
SIP Sample Configuration: Enabling Privacy on Hold and Privacy
The following example disables privacy globally, and enables it on an individual phone.
voice register global
mode cme
privacy-on-hold
no privacy
max-dn 200
max-pool 100
voicemail 5999
!
voice register pool 130
id mac 000C.1234.5678
type 7941
number 1 dn 8
privacy ON
privacy-button
More Information
Configuring Barge and Privacy
No comments:
Post a Comment