To define an extension (ephone-dn) as a paging extension that can be called to broadcast an audio page to a set of Cisco IP phones, use the paging command in ephone-dn configuration mode. To disable this feature, use the no form of this command.

Syntax Description

Command Default

No paging number is established.

Command Modes

Ephone-dn configuration (config-ephone-dn)

Command History

Usage Guidelines

To configure a set of phones to receive an audio page, follow these steps:

1. Use the paging command in ephone-dn configuration mode to define a number that people can dial to send a page. The following example defines a paging-dn tag (21) and extension number (34455) to dial to send a page.

ephone-dn 21
 paging 
 number 34455

1. Use the paging-dn command in ephone configuration mode to assign the same paging-dn tag that you defined in Step 1 to all the phones that you want to receive the page. This set of phones is called a “paging set.” You can have more than one paging set in a Cisco CME system. The following example assigns the paging-dn tag from Step 1 (21) to two phones (3 and 4) so that they will receive audio pages.

ephone 3
 paging-dn 21
ephone 4
 paging-dn 21

The paging command configures an ephone-dn as an extension that people can dial to broadcast audio pages to a specified set of idle Cisco IP phones. The extension associated with this command does not appear on any ephone; it is a “dummy” extension. The dn-tag associated with this extension becomes the paging-dn tag for this paging set.

When a person dials the number assigned to the dummy extension and speaks into the phone, the audio stream is sent as a page to the paging set (the set of all phones that have been configured with this paging-dn tag as an argument to the paging-dn command). Idle phones in the paging set automatically answer the paging call in one-way speakerphone mode. Paging sets can be joined into a single combined paging group with the paging group command.

The optional ip keyword and multicast-address argument define a paging multicast address for this paging set. If an IP multicast address is not configured, IP phones are paged individually using IP unicast transmission (to a maximum of ten IP phones). The recommended operation is with an IP multicast address. When multiple paging-dn tags are configured using the paging command, each paging-dn tag should use a unique IP multicast address.

Note	IP phones do not support multicast at 224.x.x.x addresses.

Each ephone-dn and paging-dn tag that is used for paging can support a maximum of ten distinct targets (IP addresses and interfaces). A multicast address counts as a single target for each physical interface in use (regardless of the number of phones connected via the interface). Paging using a single IP multicast address that requires output on three different Ethernet interfaces represents use of three counts out of the maximum ten. Each unicast target counts as a single target, such that paging that does not use multicast at all is limited to paging ten phones. For example, ten IP phones paged through multicast on Fast Ethernet interface 0/1.1 plus five IP phones paged through multicast on Fast Ethernet interface 0/1.2 are counted as two targets.

For simultaneous paging to more than one paging ephone-dn, Cisco recommends that you use different IP multicast addresses (not just different port numbers) for paging configuration.

Related Commands

To create a combined paging group from two or more previously established paging sets, use the paging group command in ephone-dn configuration mode. To remove a paging group, use the no form of this command.

Syntax Description

Command Default

Paging is disabled on all Cisco IP phones.

Command Modes

Ephone-dn configuration (config-ephone-dn)

Command History

Usage Guidelines

Use this command to combine previously defined sets of phones associated with individual paging extensions (ephone-dns) into a combined group to enable a single page to be sent to large numbers of phones at once. To remove a paging group, use the no form of the command. All paging-dn tags included in the list must have already been defined as paging-dns using the paging or paging-dn (voice register) command.

The use of paging groups not only allows phones to participate in a small local paging set (for example, paging to four phones in a company’s shipping and receiving department) but also supports company-wide paging when needed (for example, by combining the paging sets for shipping and receiving with the paging sets for accounting, customer support, and sales into a single paging group).

Note	The correct paging port for the paging-dn of Cisco Unified SIP IP phones in the paging command is an even number from 20480 to 32768. If you enter a wrong port number, a SIP REFER message request is sent to the IP phone but the Cisco Unified SIP IP phone is not paged.

Related Commands

To create a paging extension (paging-dn) to receive audio pages on a Cisco Unified IP phone in a Cisco Unified CME system, use the paging-dn command in ephone or ephone-template configuration mode. To disable this feature, use the no form of this command.

Syntax Description

Command Default

Paging is disabled on all Cisco Unified IP phones.

Command Modes

Ephone configuration (config-ephone)
Ephone-template configuration (config-ephone-template)

Command History

Usage Guidelines

To configure a set of phones to receive an audio page, follow these steps:

1. Use the paging command in ephone-dn configuration mode to define a number that people can dial to send a page. The following example defines a paging-dn tag (21) and extension number (34455) to dial to send a page.

ephone-dn 21
 paging 
 number 34455

1. Use the paging-dn command in ephone configuration mode to assign the same paging-dn tag that you defined in Step 1 to all the phones that you want to receive the page. This set of phones is called a “paging set.” You can have more than one paging set in a Cisco Unified CME system. The following example assigns the paging-dn tag from Step 1 (21) to two phones (3 and 4) so that they will receive audio pages.

ephone 3
 paging-dn 21
ephone 4
 paging-dn 21

This command creates a paging extension (paging-dn) associated with an IP phone. Each phone can support only one paging-dn extension. This extension does not occupy a phone button and is therefore not configured on the phone with the button command. The paging-dn allows the phone to automatically answer audio pages in one-way speakerphone mode. There is no press-to-answer option as there is with an intercom extension.

The paging-dn-tag argument in this command takes the value of the dn-tag of an extension (ephone-dn) that has been made a paging ephone-dn using the paging command. This command is the extension that callers dial to deliver an audio page. All of the phones that are going to receive the same audio pages are configured with the same paging-dn-tag. These phones form a paging set.

An IP phone can belong to only one paging set, but any number of phones can belong to the same paging set using multicast. There can be any number of paging sets in a Cisco Unified CME system, and paging sets can be joined to create a combined paging group using the paging group command. For example, you may create separate paging sets for each department (sales, support, shipping) and combine them into a single combined paging group (all departments). Only single-level grouping is supported (no support for groups of groups).

Normal phone calls that are received while an audio page is in progress interrupt the page.

The paging mechanism supports audio distribution using IP multicast, replicated unicast, and a mixture of both (so that multicast is used where possible, and unicast is used with specific phones that cannot be reached through multicast).

Note	For unicast paging to all phones, omit the IP multicast address in the ephone-dn configuration. For unicast paging to a specific phone using an ephone-dn configured for multicast, add the unicast keyword as part of the paging-dn command in ephone configuration mode.

If you use an ephone template to apply a command to a phone and you also use the same command in ephone configuration mode for the same phone, the value that you set in ephone configuration mode has priority.

Related Commands

To register a Cisco Unified SIP IP phone to an ephone-dn paging directory number (DN), use the paging-dn command in voice register pool or voice register template configuration mode. To unregister the Cisco Unified SIP IP phone from the paging directory number, use the no form of this command.

Syntax Description

Command Default

The Cisco Unified SIP IP phone is not registered to an ephone-dn paging DN and paging is disabled.

Command Modes

Voice register pool configuration (config-register-pool)

Voice register template configuration (config-register-temp)

