- Supplementary Services Feature Roadmap
- Overview of Supplementary Services for FXS Ports on Cisco IOS Voice Gateways
- Configuring FXS Ports for Basic Calls
- Enabling Fallback to Cisco Unified SRST for Call Control on Analog (FXS) Ports
- Configuring Supplementary Features
- Configuring Feature Mode
- Configuring CallBack on Busy for Analog Phones
- Configuring CallBack on No Answer
- Configuring Call Waiting Tone Cadence
- Configuring AMWI and VMWI
- Configuring DC Voltage Based VMWI for SCCP Controlled Analog Ports
- Configuring Call Hold/Resume for Shared Lines for Analog Ports
- Configuring cBarge and Privacy for Shared Lines
- Configuring Single Number Reach for Analog Phones
- Media Renegotiation
- Configuring DTMF Relay, Fax Relay and Modem Relay
- Configuring Secure Signaling and Media Encryption for the Cisco VG224
- Configuring Secure SCCP Analog Endpoints over TLS with CM
- Implementing Enhanced Serviceability
Supplementary Services Features for FXS Ports on Cisco IOS Voice Gateways Configuration Guide, Cisco IOS Release 15M&T
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- Updated:
- April 6, 2020
Chapter: Configuring cBarge and Privacy for Shared Lines
- Contents
- Prerequisites for cBarge and Privacy for Shared Lines
- Restrictions for cBarge and Privacy for Shared Lines
- Benefits of cBarge and Privacy for Shared Lines
- Information About cBarge and Privacy for Shared Lines
- How to Configure cBarge and Privacy for Shared Lines
- Configuration Examples for cBarge and Privacy for Shared Lines
- Additional References
- Feature Information for cBarge and Privacy for Shared Lines
Configuring cBarge and Privacy for Shared Lines
First Published: November 19, 2010
This module describes the cBarge and Privacy Skinny Client Control Protocol (SCCP) telephony control (STC) application (STCAPP) supplementary-service features for IP and analog phones connected to the same Foreign Exchange Station (FXS) ports on a Cisco VG2nn Analog Gateway. While the cBarge feature allows an idle phone to automatically join an already active call on the same shared line just by going offhook, the Privacy feature disallows other users to cBarge into an active call on a shared line. These features are not supported in Cisco Unified Communications Manager Express (Cisco Unified CME).
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the “Feature Information for cBarge and Privacy for Shared Lines” section.
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
- Prerequisites for cBarge and Privacy for Shared Lines
- Restrictions for cBarge and Privacy for Shared Lines
- Benefits of cBarge and Privacy for Shared Lines
- Information About cBarge and Privacy for Shared Lines
- How to Configure cBarge and Privacy for Shared Lines
- Configuration Examples for cBarge and Privacy for Shared Lines
- Additional References
- Feature Information for cBarge and Privacy for Shared Lines
Prerequisites for cBarge and Privacy for Shared Lines
cBarge and Privacy for Shared Lines require the following software component:
cBarge for Shared Lines requires the following hardware component:
Restrictions for cBarge and Privacy for Shared Lines
Benefits of cBarge and Privacy for Shared Lines
The cBarge feature provides parity with incumbent time-division multiplexing PBXs.
Information About cBarge and Privacy for Shared Lines
To enable SCCP supplementary features on analog phones connected to FXS ports on a Cisco voice gateway, you should understand the following concepts:
Feature Summary
Table 1 contains information about SCCP-based cBarge and Privacy for Shared Lines on Cisco Voice Gateways.
Table 1 cBarge and Privacy for Shared Lines
cBarge and Privacy for Shared Lines
The cBarge feature allows any idle IP or analog phone on a shared line or connected to the same port to automatically join an already active call on the same shared line by simply going offhook. Through the Cisco Unified CM, the three parties are allowed to hold a conference call.
Note
Only one analog phone is allowed to cBarge into an active call. When one phone has already been allowed to cBarge into an existing conversation, no other shared line analog phone can cBarge into it.
In analog switching systems, a single analog port can be connected to multiple analog phones such that when a phone is in an active conversation, any other phone that is connected to the same port can go offhook to join in the conversation.
In digital IP switching (or PBX) systems, a similar capability is supported and it is called a shared line. All the phones using the same directory number are called shared line phones. When there is an existing conversation on a shared line, going offhook enables another shared line phone to cBarge into the conversation.
Note When cBarge is configured, privacy might be an issue because any idle phone on the shared line that goes offhook can join an existing conversation regardless of the idle phone user’s desire to join the call or not.
Privacy is a feature that blocks other phones on a shared line to cBarge into a conversation.
Configuring the port on a shared line on the Cisco Unified CM to Privacy prevents other phones on the shared line to barge into active calls.
How to Configure cBarge and Privacy for Shared Lines
Note This document does not contain details about configuring Cisco Unified CM. See the documentation for this product for installation and configuration instructions.
This section contains the following tasks for configuring cBarge and Privacy for shared lines:
Configuring cBarge for Shared Lines
To enable cBarge for analog endpoints in the Cisco Unified CM, perform the following steps on the Cisco VG2nn Analog Gateways.
SUMMARY STEPS
DETAILED STEPS
Configuring Privacy for Shared Lines
To enable Privacy for analog endpoints in the Cisco Unified CM, perform the following steps on the Cisco VG2nn Analog Gateways.
SUMMARY STEPS
DETAILED STEPS
Configuration Examples for cBarge and Privacy for Shared Lines
This section provides the following configuration examples:
- Example: Configuring cBarge for Shared Lines
- Example: Configuring Privacy for Shared Lines
- Example: Privacy for Shared Lines on Cisco VG204
Example: Configuring cBarge for Shared Lines
The following is a sample output from the show run command showing how to enable the cBarge STCAPP supplementary-service feature for analog phones connected to port 2/4 on a Cisco VG224. A similar sample output can also be displayed using the show stcapp device voice-port x/x (or x/x/x) command.
Example: Configuring Privacy for Shared Lines
The following is a sample output from the show run command showing how to enable the Privacy STCAPP supplementary-service feature for analog phones connected to port 2/4 on a Cisco VG224. A similar sample output can also be displayed using the show stcapp device voice-port x/x (or x/x/x) command.
Example: Privacy for Shared Lines on Cisco VG204
The following is a sample output from the show stcapp device command showing the Privacy STCAPP supplementary-service feature disabled on port 0/2 of a Cisco VG204:
Additional References
The following sections provide references related to SCCP analog phone support for FXS ports on the Cisco voice gateway.
Related Documents
|
|
|
|---|---|
|
Technical Assistance
Feature Information for cBarge and Privacy for Shared Lines
Table 2 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 15.1(3)T or a later release appear in the table.
For information on a feature in this technology that is not documented here, see the “Supplementary Services Features Roadmap” section.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note Table 2 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
Table 2 Feature Information for cBarge and Privacy for Shared Lines
|
|
|
|
|---|---|---|
Allows idle IP or analog phones that are connected to the same FXS ports on a Cisco VG2nn Analog Gateway to automatically join already active calls on the same shared lines by simply going offhook. This feature is supported in Cisco Unified CM only. The following sections provide information about this feature: |
||
Disallows other users to cBarge into active calls on the same FXS ports on a Cisco VG2nn Analog Gateway. This feature is supported in Cisco Unified CM only. The following sections provide information about this feature:
The following commands were introduced or modified: privacy (supplementary-service). |
Feedback