Information About Feature Access Codes

Download as pdf or txt
Download as pdf or txt
You are on page 1of 6

Feature Access Codes

• Information About Feature Access Codes, on page 1


• Configure Feature Access Codes, on page 3
• Verify Feature Access Codes, on page 4
• Configuration Examples for Feature Access Codes, on page 5
• Feature Information for Feature Access Codes, on page 5

Information About Feature Access Codes


Feature Access Codes
Feature Access Codes (FACs) are special patterns of characters that are dialed from a telephone keypad to
invoke particular features. For example, a phone user might press **1, then press 2345 to forward all incoming
calls to extension 2345.
Typically, FACs are invoked using a short sequences of digits that are dialed using the keypad on an analog
phone, while IP phone users select softkeys to invoke the same features. In Cisco Unified CME 4.0 and later,
the same FACs that are available for analog phones can be enabled on IP phones. This allows phone users to
select a particular feature or activate/deactivate a function in the same manner regardless of phone type.
FACs are disabled on IP phones until they are explicitly enabled. You can enable all standard FACs for all
SCCP phones registered in Cisco Unified CME or you can define a custom FAC or alias to enable one or
more individual FACs.
All FACs except the call-park FAC are valid only immediately after a phone is taken off hook. The call-park
FAC is considered a transfer to a call-park slot and therefore is only valid after the Transfer softkey (IP phones)
or hookflash (analog phones) is used to initiate a transfer.

Note Directory Numbers configured on the Unified CME router should not overlap with the numbers you assign
for FAC Standard or FAC Custom in a FAC configuration. Also, ensure that the FAC code always starts with
an asterisk, followed by digits.

Feature Access Codes


1
Feature Access Codes
Feature Access Codes

Note For Custom FAC configuration, no two FAC codes should overlap with one another. A sample configuration
(with 54 overlapping) that you need to avoid, is as follows:

telephony-service fac custom


dnd *54
ephone-hunt hlog-phone *5432

Table 1: Standard Feature Access Codes, on page 2 contains a list of the standard predefined FACs.

Table 1: Standard Feature Access Codes

Standard FAC Description

**1 plus optional extension Call forward all.


number

**2 Call forward all cancel.

**3 Pick up local group.

**4 plus group number Pick up a ringing call in the specified pickup group. Specified pickup group
must already configured in Cisco Unified CME.

**5 plus extension number Pick up direct extension.

**6 plus optional park-slot Call park, if the phone user has an active call and if the phone user presses
number the Transfer softkey (IP phone) or hookflash (analog phone) before dialing
this FAC. Target park slot must be already configured in Cisco Unified
CME.

**7 Do not disturb.

**8 Redial.

**9 Dial voice-mail number.

*3 plus hunt group pilot number Join ephone-hunt group. If multiple hunt groups have been created that
allow dynamic membership, the hunt group to be joined is identified by its
pilot number.

*4 Activate or deactivate hunt group logout functionality to toggle between


ready/not-ready status of an extension when the hunt group agent is
off-hook.

*5 Activate or deactivate phone-level hunt group logout to toggle between


ready/not-ready status of all extensions on a individual phone that is a
member of an ephone hunt group when the phone is idle.

*6 Dials the voice-mail number.

#3 Leave ephone-hunt group. Telephone or extension number must already


be configured as a dynamic member of a hunt group.

Feature Access Codes


2
Feature Access Codes
Configure Feature Access Codes

Configure Feature Access Codes


To enable standard FACs or create custom FACs, perform the following steps:

SUMMARY STEPS
1. enable
2. configure terminal
3. telephony-service
4. fac {standard | custom {alias alias-tag custom-fac to existing-fac [extra-digits]} | feature
custom-fac}}
5. end

DETAILED STEPS

Command or Action Purpose


Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.
Router> enable

Step 2 configure terminal Enters global configuration mode.


Example:
Router# configure terminal

Step 3 telephony-service Enters telephony-service configuration mode.