Command History

Usage Guidelines

The paging-dn command applies to both voice register pool and voice register template configuration modes. When voice register pool is configured with the template and paging is configured in voice register pool configuration mode, paging in voice register pool configuration mode has higher precedence over paging in voice register template configuration mode.

The correct paging port for the paging-dn of Cisco Unified SIP IP phones in the paging command is an even number from 20480 to 32768. If you enter a wrong port number, a SIP REFER message request is sent to the IP phone but the Cisco Unified SIP IP phone is not paged.

Related Commands

To load and configure parameters in a package or a service (application) on the gateway, use the param command in application configuration mode. To reset a parameter to its default value, use the no form of this command.

Syntax Description

Command Default

No default behavior or value.

Command Modes

Application configuration

Command History

Usage Guidelines

Use this command in application parameter configuration mode to configure parameters in a package or service. A package is a linkable set of C or Tcl functions that provide functionality invoked by applications or other packages. A service is a standalone application.

The parameters available for configuration differ depending on the package or service that is loaded on the gateway. The param register Tcl command in a service or package registers a parameter and provides a description and default values which allow the parameter to be configured using the CLI. The param register command is executed when the service or package is loaded or defined, along with commands such as package provide, which register the capability of the configured module and its associated scripts. You must configure and load the Tcl scripts for your service or package and load the package in order to configure its parameters. See the Tcl IVR API Version 2.0 Programming Guide for more information.

When a package or service is defined on the gateway, the parameters in that package or service become available for configuration when you use this command. Additional arguments and keywords are available for different parameters. To see a list of available parameters, enter param ?.

To avoid problems with applications or packages using the same parameter names, the parameter namespace, or parameterspace concept is introduced. When a service or a package is defined on the gateway, its parameter namespace is automatically defined. This is known as the service or package’s local parameterspace, or “myparameterspace.” When you use this command to configure a service or package’s parameters, the parameters available for configuration are those contained in the local parameterspace. If you want to use parameter definitions found in different parameterspace, you can use the paramspace parameter-namespace command to map the package’s parameters to a different parameterspace. This allows that package to use the parameter definitions found in the new parameterspace, in addition to its local parameterspace.

Use this command in Cisco Unified Communication Manager Express 8.5 and later versions to define the username and password parameters to authenticate packages for Forced Authorization Code (FAC)

When a predefined password is entered using the param passwd keyword, callers are not requested to enter a password. You must define a filename for user-prompt to play an audio prompt requesting the caller to enter a valid username (in digits) for authorization. Similarly, you must define a filename for passwd-prompt to play an audio prompt requesting the caller to enter a valid password (in digits) for authorization.

Related Commands

To declare a Cisco Unified CME B-ACD menu number and associate it with the pilot number of an ephone hunt group, use the param aa-hunt command in application-parameter configuration mode. To remove the menu number and the ephone hunt group pilot number, use the no form of this command.

Syntax Description

Command Default

Menu number 1 is configured, but it is not associated with a pilot number.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant (B-ACD) service. It is configured under the service command for the call-queue script.

Up to ten aa-hunt menu options, or hunt groups, are allowed per call-queue service. You can use any of the allowable numbers in any order.

This command associates a menu option with the pilot number of an ephone hunt group. When a caller presses the digit of a menu option that has been associated with an ephone hunt group using this command, the call is routed to the pilot number of the hunt group.

Menu options for B-ACD services can be set up in many ways. For more information, see the Cisco Unified CallManager Express B-ACD and Tcl Call-Handling Applications document for your release.

The highest aa-hunt number that you establish using this command also automatically maps to zero (0) and can therefore be used to represent operator services to your callers. In the following example, callers can dial either 8 or 0 to reach aa-hunt8, the hunt group with the pilot number 8888.

application
 service queue flash:
  param aa-hunt1 1111
  param aa-hunt3 3333
  param aa-hunt8 8888

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

Related Commands

To assign a pilot number to a Cisco Unified CME B-ACD automated attendant (AA) service, use the param aa-pilot command in application-parameter configuration mode. To remove the AA pilot number, use the no form of this command.

Syntax Description

Command Default

Cisco Unified CME B-ACD menu number 1 is configured, but it has no pilot number.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant (B-ACD) service. Each AA has one AA pilot number, although there may be more than one AA used with a B-ACD service.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For more information, see the Cisco Unified CallManager Express B-ACD and Tcl Call-Handling Applications document for your release.

Related Commands

To specify the time interval before each attempt to retry to connect a call to an ephone hunt group used with a Cisco CME B-ACD service, use the param call-retry-timer command in application-parameter configuration mode. To return to the default, use the no form of this command.

Syntax Description

Command Default

Default is 15 seconds.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant (B-ACD) service. This command is configured under the service command for an AA service. A Cisco Unified CME B-ACD service can have more than one AA, and each AA can specify a different interval for retries to connect to ephone hunt group phones.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For more information, see the Cisco Unified CallManager Express B-ACD and Tcl Call-Handling Applications document for your release.

Related Commands

To set the upper boundary of the range of valid digits coming from the PSTN Central Office (CO) for use with the Direct Inward Dial (DID) Digit Translation Service, use the param co-did-max command in application-parameter configuration mode. To disable this option, use the no form of this command.

Syntax Description

Command Default

No maximum value is defined for the range of digits coming from the CO.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command defines the upper limit of the range of digits accepted from the CO when it is used with the Cisco Unified CallManager Express (Cisco Unified CME) DID Digit Translation Service. This service provides number translation for DID calls when the range of DID digits provided by the PSTN Central Office (CO) does not match the digits in the Cisco Unified CME extension numbers.

The Tcl script that provides the service accepts PSTN DID numbers of any length and maps them to the internal extension numbers that are assigned by a system administrator. Where necessary, a prefix is appended to the DID digits to create a valid extension number. The script uses the parameters that you input to determine the valid range of digits to be accepted from the CO, the valid range of digits in the local dial plan, and the prefix to append, if necessary. The script also handles DID calls that map to invalid extension numbers: a prompt is played and the calls are disconnected.

Related Commands

To set the lower boundary of the range of valid digits coming from the PSTN Central Office (CO) that is used with the Direct Inward Dial (DID) Digit Translation Service, use the param co-did-min command in application-parameter configuration mode. To disable this option, use the no form of this command.

Syntax Description

Command Default

No minimum value is defined for the range of digits coming from the CO.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command defines the upper limit of the range of digits accepted from the CO when it is used with the Cisco Unified CallManager Express (Cisco Unified CME) DID Digit Translation Service. This service provides number translation for DID calls when the range of DID digits provided by the PSTN Central Office (CO) does not match the digits in the Cisco Unified CME extension numbers.

The Tcl script that provides the service accepts PSTN DID numbers of any length and maps them to the internal extension numbers that are assigned by a system administrator. Where necessary, a prefix is appended to the DID digits to create a valid extension number. The script uses the parameters that you input to determine the valid range of digits to be accepted from the CO, the valid range of digits in the local dial plan, and the prefix to append, if necessary. The script also handles DID calls that map to invalid extension numbers: a prompt is played and the calls are disconnected.

