- 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
- Contents
- Prerequisites for SCCP Controlled Analog (FXS) Ports with Supplementary Features in CiscoIOS Gateways
- Restrictions for SCCP Controlled Analog (FXS) Ports with Supplementary Features in CiscoIOS Gateways
- Information About SCCP Controlled Analog (FXS) Ports with Supplementary Features in CiscoIOS Gateways
- How to Configure SCCP Analog FXS Ports with Supplementary Features in CiscoIOS Gateways
Configuring Supplementary Features
First Published: June 27, 2005
This module describes how to enable Skinny Client Control Protocol (SCCP) supplementary features for analog Foreign Exchange Station (FXS) ports on a Cisco voice gateway, such as a Cisco Integrated Services Router (Cisco ISR) or Cisco VG224 Analog Phone Gateway, under the control of Cisco Unified Communications Manager or 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 SCCP Controlled Analog (FXS) Ports with Supplementary Features in Cisco IOS Gateways” 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 SCCP Controlled Analog (FXS) Ports with Supplementary Features in Cisco IOS Gateways
- Restrictions for SCCP Controlled Analog (FXS) Ports with Supplementary Features in Cisco IOS Gateways
- Information About SCCP Controlled Analog (FXS) Ports with Supplementary Features in Cisco IOS Gateways
- How to Configure SCCP Analog FXS Ports with Supplementary Features in Cisco IOS Gateways
- Configuration Examples for SCCP Controlled Analog (FXS) Ports with Supplementary Features in Cisco IOS Gateways
- Additional References
- Feature Information for SCCP Controlled Analog (FXS) Ports with Supplementary Features in Cisco IOS Gateways
Prerequisites for SCCP Controlled Analog (FXS) Ports with Supplementary Features in Cisco IOS Gateways
- Cisco IOS Release 12.3(11)T or a later release.
- The Cisco voice gateway is set up and configured for operation. For information, see the appropriate Cisco configuration documentation.
- The analog FXS voice ports are set up and configured for operation. For information, see the Cisco IOS Voice Port Configuration Guide.
- SCCP and the SCCP telephony control (STC) application is enabled on the Cisco voice gateway. For configuration information, see the “Configuring FXS Ports for Basic Calls” section.
Analog Endpoints in Cisco Unified Communications Manager
- Cisco Unified Communications Manager 4.2 or a later version.
- Phones are added and configured in Cisco Unified Communications Manager. See the “Directory Number Configuration” chapter under “Call Routing Configuration” and the “Gateway Configuration” chapter under “Device Configuration” in the appropriate Cisco Unified Communications Manager Administration Guide.
Analog Endpoints in Cisco Unified CME
- Cisco CME 3.2 or a later version.
- Ephone configurations and feature parameters for analog endpoints are configured in Cisco Unified CME. For information, see the Cisco Unified CME Administration Guide.
- To use call transfer on analog endpoints, set the transfer-system command to full-blind or full-consult on Cisco router. Neither of these settings is the default for this command, so one of these settings must be manually configured. For configuration information, see the “ Configuring Call Transfer and Forwarding ” module in the Cisco Unified CME Administration Guide.
The following example shows how to configure full consultation as the call transfer method:
Restrictions for SCCP Controlled Analog (FXS) Ports with Supplementary Features in Cisco IOS Gateways
Information About SCCP Controlled Analog (FXS) Ports with Supplementary Features in Cisco IOS Gateways
To enable SCCP supplementary features on analog phones connected to FXS ports on a Cisco voice gateway, you should understand the following concepts:
- Summary of SCCP Supplementary Features for FXS ports
- Flexible Feature Access Codes
- Enhanced Speed Dial on SCCP Analog Phones
- Cancel Call Waiting
- SCCP Meet-Me Conference
Note In Cisco IOS Release15.1(2)T5 and later, Analog (FXS) phones connected to Cisco IAD2430 are recognized as SCCP endpoints. Cisco IOS Release 15.1(2)T5 also adds support for the STCAPP functionality for Cisco IAD2430.
Summary of SCCP Supplementary Features for FXS ports
Table 1 contains a list of SCCP supplementary features that are supported on analog phones connected to FXS ports, along with descriptions and information about how to configure support for each feature in your Cisco call-control system.
Note For information about individual commands in Cisco Unified CME, see the Cisco Unified CME Command Reference.
|
|
|
---|---|---|
|
User picks up handset and hears message waiting indication (MWI) tone whenever a new voice message is waiting to be heard. |
To configure, see the “Message Waiting Configuration” chapter under “Voice Mail Configuration” in the appropriate Cisco Unified Communications Manager Administration Guide. To configure, see “ Integrating Voice Mail ” in the Cisco Unified CME Administration Guide. |
Forwards calls to a target number when the called number is busy. |
User activates by using the Cisco Unified CME GUI or administrator activates by configuring this feature in the Cisco call-control system. |
For feature information, see the “Phone Features” section of the “Cisco Unified IP Phone” chapter under “Devices and protocols” in the appropriate Cisco Unified Communications Manager System Guide. To configure, see the “Configuring Directory Numbers” chapter under “Call Routing Configuration” in the appropriate Cisco Unified Communications Manager Administration Guide. To configure, see “Configuring Call Transfer and Forwarding” in the Cisco Unified CME Administration Guide. |
Forwards calls to a target number when there is no answer at the called number. |
User activates by using the Cisco Unified CME GUI or an administrator activates by configuring this feature in the Cisco call-control system. |
For feature information, see the “Phone Features” section of the “Cisco Unified IP Phone” chapter under “Devices and protocols” in the appropriate Cisco Unified Communications Manager System Guide. To configure, see the “Configuring Directory Numbers” chapter under “Call Routing Configuration” in the appropriate Cisco Unified Communications Manager Administration Guide. To configure, see “Configuring Call Transfer and Forwarding” in the Cisco Unified CME Administration Guide. |
|
During an active call, user presses hookflash and receives dial tone. User dials number for transfer and either stays online to announce (consultive transfer) or hangs up (blind transfer). When user hangs up, the call is transferred. Note When blind transfer is configured in Cisco Unified CME, the phone user does not have to hang up; the call is transferred when Cisco Unified CME receives the dialed number. |
For feature information, see “Making and Receiving Multiple Calls Per Directory Number” section of the “Understanding Directory Numbers” chapter under “Dial Plan Architecture” in the Cisco Unified Communications Manager System Guid e. To configure, see “Configuring Call Transfer and Forwarding” in the Cisco Unified CME Administration Guide. |
|
During an active call, user hears a tone and can press hookflash to toggle between the active call and the incoming call. For analog endpoints in Cisco Unified Communications Manager: The call waiting tone depends on the ring setting for the active station and the tone does not play repeatedly, it plays only once. For analog endpoints in Cisco Unified CME: The call waiting tone is played continuously. |
For feature information, see the “Understanding Directory Numbers” section of the “Understanding Route Plans” chapter under “Dial Plan Architecture” in the Cisco Unified Communications Manager System Guid e. |
|
Administrator activates on the Cisco call-control system. Time stamp is from the Cisco voice gateway. Note To display the caller ID when caller ID is supported by the local telco provider, an administrator must use the caller id enable command on the appropriate Cisco voice gateway port. |
For feature information, see the “Caller Identification and Restriction” section of the “Understanding Route Plans” chapter under “Dial Plan Architecture” in the Cisco Unified Communications Manager System Guid e. For caller-ID display on local calls (calls between FXS ports and IP phones registered to the same Cisco Unified CME router):
For restricting or blocking caller-ID display:
|
|
User in basic call mode presses hookflash to get the first dial tone, then dials an extension number to connect to a second call. When the second call is established, user presses hookflash to get feature tone and then dials #3 to initiate a three-party conference. |
For feature information, see the “Initiating an Ad Hoc Conference Bridge” section of the “Conference Bridges” chapter under “Media Resources” in the Cisco Unified Communications Manager System Guide. To configure, see the “Configuring Conferencing” section of the “Adding Features”chapter in the Cisco Unified CME Administration Guide. |
Enables distinct ring tone to alert user whether incoming call is from an internal or external phone. |
System administrator configures the ring patterns for both internal and external calls on the voice gateway port. |
To configure, see the ring cadence command in the Cisco IOS Voice Command Reference. |
Access features using an abbreviated code. Allows you to configure feature codes for FACs so that phone users are not required to dial the prefix before dialing the feature code to access an SCCP feature. Allows you to configure feature codes for FACs so that phone users are not required to dial the prefix or special characters to access an SCCP feature. |
User accesses features by dialing a FAC, typically consisting of a prefix plus a feature code. For a list of STC application call features that can be accessed by dialing a FAC, see Table 2. Note The stcapp feature access-code command must be enabled on the Cisco voice gateway. |
For feature and configuration information for individual STC application call features for which you can configure a FAC, see Table 2. |
|
User dials the feature speed dial (FSD) prefix and the redial code. Default prefix and code is *#. Note The stcapp feature speed-dial command must be enabled on the Cisco voice gateway. |
No configuration tasks required on your Cisco call-control system. |
|
User dials the FSD prefix and desired speed-dial code. The digit command determines the number of digits used for FSD codes on the Cisco voice gateway. Default prefix and code range is: User stores speed-dial destinations by using the Cisco Unified CME GUI or an administrator stores destinations on the Cisco call-control system. Note The stcapp feature speed-dial command must be enabled on the Cisco voice gateway. |
For feature information, see the “Phone Features” section of the “Cisco Unified IP Phones” chapter under “Devices and protocols” in the appropriate Cisco Unified Communications Manager System Guid e. To configure, see the “Configuring Speed-Dial Buttons” section in the “Cisco Unified Phone Configuration” chapter under “Device Configuration” in the appropriate Cisco Unified Communications Manager Administration Guide. To configure, see “Configuring Speed Dial” in the Cisco Unified CME Administration Guide. |
User dials access code and speed-dial number. Administrator activates on the Cisco call-control system. |
To configure, see the “Translation Pattern Configuration” chapter under “Call Routing Configuration” in the appropriate Cisco Unified Communications Manager Administration Guide. To configure, see “Configuring Speed Dial” in the Cisco Unified CME Administration Guide. |
|
|
User dials the FSD prefix and speed dial to voice mail code. The digit command determines the number of digits used for FSD codes. Note The stcapp feature speed-dial command must be enabled on the Cisco voice gateway. |
To configure, see the “Cisco Voice-Mail Pilot Configuration” chapter under “Voice Mail Configuration” in the appropriate Cisco Unified Communications Manager Administration Guide. To configure, see “Integrating Voice Mail” in the Cisco Unified CME Administration Guide. |
|
|
|
---|---|---|
|
User dials feature access code (FAC) prefix and call-forward-all code, and then following the confirmation tone, the target number. Default prefix and code is **1. After CFA is activated, user hears a stutter tone when the handset is picked up to indicate that all incoming calls are being forwarded. If a phone user tries to activate CFA after it is already activated, a fast busy tone is generated. Note The stcapp feature access-code command must be enabled on the Cisco voice gateway. |
For feature information, see the “Phone Features” section of the “Cisco Unified IP Phone” chapter under “Devices and Protocols” in the appropriate Cisco Unified Communications Manager System Guid e. To configure, see the “Configuring Directory Numbers” chapter under “Call Routing Configuration” in the appropriate Cisco Unified Communications Manager Administration Guide.
|
|
User dials FAC prefix and call-forward-cancel code. Default prefix and code is **2. After CFA is canceled, user hears a confirmation tone when the handset is picked up to indicate incoming calls are no longer being forwarded. Note The stcapp feature access-code command must be enabled on the Cisco voice gateway. |
For feature information, see the “Phone Features” section of the “Cisco Unified IP Phone” chapter under “Devices and Protocols” in the appropriate Cisco Unified Communications Manager System Guid e. To configure, see the “Configuring Directory Numbers” chapter under “Call Routing Configuration” in the appropriate Cisco Unified Communications Manager Administration Guide.
|
Call Pickup Directed Puts a call on hold at a designated extension so that it can be retrieved by anyone. |
During an active call, user presses hookflash for dial tone, and then dials the call-park slot number configured on the call-control system. User retrieves the call by dialing the FAC prefix, the directed pickup code, and the call-park slot number where the call was parked, and pressing hookflash. Default prefix and code is **6. For example, if the call is parked at slot 1211, user dials **61211. Users can also retrieve the last call parked by their own extensions by dialing the FAC prefix, the directed pickup code, and an asterisk (*), and pressing hookflash. Default prefix and code is **6*. Note The stcapp feature access-code command must be enabled on the Cisco voice gateway. |
This feature is not supported for Cisco Unified Communications Manager. To configure, see “Configuring Call Coverage Features” in the Cisco Unified CME Administration Guide. |
Allows incoming calls to be picked up by phones other than the ringing phone. |
User picks up a ringing extension by dialing the FAC prefix, the directed pickup code, and the ringing extension number. Default prefix and code is **6. Note The stcapp feature access-code command must be enabled on the Cisco voice gateway. |
This feature is not supported for analog endpoints in Cisco Unified Communications Manager. |
Allows incoming calls in a different pickup group than the user to be picked up. |
User picks up a ringing extension by dialing the FAC prefix, the group pickup code, and the number of the pickup group. Default prefix and code is **4. Note The stcapp feature access-code command must be enabled on the Cisco voice gateway. |
AutoCallPickupEnabled service parameter must be set to True. For feature information, see the “Call Pickup” section of the “Translation Pattern Configuration” chapter under “Call Configuration” in the appropriate Cisco Unified Communications Manager System Guid e. To configure, see the “Pick Up Phone Configuration” chapter under “Call Routing Configuration” in the appropriate Cisco Unified Communications Manager Administration Guide. To configure, see “Configuring Call Coverage Features” in the Cisco Unified CME Administration Guide. |
Allows incoming calls in the same pickup group as the user to be picked up. |
User picks up a ringing extension by dialing the FAC prefix and the local pickup code. Default prefix and code is **3. Note The stcapp feature access-code command must be enabled on the Cisco voice gateway. |
AutoCallPickupEnabled service parameter must be set to True. To configure, see the “Pick Up Phone Configuration” chapter under “Call Routing Configuration” in the appropriate Cisco Unified Communications Manager Administration Guide. To configure, see “Configuring Call Coverage Features” in the Cisco Unified CME Administration Guide. |
|
User dials the cancel call waiting FAC, receives recall dial-tone, and places a call. Default prefix and code is **8. |
For feature information, see the “Phone Features” section of the “Cisco Unified IP Phone” chapter under “Devices and Protocols” in the appropriate Cisco Unified Communications Manager System Guid e. To configure, see the “Configuring Directory Numbers” chapter under “Call Routing Configuration” in the appropriate Cisco Unified Communications Manager Administration Guide. |
|
User dials FAC prefix and voice-mail code. Default prefix and code is **7. Note The stcapp feature access-code command must be enabled on the Cisco voice gateway. |
For feature information, see the “Phone Features” section of the “Cisco Unified IP Phone” chapter under “Devices and Protocols” in the appropriate Cisco Unified Communications Manager System Guid e. To configure, see the “Configuring Directory Numbers” chapter under “Call Routing Configuration” in the appropriate Cisco Unified Communications Manager Administration Guide. |
Enables user on an analog SCCP phone to start or join a meet-me conference call. |
To start a meet-me conference, user dials FAC prefix and meet-me conference code, and following the confirmation tone, the meet-me conference number. Default prefix and code is **5. Participants can join the conference by dialing the meet-me conference number. Participants hear a busy tone if they call the conference number before the conference controller has joined. In this case, participants must call back. To end a meet-me conference, all participants must hang up. The conference does not automatically end when the conference controller disconnects. Before a conference controller can start a meet-me conference, meet-me conference numbers must be configured in your Cisco call-control system by the system administrator. Note The stcapp feature access-code command must be enabled on the Cisco voice gateway. |
To configure meet-me conferencing and meet-me conference numbers, see “SCCP: Configuring Conferencing” in the Cisco Unified CME Administration Guide. |
Flexible Feature Access Codes
To access certain STC application call features on analog phones connected to a voice gateway, phone users must dial a FAC consisting of a prefix plus a feature code, for example **1.
The prefix for FACs is a one to five-character string beginning with an asterisk (*) or number sign (#). The default value is **.
Before Cisco IOS Release 12.4(20)YA, feature codes for FACs were limited to a single character (0-9, *, or #). In Cisco IOS Release 12.4(20)YA and later releases, the Flexible FAC feature allows you to configure feature codes as follows:
- For feature codes to be dialed after dialing the prefix, you can configure one character (0-9, *, or #) or two digits (00-99) that can be dialed on phone keypad.
- For feature codes that do not require the prefix to be dialed to access the feature, you can configure two to four characters that can be dialed on phone keypad and the leading or ending character must be an asterisk (*) or number sign (#).
- The default values for specific FACs are listed in Table 2.
Flexible FACs allow you to configure feature codes for FACs so that phone users are not required to dial the prefix before dialing the feature code to access an SCCP feature on an analog phone. If you configure a feature code that is at least two characters and the leading or ending character is an asterisk (*) or number sign (#), no prefix is required to access the feature. For example, if you configure a feature code of 78# for Call Forward Cancel, the phone user dials just the feature code (78#) to access that feature. If you configure a feature code of 78 for Call Forward Cancel, the phone user must dial the prefix, whatever it is, plus the feature code (78) to access that feature.
If you attempt to set a feature code to a value that is already configured for another feature code, a speed-dial code, or the Redial FSD, you receive a warning message. If you configure a duplicate code, the system implements the first feature it matches in the order shown in the output of the show stcapp feature codes command. Precedence is determined by the value for each feature code.
If you attempt to set a feature code to a value that precludes or is precluded by another feature code, a speed-dial code, or the Redial FSD, you receive a warning message. For example, if you attempt to set a feature code of #123 and #12 is already configured for another feature, such as Call Forward Cancel, the following message appears:
Or if you attempt to configure #1 and #12 is already configured for another feature, such as Call Forward Cancel, the following message appears:
These messages will not prevent you from configuring the feature code.
After a phone user dials the FAC or FSD, the system matches the dialed string with configured FACs, Redial, and speed-dial codes in the following order and executes the first complete match, ignoring the longer feature code:
- Malicious call ID (MCID)
- Call forward all
- Call forward cancel
- Pickup local group
- Pickup different group
- Pickup direct
- Redial
- Speeddial1
- Speeddial2
- Speeddial3
- and so on...
For example, assume that Call Forward All is #123, Call forward Cancel is #12, and Pickup Local Group and Redial are both #1. After the phone user dials #1, the system matches the dialed characters to the configured codes in the order listed and because it is the first exact match, executes Pickup Local Group. If the phone user dials #12, the digit 2 will be ignored because #1 is an exact match and the system executes Pickup Local Group again. In this configuration, the phone user is unable to access Call Forward All (#123), Call Forward Cancel (#12), or Redial (#1) because all are precluded by #1 for Pickup Local Group. You must configure a new value for a precluded feature code in order to enable a FAC for that feature.
To enable and configure FACs on an analog FXS port, see the “Configuring Feature Access Codes” section.
Enhanced Flexible Feature Access Code
In Cisco IOS 15.0(1)M and later releases, you can configure an all-numeric three or four-digit feature codes so that users are not required to dial a prefix or special characters. For example, if you configure a feature code of 788 for Call Forward Cancel, the phone user dials just the feature code (788) to access that feature.
Flexible Feature Access Code Support for Redial
Flexible feature access codes includes support for Redial. To access Redial using an FSD, analog phone users must dial a prefix and speed-dial code. The default prefix and speed-dial code for Redial is *#.
In Cisco IOS Release 12.4(20)YA and later releases, if you configure a speed-dial code for Redial of one or two characters that can be dialed on a phone keypad, the phone user must dial the FSD prefix before dialing the speed-dial code. If you configure a speed-dial code for Redial of two to four characters and the leading or ending character is an asterisk (*) or a number sign (#), the phone user is not required to dial the FSD prefix before dialing the speed-dial code for Redial.
In Cisco IOS 15.0(1)M and later releases, you can configure a speed-dial code of three or four digits for Redial so that the phone user is not required to dial the FSD prefix or any special character to dial the speed-dial code for Redial.
For configuration information, see the “Enabling and Changing Feature Speed-Dial Codes” section.
Enhanced Speed Dial on SCCP Analog Phones
To access predefined speed-dial numbers used with the STC application, analog phone users must dial a FSD consisting of a prefix and speed-dial code, for example *9. The FSD prefix and speed-dial codes are set on the Cisco voice gateway; the telephone numbers that are speed dialed must be configured on your Cisco call-control system.
The speed-dial codes on the Cisco voice gateway are mapped to speed-dial positions on the call-control device, starting with position 1. For example, if you configure speed-dial codes 00 to 20 on the Cisco voice gateway, the system maps code 00 to speed-dial 1 on the call-control device, code 01 to speed-dial 2, code 02 to speed-dial 3, and so on. Dialing 00 on the analog phone dials the telephone number associated with speed-dial 1.
Prior to Cisco IOS Release 12.4(6)T, speed-dial codes for FSDs were limited to a single digit, 0 to 9. In Cisco IOS Release 12.4(6)T and later releases, you can define two-digit speed-dial codes to access up to 99 local speed-dial numbers configured on the call-control device.
In Cisco IOS 15.0(1)M and later releases, for speed-dial to voice mail, you can dial a three or four digit FAC without a prefix. For example:
Flexible FACs supports only the FSD for Redial. In Cisco IOS Release 12.4(20)YA and later releases, if you configure a speed-dial code for Redial of two to four characters that can be dialed on a phone keypad and the leading or ending character is an asterisk (*) or a number sign (#), the phone user is not required to dial the FSD prefix before dialing the speed-dial code for Redial. For information about Flexible FACs, see the “Flexible Feature Access Codes” section.
To enable FSDs on an analog FXS port, see the “Enabling and Changing Feature Speed-Dial Codes” section.
To use bulk speed-dial codes up to 9,999, no specific configuration is required on the Cisco voice gateway. Analog phone users do not need to use an FSD prefix or speed-dial codes to access bulk speed-dial numbers. See the documentation for your Cisco call-control system for information about configuring up to 9,999 speed dials.
Cancel Call Waiting
In Cisco IOS Release 15.1(1)T and later releases, the Cancel Call Waiting feature allows a phone user with Call Waiting service to disable the Call Waiting feature for one call. The user dials the cancel call waiting FAC, receives recall dial-tone, and places a call normally. The Call Waiting service is inactive during this call. Anyone calling the user receives the normal busy treatment and no call waiting tone interrupts the user’s active call. Cancel Call Waiting automatically deactivates when the user disconnects from the call.
For configuration information, see the “Configuring Feature Access Codes” section.
SCCP Meet-Me Conference
In Cisco IOS Release 12.4(20)YA and later releases, hardware-based meet-me conferencing is supported on analog phones connected to the FXS port of Cisco voice gateways. Hardware-based conferencing uses digital signal processors (DSPs) to allow more parties than the three-party limit allowed by software-based ad hoc conferencing. Meet-me conferencing requires a range of meet-me conference numbers that are created in the Cisco call-control system and allocated for exclusive use of the conference.
To start an SCCP Meet-Me Conference on an analog phone connected to a voice gateway, you must dial a FAC consisting of a prefix plus a feature code. The default FAC for SCCP Meet-Me Conference is **5.
When you start a meet-me conference, the Cisco call-control system considers you the conference controller. When a meet-me conference is set up, you choose a meet-me conference number and advertise it to conference participants. Participants call the number to join the conference. Anyone who calls the number while the conference is active joins the conference if the number of participants does not exceed the maximum number of parties specified for the conference type and sufficient streams are available on the conference device.
In Figure 1, extensions 1215, 1225, and 1235 are all parties in a meet-me conference on extension number 1500. The conference is created as follows:
1. The conference controller at extension 1215 presses the FAC for SCCP Meet-Me Conference, hears a confirmation tone, and then dials the meet-me conference number 1500.
2. Extension 1225 and extension 1235 joins the meet-me conference by dialing 1500.
3. Extension 1235 joins the meet-me conference by dialing 1500.
Figure 1 Simple Meet-Me Conference
If other phone users press the meet-me FAC and then dial the same meet-me conference number, the Cisco call-control system ignores the signal.
A meet-me conference continues even if the conference controller hangs up.
If only one participant remains in the meet-me conference, for example, if one participant forgets to hang up, the conference call is disconnected after five minutes to free system resources.
If the conference controller is waiting for participants to join the conference and is the only party on the conference, the conference is not disconnected because significant resources are not being used.
For configuration information, see the “Configuring Feature Access Codes” section.
How to Configure SCCP Analog FXS Ports with Supplementary Features in Cisco IOS Gateways
Note This document does not contain details about configuring Cisco Unified Communications Manager or Cisco Unified CME. See the documentation for these products for installation and configuration instructions.
This section contains the following tasks for setting up SCCP analog phone support:
- Configuring Feature Access Codes (optional)
- Enabling and Changing Feature Speed-Dial Codes (optional)
Configuring Feature Access Codes
To enable FACs and enter STC application feature access-code configuration mode for defining a prefix other than the default (**) or a feature code other than the default for a particular feature, perform the following steps.
Note The Flexible Feature Access Code feature also affects only the FSD for redial. If you want the phone user to just dial the speed-dial code to access the Redial feature, configure a redial speed-dial code that begins or ends with an asterisk (*) or number sign (#) by using the redial command. For configuration information, see the “Enabling and Changing Feature Speed-Dial Codes” section.
Note In Cisco IOS 15.0(1)M and later releases, a user can dial a three or four digit FAC without a prefix, for all the features under stcapp FACs and for voice mail under stcapp feature speed-dial.
Prerequisites
- Cisco IOS Release 12.4(2) or a later release.
- To configure a FAC that does not require the user to dial a prefix, Cisco IOS Release 12.4(20)YA or a later release.
- To configure an all-numeric feature code, Cisco IOS Release 15.0(1)M or a later release.
For SCCP Meet-Me Conference and Analog Endpoints in Cisco Unified Communications Manager
- A hardware conference bridge is configured in Cisco Unified Communications Manger. Configure the same bridge name for the hardware conference bridge and for the Cisco IOS bridge. Security mode can be encrypted, authenticated or non-secure. See the “Conference Bridge Configuration” section of the “Media Resource Configuration” chapter in the appropriate Cisco Unified Communications Manager Administration Guide.
- Meet-Me page and conference numbers are configured in Cisco Unified Communications Manager. See the “Meet-Me Number/Pattern Configuration” section of the “Call Routing” chapter in the appropriate Cisco Unified Communications Manager Administration Guide.
For SCCP Meet-Me Conference and Analog Endpoints in Cisco Unified CME
- Meet-Me Conferencing and meet-me conference numbers are configured in Cisco Unified CME. For configuration information, see “How to Configure Conferencing” in the Cisco Unified CME System Administrator Guide.
Restrictions
- In Cisco IOS Release 12.4(20)YA and later releases, if you configure the same value for more than one feature code or speed-dial code, or for the Redial FSD, the system implements the first feature it matches in the order of precedence shown in the output of the show stcapp feature codes command.
- In Cisco IOS Release 12.4(20)YA and later releases, if you configure feature codes for FACs or speed-dial codes for FSDs, including the Redial FSD, to a value that precludes or is precluded by another code, the system implements the feature with the shortest feature code first. The precluded codes cannot be implemented.
SUMMARY STEPS
5. call forward all keypad-character
6. call forward cancel keypad-character
7. cancel-call-waiting keypad-character
8. meetme-conference keypad-character
9. pickup local keypad-character
10. pickup group keypad-character
DETAILED STEPS
Examples
The following example shows FACs enabled and the changes to some of the default settings:
The following output from the show stcapp feature codes command displays the default and nondefault settings for FACs. The FAC prefix has been set to *# (asterisk, number sign).
Cisco IOS Release 12.4(20)YA and Later Releases
In the following example configuration, phones users are not required to dial the FAC prefix to access the Call Forward All and Call Forward Cancel features because the feature code is at least two characters and begins or ends with an asterisk (*) or number sign (#), making it a flexible FAC. A phone user must dial only #74 and, following the confirmation tone, the target number to forward all incoming calls to the target phone number.
The following output from the show stcapp feature codes command displays the default and nondefault settings for FACs. In this configuration, all of the FACs settings are for default values.
Enabling and Changing Feature Speed-Dial Codes
To enable FSDs, define a prefix other than the default (*), and define speed-dial codes, perform the following steps on the Cisco voice gateway.
Note This procedure enables analog phone users to access up to 99 speed-dial numbers configured on the call-control device. To use bulk speed-dial numbers up to 9,999, no specific configuration is required on the Cisco voice gateway. See the documentation provided for your call-control system for information on configuring up to 9,999 speed dials.
Prerequisites
- Speed dial codes from 0 to 9 require Cisco IOS Release 12.4(2)T or a later release; speed dial codes from 10 to 99 require Cisco IOS Release 12.4(6)T or a later release.
- To use speed-dial codes 34 to 99 on analog phones controlled by Cisco Unified CME, you must configure directory entries in telephony-service configuration mode. The following example sets a directory entry for speed-dial codes 34 and 35. When an analog phone user dials 34, extension 1602 is dialed.
For more information, see “Configuring Speed Dial” in the Cisco Unified Communications Manager Express System Administration Guide.
Restrictions
- In Cisco IOS Release 12.4(20)YA and later releases, if you configure the same value for more than one feature code or speed-dial code, or for the Redial FSD, the system implements the first feature it matches in the order of precedence shown in the output of the show stcapp feature codes command.
- In Cisco IOS Release 12.4(20)YA and later releases, if you configure feature codes for FACs or speed-dial codes for FSDs, including the Redial FSD, to a value that precludes or is precluded by another code, the system implements the feature with the shortest feature code first. The precluded codes cannot be implemented.
SUMMARY STEPS
DETAILED STEPS
Examples
The following example shows FSD codes enabled and the changes to some of the default settings in Cisco IOS Release 12.4(2)T:
The following output from the show stcapp feature codes command displays the default and nondefault settings for FSD codes and shows how the speed-dial range set in the example above is mapped to the speed-dial positions on the call-control system. Note that the range from 2 to 7 is mapped to speed-dial 1 to 6. To dial the telephone number that is stored for speed-dial 1 on Cisco Unified Communications Manager or Cisco Unified CME, an analog phone user presses ##2.
The following example shows FSD codes enabled and the changes to some of the default settings in Cisco IOS Release 12.4(6)T:
The following output from the show stcapp feature codes command displays the default and nondefault settings for FSD codes and shows how the speed-dial range set in the preceding example is mapped to the speed-dial positions on the call-control system. Note that the range from 11 to 17 is mapped to speed-dial 1 to 7. To dial the telephone number that is stored for speed-dial 1 on Cisco Unified Communications Manager or Cisco Unified CME, an analog phone user presses *11.
Configuration Examples for SCCP Controlled Analog (FXS) Ports with Supplementary Features in Cisco IOS Gateways
The following example shows a configuration for a Cisco VG224 Analog Phone Gateway:
The following example shows the expanded command for call-control mode feature:
You can now configure a string of up to 4 characters (0 – 9, *, #) as the feature code for the 5 features (the defaults are #1 for “hangup last active call”, #2 for “transfer”, #3 for “conference”, #4 for “drop last conferee”, and #5 for “toggle between two calls”) under stcapp feature mode.
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 SCCP Controlled Analog (FXS) Ports with Supplementary Features in Cisco IOS Gateways
Table 3 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.4(2)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 3 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.
|
|
|
---|---|---|
Adds FAC for Cancel Call Waiting feature. The following sections provide information about this feature: The following commands were introduced or modified by this feature: cancel-call-waiting, show stcapp device, show stcapp feature codes. |
||
Enables distinct ring tone to alert user whether incoming call is from an internal or external phone. The following section provides information about this feature: The following command was modified by this feature: ring cadence |
||
Allows you to define two-digit speed-dial codes for accessing up to 99 local speed-dial numbers configured on the call-control device. The following sections provide information about this feature: The following commands were new or modified by this feature: digit, speed dial |
||
Allows you to configure feature codes for feature access codes (FACs), and the speed-dial code for Redial, so that phone users are not required to dial the prefix before dialing the feature code to access an SCCP feature on an analog phone. The following sections provide information about this feature:
The following commands were modified by this feature: call forward all, call forward cancel, pickup direct, pickup group, pickup local, redial. |
||
Allows you to configure feature codes for Flexible feature access codes (FACs) so that phone users are not required to dial the prefix or special characters to access an SCCP feature on an analog phone. The following sections provide information about this feature: The following commands were modified by this feature: call forward all, call forward cancel, pickup direct, pickup group, pickup local, redial. |
||
Adds FAC for Forward to Voice Mail feature. The following sections provide information about this feature: |
||
SCCP Controlled Analog (FXS) Ports with Supplementary Features in Cisco IOS Gateways |
Enables SCCP supplementary features on analog FXS ports on a Cisco VG224 Analog Phone Gateway under the control of Cisco Unified Communications Manager or Cisco Unified CME. The following sections provide information about this feature: The following commands were introduced or modified by this feature: call forward all, call forward cancel, debug voip application stcapp buffer-history, pickup direct, pickup group, pickup local, prefix (stcapp-fac), prefix (stcapp-fsd), redial, show stcapp buffer-history, show stcapp device, show stcapp feature codes, speed dial, stcapp feature access-code, stcapp feature speed-dial, voicemail (stcapp-fsd). |
|
Adds support for SCCP supplementary features on analog FXS ports on Cisco ISRs. |
||
Adds FAC to enable user on an analog SCCP phone to start or join a meet-me conference call. To initiate a meet-me conference, a phone user presses the FAC prefix and feature code for SCCP Meet-Me Conference (default **5) and dials the meet-me conference number. Participants can join the conference by dialing in. The following sections provide information about this feature: The following commands were introduced by this feature: meetme-conference. |