Example:
Router(config)# telephony-service

Step 4 fac {standard | custom {alias alias-tag custom-fac to Enables standard FACs or creates a custom FAC or alias.
existing-fac [extra-digits]} | feature custom-fac}}
• standard—Enables standard FACs for all phones.
Example:
• custom—Creates a custom FAC for a FAC type.
Router(config-telephony)# fac custom callfwd *#5
• alias—Creates a custom FAC for an existing FAC or
a existing FAC plus extra digits.
• alias-tag—Unique identifying number for this alias.
Range: 0 to 9.
• custom-fac—User-defined code to be dialed using the
keypad on an IP or analog phone. Custom FAC can
be up to 256 characters long and contain numbers 0 to
9 and * and #.
• to—Maps custom FAC to specified target.
• existing-fac—Already configured custom FAC that is
automatically dialed when the phone user dials the
custom FAC being configured.

Feature Access Codes


3
Feature Access Codes
Verify Feature Access Codes

Command or Action Purpose


• extra-digits—(Optional) Additional digits that are
automatically dialed when the phone user dials the
custom FAC being configured.
• feature—Predefined alphabetic string that identifies a
particular feature or function. Type ? for a list.

Step 5 end Returns to privileged EXEC mode.


Example:
Router(config-telephony)# end

Verify Feature Access Codes


To verify the FAC configuration, perform the following step.

show telephony-service fac


Example:
This command displays a list of FACs that are configured on the Cisco Unified CME router. The following example
shows the output when standard FACs are enabled:

Router# show telephony-service fac


telephony-service fac standard
callfwd all **1
callfwd cancel **2
pickup local **3
pickup group **4
pickup direct **5
park **6
dnd **7
redial **8
voicemail **9
ephone-hunt join *3
ephone-hunt cancel #3
ephone-hunt hlog *4
ephone-hunt hlog-phone *5
trnsfvm *6

The following example shows the output when custom FACs are configured:

Router# show telephony-service fac


telephony-service fac custom
callfwd all #45
alias 0 #1 to **4121
alias 1 #2 to **4122
alias 4 #4 to **4124

Feature Access Codes


4
Feature Access Codes
Configuration Examples for Feature Access Codes

Configuration Examples for Feature Access Codes


Example for Enabling Standard FACs for All Phones
The following example shows how to enable standard FACs for all phones:

Router# telephony-service
Router(config-telephony)# fac standard
fac standard is set!
Router(config-telephony)#

The following example shows how the standard FAC for the Call Forward All feature is changed to a custom
FAC (#45). Then an alias is created to map a second custom fac to #45 plus an extension (1111). The custom
FAC (#44) allows the phone user to press #44 to forward all calls to extension 1111, without requiring the
phone user to dial the extra digits that are the extension number.

Router# telephony-service
Router(config-telephony)# fac custom callfwd all #45
fac callfwd all code has been configured to #45
Router(config-telephony)# fac custom alias 0 #44 to #451111
fac alias0 code has been configurated to #44!
alias0 map code has been configurated to #451111!

The following example shows how to define an alias for the group pickup of group 123. The alias substitutes
the digits #4 for the standard FAC for group pickup (**4) and adds the group number (123) to the dial pattern.
Using this custom FAC, a phone user can dial #4 to pick up a ringing call in group 123, instead of dialing the
standard FAC **4 plus the group number 123.

Router# telephony-service
Router(config-telephony)# fac custom alias 5 #4 to **4123

Feature Information for Feature Access Codes


The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Table 2: Feature Information for Feature Access Codes

Feature Name Cisco Unified CME Version Feature Information

Transfer to Voice Mail. 7.0/4.3 FAC for Transfer to Voice Mail was added.

Feature Access Codes (FACs) 4.0 FACs were introduced.

Feature Access Codes


5
Feature Access Codes
Feature Information for Feature Access Codes

Feature Access Codes


6

You might also like