Related Commands

To assign a menu number to an Cisco CME B-ACD option by which callers can directly dial known extension numbers, use the param dial-by-extension-option command in application-parameter configuration mode. To disable this option, use the no form of this command.

Syntax Description

Command Default

Dial-by-extension option is not assigned.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant (B-ACD) service. This command is configured under the service command for an AA service.

This command allows you to designate a menu option number for callers to press if they want to dial an extension number that they already know. This command also enables the playing of the en_bacd_enter_dest.au audio file after a caller presses the dial-by-extension menu number. The default announcement in this audio file is “Please enter the extension number you want to reach.”

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For more information, see the Cisco Unified CallManager Express B-ACD and Tcl Call-Handling Applications document for your release.

Related Commands

To set a prefix to add to digits coming from the PSTN Central Office (CO) to create valid extension numbers when using the Direct Inward Dial (DID) Digit Translation Service, use the param did-prefix command in application-parameter configuration mode. To disable this option, use the no form of this command.

Syntax Description

Command Default

No prefix is defined.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CallManager Express (Cisco Unified CME) DID Digit Translation Service, which provides number translation for DID calls when the range of DID digits provided by the PSTN Central Office (CO) does not match the digits in the Cisco Unified CME extension numbers.

The Tcl script that provides the service accepts PSTN DID numbers of any length and maps them to the internal extension numbers that are assigned by a system administrator. Where necessary, a prefix is appended to the DID digits to create a valid extension number. The script uses the parameters that you input to determine the valid range of digits to be accepted from the CO, the valid range of digits in the local dial plan, and the prefix to append, if necessary. The script also handles DID calls that map to invalid extension numbers: a prompt is played and the calls are disconnected.

Related Commands

To assign the drop-through option to a Cisco Unified CME B-ACD auto-attendant (AA) application, use the param drop-through option command in application-parameter configuration mode. To disable this option, use the no form of this command.

Syntax Description

Command Default

Drop-through option is not assigned.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant (B-ACD) service. This command is configured under the service command for an AA service.

When an AA is configured for drop-through mode, the AA sends incoming calls directly to the call queue associated with the menu number specified in this command. Once in the queue, a caller hears ringback if an agent is available or music on hold (MOH) if all agents are busy. If a greeting prompt for drop-through mode is configured using the param drop-through-prompt command, a caller hears the prompt before being sent to the queue as described.

The menu option number is an aa-hunt number that is associated with an ephone hunt group using the param aa-hunt command.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For more information, see the Cisco Unified CallManager Express B-ACD and Tcl Call-Handling Applications document for your release.

Related Commands

To associate an audio prompt file with the drop-through option for a Cisco Unified CME B-ACD automated attendant (AA) application, use the param drop-through-prompt command in application-parameter configuration mode. To disable the prompt, use the no form of this command.

Syntax Description

Command Default

No prompt is designated for the drop-through option.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant (B-ACD) service. This command is configured under the service command for an AA service.

When an AA is configured for drop-through mode, the AA sends incoming calls directly to the call queue associated with the menu number specified in this command. Once in the queue, a caller hears ringback if an agent is available or music on hold (MOH) if all agents are busy. If an greeting prompt for drop-through mode is configured, a caller hears the prompt before being sent to the queue as described.

The menu option number is an aa-hunt number that is associated with an ephone hunt group using the param aa-hunt command.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For more information, see the Cisco Unified CallManager Express B-ACD and Tcl Call-Handling Applications document for your release.

Related Commands

To create a password for accessing the extension assigner application, use the param ea-password command in application-parameter configuration mode.

Syntax Description

Command Default

No password is created.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command creates a password for using the extension assigner application.

If this command is not configured, you cannot use the extension assigner application.

Note	There is no no form of this command. To change or remove the password for the extension assigner application, remove the service using the no form of the service command in application configuration mode.

Related Commands

To specify the name of a Cisco Unified CME B-ACD auto-attendant (AA) to be passed to the call-queue script, use the param handoff-string command in application-parameter configuration mode. To disable the handoff string, use the no form of this command.

Syntax Description

Command Default

No string is designated to be passed to the call-queue service.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant (B-ACD) service. This command is configured under the service command for an AA service.

The handoff string is used only when the call-queue script starts for the first time or restarts after a failure.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For more information, see the Cisco Unified CallManager Express B-ACD and Tcl Call-Handling Applications document for your release.

Related Commands

To specify the maximum number of digits callers can dial when they choose the dial-by-extension option from the Cisco Unified CME B-ACD service, use the param max-extension-length command in application-parameter configuration mode. To return to the default, use the no form of this command.

Syntax Description

Command Default

The default number of digits callers can dial using the dial-by-extension option is 5.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant (B-ACD) service. This command is configured under the service command for an AA service.

Use this command to restrict the number of digits that callers can dial when using the dial-by-extension option.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For more information, see the Cisco Unified CallManager Express B-ACD and Tcl Call-Handling Applications document for your release.

Related Commands

To specify the maximum length of time for which calls to the Cisco Unified CME B-ACD service can stay in a call queue, use the param max-time-call-retry command in application-parameter configuration mode. To return to the default, use the no form of this command.

Syntax Description

Command Default

A call in a B-ACD call queue continues to try to connect to a hunt group for 600 seconds.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution (B-ACD) and Auto-Attendant (AA) service. Configure this command under the service command for an AA service.

A call to a Cisco Unified CME B-ACD service is put into a call queue if the hunt group that the call tried to reach has no phones available to take the call because they are all busy. While the call is in the queue, a second greeting is played at intervals specified by the param second-greeting-time command. From the queue, the call makes retries to connect at intervals specified by the param call-retry-timer command until the maximum amount of time to be spent in the queue expires. The maximum amount of time is set by the param max-time-call-retry command. After the maximum amount of time expires, the call is routed to the alternate destination specified in the param voice-mail command. If the alternate destination number is busy, the call makes the number of retries to connect specified in the param max-time-vm-retry command. If the call is unable to connect to the alternate destination after the number of retries that has been specified, it is disconnected.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For configuration information, see the “Setting Up Call-Queue and AA Services” section in the Cisco Unified CME B-ACD and Tcl Call-Handling Applications document.

Related Commands

To specify the maximum number of times that calls in a Cisco Unified CME B-ACD call queue can attempt to connect to the alternate destination number, use the param max-time-vm-retry command in application-parameter configuration mode. To return to the default, use the no form of this command.

Syntax Description

Command Default

A call in a B-ACD call queue tries to connect to an alternate destination number 1 time.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant (B-ACD) service. This command is configured under the service command for an AA service.

A call to a Cisco Unified CME B-ACD service is put into a call queue if the hunt group that the call tried to reach has no phones available to take the call because they are all busy. While the call is in the queue, a second greeting is played at intervals specified by the param second-greeting-time command. From the queue, the call makes retries to connect at intervals specified by the param call-retry-timer command until the maximum amount of time to be spent in the queue expires. The maximum amount of time is set by the param max-time-call-retry command. After the maximum amount of time expires, the call is routed to the alternate destination specified in the param voice-mail command. If the alternate destination number is busy, the call makes the number of retries to connect specified in the param max-time-vm-retry command. If the call is unable to connect to the alternate destination after the number of retries that has been specified, it is disconnected.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For more information, see the Cisco Unified CallManager Express B-ACD and Tcl Call-Handling Applications document for your release.

