Configuring Feature Mode
First Published: June 22, 2006
Last Updated: March 19, 2010
This module describes how to enable the Skinny Client Control Protocol (SCCP) feature mode call-control mode for analog foreign exchange service (FXS) ports on Cisco voice gateways, including Cisco VG224 Analog Phone Gateways and Cisco Integrated Services Routers (ISRs), and 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 Feature Mode for SCCP FXS Ports in Cisco IOS Feature” 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.
Restrictions for Feature Mode for SCCP FXS Ports in Cisco IOS
Analog Endpoints in Cisco Unified CME
- Autoconfiguration using TFTP download of extensible markup language (XML) dial-peer configuration files from Cisco Unified Communications Manager is not supported
- This feature is not supported on a VIC2-2BRI-NT/TE.
Information About Feature Mode for SCCP FXS Ports in Cisco IOS
To configure the Feature Mode for SCCP FXS Ports in Cisco IOS feature, you should understand the following concepts:
Summary of Supported Features in Feature Mode
Table 1 contains a list of SCCP supplementary features that are supported in feature mode 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.
Table 1 Feature Mode: Supported Supplementary Features
|
How Phone User Accesses Feature
|
Configuration on Call-Control System
|
Connects call to a third party that the phone user dials. |
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 #2 to transfer the call; the user hears silence after the call is transferred. |
Cisco Unified Communications Manager
For feature information, see the “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. |
Initiates a three-party conference. |
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. |
Cisco Unified Communications Manager
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 Guid e.
To configure, see “Configuring Conferencing” in the Cisco Unified CME Administration Guide. |
|
Cisco Unified Communications Manager
The next hookflash after a three-party conference call is established drops the last conferee.
During a three-party conference, user presses hookflash to get feature tone and then dials #4 to drop the last active party. The conference becomes a basic call to the second call party. |
No additional configuration is required on the Cisco call-control system. |
|
During a three-party conference, user presses hookflash to get feature tone and then dials #1 to drop the last active call party. The conference becomes a basic call. |
Cisco Unified Communications Manager
No additional configuration is required on the Cisco call-control system.
The keep-conference drop-last command is enabled on Cisco router. For configuration information, see the “ Configuring Conferencing ” module in the Cisco Unified CME Administration Guide. |
|
User in basic call mode presses hookflash to get the first dial tone, then dials an extension number to connect to a second call. During the second call, user presses a hookflash to get feature tone and then dials #5 to toggle back to the previous call party. |
No additional configuration is required on the Cisco call-control system. |
Feature Mode for SCCP FXS Ports in Cisco IOS
In Cisco IOS Release 12.4(6)XE and later releases, Feature Mode for SCCP FXS Ports in Cisco IOS provides enhanced call-control mode capability on analog ports on Cisco voice gateways. Before Cisco IOS Release 12.4(6)XE, the SCCP analog gateway supported only standard mode feature activation, the default telephony mode which provides standard Bellcore features.
When feature mode is enabled on a Cisco voice gateway, calls through the analog FXS ports are controlled by Cisco Unified Communications Manager or by Cisco Unified CME, with basic call support in SRST mode. The SCCP telephony control (STC) application on the Cisco voice gateway functions as a proxy to translate call-control messages between the Cisco call-control system and the voice gateway.
In feature mode, the user enters a specific combination of digits called feature access codes (FACs) consisting of a prefix plus a feature code, for example #1. The prefix for FACs in feature mode is a number sign (#). In standard mode, the user uses a hookflash to activate supplementary features like call transfer and call conference.
Feature mode is limited to outgoing calls only. All feature mode functions are performed after the second call is established. A user in basic call mode performs a hookflash to get the first dial tone, then dials an extension number to connect to a second call. When the second call is established, the user performs a hookflash to get a feature tone, a special dial tone used to indicate feature mode, then dials the FAC.
Table 2 lists FACs used to access telephony features in feature mode only.
Table 2 FACs Used to Access Telephony Features in Feature Mode
|
|
Drop last active call |
#1 |
Call transfer |
#2 |
Call conference |
#3 |
Drop last conferee |
#4 |
Toggle between two calls |
#5 |
Note For a list of FACs and feature speed dials (FSDs) that are available in both feature mode and standard mode, see the “Summary of SCCP Supplementary Features for FXS ports” section.
For configuration information for feature mode, see the “How to Configure Feature Mode for SCCP FXS Ports in Cisco IOS” section.
Flexible FACs in Feature Mode
Before Cisco IOS Release 15.0(1)M, FACs in feature mode were limited to two characters (# and 1 to 5) and could not be modified.
In Cisco IOS Release 15.0(1)M and later releases, you can configure FACs for accessing features that are supported in feature mode to create four-character (0-9, #, *) strings that can be dialed on the keypad after the user hears the feature tone. The default FACs for telephony features in feature mode continue to be supported. For default FACs in feature mode, see Table 2 .
If you attempt to set a FAC to a value that is already configured for another FAC in feature mode, you receive a warning message. If you configure a duplicate FAC, the system implements the first feature it matches in the order of precedence as determined by the value for each FAC.
If you attempt to set a FAC to a value that precludes or is precluded by another FAC in feature mode, you receive a warning message. For example, if you attempt to set a FAC of 123 and 12 is already configured for another feature, such as Call Transfer, the following message appears:
123 is precluded by call transfer(12)
Or if you attempt to configure1 and 12 is already configured for another feature, such as Call Transfer, the following message appears:
1 precludes call transfer(12)
These messages will not prevent you from configuring the feature code.
For configuration information, see the “Configuring Flexible FACs in Feature Mode” section.
Feature Mode Error Handling
If the user does nothing after feature tone is heard, the interdigit timeout expires and a fast busy tone is played. The user must press hookflash again to toggle back to the previous state. User input other than a hookflash is not accepted during a fast busy tone.
If the user dials an incorrect combination of digits, the fast busy tone is played. The user must perform a hookflash to toggle back to the previous state.
If the user hangs up after feature tone is heard, then power-ring-back on the phone is played. If the user goes off hook, the user is connected to the first call.
If the user performs any of the following actions, the call is transferred:
- Hangs up after feature tone is heard and before the interdigit timeout expires.
- Hangs up after feature tone is heard and after the interdigit timeout expires and the fast busy tone is heard.
- Hangs up after the feature tone is heard and after an incomplete digit is pressed and no fast busy tone is heard.
- Hangs up after the feature tone is heard and after an incorrect digit combination is pressed and a fast busy tone is heard.
How to Configure Feature Mode for SCCP FXS Ports in Cisco IOS
This section contains the following tasks:
Configuring Feature Mode
To configure feature mode for SCCP analog phones on a Cisco voice gateway and enable SCCP analog phones to invoke features using standard FACs after hookflash, perform the following steps.
SUMMARY STEPS
1. enable
2. configure terminal
3. stcapp call-control mode feature
4. end
DETAILED STEPS
|
|
|
Step 1 |
enable
Router> enable |
Enables privileged EXEC mode.
- Enter your password if prompted.
|
Step 2 |
configure terminal
Router# configure terminal |
Enters global configuration mode. |
Step 3 |
stcapp call-control mode feature
Router(config)# stcapp call-control mode feature |
Enables feature call control mode. |
Step 4 |
exit
Router(config-stcapp-fmcode)# exit |
Exits global configuration mode. |
Troubleshooting the Feature Mode for SCCP FXS Ports Configuration
Use the following commands to verify and troubleshoot call control modes and display debugging information for feature mode calls:
- show stcapp feature codes —Displays feature access codes.
- debug voip application stcapp all —Displays debugging messages for STC application-controlled phones configured in feature mode.
- debug voip application stcapp port —Displays debugging information for the components of the STCAPP for a specified port
- debug vpm signal —Displays information for signaling events for feature and standard mode calls, including PBX signaling.
For information about these commands, see the Cisco IOS Voice Command Reference or the Cisco IOS Debug Command Reference, Release 12.4T, and Cisco IOS Configuration Fundamentals Command Reference, Release 12.4.
Configuring Flexible FACs in Feature Mode
To define a feature access codes (FACs) to invoke features supported in feature mode, perform the following steps.
Prerequisites
- Cisco IOS Release 15.0(1)M or a later release.
Restrictions
- If you configure the same value for more than one feature code in feature mode, the system implements the first feature it matches in the order of precedence.
- If you configure a FAC to a value that precludes or is precluded by another FAC in feature mode, the system implements the feature with the shortest FAC first. The precluded FAC cannot be implemented.
SUMMARY STEPS
1. enable
2. configure terminal
3. stcapp call-control mode feature
4. conference keypad-character
5. hangup-last-active-call keypad-character
6. drop-last-conferee keypad-character
7. toggle-between-two-calls keypad-character
8. transfer keypad-character
9. end
DETAILED STEPS
|
|
|
Step 1 |
enable
Router> enable |
Enables privileged EXEC mode.
- Enter your password if prompted.
|
Step 2 |
configure terminal
Router# configure terminal |
Enters global configuration mode. |
Step 3 |
stcapp call-control mode feature
Router(config-stcapp-fmcode)# stcapp call-control mode feature |
Enables feature call control mode and enters STC application feature-call-control configuration mode. |
Step 4 |
conference keypad-character
Router(config-stcapp-fmcode)# conference * |
(Optional) Sets the code to use for initiating a three-party conference.
- keypad-character —String that can be dialed on a phone keypad. The length of keypad-character must be 1 to 4 characters (0-9, #, *). Default is #3.
|
Step 5 |
drop-last-conferee keypad-character
Router(config-stcapp-fmcode)# drop-last-conferee 44 |
(Optional) Sets the code to use for dropping last active call during a three-party conference.
- keypad-character —String that can be dialed on a phone keypad. The length of keypad-character must be 1 to 4 characters (0-9, #, *). Default is #4.
- The keep-conference drop-last command must be enabled on Cisco router.
|
Step 6 |
hangup-last-active-call keypad-character
Router(config-stcapp-fmcode)# hangup-last-active-call 11 |
(Optional) Sets the code to use for dropping last active call during a three-party conference.
- For phones controlled by Cisco Unified CME. This command does not affect user experience on phones controlled by Cisco Unified Communications Manager.
- keypad-character —String that can be dialed on a phone keypad. The length of keypad-character must be 1 to 4 characters (0-9, #, *). Default is #1.
|
Step 7 |
toggle-between-two-calls keypad-character
Router(config-stcapp-fmcode)# toggle-between-two-calls 55 |
(Optional) Sets the code to use for toggling between two active calls.
- keypad-character —String that can be dialed on a phone keypad. The length of keypad-character must be 1 to 4 characters (0-9, #, *). Default is #5.
|
Step 8 |
transfer keypad-character
Router(config-stcapp-fmcode)# transfer ## |
(Optional) Sets the code to use for connecting a call to a third party that the phone user dials.
- keypad-character —String that can be dialed on a phone keypad. The length of keypad-character must be 1 to 4 characters (0-9, #, *). Default is #2.
|
Step 9 |
end
Router(config-stcapp-fmcode)# end |
Exits STC application feature access-code configuration mode and returns to privileged EXEC mode. |
Examples
The following example shows how to change the value of the feature code for supplementary features supported in feature mode from the defaults:
Router(config)# stcapp call-control mode feature
Router(config-stcapp-fmcode)# conference 33
Router(config-stcapp-fmcode)# drop-last-active-conferee 44
Router(config-stcapp-fmcode)# hangup-last-active-call 11
Router(config-stcapp-fmcode)# toggle-between-two-calls 55
Router(config-stcapp-fmcode)# transfer 22
Router(config-stcapp-fmcode)# exit
Configuration Examples for Feature Mode for SCCP FXS Ports in Cisco IOS
The following example shows feature call control mode enabled:
Router# show running-config
stcapp call-control mode feature
The following example shows standard call control mode enabled:
Router# show running-config
stcapp call-control mode standard
Additional References
The following sections provide references related to the Feature Mode for SCCP FXS Ports in Cisco IOS feature.
Technical Assistance
|
|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
http://www.cisco.com/techsupport |
Feature Information for Feature Mode for SCCP FXS Ports in Cisco IOS Feature
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(6)XE 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.
Table 3 Feature Information for Feature Mode for SCCP FXS Ports in Cisco IOS Feature
|
|
|
Feature Mode for SCCP FXS Ports in Cisco IOS |
12.4(6)XE 12.4(11)T |
Enables feature mode call control on analog FXS ports on Cisco voice gateways and 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: debug voip application stcapp all ; debug voip application stcapp port ; show stcapp feature codes ; stcapp call-control mode |
Flexible FACs in Feature Mode |
15.0(1)M |
Enables configurable feature access codes (FACs) for accessing supplementary features that are supported in feature mode. The following sections contain information about this feature:
The following commands were introduced or modified by this feature: conference ; drop-last-conferee ; hangup-last-active-call ; toggle-between-two-calls ; transfer |