|
|
Table Of Contents
after-hour exempt (voice register)
application (telephony-service)
application (voice register global)
application (voice register pool)
authenticate (voice register global)
Cisco Unified CME Commands: A
Last Updated: September 4, 2007First Published: February 27, 2006This chapter contains commands to configure and maintain Cisco Unified Communications Manager Express (formally known as Cisco Unified CallManager Express). The commands are presented in alphabetical order. Some commands required for configuring Cisco Unified Communications Manager Express (Cisco Unified CME) may be found in other Cisco IOS command references. Use the command reference master index or search online to find these commands.
after-hour exempt
To specify that an individual IP phone in Cisco Unified CME does not have any of its outgoing calls blocked even though after-hour call blocking has been enabled, use the after-hour exempt command in ephone or ephone-template configuration mode. To remove the exemption, use the no form of this command.
after-hour exempt
no after-hour exempt
Syntax Description
This command has no arguments or keywords.
Command Default
The SCCP phone is not exempt from call blocking.
Command Modes
Ephone configuration
Ephone-template configurationCommand History
Usage Guidelines
Use this command to exempt an individual SCCP phone from call blocking and enable the phone user to place outgoing calls regardless of whether the outgoing called number matches the defined pattern of digits during the call blocking periods.
By default, all IP phones in a Cisco Unified CME system are subject to call blocking if the Call Blocking feature is configured.
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.
Examples
The following example shows how to configure this phone so that outgoing calls are not blocked:
Router(config)# ephone 23Router(config-ephone)# mac 00e0.8646.9242Router(config-ephone)# button 1:33Router(config-ephone)# after-hour exemptRelated Commands
after-hour exempt (voice register)
To specify that call blocking criteria is not applied, enabling the phone user to place outgoing calls on a SIP IP phone or extension even though global system call blocking is enabled, use the after-hour exempt command in voice register dn configuration or voice register pool mode. To return to the default, use the no form of this command.
after-hour exempt
no after-hour exempt
Syntax Description
This command has no arguments or keywords.
Command Default
Disabled (global call blocking remains active, as configured).
Command Modes
Voice register dn configuration
Voice register pool configurationCommand History
12.4(4)T
Cisco CME 3.4 and Cisco SIP SRST 3.4
This command was introduced.
Usage Guidelines
This command in voice register dn configuration exempts an individual SIP extension number or telephone number from call-blocking criteria.
This command in voice register pool configuration exempts all numbers associated with a SIP IP phone from call-blocking criteria.
To define call blocking for IP phones in Cisco Unified CME: First, define one or more patterns of outgoing digits by using the after-hours block pattern command in either telephony-service configuration mode for Cisco Unified CME or in call-manager-fallback configuration mode for Cisco Unified SIP SRST. Next, define one or more time periods during which calls that match those patterns are to be blocked by using the after-hours date or after-hours day command or both.
By default, all Cisco IP phones in a Cisco Unified CME or Cisco Unified SIP SRST system are restricted during the specified time if at least one pattern and at least one time period are defined. A SIP phone extension is exempt as long as the after-hour exempt command is configured in voice register dn or in voice register pool configuration mode.
Note
This command can also be used for Cisco SIP SRST.
Examples
The following example shows how to configure extension 5001, under directory number 2 so that outgoing calls are not blocked:
Router(config)# voice register dn 2Router(config-register-dn)# number 5001Router(config-register-dn)# after-hour exemptThe following example shows how to configure a particular SIP phone, specified by the voice register pool command, so that outgoing calls are not blocked:
Router(config)# voice register pool 23Router(config-register-pool)# after-hour exemptRelated Commands
after-hours block pattern
To define a pattern of outgoing digits for call blocking from IP phones, use the after-hours block pattern command in telephony-service configuration mode. To delete a call-blocking pattern, use the no form of this command.
after-hours block pattern pattern-tag pattern [7-24]
no after-hours block pattern pattern-tag
Syntax Description
Command Default
No pattern is defined.
Command Modes
Telephony-service configuration
Command History
12.2(15)ZJ
3.0
This command was introduced.
12.3(4)T
3.0
This command was integrated into Cisco IOS Release 12.3(4)T.
Usage Guidelines
Call blocking on IP phones is defined in the following way. First, one or more patterns of outgoing digits are defined using the after-hours block pattern command. Next, one or more time periods during which calls that match those patterns are to be blocked are defined using the after-hours date or after-hours day command or both. By default, all IP phones in a Cisco CallManager Express system are restricted during the specified time if at least one pattern and at least one time period are defined. Individual phones can be exempted from call blocking using the after-hour exempt command.
Blocked calls return a fast-busy tone to the user for approximately 10 seconds before the call is terminated and the line is returned to on-hook status.
Examples
The following example defines pattern 1, which blocks international calls after hours for a Cisco CallManager Express system that requires dialing 9 for external calls:
Router(config)# telephony-serviceRouter(config-telephony)# after-hours block pattern 1 9011Related Commands
after-hours date
To define a recurring period based on date during which outgoing calls that match defined block patterns are blocked on IP phones, use the after-hours date command in telephony-service configuration mode. To delete a defined time period, use the no form of this command.
after-hours date month date start-time stop-time
no after-hours date month date
Syntax Description
Command Default
No time period based on date is defined for call blocking.
Command Modes
Telephony-service configuration
Command History
12.2(15)ZJ
3.0
This command was introduced.
12.3(4)T
3.0
This command was integrated into Cisco IOS Release 12.3(4)T.
Usage Guidelines
Call blocking on IP phones is defined in the following way. First, one or more patterns of outgoing digits are defined using the after-hours block pattern command. Next, one or more time periods during which calls that match those patterns are to be blocked are defined using the after-hours date or after-hours day command or both. By default, all IP phones in a Cisco CallManager Express system are restricted during the specified time if at least one pattern and at least one time period are defined. Individual IP phones can be exempted from call blocking using the after-hour exempt command.
Call blocking for the time period that is defined in this command recurs annually on the date specified in the command.
Examples
The following example defines January 1 as an entire day on which calls that match the pattern specified in the after-hours block pattern command are blocked:
Router(config)# telephony-serviceRouter(config-telephony)# after-hours date jan 1 00:00 00:00Related Commands
after-hours day
To define a recurring period based on day of the week during which outgoing calls that match defined block patterns are blocked on IP phones, use the after-hours day command in telephony-service configuration mode. To delete a defined time period, use the no form of this command.
after-hours day day start-time stop-time
no after-hours day day
Syntax Description
Defaults
No time period based on day of the week is defined for call blocking.
Command Modes
Telephony-service configuration
Command History
12.2(15)ZJ
3.0
This command was introduced.
12.3(4)T
3.0
This command was integrated into Cisco IOS Release 12.3(4)T.
Usage Guidelines
Call blocking on IP phones is defined in the following way. First, one or more patterns of outgoing digits are defined using the after-hours block pattern command. Next, one or more time periods during which calls that match those patterns are to be blocked are defined using the after-hours date or after-hours day command or both. By default, all IP phones in a Cisco CallManager Express system are restricted during the specified time if at least one pattern and at least one time period are defined. Individual phones can be exempted from call blocking using the after-hour exempt command.
Call blocking occurs during the hours between the start time and stop time on the day of the week that is specified in this command. This time period recurs weekly unless it is removed using the no form of this command.
Examples
The following example defines the period from Monday night at 7 p.m. to Tuesday morning at 7 a.m. as an after-hours call-blocking period:
Router(config)# telephony-serviceRouter(config-telephony)# after-hours day mon 19:00 07:00Related Commands
allow watch
To allow a directory number on a phone registered to Cisco Unified CME to be watched in a presence service, use the allow watch command in ephone-dn, ephone-dn-template, or voice register dn configuration mode. To reset to the default condition, use the no form of this command.
allow watch
no allow watch
Syntax Description
This command has no arguments or keywords.
Command Default
Watching of the phone line is disabled.
Command Modes
Ephone-dn
Ephone-dn-template
Voice register dnCommand History
Usage Guidelines
This command controls whether a phone line associated with a directory number can be watched as part of a presence service. The directory number is enabled as a presentity that can be watched by internal and external watchers. Presence service must be enabled on Cisco Unified CME. Another phone, acting as a watcher, can monitor the status of this phone line when the blf-speed-dial or presence call-list command is enabled for that phone.
If you use an ephone-dn template to apply a command to a directory number and you also use the same command in ephone-dn configuration mode, the value that you set in ephone-dn configuration mode has priority over the ephone-dn template configuration.
Examples
The following example shows that the extension associated with voice register dn 2 can be watched by the phone associated with voice register pool 1:
Router(config)# voice register dn 2Router(config-register-dn)# number 2102Router(config-register-dn)# allow watchRouter(config)# voice register pool 1Router(config-register-pool)# id mac 0015.6247.EF90Router(config-register-pool)# type 7971Router(config-register-pool)# number 1 dn 2Router(config-register-pool)# blf-speed-dial 1 2102 label 2102Related Commands
anonymous block
To enable anonymous call blocking in a SIP phone template, use the anonymous block command in voice register template configuration mode. To return to the default, use the no form of this command.
anonymous block
no anonymous block
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Voice register template configuration
Command History
Usage Guidelines
This command blocks incoming calls in which the caller is not identified. To apply a template to a SIP phone, use the template command in voice register pool configuration mode.
Examples
The following example shows how to set anonymous call blocking in template 1:
Router(config)# voice register template 1Router(config-register-temp)# anonymous blockRelated Commands
caller-id block (voice register template)
Enables caller-ID blocking for outbound calls from a SIP phone.
template (voice register pool)
Applies a template to a SIP phone.
application (ephone-dn)
To select a session-level application for a specific extension (ephone-dn) in a Cisco CallManager Express (Cisco CME) system, use the application command in ephone-dn configuration mode. To disable use of the application, use the no form of this command.
application application-name [out-bound]
no application application-name [out-bound]
Syntax Description
application-name
Interactive voice response (IVR) application name.
out-bound
(Optional) Application handles the dial peer in outgoing mode.
Defaults
No application is selected for the phone.
Command Modes
Ephone-dn configuration
Command History
Usage Guidelines
Use this command to assign a Tool Command Language (Tcl) IVR application to a Cisco IP phone extension (ephone-dn).
Use the show call application voice summary command to display a list of applications.
Examples
The following example sets the IVR application for directory number 1:
Router(config)# ephone-dn 1Router(config-ephone-dn) application TCL IVRRelated Commands
ephone-dn
Enters ephone-dn configuration mode.
show call application voice summary
Displays information about voice applications.
application (telephony-service)
To select a session-level application for all extensions (ephone-dns) in a Cisco CallManager Express (Cisco CME) system, use the application command in telephony-service configuration mode. To disable use of an application for all extensions, use the no form of this command.
application application-name
no application
Syntax Description
Defaults
No application is selected for all extensions.
Command Modes
Telephony-service configuration
Command History
12.2(11)YT
2.1
This command was introduced.
12.2(15)T
2.1
This command was integrated into Cisco IOS Release 12.2(15)T.
Usage Guidelines
Use this command to assign a Tool Command Language (Tcl) IVR application to all extensions served by the CME router.
Use the show call application voice summary command to display a list of applications.
Examples
The following example sets the IVR application for all phones:
Router(config)# telephony-serviceRouter(config-telephony) application TCL IVRRelated Commands
show call application voice summary
Displays information about voice applications.
telephony-service
Enters telephony-service configuration mode.
application (voice register global)
To select the session-level application for all dial peers associated with Session Initiation Protocol (SIP) phones, use the application command in voice register global configuration mode. To disable use of the application, use the no form of this command.
application application-name
no application
Syntax Description
Command Default
Default application on router
Command Modes
Voice register global configuration
Command History
12.4(4)T
Cisco CME 3.4
Cisco SIP SRST 3.4This command was introduced.
Usage Guidelines
During Cisco Unified CallManager Express (Cisco Unified CME) or Cisco Unified Session Initiation Protocol (SIP) Survivable Remote Site Telephony (SRST) registration, a dial peer is created for each SIP phone and that dial peer includes the default session application. The application command allows you to change the default application for all dial peers associated with the Cisco SIP IP phones, if desired. The applied application (or TCL IVR script) must support call redirection. Use the show call application voice summary command to display a list of applications.
The application command in voice register pool configuration mode takes precedence over this command in voice register global configuration mode.
Note
Examples
The following example shows how to set the Tcl IVR application globally for all SIP phones:
Router(config)# voice register globalRouter(config-register-global)# mode cmeRouter(config-register-global)# application sipapp2Related Commands
application (voice register pool)
To select the session-level application for the dial peer associated with an individual Session Initiation Protocol (SIP) phone in a Cisco Unified CallManager Express (Cisco Unified CME) environment or for a group of phones in a Cisco Unified SIP Survivable Remote Site Telephony (SRST) environment, use the application command in voice register pool configuration mode. To disable use of the application, use the no form of this command.
application application-name
no application
Syntax Description
Command Default
Default application on router
Command Modes
Voice register pool configuration
Command History
Usage Guidelines
During Cisco Unified CME or Cisco Unified SIP SRST registration, a dial peer is created for each SIP phone and that dial peer includes the default session application. The application command allows you to change the default application for all dial peers associated with the Cisco SIP IP phones, if desired. The applied application (or TCL IVR script) must support call redirection. Use the show call application voice summary command to display a list of applications.
The application command in voice register pool configuration mode takes precedence over this command in voice register global configuration mode.
Note
Examples
The following example shows how to set the IVR application for the SIP phone specified by the voice register pool command:
Router(config)# voice register pool 1Router(config-register-pool) application sipapp2The following partial sample output from the show running-config command shows that voice register pool 1 has been set up to use the SIP.app application:
voice register pool 1id network 172.16.0.0 mask 255.255.0.0application SIP.appvoice-class codec 1Related Commands
authenticate (voice register global)
To define the authenticate mode for SIP phones in a Cisco Unified CME or Cisco Unified SRST system, use the authenticate command in voice register global configuration mode. To return to the default, use the no form of this command.
Cisco IOS Release 12.4(11)XJ and later releases
authenticate {credential tag location | ood-refer | presence | realm string | register}
no authenticate {credential tag location | ood-refer | presence | realm string | register}
Cisco IOS Release 12.4(4)T
authenticate [all] [realm string]
no authenticate [all] [realm string]
Syntax Description
Command Default
Authenticate mode is disabled.
Command Modes
Voice register global configuration
Command History
Usage Guidelines
The credential keyword allows OOD-R and presence service to use credential files for authentication. Up to five text files containing username and password pairs can be defined and loaded into the system. The contents of these five files are mutually exclusive; the username and password pairs must be unique across all the files. For Cisco Unified CME, the username and password pairs cannot be the same ones defined for SCCP or SIP phones with the username command.
The ood-refer keyword specifies that any OOD-R request that passes authentication is authorized to setup calls between referee and refer-target if OOD-R is enabled with the refer-ood enable command.
The presence keyword enables digest authentication for external watchers. Credentials are verified against a credential file stored in flash. This applies to both OOD-R and presence. The default is to authenticate all SUBSCRIBE requests from external watchers. An external watcher that passes authentication is authorized to subscribe to presence service for all lines allowed to be watched.
The register keyword enables authentication for registration requests in which the MAC address of the SIP phone cannot be identified by using other methods. All incoming register requests are challenged and authenticated. The realm keyword with the string argument specifies the character string to be included in the challenge.
Examples
The following example shows that all registration requests from SIP phones in a Cisco Unified CME system must be authenticated:
Router(config)# voice register globalRouter(config-register-global)# mode cmeRouter(config-register-global)# authenticate registerRelated Commands
auth-mode
To specify the type of authentication to use during CAPF sessions, use the auth-mode command in CAPF-server configuration mode. To return to the default, use the no form of this command.
auth-mode {auth-string | LSC | MIC | none | null-string}
no auth-mode
Syntax Description
Command Default
No certificate upgrade is initiated (same as the keyword none).
Command Modes
CAPF-server configuration
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)T
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
This command is used with Cisco Unified CME phone authentication.
If you use the auth-string keyword with this command, the phone user is required to enter a specified digit string at the phone to be authenticated for CAPF sessions. The digit string is entered into the configuration using the auth-string command or the capf-auth-str command and must be communicated to the phone user.
Use the show capf-server command to display parameters that you have set with this command.
Examples
The following example specifies authentication strings as the method of CAPF authentication. The auth-string command specifies that random authentication strings should be generated for all ephones.
capf-serverauth-mode auth-stringauth-string generate allRelated Commands
auth-string
To generate or remove authentication strings for one or all secure ephones, use the auth-string command in CAPF-server configuration mode. To return to the default, use the no form of this command.
auth-string {delete | generate} {all | ephone-tag} [digit-string]
no auth-string {delete | generate} {all | ephone-tag} [digit-string]
Syntax Description
Command Default
No authentication string exists.
Command Modes
CAPF-server configuration
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)T
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
This command is used with Cisco Unified CME phone authentication.
This command creates or removes authentication strings for all secure ephones or for a specified secure ephone. Use this command when the auth-string keyword is specified in the auth-mode command.
Authentication mode for individual ephones can also be set using the cert-oper (ephone) command.
CAPF authentication strings for particular ephones can also be entered using the capf-auth-str command in ephone configuration mode.
Use the show capf-server auth-string command to display configured authentication strings.
When a phone is configured for a certificate upgrade that requires auth-string authentication, then the CAPF initiation needs to be performed manually by the phone user using the following steps:
1.
2.
3.
4.
5.
Examples
The following example specifies authentication strings as the method of CAPF authentication. The auth-string command specifies that random authentication strings should be generated for all ephones.
capf-serverauth-mode auth-stringauth-string generate allRelated Commands
auto assign
To automatically assign an already defined telephone or extension number to button 1 of Cisco Unified IP phones as they register for service with a Cisco Unified CME router, use the auto assign command in telephony-service configuration mode. To return to the default of not automatically assigning dn-tags, use the no form of this command.
auto assign dn-tag to dn-tag [type phone-type] [cfw extension-number timeout seconds]
no auto assign dn-tag to dn-tag [type phone-type] [cfw extension-number timeout seconds]
Syntax Description
Command Default
Ephone-dn tags are not automatically assigned to registering Cisco Unified IP phones.
Command Modes
Telephony-service configuration (config-telephony)
Command History
Usage Guidelines
Use this command to create an ephone configuration for a Cisco Unified IP phone whose MAC address is not explicitly configured as it registers in Cisco Unified CME. The system-created ephone configuration includes the MAC address of the Cisco Unified IP phone being registered and an already-defined available ephone-dn assigned to button 1 of this phone.
The auto-reg-ephone command must be enabled (default) to use this command. If the auto registration feature is disabled, a Cisco Unified IP phone whose MAC address is not explicitly configured cannot register in Cisco Unified CME.
Before using this command, configure the ephone-dn tags to be assigned and define at least one primary number for each dn-tag.
All ephone-dns in a specified range should be of the same type, either single-line or dual-line.
Ephone-dn tags to be assigned must belong to normal ephone-dns and cannot belong to paging ephone-dns, intercom ephone-dns, music-on-hold (MOH) ephone-dns, or message-waiting-indication (MWI) ephone-dns.
The auto assign command cannot create shared lines.
If an insufficient number of dn-tags is available, some ephone configurations will not include a telephone or extension number.
Use multiple auto assign commands to assign discontinuous ranges of ephone-dn tags and to support multiple types of IP phones. Overlapping ranges of dn-tags may be assigned so that they map to more than one type of phone. If no type is specified, the values in the range are assigned to phones of any type, and if a specific range is assigned for a specific phone type, the available ephone-dn tag in that range are used first.
If the phone being registered is connected to a Cisco VG200 series analog phone gateway, configuring the
auto assign command will automatically create one ephone configuration for each configured port, as the port registers with the Cisco Unified CME router. To ensure that the tag-to-port assignment will match the numbering order of the physical ports; for example, dn-tags 1 to 24 assigned to ports 1 to 24 of a Cisco VG224 analog phone gateway, in that order, we recommend that the Cisco Unified CME system be up, running, and configured before you boot the analog phone gateway.
The auto assign command cannot be used for the Cisco Unified IP Phone 7914 Expansion Module. Phones with one or more expansion modules must be configured manually.
After using this command, reboot the phone for which an ephone is to be configured.
This command is also used by the Cisco Unified CME setup tool to automatically assign ephone-dns after the tool has gathered information about the setup from the user. When lines are assigned by the Cisco Unified CME setup tool in keyswitch mode with two ephone-dn entries created for each individual extension number, the automatic assignment mechanism assigns both ephone-dn entries to an individual ephone associated with an IP phone.
Note
Examples
The following examples show how to configure the Auto Assign feature, including prerequisite commands for configuring the auto assign command.
The following example shows how to enter the ephone-dn configuration and create ephone-dns configurations, tags 1-4, each having a single primary number:
Router(config)# ephone-dn 1
Router(config-ephone-dn)# number 2000
Router(config-ephone-dn)# exit
Router(config)# ephone-dn 2
Router(config-ephone-dn)# number 3000
Router(config-ephone-dn)# exit
Router(config)# ephone-dn 3
Router(config-ephone-dn)# number 4000
Router(config-ephone-dn)# exit
Router(config)# ephone-dn 4
Router(config-ephone-dn)# number 4001
Router(config-ephone-dn)# exit
The following example shows how to designate ephone-dn tags 1 to 4 for automatic assignment to any type of IP phone and then perform a fast reboot of all phones:
Router(config)# telephony-service
Router(config-telephony)# auto assign 1 to 4
Router (config-telephony)# restart all
The following example is the partial output from the show ephone registered command listing four registered IP phones, to which ephone-dn tags 1 to 4 have been automatically assigned, after the phones were booted:
Router# show ephone registered
ephone-1 Mac:0003.E3E7.F627 TCP socket:[2] activeLine:0 REGISTERED
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0
IP:10.0.0.2 51671 Telecaster 7940 keepalive 28 max_line 2
button 1: dn 1 number 2000
ephone-2 Mac:0030.94C3.F43A TCP socket:[1] activeLine:0 REGISTERED
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0
IP:10.0.0.3 50094 Telecaster 7960 keepalive 28 max_line 6
button 1: dn 2 number 3000
ephone-3 Mac:0003.6B40.99DA TCP socket:[3] activeLine:0 REGISTERED
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0
IP:10.0.0.200 51879 Telecaster 7960 keepalive 28 max_line 6
button 1: dn 3 number 4000
ephone-4 Mac:0010.406B.99D9 TCP socket:[4] activeLine:0 REGISTERED
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0
IP:10.0.0.012 51879 Telecaster 7960 keepalive 28 max_line 6
button 1: dn 4 number 4001
.
.
.
The following example shows how to designate ephone-dn tags 1 to 12 for automatic assignment to Cisco Unified IP Phone 7910Gs only and ephone-dn tags 13 to 20 for automatic assignment to a Cisco Unified IP Phones 7960 and 7960Gs only, with call forwarding to extension 5001 on busy or after 30 seconds of ringing with no answer:
Router(config)# telephony-service
Router(config-telephony)# auto assign 1 to 12 type 7910
Router(config-telephony)# auto assign 13 to 20 type 7960 cfw 5001 timeout 30
Related Commands
auto logout
To enable the automatic change of an ephone hunt group agent's ephone-dn to not-ready status after a specified number of hunt-group calls are not answered, use the auto logout command in ephone-hunt configuration mode. To disable automatic logout, use the no form of this command.
auto logout [number-of-calls] [dynamic | static]
no auto logout [number-of-calls] [dynamic | static]
Syntax Description
Command Default
Automatic change of agent status to not-ready is disabled.
Command Modes
Ephone-hunt configuration
Command History
Usage Guidelines
This command is valid only for the following Cisco IP phones:
•
•
•
•
This command is used with the Automatic Agent Status Not-Ready feature for ephone hunt groups, which automatically puts an agent's phone in not-ready status when it exceeds a specified limit. The limit at which the Automatic Agent Status Not-Ready feature is triggered depends on the Cisco CME version that you are using, as follows:
•
•
When Automatic Agent Status Not-Ready is specified for an ephone hunt group and it is triggered because an ephone-dn member does not answer a specified number of ephone hunt group calls, the following actions take place:
•
•
•
Note
You can use the auto logout command with any number of ephone hunt groups, but any ephone-dn to which the auto logout command applies must belong to only one ephone. Automatic Agent Status Not-Ready is not supported on shared lines.
Examples
This section provides the following examples:
•
•
Cisco CME 3.3 and Earlier Versions
In the following example, ephone hunt group 1 is configured to permit automatic logout. If hunt group calls that are presented to 1001 and 1002 are unanswered (that is, if they ring longer than 40 seconds each), ephone 1 and ephone 2 are automatically put into DND mode. All unanswered calls are sent to voice mail (5000).
Router(config)# ephone-dn 1Router(config-ephone-dn)# number 1001Router(config)# ephone-dn 2Router(config-ephone-dn)# number 1002Router(config)# ephone-hunt 1 peerRouter(config-ephone-hunt)# pilot 1111Router(config-ephone-hunt)# list 1001, 1002Router(config-ephone-hunt)# final 5000Router(config-ephone-hunt)# timeout 40Router(config-ephone-hunt)# auto logoutRouter(config)# ephone 1Router(config-ephone)# button 1:1Router(config)# ephone 2Router(config-ephone)# button 1:2Cisco Unified CME 4.0 and Later Versions
In the following example, Automatic Agent Status Not-Ready is limited to dynamic hunt group members who do not answer two consecutive ephone hunt group calls. Ephone-dn 33, extension 1003, has dynamically joined ephone-hunt group 1. Ephone 3 will be put into DND mode if extension 1003 does not answer two consecutive hunt group calls. Ephones 1 and 2 will not be put into DND if they do not answer hunt-group calls, because the auto logout command applies only to dynamic hunt-group agents.
Router(config)# telephony-serviceRouter(config-telephony)# hunt-group logout DNDRouter(config)# ephone-dn 11Router(config-ephone-dn)# number 1001Router(config)# ephone-dn 22Router(config-ephone-dn)# number 1002Router(config)# ephone-dn 33Router(config-ephone-dn)# number 1003Router(config-ephone-dn)# ephone-hunt loginRouter(config)# ephone-hunt 1 peerRouter(config-ephone-hunt)# pilot 1111Router(config-ephone-hunt)# list 1001, 1002, *Router(config-ephone-hunt)# final 5000Router(config-ephone-hunt)# auto logout 2 dynamicRouter(config)# ephone 1Router(config-ephone)# button 1:11Router(config)# ephone 2Router(config-ephone)# button 1:22Router(config)# ephone 3Router(config-ephone)# button 1:33In the following example, Automatic Agent Status Not-Ready cannot be used because all of the ephone-dns are shared.
Router(config)# ephone-dn 1Router(config-ephone-dn)# number 1001Router(config)# ephone-dn 2Router(config-ephone-dn)# number 1002Router(config)# ephone-hunt 1 peerRouter(config-ephone-hunt)# pilot 1111Router(config-ephone-hunt)# list 1001, 1002Router(config-ephone-hunt)# final 6000Router(config)# ephone 1Router(config-ephone)# button 1o1,2Router(config)# ephone 2Router(config-ephone)# button 1o1,2Related Commands
auto-answer
To enable the intercom auto-answer feature on a SIP phone extension, use the auto-answer command in voice register dn configuration mode. To return to the default, use the no form of this command.
auto-answer
no auto-answer
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Voice register dn configuration
Command History
Usage Guidelines
This command creates an IP phone line connection that resembles a private line, automatic ring-down (PLAR). The auto-answer causes an extension (directory number) to operate in auto-dial fashion for outbound calls and auto answer-with-mute for inbound calls. If an extension is configured for intercom operation, it can be associated with one Cisco IP phone only.
Any caller can dial an intercom extension, and a call to an intercom extension that is originated by a nonintercom caller triggers an automatic answer exactly like a legitimate intercom call. To prevent nonintercom originators from manually dialing an intercom destination, you can use alphabetic characters when you assign numbers to intercom extensions by using the number command. These characters cannot be dialed from a normal phone but can be dialed by preprogrammed intercom extensions when calls are made by the router.
Use the reset command to reset an individual SIP phone after you make changes to an extension for a SIP phone in Cisco CME.
Examples
The following example shows how to set the auto-answer feature on SIP phone directory number 1:
Router(config)# voice register dn 1Router(config-register-dn) number A5001Router(config-register-dn) auto-answerRelated Commands
auto-line
To enable automatic line selection on an IP phone in a Cisco CallManager Express (Cisco CME) system, use the auto-line command in ephone configuration mode. To disable automatic line selection, use the no form of this command.
auto-line [button-number [answer-incoming] | incoming]
no auto-line
Syntax Description
Command Default
Automatic line selection is enabled.
Command Modes
Ephone configuration
Command History
Usage Guidelines
Use the auto-line command with no keyword or argument enables automatic line selection on the specified ephone. Picking up a handset answers the first ringing line or, if no line is ringing, selects the first idle line. This is also the default behavior if this command is not used.
Use the auto-line incoming command enables automatic line selection for incoming calls only. Picking up the handset answers the first ringing line and, if no line is ringing, does not select an idle line for an outgoing call. Pressing a line button selects a line for an outgoing call.
Use the auto-line command with the button-number argument specifies the line that will automatically be selected when the handset is picked up to make an outgoing call. If a button number is specified and the line associated with that button is unavailable (because it is a shared line in use on another phone), no dial tone is heard when the handset is lifted. You must press an available line button to make an outgoing call. Incoming calls must be answered by pressing the Answer soft key or pressing the ringing line button.
Use the answer-incoming keyword with the button-number argument enables automatic line selection for incoming calls on the specified button. Picking up the handset answers the incoming call on the line button associated with the button-number argument.
Use the no auto-line command disables automatic line selection on the ephone that is being configured. Pressing the Answer soft key answers the first ringing line, and pressing a line button selects a line for an outgoing call. Picking up the handset does not answer calls or provide dial tone.
Examples
The following example shows how to disable automatic line selection. The phone user must use the Answer soft key or press a line button to answer calls, or the phone user must press a line button to initiate outgoing calls.
Router(config)# ephone 23Router(config-ephone)# no auto-lineThe following example shows how to enable automatic line selection for incoming calls only. The phone user picks up the handset to answer the first ringing line. To make outgoing calls, the phone user must press a line button.
Router(config)# ephone 24Router(config-ephone)# auto-line incomingThe following example shows how to enable the automatic selection of line button 3 for outgoing calls when the handset is lifted. There is no automatic answering of incoming calls; the user presses the Answer soft key or presses a line button to answer a call.
Router(config)# ephone 26Router(config-ephone)# auto-line 3The following example shows how to enable the automatic selection of line button 3 when the handset is lifted to answer incoming calls or to make outgoing calls.
Router(config)# ephone 26Router(config-ephone)# auto-line 3 answer-incomingRelated Commands
auto-reg-ephone
To enable automatic registration of ephones with the Cisco Unified CME system, use the auto-reg-ephone command in telephony-service configuration mode. To disable automatic registration, use the no form of this command.
auto-reg-ephone
no auto-reg-ephone
Syntax Description
This command has no keywords or arguments.
Command Default
Automatic registration is enabled.
Command Modes
Telephony-service configuration
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)T
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
This command is enabled by default and allows automatic registration, in which Cisco Unified CME allocates an ephone slot to any ephone that connects to it, regardless of whether the ephone appears in the configuration or not.
The no form of this command blocks the automatic registration of ephones whose MAC addresses are not explicitly listed in the configuration. When automatic registration is blocked, Cisco Unified CME records the MAC addresses of phones that attempt to register but cannot because they are blocked.
Use the show ephone attempted-registrations command to view the list of phones that have attempted to register but have been blocked. Use the clear telephony-service ephone-attempted-registrations command to clear the list of phones that have attempted to register but have been blocked.
Examples
The following example disables automatic registration of ephones that are not listed in the configuration:
Router(config)# telephony-serviceRouter(config-telephony)# no auto-reg-ephoneRelated Commands
Posted: Tue Sep 4 14:04:23 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