Related Commands

To set the number of times the AA service will loop the menu prompt before connecting the caller to an operator if the caller does not select a menu option, use the param menu-timeout command in application-parameter configuration mode. To return to the default, use the no form of this command.

Syntax Description

Command Default

Auto-attendant service replays menu prompt 4 times before connecting the caller to an operator.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with Cisco Unified CME Basic Automatic Call Distribution (B-ACD) and Auto-Attendant (AA) service.

If a caller does not select a menu option before the timeout set with this command expires, the call is transferred to the operator hunt group. The operator hunt-group is the hunt group with the highest aa-hunt number set with the param aa-hunt command.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For configuration information, see the “Setting Up Call-Queue and AA Services” section in the Cisco Unified CME B-ACD and Tcl Call-Handling Applications document.

Related Commands

To specify the number of hunt groups used with a Cisco Unified CME B-ACD call-queue or AA service, use the param number-of-hunt-grps command in application-parameter configuration mode. To return to the default, use the no form of this command.

Syntax Description

Command Default

This parameter is not set.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant (B-ACD) service. This command is configured both under the service command for the call-queue service and under the service command for an AA service.

The number of hunt groups specified for the call-queue service is the total of the number of hunt groups used with all the AAs with which it is associated. For example, if a B-ACD has three AAs, each with two hunt groups, the number of hunt groups for each AA is two and the number of hunt groups for the call-queue service is six.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For more information, see the Cisco Unified CallManager Express B-ACD and Tcl Call-Handling Applications document for your release.

Related Commands

To assign an extension number to a call-queue exit option, use the param queue-exit-extension command in application-parameter configuration mode. To remove an exit option, use the no form of this command.

Syntax Description

Command Default

Call-queue exit option is not defined.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution (B-ACD) and Auto-Attendant (AA) service.

Use this command together with the param queue-exit-option command to enable callers to select from up to three different options to exit from a call queue. The option-number argument in this command corresponds to the option-number argument in the param queue-exit-option command.

You can record a customized second greeting that offers callers up to three options to exit from the call queue. For example, you might record a message that says, “To leave a message, press 6; to hear more options, press 7; to speak to an operator, press 8.”

This second greeting is stored in the audio file named en_bacd_allagentsbusy.au. You can record over the default message in this file, provided you do not change the name of the file.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For configuration information, see the “Setting Up Call-Queue and AA Services” section in the Cisco Unified CME B-ACD and Tcl Call-Handling Applications document.

Related Commands

To assign a menu number to a call-queue exit option, use the param queue-exit-option command in application-parameter configuration mode. To disable this option, use the no form of this command.

Syntax Description

Command Default

Call-queue exit option is not assigned.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution (B-ACD) and Auto-Attendant (AA) service.

Use this command together with the param queue-exit-extension command to enable callers to select from up to three different options to exit from a call queue. The option-number argument in this command corresponds to the option-number argument in the param queue-exit-extension command.

You can record a customized second greeting that offers callers up to three options to exit from the call queue. For example, you might record a message that says, “To leave a message, press 6; to hear more options, press 7; to speak to an operator, press 8.”

This second greeting is stored in the audio file named en_bacd_allagentsbusy.au. You can record over the default message in this file, provided you do not change the name of the file.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For configuration information, see the “Setting Up Call-Queue and AA Services” section in the Cisco Unified CME B-ACD and Tcl Call-Handling Applications document.

Related Commands

To specify the number of calls that can be held in each call queue in a Cisco Unified CME B-ACD service, use the param queue-len command in application-parameter configuration mode. To return to the default, use the no form of this command.

Syntax Description

Command Default

The default queue length is 10.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant (B-ACD) service. This command is configured under the service command for a call-queue service.

This command specifies the maximum number of calls that can be held in a call queue for a hunt group used with B-ACD when all of the hunt group member phones are busy.

Note that having calls in queue keeps PSTN ports occupied for a longer time, and you may want to plan for more ports if you have longer queues. The maximum number of calls allowed in the queues of ephone hunt groups must be based on the number of ports or trunks available. For example, if you have 20 foreign exchange office (FXO) ports and two ephone hunt groups, you can configure a maximum of ten calls per ephone hunt-group queue using the param queue-len 10 command. You can use the same configuration if you have a single T1 trunk, which supports 23 channels.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For more information, see the Cisco Unified CallManager Express B-ACD and Tcl Call-Handling Applications document for your release.

Related Commands

To enable the collection of call-queue debug information in a Cisco Unified CME B-ACD service, use the param queue-manager-debugs command in application-parameter configuration mode. To remove the setting, use the no form of this command with the keyword that was previously used.

Syntax Description

Command Default

Collection of debug information is disabled.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant (B-ACD) service. This command is configured under the service command for the call-queue service.

This command enables the collection of data regarding call queue activity. It is used in conjunction with the debug voip ivr script command. Both commands must be enabled at the same time.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For more information, see the Cisco Unified CallManager Express B-ACD and Tcl Call-Handling Applications document for your release.

Related Commands

To set the extension number to route calls to when the call queue for the auto-attendant service is full, use the param queue-overflow-extension command in application-parameter configuration mode. To return to the default, use the no form of this command.

Syntax Description

Command Default

No overflow extension is defined. Calls disconnect if the queue becomes full.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution (B-ACD) and Auto-Attendant (AA) service.

This command specifies the extension number where calls are sent when the number of calls waiting in a B-ACD call queue exceeds the number set with the param queue-len command.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For configuration information, see the “Setting Up Call-Queue and AA Services” section in the Cisco Unified CME B-ACD and Tcl Call-Handling Applications document.

Related Commands

To set a prefix to add to digits coming from the PSTN Central Office (CO) to route calls from a secondary Cisco Unified CME router to a primary Cisco Unified CME router when using the Direct Inward Dial (DID) Digit Translation Service, use the param secondary-prefix command in application-parameter configuration mode. To disable this option, use the no form of this command.

Syntax Description

Command Default

No prefix is defined.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CallManager Express (Cisco Unified CME) DID Digit Translation Service, which provides number translation for DID calls when the range of DID digits provided by the PSTN Central Office (CO) does not match the digits in the Cisco Unified CME extension numbers.

The Tcl script that provides the service accepts PSTN DID numbers of any length and maps them to the internal extension numbers that are assigned by a system administrator. Where necessary, a prefix is appended to the DID digits to create a valid extension number. The script uses the parameters that you input to determine the valid range of digits to be accepted from the CO, the valid range of digits in the local dial plan, and the prefix to append, if necessary. The script also handles DID calls that map to invalid extension numbers: a prompt is played and the calls are disconnected.

