|
Table Of Contents
keepalive (ephone and ephone-template)
keepalive (voice register session-server)
keep-conference (voice register pool)
Cisco Unified CME Commands: K
Last Updated: July 19, 2007First Published: February 27, 2006
This 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.
.
keepalive (ephone and ephone-template)
To set the length of the time interval between successive keepalive messages from the Cisco Unified CME router to a particular IP phone, use the keepalive command in ephone or ephone-template configuration mode. To reset this length to the default value, use the no form of this command.
keepalive seconds
no keepalive
Syntax Description
Defaults
30 seconds
Command Modes
Ephone configuration
Ephone-template configurationCommand History
Usage Guidelines
If the router fails to receive three successive keepalive messages, it considers the phone to be out of service until the phone reregisters.
This command allows the keepalive interval to be set for individual phones so that wireless phone batteries are not run down too quickly by overly frequent keepalive signals.
If the keepalive (telephony-service) command and the keepalive (ephone) command are set to different time intervals, the value that has been set using the keepalive (ephone) command is used for that phone only.
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 sets the keepalive interval to 300 seconds:
Router(config)# ephone 1
Router(config-ephone)# keepalive 300
Related Commands
Command Descriptionephone
Enters ephone configuration mode.
keepalive (telephony-service)
Sets the time interval for keepalive messages between IP phones and the Cisco Unified CME router.
keepalive (telephony-service)
To set the length of the time interval between successive keepalive messages from the Cisco CallManager Express router to IP phones, use the keepalive command in telephony-service configuration mode. To reset this length to the default value, use the no form of this command.
keepalive seconds
no keepalive
Syntax Description
Defaults
30 seconds
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
If the router fails to receive three successive keepalive messages, it considers the phone to be out of service until the phone reregisters.
If the keepalive (telephony-service) command and the keepalive (ephone) command are set to different time intervals, the value that is set for the keepalive (ephone) command is used for that phone only.
Examples
The following example sets the keepalive time interval to 40 seconds:
Router(config)# telephony-service
Router(config-telephony)# keepalive 40
Related Commands
keepalive (voice register session-server)
To define the duration for registrations of external feature servers after which the registration expires, use the keepalive command in voice register session-server configuration mode. To return to the default, use the no form of this command.
keepalive seconds
no keepalive
Syntax Description
Command Default
300 seconds
Command Modes
Voice register session-server configuration (config-register-fs)
Command History
Cisco IOS Release Cisco Product Modification12.4(11)XW2
Cisco Unified CME 4.2
This command was introduced.
Usage Guidelines
Use this command to define the duration for registration, in seconds, after which the registration expires unless the feature server reregisters before the registration expiry.
Examples
The following partial output shows the configuration for a session manager for an external feature server, including a keepalive expiry of 360 seconds:
router# show running-configuration
!
!
voice register session-server 1
register-id CSR1
keepalive 360
Related Commands
Command Descriptionregister id
Creates an ID for explicitly identifying an external feature server during Register requests.
keep-conference
To allow conference initiators to exit from conference calls and to either end or maintain the conference for the remaining parties, use the keep-conference command in ephone or ephone-template configuration mode. To return to the default, use the no form of this command.
keep-conference [drop-last] [endcall] [local-only]
no keep-conference
Syntax Description
Defaults
The default is that the keep-conference command is not enabled. A conference initiator can hang up or press the EndCall soft key to end a conference and disconnect all parties or press the Confrn soft key to drop only the last party that was connected to the conference.
Command Modes
Ephone configuration
Ephone-template configurationCommand History
Usage Guidelines
Note This feature uses call transfer to connect the two remaining parties of a conference when a conference initiator leaves the conference. To use this feature, you must configure the transfer-system command using the full-blind, full-consult, or full-consult dss keywords.
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.
If the keep-conference command is configured with no keywords, a conference initiator can hang up to leave the conference and the other two parties will remain connected. Alternatively, the conference initiator can use the EndCall soft key to terminate the conference and disconnect all parties.
If the keep-conference command is configured with no keywords, a conference initiator can use the Confrn soft key (IP phone) or hookflash (analog phone) to break up the conference but stay connected to both parties. The oldest call will be put on hold, and the most recent call will be actively connected to the initiator. The conference initiator can navigate between the two parties by pressing the Hold soft key or the appropriate line button on the phone.
If the endcall keyword is used, the conference initiator can hang up or press the EndCall soft key to leave the conference with the other two parties remaining connected.
In Cisco CME 3.2.3 and later versions, if the keep-conference command is not configured (the default) or if the no keep-conference command is used, a conference initiator can drop the last party that was added to the conference by pressing the Confrn soft key (IP phone) or hookflash (analog phone).
Note Analog phones connected to the Cisco Unified CME system through a Cisco VG 224 require Cisco IOS Release 12.3(11)YL1 or a later release to use this feature.
Examples
In the following example, extension 3555 initiates a three-way conference. After the conference is established, extension 3555 can press the Confrn soft key to disconnect the last party that was connected and remain connected to the first party that was connected. If extension 3555 hangs up from the conference, the other two parties remain connected if one of them is local to the Cisco Unified CME system.
ephone-dn 35
number 3555
ephone 24
button 1:35
keep-conference drop-last local-only
In the following example, extension 3666 initiates a three-way conference. After the conference is established, extension 3666 can press the Confrn soft key to disconnect the last party that was connected and remain connected to the first party that was connected. Also, extension 3666 can hang up from a three-way conference to terminate the conference and disconnect all parties or can press the EndCall soft key to leave the conference and keep the other two parties connected.
ephone-dn 36
number 3666
ephone 25
button 1:36
keep-conference drop-last endcall
In the following example, extension 3777 initiates a three-way conference. After the conference is established, extension 3777 can press the Confrn soft key to disconnect the last party that was connected and remain connected to the first party that was connected. Also, extension 3777 can hang up from a three-way conference to terminate the conference and disconnect all parties or press the EndCall soft key to leave the conference and keep the other two parties connected only if one of the two parties is local to the Cisco Unified CME system.
ephone-dn 38
number 3777
ephone 27
button 1:38
keep-conference drop-last endcall local-only
In the following example, extension 3999 initiates a three-way conference. After the conference is established, extension 3999 can hang up to terminate the conference and disconnect all parties or press the EndCall soft key to leave the conference and keep the other two parties connected only if one of the two parties is local to the Cisco Unified CME system.
ephone-dn 39
number 3999
ephone 29
button 1:39
keep-conference endcall local-only
Related Commands
keep-conference (voice register pool)
To allow IP phone conference initiators to exit from conference calls and keep the remaining parties connected, use the keep-conference command in voice register pool configuration mode. To disable the keep-conference feature, use the no form of this command.
keep-conference
no keep-conference
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Voice register pool configuration
Command History
Usage Guidelines
When the conference initiator hangs up, Cisco CallManager Express (Cisco CME) executes a call transfer to connect the two remaining lines. The remaining calls are transferred without consultation. To facilitate call transfer, the transfer-attended command or transfer-blind command must be enabled.
Conference initiators can disconnect from their conference calls by pressing the Confrn (conference) soft key. When an initiator uses the Confrn soft key to disconnect from the conference call, the oldest call leg is put on hold, leaving the initiator connected to the most recent call leg. The conference initiator can then navigate between the two separate parties by pressing either the Hold soft key or the line buttons to select the desired call.
Examples
The following example shows how to configure Cisco IP phones in Cisco CME to keep remaining conference legs after the conference initiator hangs up.
Router(config)# voice register pool 1
Router(config-register-pool)# keep-conference
Related Commands
keygen-retry
To specify the number of times that a CAPF server sends a key generation request, use the keygen-retry command in CAPF-server configuration mode. To return to the default, use the no form of this command.
keygen-retry number
no keygen-retry
Syntax Description
Command Default
Number of retries is 3.
Command Modes
CAPF-server configuration
Command History
Cisco IOS Release Cisco Product Modification12.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.
Examples
The following example specifies that the key generation process should be tried 5 times.
Router(config)# capf-server
Router(config-capf-server)# source address 10.10.10.1
Router(config-capf-server)# trustpoint-label server25
Router(config-capf-server)# cert-oper upgrade all
Router(config-capf-server)# cert-enroll-trustpoint server12 password 0 x8oWiet
Router(config-capf-server)# auth-mode auth-string
Router(config-capf-server)# auth-string generate all
Router(config-capf-server)# port 3000
Router(config-capf-server)# keygen-retry 5
Router(config-capf-server)# keygen-timeout 45
Router(config-capf-server)# phone-key-size 2048
keygen-timeout
To specify the number of minutes that the CAPF server waits for a key-generation response from a phone, use the keygen-timeout command in CAPF-server configuration mode. To return to the default, use the no form of this command.
keygen-timeout minutes
no keygen-timeout
Syntax Description
minutes
Number of minutes before the generation process times out. Range is from 1 to 120. Default is 30.
Command Default
30 minutes
Command Modes
CAPF-server configuration
Command History
Cisco IOS Release Cisco Product Modification12.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.
Examples
The following example specifies a period of 45 minutes before the key generation process times out.
Router(config)# capf-server
Router(config-capf-server)# source address 10.10.10.1
Router(config-capf-server)# trustpoint-label server25
Router(config-capf-server)# cert-oper upgrade all
Router(config-capf-server)# cert-enroll-trustpoint server12 password 0 x8oWiet
Router(config-capf-server)# auth-mode auth-string
Router(config-capf-server)# auth-string generate all
Router(config-capf-server)# port 3000
Router(config-capf-server)# keygen-retry 5
Router(config-capf-server)# keygen-timeout 45
Router(config-capf-server)# phone-key-size 2048
keypad-normalize
To impose a 200-millisecond delay before each keypad message from an IP phone, use the keypad-normalize command in ephone or ephone-template configuration mode. To return to the default, use the no form of this command.
keypad-normalize
no keypad-normalize
Syntax Description
This command has no keywords or arguments.
Command Default
Keypad messages are handled as fast as the system can handle them, without an imposed delay.
Command Modes
Ephone configuration
Ephone-template configurationCommand History
Cisco IOS Release Cisco Product Modification12.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 normalizes the processing of incoming keypad messages from an IP phone so that one message is processed every 200 milliseconds. This is useful for handling the personal speed dial (fastdial) feature when the destination of the call tends to be slower in accepting the digits, or when converting keypad messages into appropriate digit events on the network side, such as RFC 2833 digits.
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 normalizes the sending of digits from ephone 43.
ephone 43
button 1:29
keypad-normalize
keyphone
To designate a Cisco Unified IP phone as a marked or "key" phone when using the Cisco Unified CME eXtensible Markup Language (XML) application program interface (API), use the keyphone command in ephone or ephone-template configuration mode. To remove the keyphone designation, use the no form of this command.
keyphone
no keyphone
Syntax Description
This command has no arguments or keywords.
Defaults
The phone that is being configured is not a "key" phone.
Command Modes
Ephone configuration
Ephone-template configurationCommand History
Usage Guidelines
This command is used with the XML API to mark a Cisco Unified IP phone as a "key" phone to be tracked while using the XML API. The XML API can be instructed to report the status of only the "key" phones in the system for network management purposes, for example.
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 sets the phone with the phone tag of 1 as a "key" phone for the XML API:
Router(config)# ephone 1
Router(config-ephone)# keyphone
Related Commands
Posted: Thu Jul 19 11:07:00 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.