When calls are received by a secondary Cisco Unified CME router, they are routed to the primary router by configuring an H.323 VoIP dial peer and matching the destination pattern for that dial peer. The DID prefix that was configured for use with the DID script is appended to the incoming DID digits first. The secondary prefix is appended next. For example, if the incoming DID digits are 25, the DID prefix is 3, and the secondary prefix is 7, the transformed number will be 7325. The transformed number matches a VoIP dial peer, which uses the forward-digits command to send only the three relevant digits, the extension number, to the primary router.

See the Cisco Unified CallManager Express B-ACD and Tcl Call-Handling Applications document for your release.

Related Commands

To set the length of the intervals between playouts of the second greeting to calls waiting in hunt group call queues that are part of a Cisco Unified CME B-ACD service, use the param second-greeting-time command in application-parameter configuration mode. To return to the default, use the no form of this command

Syntax Description

Command Default

The second greeting is played out every 60 seconds to calls in B-ACD call queues.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant (B-ACD) service. This command is configured under the service command for an AA service.

A call to a Cisco Unified CME B-ACD service is put into a call queue if the hunt group that the call tried to reach has no phones available to take the call because they are all busy. While the call is in the queue, a second greeting is played at intervals specified by the param second-greeting-time command. From the queue, the call retries to connect to the hunt group at intervals specified by the param call-retry-timer command until the maximum amount of time to be spent in the queue expires. The maximum amount of time is set by the param max-time-call-retry command. After the maximum amount of time expires, the call is routed to the alternate destination specified in the param voice-mail command. If the alternate destination number is busy, the call makes the number of retries to connect specified in the param max-time-vm-retry command. If the call is unable to connect to the alternate destination after the number of retries that has been specified, it is disconnected.

The second greeting is stored in the audio file named en_bacd_allagentsbusy.au. You can rerecord over the default message that is provided in the file, but you cannot change the name of the file.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For more information, see the Cisco Unified CallManager Express B-ACD and Tcl Call-Handling Applications document for your release.

Related Commands

To generate call detail records (CDRs) for calls that are handled by the Cisco Unified CME B-ACD service, use the param send-account command in application-parameter configuration mode. To return to the default, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Command Default

CDRs are not generated.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command captures CDRs in RADIUS format for calls handled by the Cisco Unified CME Basic Automatic Call Distribution (B-ACD) and Auto-Attendant (AA) service. The call record includes the name of the AA service, hunt group pilot-number, and globally unique identifier (GUID).

For configuration information, see the “Setting Up Call-Queue and AA Services” section in the Cisco Unified CME B-ACD and Tcl Call-Handling Applications document.

For information on enabling RADIUS accounting, see the CDR Accounting for Cisco IOS Voice Gateways guide.

Related Commands

To specify a Cisco Unified CME B-ACD call-queue service to use with an automated attendant (AA) service, use the param service-name command in application-parameter configuration mode. To return to the default, use the no form of this command.

Syntax Description

Command Default

No call-queue service is specified.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant (B-ACD) service. This command is configured under the service command for an AA service.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For more information, the Cisco Unified CallManager Express B-ACD and Tcl Call-Handling Applications document for your release.

Related Commands

To set the upper boundary of the range of digits that is valid in the Cisco Unified CME numbering plan used with the Direct Inward Dial (DID) Digit Translation Service, use the param store-did-max command in global configuration mode. To disable this option, use the no form of this command.

Syntax Description

Command Default

No maximum value is defined for the range of digits in the dial plan.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command defines the upper limit of the range of digits in the site dial plan for the Cisco Unified CallManager Express (Cisco Unified CME) Direct Inward Dial Digit Translation Service, which provides number translation for DID calls when the DID digits provided by the PSTN Central Office (CO) do not match the digits in the Cisco Unified CME extension numbers.

The Tcl script that provides the service accepts PSTN DID numbers of any length and maps them to the internal extension numbers that are assigned by a system administrator. Where necessary, a prefix is appended to the DID digits to create a valid extension number. The script uses the parameters that you input to determine the valid range of digits to be accepted from the CO, the valid range of digits in the local dial plan, and the prefix to append, if necessary. The script also handles DID calls that map to invalid extension numbers. A prompt is played and the calls are disconnected.

Related Commands

To set the lower boundary of the range of digits that is valid in the Cisco Unified CME numbering plan used with the Direct Inward Dial (DID) Digit Translation Service, use the param store-did-min command in application-parameter configuration mode. To disable this option, use the no form of this command.

Syntax Description

Command Default

No minimum value is defined for the range of digits in the dial plan.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command defines the lower limit of the range of digits in the site dial plan when it is used with the Cisco Unified CallManager Express (Cisco Unified CME) DID Digit Translation Service. This service provides number translation for DID calls when the range of DID digits provided by the PSTN Central Office (CO) does not match the digits in the Cisco Unified CME extension numbers.

The Tcl script that provides the service accepts PSTN DID numbers of any length and maps them to the internal extension numbers that are assigned by a system administrator. Where necessary, a prefix is appended to the DID digits to create a valid extension number. The script uses the parameters that you input to determine the valid range of digits to be accepted from the CO, the valid range of digits in the local dial plan, and the prefix to append, if necessary. The script also handles DID calls that map to invalid extension numbers: a prompt is played and the calls are disconnected.

Related Commands

To set an alternate destination number to which to route calls that cannot be connected to a hunt group that is part of a Cisco Unified CME B-ACD service, use the param voice-mail command in application-parameter configuration mode. To return to the default, use the no form of this command

Syntax Description

Command Default

No alternate destination number is set.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant (B-ACD) service. This command is configured under the service command for an AA service.

Calls are diverted to an alternate destination only when one of the following criteria is met:

• The hunt group to which the call has been transferred is unavailable because all members are logged out.
• The call-queue maximum retry timer has expired.

The alternate destination can be any number at which you can assure call coverage, such as a voice-mail number, a permanently staffed number, or a number that rings an overhead night bell. Once a call is diverted to an alternate destination, it is no longer controlled by the B-ACD service. This parameter is set with the param voice-mail command.

If you send calls to a voice-mail system as an alternate destination, be sure to set up the voice-mail system as specified in the documentation for the system.

If you specify a number for an alternate destination, the number must be associated with a dial peer that is reachable by the Cisco Unified CME system.

For any configuration changes to take effect, you must reload the Cisco Unified CME B-ACD scripts.

For more information about B-ACD, see the Cisco Unified CallManager Express B-ACD and Tcl Call-Handling Applications document for your release.

Related Commands

To specify an audio file containing a prompt to be played as a welcome for callers to an automated attendant (AA) that is part of a Cisco Unified CME B-ACD service, use the param welcome-prompt command in application-parameter configuration mode. To return to the default, use the no form of this command.

Syntax Description

Command Default

The audio file named en_bacd_welcome.au is used as a welcome prompt.

Command Modes

Application-parameter configuration (config-app-param)

Command History

Usage Guidelines

This command is used with the Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant (B-ACD) service. This command is configured under the service command for an AA service.

Each AA service that is used with the Cisco Unified CME B-ACD service needs a welcome greeting to tell callers the destination they have reached and, sometimes, the options that they have. The en_bacd_welcome. au audio file is used by default. It announces “Thank you for calling,” and includes a two-second pause after the message. The filename of the welcome prompt audio file has two parts: a two-letter prefix that denotes a language code specified in the paramspace language command, and the identifying part that indicates the purpose of the file. In the default welcome prompt audio file, the prefix is en and the identifying part is _bacd_welcome.au. Note that the identifying part starts with an underscore.

If your Cisco Unified CME B-ACD service uses a single AA application, you can record a custom welcome greeting in the audio file named en_welcome_prompt.au and record instructions about menu choices in the audio file named en_bacd_options_menu.au.

If your Cisco Unified CME B-ACD service uses multiple AA applications, you will need separate greetings and menu options for each AA. Use the following guidelines:

• Record a separate welcome prompt for each AA application, using a different name for the audio file for each welcome prompt. For example, en_welcome_aa1.au and en_welcome_aa2.au. The welcome prompts that you record in these files should include both the greeting and the instructions about menu options.
• Record silence in the audio file en_bacd_options_menu.au. A minimum of one second of silence must be recorded. Note that you cannot change the identifier part of the name of this audio file.

For any Cisco Unified CME B-ACD configuration changes to take effect, you must reload the scripts.

For more information, see the Cisco Unified CallManager Express B-ACD and Tcl Call-Handling Applications document for your release.

Related Commands

To specify that an individual dial peer does not have any of its calls blocked by the Cisco router even though call blocking has been enabled, use the paramspace callsetup after-hours-exempt command in dial-peer configuration mode. To return to the default, use the no form of this command.

Syntax Description

Command Default

All dial peers are subject to call-blocking configuration.

Command Modes

Dial-peer configuration (config-dial-peer)

Command History

Usage Guidelines

This command is intended to allow H.323 and SIP trunk calls to utilize the voice gateway in spite of the the after-hours configuration in Cisco Unified CME or Cisco Unified SRST.

A Cisco voice gateway (session application) accesses the after-hours call-blocking configuration set by Cisco Unified CME or Cisco Unified SRST and blocks all SCCP, SIP, H.323, and POTS calls that go through the Cisco router regardless of whether the call is from a phone controlled by the Cisco router or from a phone controlled by some other call control application, such as Cisco Unified CallManager.

To disable the After Hours Call Blocking feature for incoming calls from phones other than those registered to a Cisco Unified CME or Cisco Unified SRST router, use this command to exempt an individual H.323, SIP, or POTS dial peer from the call blocking configuration.

To disable the After Hours Call Blocking feature for an individual IP phone registered in Cisco Unified CME or Cisco Unified SRST:

• In Cisco CME 3.4 and later, disable the After Hours Call Blocking feature for a directory number on a SIP phone by using the after-hour exempt command in voice register pool or voice register dn configuration mode.
• In Cisco CME 3.0 and later, disable the After Hours Call Blocking feature for an individual SCCP phone by using the after-hour exempt command in ephone or ephone-template configuration mode.
• In Cisco SIP SRST 3.4 and later, disable the After Hours Call Blocking feature for SIP phones in a voice register pool by using the after-hour exempt command in voice register pool configuration mode.
• In Cisco SRST, you cannot create an exemption for an individual phone from the call-blocking configuration.

Related Commands

To assign a call-park reservation group to a phone, use the reservation-group command in ephone, ephone-template, voice register pool, or voice register template configuration mode. To remove the group from the phone, use the no form of this command.

Syntax Description

Command Default

Extension does not belong to any reservation group.

Command Modes

Ephone configuration (config-ephone)
Ephone-template configuration (config-ephone-template)
Voice register pool configuration (config-register-pool)
Voice register template configuration (config-register-temp)

Command History

Usage Guidelines

This command allows you to assign ownership to call-park slots by using Park Reservation Groups. A phone configured with a park reservation group can retrieve calls only from park slots configured with the same park reservation group. A phone without a park reservation group can retrieve calls from any park slot without an assigned park reservation group.

To assign a reservation group to a park-slot extension, use the park-slot reservation-group command.

If you use a template to apply a command to a phone and you also use the same command in ephone or voice register pool configuration mode for the same phone, the value that you set in the phone configuration mode has priority.

Related Commands

To create an extension (call-park slot) at which calls can be temporarily held (parked), use the park-slot command in ephone-dn configuration mode. To disable the extension, use the no form of this command.

Syntax Description

Command Default

No call-park slot is defined.

Command Modes

Ephone-dn configuration (config-ephone-dn)

Command History

Usage Guidelines

This command creates a call-park slot that is a floating extension, or ephone-dn that is not bound to a physical phone, at which phone users can place calls on hold for later retrieval from the same phone or from another phone.

At least one call-park slot must be defined with this command before the Park soft key displays on IP phones in a Cisco Unified CME system.

Phone users park calls using the Park soft key. A phone user can then retrieve a call by dialing the extension number of the call-park slot. On SCCP phones, the phone user who parks the call can also retrieve the call by using the PickUp soft key and an asterisk (*). Other SCCP phone users can retrieve the call by using the PickUp soft key and dialing the extension number of the call-park slot.

Calls can also be transferred to a call-park slot using the Transfer key; a transfer to a call-park slot is always a blind transfer. Calls can also be forwarded to a call-park slot, and callers can directly dial call-park slots.

When a call that uses a G.711 codec is parked, the caller hears the music-on-hold (MOH) audio stream; otherwise, the caller hears the on-hold tone.

The directed keyword enables the extension as a park slot for Directed Call Park. To retrieve a call from a directed call-park slot, you must define the retrieval prefix with the fac command. The retrieval prefix is supported for both SCCP and SIP phones.

The reservation-group keyword allows you to assign ownership to call-park slots by using Park Reservation Groups. A park slot configured with a park reservation group can only be used by phones configured with the same park reservation group. A park slot without a park reservation group can be used by any phone not assigned to a park reservation group.

A reminder ring can be sent to the extension that parked the call by using the timeout keyword, which sets the interval length to wait before sending call-park reminder rings. The number of time-out intervals and reminder rings are configured with the limit keyword and argument. For example, a limit of 3 timeout intervals sends 2 reminder rings (interval 1, ring 1, interval 2, ring 2, interval 3). The timeout and limit keywords and arguments also set the maximum time that calls stay parked. For example, a timeout interval of 10 seconds and a limit of 5 timeout intervals (park-slot timeout 10 limit 5) will park calls for approximately 50 seconds.

If the timeout keyword is not used with this command, no reminder ring is sent to the extension that parked the call. If the timeout keyword is used, a reminder ring is sent only to the extension that parked the call unless the notify keyword is also used to specify an additional extension number to receive a reminder ring. When an additional extension number is specified using the notify keyword, the phone user at that extension can retrieve a call from this slot by pressing the PickUp soft key and an asterisk (*).

Each call-park slot can hold one call at a time, so the number of simultaneous calls that can be parked is equal to the number of slots that have been created. The reserved-for keyword creates a call-park slot that is dedicated for use by one extension so that extension always has a slot available at which to park a call. With nonreserved slots, multiple call-park slots can be created with the same extension number so that all the calls that are parked for a particular group can be parked at a known extension number. For example, at a hardware store, calls for the plumbing department can be parked at extension 101, calls for lighting can be parked at 102, and so forth. Then, anyone in the plumbing department can pick up calls from extension 101. When multiple calls are parked at the same extension number, they are picked up in the order in which they were parked; that is, the call that has been parked the longest is the first call picked up from that extension number.

IP phone users park calls at their dedicated call-park slots using the Park soft key. Phone users can also transfer calls to dedicated call-park slots using the Transfer soft key and a standard or custom feature access code (FAC) for call park. On analog phones, users transfer calls to dedicated call-park slots using hookflash and a standard or custom FAC for call park. The standard FAC for call park is **6. Custom FACs are created using the fac command.

If a dedicated park slot is not found for an ephone-dn attempting to park a call, Cisco Unified CME uses the standard call-park procedure; that is, the system searches for a preferred park slot (one with an ephone-dn number that matches the last two digits of the ephone-dn attempting to park the call) and if none is found, uses any available call-park slot.

If a name has been specified for a call-park slot, that name is displayed instead of an extension number on a recall or transfer of the call.

A parked call can have the following dispositions after its timeouts expire:

• Recall—If you specify that a call should be recalled to the parking phone after the timeout interval expires, the call is always returned to the phone's primary extension number, regardless of which extension on the phone did the parking.
• Transfer—If you specify a transfer target, the call is transferred to the specified number after the timeout intervals expire instead of returning to the primary number of the phone that did the parking.
• Alternate—You can also specify an alternate target extension to which to transfer a parked call if the recall or transfer target is in use. In use is defined as either ringing or connected to a call. For example, a call is parked at the dedicated park slot for the phone with the primary extension of 2001. After the timeouts expire, the system attempts to recall the call to extension 2001, but that line is now connected to a different call. The system transfers the call to the alternate target that was specified when the park slot was defined.
• Disconnect—When a timeout limit is set and no other disposition has been specified, a call parked at a call-park slot is disconnected after the number of reminder timeouts are reached.

Related Commands

To configure the mandatory password for automatic registration of SIP phones with the Cisco Unified CME system, use the password command in voice auto register configuration mode. This command is a sub-mode CLI of the command auto-register . To disable configuring password for auto registration of SIP phones, use the no form of this command.

Syntax Description

Command Default

By default, this command is disabled.

Command Modes

voice auto register configuration (config-voice-auto-register)

Command History

Usage Guidelines

This command enables the administrator to configure the password credentials for SIP phones auto registering on Unified CME. It is mandatory that the password is configured before assigning the DN range.

Related Commands

To configure password-persistent option for a vpn-profile, use the password-persistent command in vpn-profile configuration mode.

Syntax Description

Command Default

Password-persistent is disabled.

Command Modes

Vpn-profile configuration (conf-vpn-profile)

Command History

Usage Guidelines

Use this command to enable or disable password-persistent option for a vpn-profile.

Related Commands

To define a dial pattern for a SIP dial plan, use the pattern command in voice register dialplan configuration mode. To remove the pattern, use the no form of this command.

Syntax Description

Command Default

No pattern is defined.

Command Modes

Voice register dialplan configuration (config-register-dialplan)

Command History

Usage Guidelines

This command defines a pattern of dialed digits that are matched by the phone and passed to Cisco Unified CME to initiate a call. Dial strings that match the pattern trigger the sending of a SIP INVITE message to Cisco Unified CME. Patterns are matched sequentially in order of the tag number.

You must first use the type command to specify the type of phone that the dial plan is being defined for before you can enter a pattern. Enter this command for each dial pattern that is part of the dial plan definition. After you define a dial plan, assign it to a SIP phone by using the dialplan command.

The button keyword specifies the button to which the dial pattern applies. If the user is initiating a call on line button 1, only the dial patterns specified for button 1 apply. If this keyword is not configured, the dial pattern applies to all lines on the phone. This keyword is not supported on Cisco Unified IP Phones 7905 or 7912. The button number corresponds to the order of the buttons on the side of the screen, from top to bottom, with 1 being the top button.

The pattern command and filename command are mutually exclusive. You can use either the pattern command to define dial patterns manually for a dial plan, or the filename command to select a custom dial pattern file that is loaded in system flash.

Related Commands

To configure the dual tone multifrequency (DTMF) digit pattern forwarding necessary to activate the voice-mail system when a user presses the Messages button on an IP phone in a Cisco CallManager Express (Cisco CME) system, use the pattern direct command in voice-mail integration configuration mode. To disable DTMF pattern forwarding when a user presses the Messages button on a phone, use the no form of this command.

Syntax Description

Command Default

This feature is disabled.

Command Modes

Voice-mail integration configuration (config-vm-integration)

Command History

Usage Guidelines

The pattern direct command is used to configure the sequence of dual tone multifrequency (DTMF) digits passed to a voice-mail system attached to the router through one or more voice ports. When a call is placed directly from a Cisco IP phone attached to the router, the voice-mail system expects to receive a sequence of DTMF digits at the beginning of the call to identify the user’s mailbox, accompanied by a string of digits to indicate that the caller is attempting to access the designated mailbox in order to retrieve messages.

Although it is unlikely that you will use multiple instances of the CDN, CGN, or FDN keywords in a single command line, it is permissible to do so.

Related Commands

To configure the dual tone multifrequency (DTMF) digit pattern forwarding necessary to activate a voice-mail system after an internal extension attempts to connect to a busy extension and the call is forwarded to voice mail, use the pattern ext-to-ext busy command in voice-mail integration configuration mode. To disable the feature, use the no form of this command.

Syntax Description

Command Default

This feature is disabled.

Command Modes

Voice-mail integration configuration (config-vm-integration)

Command History

Usage Guidelines

The pattern ext-to-ext busy command is used to configure the sequence of DTMF digits passed to a voice-mail system attached to the router through one or more voice ports. When a call is routed to the voice-mail system by call forward on busy from a Cisco IP phone attached to the router, the voice-mail system expects to receive digits that identify the mailbox associated with the forwarding phone together with digits that identify the extension number of the calling IP phone.

Although it is unlikely that you will use multiple instances of the CDN, CGN, or FDN keywords in a single command line, it is permissible to do so.

Related Commands

To configure the dual tone multifrequency (DTMF) pattern forwarding necessary to activate the voice-mail system once an internal extension fails to connect to a non answering extension and the call is forwarded to voice mail, use the pattern ext-to-ext no-answer command in voice-mail integration configuration mode. To disable this feature, use the no form of this command.

Syntax Description

Command Default

This feature is disabled.

Command Modes

Voice-mail integration configuration (config-vm-integration)

Command History

Usage Guidelines

The pattern ext-to-ext no-answer command is used to configure the sequence of DTMF digits passed to a voice-mail system attached to the router through one or more voice ports. When a call is routed to the voice-mail system by call forward on no-answer from an IP phone attached to the router, the voice-mail system expects to receive digits that identify the mailbox associated with the forwarding phone together with digits that identify the extension number of the calling IP phone.

Although it is unlikely that you will use multiple instances of the CDN, CGN, or FDN keywords in a single command line, it is permissible to do so.

Related Commands

To configure the dual tone multifrequency (DTMF) digit pattern forwarding necessary to activate the voice-mail system once an external trunk call reaches a busy extension and the call is forwarded to voice mail, use the pattern trunk-to-ext busy command in voice-mail integration configuration mode. To return to the default, use the no form of this command.

Syntax Description

Command Default

This feature is disabled by default.

Command Modes

Voice-mail integration configuration (config-vm-integration)

Command History

Usage Guidelines

The pattern trunk-to-ext busy command is used to configure the sequence of DTMF digits passed to a voice-mail system attached to the router through one or more voice ports. When a call is routed to the voice-mail system by call forward on busy from an IP phone attached to the router, the voice-mail system expects to receive a sequence of digits identifying the mailbox associated with the forwarding phone together with digits indicating that the call originated from a PSTN or VoIP caller.

Although it is unlikely that you will use multiple instances of the CDN, CGN, or FDN keywords in a single command line, it is permissible to do so.

Related Commands

To configure the dual tone multifrequency (DTMF) digit pattern forwarding necessary to activate the voice-mail system when an external trunk call reaches an unanswered extension and the call is forwarded to voice mail, use the pattern trunk-to-ext no-answer command in voice-mail integration configuration mode. To disable this feature, use the no form of this command.

Syntax Description

Command Default

This feature is disabled.

Command Modes

Voice-mail integration configuration (config-vm-integration)

Command History

Usage Guidelines

The pattern trunk-to-ext no-answer command is used to configure the sequence of DTMF digits passed to a voice-mail system attached to the router through one or more voice ports. When a call is routed to the voice-mail system by call forward on no-answer from an IP phone attached to the router, the voice-mail system expects to receive digits that identify the mailbox associated with the forwarding phone together with digits that indicate that the call originated from a PSTN or VoIP caller.

Although it is unlikely that you will use multiple instances of the CDN, CGN, or FDN keywords in a single command line, it is permissible to do so.

Related Commands

To enable a phone user to display voice hunt group information using the Services button on the phone, use the phone-display command in voice hunt group configuration mode. To remove the configuration, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Command Default

By default, this command is disabled.

Command Modes

Usage Guidelines

This command when configured, enables the user to view the information of a specific voice hunt group on the phone.

To enable Jabber phone-only client support, use the phone-mode only command. To remove t the configuration, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Command Default

By default, this feature is disabled.

Command Modes

voice register global (config-register global)

voice register pool (config-register pool)

voice register template (config-register template)

Usage Guidelines

This command enables Jabber phone-only client support.

Related Commands

To specify the size of the RSA key pair that is generated on phones, use the phone-key-size command in CAPF-server configuration mode. To return the size to the default, use the no form of this command.

Syntax Description

Command Default

RSA key pair size is 1024.

Command Modes

CAPF-server configuration (config-capf-server)

Command History

Command History

Usage Guidelines

This command is used with Cisco Unified CME phone authentication.

If you choose a higher key size than the default setting, the phones take longer to generate the entropy that is required to generate the keys. Key generation, which is set at low priority, allows the phone to function while the action occurs. Depending on the phone model, you may notice that key generation takes up to 30 or more minutes to complete.

To define the phone firmware support for a phone type, use the phoneload command in ephone-type configuration mode. To remove firmware support, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Command Default

Phone type supports firmware configuration.

Command Modes

Ephone-type configuration (config-ephone-type)

Command History

Usage Guidelines

This command specifies whether the phone type defined in the phone-type template supports firmware configuration using the load command.

Related Commands

To define the phone support for firmware download from CME, use the phoneload-support command in voice register pool-type mode. To disable phoneload support, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Command Default

The phoneload support is disabled. When the reference-pooltype command is configured, phoneload support property of the reference phone is inherited.

Command Modes

Voice Register Pool Configuration (config-register-pool)

Usage Guidelines

Use this command to define the default transport type. If the new phone supports the phoneload, you can use the load command in voice register global” mode to configure the corresponding phoneload for the new phone model. When you use the no form of this command, the inherited properties of the reference phone takes precedence over the default value.

Related Commands

To set the number of 3XX responses an originating SIP phone in a Cisco CallManager Express (Cisco CME) system can accept for a single call, use the phone-redirect-limit command in voice register global configuration mode. To revert to the default, use the no form of this command.

Syntax Description

Command Default

Default is 5

Command Modes

Voice register global configuration (config-register-global)

Command History

Usage Guidelines

Use this command to control how many subsequent 3XX responses an originating SIP phone can handle for a single call. The terminating side is any forwarding party which does not use B2BUA, but sends 3XX directly to the originating calling phone. When Cisco CME gets a 3XX from the terminating side, Cisco CME relays the 3XX to the originating SIP phone. The default number of 3XXs that the originating phone can accept is 5.

The following example shows how to set the maximum number of redirects to 6:

Router(config)# voice register global
Router(config-register-global)# phone-redirect-limit 6
 

Related Commands

To enable a phone user to view the list of active parked calls, use the phone-ui park-list command in the ephone configuration mode. To remove the configuration, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Command Default

By default, this feature is enabled for Skinny Call Control Protocol (SCCP) phones.

Command Modes

ephone configuration (config-ephone)

Usage Guidelines

This command enables the park-list menu option under My-Phone-Apps service button menu.

Related Commands

To enable a phone user to configure speed-dial and fast-dial numbers from their phone, use the phone-ui speeddial-fastdial command in ephone configuration mode. To reset to the default value, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Command Default

Enabled (speed-dial and fast-dial numbers are configurable from phone).

Command Modes

Ephone configuration (config-ephone)

Command History

Usage Guidelines

This command enables the speed-dial and fast-dial configuration menu on the phone so that users can configure these options directly.

The services URL must be configured using the url services command.

Related Commands

To enable a Skinny Call Control Protocol (SCCP) phone user to display voice hunt group information using the Services button on a phone, use the phone-ui voice-hunt-groups command in ephone configuration mode. To remove the configuration, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Command Default

By default, this command is enabled.

Command Modes

ephone configuration (config-ephone)

Usage Guidelines

This command enables the Voice Hunt Groups menu option under the My-Phone-Apps service button menu .

Related Commands

To enable a phone user to pickup a ringing call on extensions in any pickup group, use the pickup-call any-group command in ephone-dn or voice register dn configuration mode. To reset to the default value, use the no form of this command.

Syntax Description

This command has no arguments or keywords.

Command Default

User can pickup calls in other groups by pressing GPickUp soft key and dialing pickup group number.

Command Modes

Ephone-dn configuration (config-ephone-dn)
Voice register dn configuration (config-register-dn)

Command History

Usage Guidelines

This command allows a phone user to pickup any ringing call within the local Cisco Unified CME system by pressing the GPickUp soft key and asterisk (*), if the ringing extension is configured with a pickup group using the pickup-group command.

If this command is not configured, a phone user can pickup calls only from their local group by pressing the GPickUp soft key and *. To pickup calls in another group, the user must press the GPickUp soft key and dial the pickup group number.

Related Commands