Cisco CallManager Express 3.0 Command Reference: N through Z
Available Languages
Table Of Contents
Cisco CallManager Express 3.0 Commands:
N through Znight-service bell (ephone-dn)
pattern trunk-to-ext no-answer
show telephony-service dial-peer
show telephony-service directory-entry
show telephony-service ephone-dn
show telephony-service tftp-bindings
show telephony-service voice-port
timeouts interdigit (telephony-service)
timeouts ringing (telephony-service)
time-webedit (telephony-service)
transfer-pattern (telephony-service)
Cisco CallManager Express 3.0 Commands:
N through Z
This chapter documents commands to configure and maintain Cisco CallManager Express. The commands are presented in alphabetical order. Some commands required for configuring voice may be found in other Cisco IOS command references. Use the Cisco IOS Release 12.3 Master Indexes or search online to find these commands.
For detailed information on how to configure Cisco CallManager Express applications and features, refer to the Cisco CallManager Express 3.0 System Administration Guide.
Note
Prior to Version 3.0, Cisco CallManager Express was known as Cisco IOS Telephony Services (Cisco ITS).
name (ephone-dn)
To associate a name with a Cisco CallManager Express (Cisco CME) extension (ephone-dn), use the name command in ephone-dn configuration mode. To disassociate a name from an extension, use the no form of this command.
name name
no name
Syntax Description
name
Name of the person associated with this extension (ephone-dn). Name must follow the order specified in the directory (telephony-service) command, either first-name-first or last-name-first.
Defaults
No default behavior or values
Command Modes
Ephone-dn configuration
Command History
Usage Guidelines
The username argument is used to provide caller ID for calls originating from a Cisco CME extension. This command is also used to generate directory information for the local directory that is accessed from the Directories button on a Cisco IP phone.
Examples
The following example configures the username John Smith with the pattern first-name-first:
Router(config)# ephone-dn 1Router(config-ephone-dn) name John SmithThe following example configures the username Jane Smith with the pattern last-name-first:
Router(config)# ephone-dn 1Router(config-ephone-dn) name Smith, JaneRelated Commands
directory (telephony-service)
Defines the name order for the local directory of Cisco IP phone users.
ephone-dn
Enters ephone-dn configuration mode.
network-locale
To select a code for a geographically-specific set of tones and cadences on the Cisco IP Phone 7940 and Cisco IP Phone 7960, use the network-locale command in telephony-service configuration mode. To disable selection of a code, use the no form of this command.
network-locale locale-code
no network-locale locale-code
Syntax Description
Defaults
The default country code is US (United States).
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 with Cisco IOS Telephony Services V2.1, Cisco CallManager Express 3.0, or a later version.
The show telephony-service tftp-bindings command displays the locale-specific call-progress tone files that are accessible to IP phones using TFTP.
Examples
The following example sets tones and cadences for France:
Router(config)# telephony-serviceRouter(config-telephony-service)# network-locale FRRelated Commands
show telephony-service tftp-bindings
Displays the current configuration files that are accessible to IP phones.
telephony-service
Enters telephony-service configuration mode.
night-service bell (ephone)
To mark an IP phone to receive night-service bell notification when incoming calls are received on ephone-dns that are marked for night service during night-service time periods, use the night-service bell command in ephone configuration mode. To remove night-service notification capability from a phone, use the no form of this command.
night-service bell
no night-service bell
Syntax Description
This command has no arguments or keywords.
Defaults
A phone is not marked for night-service bell notification.
Command Modes
Ephone 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
When an ephone-dn is marked for night-service treatment using the night-service bell (ephone-dn) command, incoming calls that ring during the night-service time period on that ephone-dn send an alert indication to all IP phones that are marked to receive night-service bell notification with this command. The alert notification is in the form of a splash ring (not associated with any of the individual lines on the IP phone) and a visible display of the ephone-dn extension number. The phone user retrieves the call by pressing a PickUp or GPickUp soft key and dialing the appropriate digits.
Night-service periods are defined using the night-service date and night-service day commands. Night service can be manually disabled or reenabled from a phone with ephone-dns in night-service mode if the night-service code command has been set.
Examples
The following example designates the IP phone that is being configured as a phone that will receive night-service bell notification when ephone-dns marked for night service receive incoming calls during a night-service period:
Router(config)# ephone 4Router(config-ephone)# night-service bellRelated Commands
night-service bell (ephone-dn)
To mark an ephone-dn for night-service treatment, use the night-service bell command in ephone-dn configuration mode. To remove the night-service treatment from the ephone-dn, use the no form of this command.
night-service bell
no night-service bell
Syntax Description
This command has no arguments or keywords.
Defaults
An ephone-dn is not marked for night service.
Command Modes
Ephone-dn 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
When an ephone-dn is marked for night-service treatment using this command, incoming calls that ring during the night-service time period on that ephone-dn send an alert indication to all IP phones that are marked to receive night-service bell notification using the night-service bell (ephone) command. The alert notification is in the form of a splash ring (not associated with any of the individual lines on the IP phone) and a visible display of the ephone-dn extension number. The phone user retrieves the call by pressing a PickUp or GPickUp soft key and dialing the appropriate digits.
Night-service periods are defined using the night-service date and night-service day commands. Night service can be manually disabled or reenabled from a phone with ephone-dns in night-service mode if the night-service code command has been set.
Examples
The following example marks an ephone-dn as a line that will ring on IP phones designated to receive night-service bell notification when incoming calls are received on this ephone-dn during night-service periods:
Router(config)# ephone-dn 16Router(config-ephone-dn)# night-service bellRelated Commands
night-service code
To define a code to disable or reenable night service on IP phones, use the night-service code command in telephony-service configuration mode. To remove the code, use the no form of this command.
night-service code digit-string
no night-service code digit-string
Syntax Description
Defaults
No code 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
When an ephone-dn is marked for night-service treatment using the night-service bell (ephone-dn) command, incoming calls that ring during the night-service time period on that ephone-dn send an alert indication to all IP phones that are marked to receive night-service bell notification using the night-service bell (ephone) command. The alert notification is in the form of a splash ring (not associated with any of the individual lines on the IP phone) and a visible display of the ephone-dn extension number. The phone user retrieves the call by pressing a PickUp or GPickUp soft key and dialing the appropriate digits.
Night-service periods are defined with the night-service date and night-service day commands. Night service can be manually disabled or reenabled from a phone with ephone-dns in night-service mode if the night-service code command has been set.
Examples
The following example defines a night-service code of *2985:
Router(config)# telephony-serviceRouter(config-telephony-service)# night-service code *2985Related Commands
night-service date
To define a recurring time period associated with a date during which night service is active, use the night-service date command in telephony-service configuration mode. To delete the defined time period, use the no form of this command.
night-service date month date start-time stop-time
no night-service date month date start-time stop-time
Syntax Description
Defaults
No time period based on date is defined for night service.
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
After you define night-service periods using this command and the night-service day command, use the night-service bell (ephone-dn) command to specify the extensions that will ring on other phones and the night-service bell (ephone) command to specify the phones on which the extensions will ring during the designated night-service periods.
Examples
The following example defines a night-service time period for the entire day of January 1:
Router(config)# telephony-serviceRouter(config-telephony-service)# night-service date jan 1 00:00 00:00Related Commands
night-service day
To define a recurring time period associated with a day of the week during which night service is active, use the night-service day command in telephony-service configuration mode. To delete the defined time period, use the no form of this command.
night-service day day start-time stop-time
no night-service day day start-time stop-time
Syntax Description
Defaults
No time period based on day of the week is defined for night service.
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
After you define night-service periods using this command and the night-service date command, use the night-service bell (ephone-dn) command to specify the extensions that will ring on other phones and the night-service bell (ephone) command to specify the phones on which the extensions will ring during the designated night-service periods.
Examples
The following example defines a night-service time period from Monday at 7 p.m. to Tuesday at 7 a.m.:
Router(config)# telephony-serviceRouter(config-telephony-service)# night-service day mon 19:00 07:00Related Commands
no-reg (ephone-hunt)
To specify that the pilot number for a Cisco CallManager Express (Cisco CME) peer ephone hunt group not register with an H.323 gatekeeper, use the no-reg command in ephone-hunt configuration mode. To return to the default, use the no form of this command.
no-reg
no no-reg
Syntax Description
This command has no arguments or keywords.
Defaults
The pilot number registers with the H.323 gatekeeper.
Command Modes
Ephone-hunt 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
This command is valid only for Cisco CME peer ephone hunt groups.
Examples
The following example specifies that the pilot number of peer ephone hunt group 2 not register with the H.323 gatekeeper:
Router(config)# ephone-hunt 2 peerRouter(config-ephone-hunt)# no-regRelated Commands
number (ephone-dn)
To associate a telephone or extension number with an extension (ephone-dn) in a Cisco CallManager Express (Cisco CME) system, use the number command in ephone-dn configuration mode. To disassociate a number from an extension, use the no form of this command.
number number [secondary number] [no-reg [both | primary]]
no number
Syntax Description
Defaults
No primary or secondary phone number is associated with the ephone-dn.
Command Modes
Ephone-dn configuration
Command History
Usage Guidelines
This command defines a valid number for an ephone-dn (extension) that is to be assigned to an IP phone. The secondary keyword allows you to associate a second telephone number with an ephone-dn so that it can be called by dialing either the main or secondary phone number. The secondary number may contain wildcards; for example, 50.. (the number 50 followed by wildcards).
The no-reg keyword causes an E.164 number in the dial peer not to register with the gatekeeper. If you do not specify both or primary after the no-reg keyword, only the secondary number does not register.
A number normally contains only numeric characters, which allow it to be dialed from any telephone keypad. However, in certain cases, such as the numbers for intercom extensions, you want to use numbers that can only be dialed internally from the Cisco CallManager Express router and not from telephone keypads. Intercoms consist of a pair of extensions on different phones that are preprogrammed using the intercom command to dial each other. The phone user just presses an intercom button and the actual dialing is done by the router. At the other end, the receiving phone automatically answers the intercom call. Generally you do not want free access to this functionality; that is, you do not want other phone users to be able to dial an intercom number. The number command allows you to assign alphabetic characters to the number so that the extension can be dialed by the router for intercom calls but not by unauthorized individuals from other phones.
After you use the number command, an ephone-dn is assigned to an ephone using the button command. Following the button command, the restart command must be used to initiate a quick reboot of the phone to which this number is assigned.
Examples
The following example sets 5001 as the primary extension number for a Cisco IP phone and 0 as the secondary number. This configuration allows the telephone number 5001 to act as a regular extension number and also to act as the operator line such that callers who dial 0 are routed to the phone line with extension number 5001.
Router(config)# ephone-dn 1Router(config-ephone-dn)# number 5001 secondary 0The following example sets 5001 as the primary extension number for a Cisco IP phone and "500." (the number 500 followed by a decimal point) as the secondary number. This configuration allows any calls to extension numbers from the range 5000 to 5009 to be routed to extension 5001 if the actual extension number dialed cannot be found. For example, IP phones may be active in the system with lines that correspond to 5001, 5002, 5004, 5005, and 5009. A call to 5003 would be unable to locate a phone with extension 5003, so the call would be routed to extension 5001.
Router(config-ephone-dn)# number 5001 secondary 500.The following example defines a pair of intercom ephone-dns that are programmed to call each other. The intercom numbers contain alphabetic characters to prevent anyone from dialing them from another phone. Ephone-dn 19 is assigned the number A5511 and is programmed to dial A5522, which belongs to ephone-dn 20. Ephone-dn 20 is programmed to dial A5511. No one else can dial these numbers.
Router(config)# ephone-dn 19Router(config-ephone-dn)# number A5511Router(config-ephone-dn)# name IntercomRouter(config-ephone-dn)# intercom A5522Router(config-ephone-dn)# exitRouter(config)# ephone-dn 20Router(config-ephone-dn)# number A5522Router(config-ephone-dn)# name IntercomRouter(config-ephone-dn)# intercom A5511Related Commands
paging (ephone-dn)
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.
paging [ip multicast-address port udp-port-number]
no paging [ip]
Syntax Description
Defaults
No paging number is established.
Command Modes
Ephone-dn configuration
Command History
Usage Guidelines
To configure a set of phones to receive an audio page, follow these steps:
1.
ephone-dn 21pagingnumber 344552.
ephone 3paging-dn 21ephone 4paging-dn 21The 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
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.
Examples
The following example creates a paging extension number that uses IP multicast paging:
Router(config)# ephone-dn 20Router(config-ephone-dn) number 2000Router(config-ephone-dn) paging ip 239.0.1.1 port 2000A more complete configuration example follows, in which paging sets 20 and 21 are created. Pages to extension 2000 are multicast to ephones 1 and 2. Pages to extension 2001 are multicast to ephones 3 and 4.
ephone-dn 1number 2345ephone-dn 2number 2346ephone-dn 3number 2347ephone-dn 4number 2348ephone-dn 20number 2000paging ip 239.0.1.20 port 2000ephone-dn 21number 2001paging ip 239.0.1.21 port 2000ephone 1button 1:1paging-dn 20ephone 2button 1:2paging-dn 20ephone 3button 1:3paging-dn 21ephone 4button 1:4paging-dn 21Related Commands
paging group (ephone-dn)
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.
paging group paging-dn-tag, paging-dn-tag...
no paging group
Syntax Description
Defaults
Paging is disabled on all Cisco IP phones.
Command Modes
Ephone-dn configuration
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 command.
The use of paging groups 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).
Examples
In the following example, paging sets 20 and 21 are defined and then combined into paging group 22. Paging set 20 has a paging extension of 2000. When someone dials extension 2000 to deliver a page, the page is sent to Cisco IP phones (ephones) 1 and 2. Paging set 21 has a paging extension of 2001. When someone dials extension 2001 to deliver a page, the page is sent to ephones 3 and 4. Paging group 22 combines sets 20 and 21, and when someone dials its paging extension, 2002, the page is sent to all the phones in both sets and to ephone 5, which is directly subscribed to the combined paging group.
ephone-dn 20number 2000paging ip 239.0.1.20 port 2000ephone-dn 21number 2001paging ip 239.0.1.21 port 2000ephone-dn 22number 2002paging ip 239.0.2.22 port 2000paging group 20,21ephone 1button 1:1paging-dn 20ephone 2button 1:2paging-dn 20ephone 3button 1:3paging-dn 21ephone 4button 1:4paging-dn 21ephone 5button 1:5paging-dn 22Related Commands
paging-dn (ephone)
To create a paging extension (paging-dn) to receive audio pages on a Cisco IP phone in a Cisco CallManager Express (Cisco CME) system, use the paging-dn command in ephone configuration mode. To disable this feature, use the no form of this command.
paging-dn paging-dn-tag {multicast | unicast}
no paging-dn
Syntax Description
Defaults
Paging is disabled on all Cisco IP phones.
Command Modes
Ephone configuration
Command History
Usage Guidelines
To configure a set of phones to receive an audio page, follow these steps:
1.
ephone-dn 21pagingnumber 344552.
ephone 3paging-dn 21ephone 4paging-dn 21This 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 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 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
Examples
The following example creates paging number 5001 on ephone-dn 22 and adds ephone 4 as a member of the paging set. Multicast is set for the paging-dn. Note that IP phones do not support multicast at 224.x.x.x addresses.
ephone-dn 1number 5123ephone-dn 22name Paging Shippingnumber 5001paging ip 239.1.1.10 port 2000ephone 4mac-address 0030.94c3.8724button 1:1paging-dn 22 multicastRelated Commands
pattern direct
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.
pattern direct tag1 {CDN | CGN | FDN} [tag2 {CDN | CGN | FDN}]
[tag3 {CDN | CGN | FDN}] [last-tag]no pattern direct
Syntax Description
Defaults
This feature is disabled.
Command Modes
Voice-mail integration configuration
Command History
Usage Guidelines
The pattern direct 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 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.
Examples
The following example sets the DTMF pattern for a calling number ($CGN) for a direct call to the voice-mail system:
Router(config) vm-integrationRouter(config-vm-integration) pattern direct 2 CGN *Related Commands
pattern ext-to-ext busy
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.
pattern ext-to-ext busy tag1 {CDN | CGN | FDN} [tag2 {CDN | CGN | FDN}]
[tag3 {CDN | CGN | FDN}] [last-tag]no pattern ext-to-ext busy
Syntax Description
Defaults
This feature is disabled.
Command Modes
Voice-mail integration configuration
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.
Examples
The following example sets the DTMF pattern for a local call forwarded on busy to the voice-mail system:
Router(config) vm-integrationRouter(config-vm-integration) pattern ext-to-ext busy 7 FDN * CGN *Related Commands
pattern ext-to-ext no-answer
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 nonanswering 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.
pattern ext-to-ext no-answer tag1 {CDN | CGN | FDN} [tag2 {CDN | CGN | FDN}]
[tag3 {CDN | CGN | FDN}] [last-tag]no pattern ext-to-ext no-answer
Syntax Description
Defaults
This feature is disabled.
Command Modes
Voice-mail integration configuration
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.
Examples
The following example sets the DTMF pattern for a local call forwarded on no-answer to the voice-mail system:
Router(config) vm-integrationRouter(config-vm-integration) pattern ext-to-ext no-answer 5 FDN * CGN *Related Commands
pattern trunk-to-ext busy
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.
pattern trunk-to-ext busy tag1 {CDN | CGN | FDN} [tag2 {CDN | CGN | FDN}]
[tag3 {CDN | CGN | FDN}] [last-tag]no pattern trunk-to-ext busy
Syntax Description
Defaults
This feature is disabled by default.
Command Modes
Voice-mail integration configuration
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.
Examples
The following example sets the DTMF pattern for call forwarding when an external trunk call reaches a busy extension and the call is forwarded to the voice-mail system:
Router(config) vm-integrationRouter(config-vm-integration) pattern trunk-to-ext busy 6 FDN * CGN *Related Commands
pattern trunk-to-ext no-answer
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.
pattern trunk-to-ext no-answer tag1 {CDN | CGN | FDN} [tag2 {CDN | CGN | FDN}]
[tag3 {CDN | CGN | FDN}] [last-tag]no pattern trunk-to-ext no-answer
Syntax Description
Defaults
This feature is disabled.
Command Modes
Voice-mail integration configuration
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.
Examples
The following example sets the DTMF pattern for call forwarding when an external trunk call reaches an unanswered extension and the call is forwarded to a voice-mail system:
Router(config) vm-integrationRouter(config-vm-integration) pattern trunk-to-ext no-answer 4 FDN * CGN *Related Commands
pickup-group
To assign an extension (ephone-dn) to a Cisco CallManager Express (Cisco CME) call-pickup group, use the pickup-group command in ephone-dn configuration mode. To remove the extension from the group, use the no form of this command.
pickup-group number
no pickup-group
Syntax Description
number
Digit string representing a pickup group number. The string can contain a maximum of 32 digits.
Defaults
An extension does not belong to any pickup group.
Command Modes
Ephone-dn 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
This command allows administrators to assign an individual ephone-dn to a call-pickup group. Phone users can pick up ringing calls within their own pickup group more easily than calls outside their group.
Each ephone-dn can be assigned to a maximum of one pickup group.
Pickup group numbers may be of varying length, but their leading digits must be unique. For example, you cannot define both pickup group 17 and pickup group 177 in the same Cisco CME system, because a pickup in group 17 will always be triggered before the user can enter the final 7 for group 177. You can, however, define pickup groups 27 and 177 in the same Cisco CME system.
There is no limit to the number of ephone-dns that can be assigned to a single pickup group, and there is no limit to the number of pickup groups that can be defined in a Cisco CME system.
Examples
The following example assigns an ephone-dn to pickup group 25:
Router(config)# ephone-dn 4Router(config-ephone-dn)# pickup-group 25Related Commands
pilot
To define the ephone-dn that callers dial to reach a Cisco CallManager Express (Cisco CME) ephone hunt group, use the pilot command in ephone-hunt configuration mode. To remove the pilot number from the ephone hunt group, use the no form of this command.
pilot number
no pilot number
Syntax Description
Defaults
No pilot number is defined.
Command Modes
Ephone-hunt 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
This command is valid only for Cisco CME ephone hunt groups.
The dial-plan pattern can be applied to the pilot number.
Examples
The following example sets the pilot number to 2345 for peer ephone hunt-group number 5:
Router(config)# ephone-hunt 5 peerRouter(config-ephone-hunt)# pilot 2345Related Commands
pin
To set an individual personal identification number (PIN) for an IP phone in a Cisco CallManager Express (Cisco CME) system, use the pin command in ephone configuration mode. To remove a PIN, use the no form of this command.
pin number
no pin
Syntax Description
number
PIN to use to log in to a Cisco IP phone. This is a numeric string from four to eight digits in length.
Defaults
No PIN is set.
Command Modes
Ephone 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
The pin command allows individual phone users to override call-blocking patterns that are associated with defined time periods. Call-blocking patterns that are in effect at all times (7 days a week, 24 hours a day) cannot be overridden using a PIN.
Call blocking on IP phones is defined in the following way. First, one or more patterns of outgoing digits to be blocked are defined using the after-hours block pattern command. Next, one or more time periods during which calls to 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 CME system are restricted if at least one pattern and at least one time period are defined. Individual phones can be completely exempted from call blocking using the after-hour exempt command. An individual with a PIN can override call blocking by entering the PIN after pressing the Login soft key to log in to a phone that has been configured for that PIN using the pin command.
The PIN functionality applies only to IP phones that have soft keys, such as the Cisco IP Phone 7940 and the Cisco IP Phone 7960.
Examples
The following example sets a PIN for an IP phone:
Router(config)# ephone 1Router(config-ephone)# pin 1000Related Commands
preference (ephone-dn)
To set dial-peer preference order for an extension (ephone-dn) associated with a Cisco IP phone, use the preference command in ephone-dn configuration mode. To reset the preference order to the default, use the no form of this command.
preference preference-order [secondary secondary-order]
no preference
Syntax Description
Defaults
preference-order: 0 (highest preference)
secondary-order: 9Command Modes
Ephone-dn configuration
Command History
Usage Guidelines
When you create an ephone-dn for an IP phone in a Cisco CallManager Express (Cisco CME) system, you automatically create a virtual voice port and one to four virtual dial peers to be used by that ephone-dn. This command sets a preference value for the primary and secondary numbers that are associated with the ephone-dn that you are creating. The preference values are passed transparently into the dial peer or dial peers created by the ephone-dn. The preference values allow you to control the selection of a desired dial peer when multiple dial peers are matched on the same destination-pattern (target) number value. In this way, the preference command can be used to establish a hunt strategy for incoming calls.
The huntstop command can be used to prevent further hunting for a dial-peer match when an ephone-dn is busy or does not answer.
Examples
The following example sets a preference of 2 for the directory number 3000:
ephone-dn 1number 3000preference 2In the following example, the number 1222 under ephone-dn 4 has a higher preference than the number 1222 under ephone-dn 5.
ephone-dn 4number 1222preference 0!!ephone-dn 5number 1222preference 1The following example shows an ephone-dn with two numbers. The primary number has a higher preference than the secondary number.
ephone-dn 6number 2233 secondary 2234preference 0 secondary 1Related Commands
ephone-dn
Enters ephone-dn configuration mode.
huntstop
Discontinues call hunting behavior for an extension (ephone-dn) or an extension channel.
preference (ephone-hunt)
To set preference order for the ephone-dn associated with a Cisco CallManager Express (Cisco CME) ephone-hunt-group pilot number, use the preference command in ephone-hunt configuration mode. To delete this preference order, use the no form of this command.
preference preference-order
no preference preference-order
Syntax Description
preference-order
Preference order. Range is from 0 to 8, where 0 is the highest preference and 8 is the lowest preference. Default is 0.
Defaults
0 (highest preference)
Command Modes
Ephone-hunt 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
This command sets a preference value that is used for matching dial peers in a Cisco IP phone virtual dial-peer group. The preference value is associated with a pilot number for a Cisco CME ephone hunt group. The preference value is passed transparently into the dial peer created by the pilot number. Setting the preference enables the desired dial peer to be selected when multiple dial peers within a hunt group are matched for a dial string.
Examples
The following example sets the preference for the pilot number of hunt group 23 to 1:
Router(config)# ephone-hunt 23 sequentialRouter(config-ephone-hunt)# pilot 2355Router(config-ephone-hunt)# preference 1Related Commands
reset (ephone)
To perform a complete reboot of a single phone associated with a Cisco CallManager Express (Cisco CME) router, use the reset command in ephone configuration mode.
reset
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Ephone configuration
Command History
Usage Guidelines
After you update information for one or more phones associated with a Cisco CME router, the phone or phones must be rebooted. There are two commands to reboot the phones: reset and restart. The reset command performs a "hard" reboot similar to a power-off-power-on sequence. It reboots the phone and contacts the DHCP server and TFTP server to update from their information as well. The restart command performs a "soft" reboot by simply rebooting the phone without contacting the DHCP and TFTP servers. The reset command takes significantly longer to process than the restart command when you are updating multiple phones, but it must be used after updating phone firmware, user locale, network locale, or URL parameters. For simple button, line, or speed-dial changes, you can use the restart command.
Use the reset (ephone) command to perform a complete reboot of an IP phone when you are in ephone configuration mode. This command has the same effect as a reset (telephony-service) command that is used to reset a single phone.
This command has a no form, but the no form has no effect.
Examples
The following example resets the Cisco IP phone with a phone-tag of 1:
Router(config)# ephone 1Router(config-ephone)# resetRelated Commands
reset (telephony-service)
To perform a complete reboot of one or all phones associated with a Cisco CallManager Express (Cisco CME) router, use the reset command in telephony-service configuration mode. To interrupt and cancel a sequential reset cycle, use the no form of the command with the sequence-all keyword.
reset {all [time-interval] | cancel | mac-address | sequence-all}
no reset {all [time-interval] | cancel | mac-address | sequence-all}
Syntax Description
Defaults
time-interval: 15
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
After you update information for one or more phones associated with a Cisco CME router, the phone or phones must be rebooted using either the reset command or the restart command. The reset command performs a "hard" reboot similar to a power-off-power-on sequence and contacts the DHCP server and TFTP server for updated information as well. The restart command performs a "soft" reboot by simply rebooting the phone without contacting the DHCP and TFTP servers. The reset command takes significantly longer to process than the restart command when you are updating multiple phones, but it must be used after you make changes to phone firmware, user locale, network locale, or URL parameters. For simple button, line, or speed-dial changes, you can use the restart command.
When using the reset command, the default time interval of 15 seconds is recommended for an 8- to 10-phone office so that all the phones do not attempt to access TFTP server resources simultaneously. This value should be modified accordingly for larger networks.
When you use the reset sequence-all command, the router waits for one phone to complete its reset and reregister before starting to reset the next phone. The delay provided by this command prevents multiple phones from attempting to access the TFTP server simultaneously and therefore failing to reset properly. Each reset operation can take several minutes when you use this command. There is a reset timeout of 4 minutes, after which the router stops waiting for the currently registering phone to complete registration and starts to reset the next phone.
If the router configuration is changed so that the XML configuration files for the phones are modified (changes are made to user locale, network locale, or phone firmware), then whenever you use the reset all or restart all command, the router automatically executes the reset sequence-all command instead. The reset sequence-all command resets phones one at a time in order to prevent multiple phones trying to contact the TFTP server simultaneously. This one-at-a-time sequencing can take a long time if there are many phones. To avoid this automatic behavior, use the reset all time-interval command or the restart all time-interval command with an explicit argument that is not equal to the default 15-second time interval; for example, set a time interval of 14 seconds. If a reset sequence-all command has been started in error, use the reset cancel command to interrupt and cancel the sequence of resets.
The restart command allows the system to perform quick phone resets in which only the button template, line information, and speed-dial information is updated. Refer to the command reference entry for restart for more information.
The no form of the command has an effect only when used with the all or sequence-all keyword, when it interrupts and cancels the sequential resetting of phones.
Examples
The following example resets all IP phones served by the Cisco CME router:
Router(config)# telephony-serviceRouter(config-telephony-service)# reset allThe following example resets the Cisco IP phone with the MAC address CFBA.321B.96FA:
Router(config)# telephony-serviceRouter(config-telephony-service)# reset CFBA.321B.96FAThe following example resets all IP phones in sequential, nonoverlapping order:
Router(config)# telephony-serviceRouter(config-telephony-service)# reset sequence-allRelated Commands
restart (ephone)
To perform a fast reboot of an IP phone associated with a Cisco CallManager Express (Cisco CME) router, use the restart command in ephone configuration mode. To cancel the reboot, use the no form of this command.
restart
no restart
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Ephone configuration
Command History
12.2(11)YT1
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
This command causes the system to perform a fast phone reboot in which only the button template, lines, and speed-dial numbers are updated on the phone. For updates related to phone firmware, user locale, network locale, or URL parameters, use the reset command. The restart command is much faster than the reset command because the phone does not need to access the DHCP or TFTP server.
To restart all phones in a Cisco CME system for quick changes to buttons, lines, and speed-dial numbers, use the restart command in telephony-service configuration mode.
This command has a no form, but the no form has no effect.
Examples
The following example restarts the phone with phone-tag 1:
Router(config)# ephone 1Router(config-ephone)# restartRelated Commands
restart (telephony-service)
To perform a fast reboot of one or all phones associated with a Cisco CallManager Express (Cisco CME) router, use the restart command in telephony-service configuration mode. To cancel the reboot, use the no form of this command.
restart {all [time-interval] | mac-address}
no restart {all [time-interval] | mac-address}
Syntax Description
Defaults
time-interval: 15
Command Modes
Telephony-service configuration
Command History
12.2(11)YT1
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
This command causes the system to perform a fast phone reset in which only the button template, lines, and speed-dial numbers are updated on the phone. For updates related to phone firmware, user locale, network locale, or URL parameters, use the reset command.
Use the restart command to reboot IP phones after quick changes to buttons, lines, and speed-dial numbers. This command is much faster than the reset command because the phone does not access the DHCP or TFTP server.
To restart a single phone, use the restart command with the mac-address argument or use the restart command in ephone configuration mode.
If the router configuration is changed so that the XML configuration files for the phones are modified (changes are made to user locale, network locale, or phone firmware), then whenever you use the reset all or restart all command, the router automatically executes the reset sequence-all command instead. The reset sequence-all command resets phones one at a time in order to prevent multiple phones trying to contact the TFTP server simultaneously. This one-at-a-time sequencing can take a long time if there are many phones. To avoid this automatic behavior, use the reset all time-interval command or the restart all time-interval command with an explicit argument that is not equal to the default 15-second time interval; for example, set a time interval of 14 seconds. If a reset sequence-all command has been started in error, use the reset cancel command to interrupt and cancel the sequence of resets.
The no form of the command has an effect only when used with the all keyword, when it interrupts and cancels the sequential restarting of phones.
Examples
The following example performs a quick restart of all phones in a Cisco CME system:
Router(config)# telephony-serviceRouter(config-telephony-service)# restart allRelated Commands
secondary-dialtone
To activate a secondary dial tone when a Cisco IP phone user dials a defined PSTN access prefix, use the secondary-dialtone command in telephony-service configuration mode. To disable the secondary dial tone, use the no form of this command.
secondary-dialtone digit-string
no secondary-dialtone
Syntax Description
Defaults
No secondary dial tone is enabled.
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
The secondary dial tone is turned off when the next number after the digit string is pressed. For example, if 8 were the digit string and a person dialed 8 555-0145, the secondary dial tone would be turned off when the 5 key is pressed.
Examples
The following example enables a secondary dial tone when a Cisco IP phone users press the 9 button to get an outside line:
Router(config)# telephony-serviceRouter(config-telephony-service)# secondary-dialtone 9Related Commands
service local-directory
To enable the availability of the local directory service on IP phones served by the Cisco CallManager Express (Cisco CME) router, use the service local-directory command in telephony-service configuration mode. To disable the local directory display on IP phones, use the no form of this command.
service local-directory [authenticate]
no service local-directory [authenticate]
Syntax Description
Defaults
Local directory service is available on IP phones.
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
Use this command with Cisco IOS Telephony Services V2.1, Cisco CME 3.0, or a later version.
Examples
The following example specifies that the directory service should not be available on the IP phones served by the Cisco CME router:
Router(config)# telephony-serviceRouter(config-telephony-service)# no service local-directoryRelated Commands
show ephone
To display information about registered Cisco IP phones, use the show ephone command in privileged EXEC mode.
show ephone [mac-address | phone-type]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
Significant fields in the output from this command are described in Table 1.
The following sample output shows general information for registered phones:
Router# show ephoneephone-1 Mac:0003.E3E7.F627 TCP socket:[2] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0IP:10.0.0.2 51671 Telecaster 7940 keepalive 28 max_line 2button 1: dn 1 number 4444 CM Fallback IDLEephone-2 Mac:0030.94C3.F43A TCP socket:[1] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0IP:10.0.0.3 50094 Telecaster 7960 keepalive 28 max_line 6button 1: dn 3 number 5555 CM Fallback IDLEephone-3 Mac:0003.6B40.99DA TCP socket:[3] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0IP:10.2.168.200 51879 Telecaster 7960 keepalive 28 max_line 6button 1: dn 2 number 3333 CM Fallback IDLEThe following sample output shows general information for the phone with the MAC address 0003.E3E7.F627:
Router# show ephone 0003.E3E7.F627ephone-1 Mac:0003.E3E7.F627 TCP socket:[2] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0IP:20.0.0.2 51671 Telecaster 7940 keepalive 28 max_line 2button 1: dn 1 number 4444 CM Fallback IDLEActive Call on DN 1:3001 10.0.0.51 31808 to 1.2.159.100 22708Tx Pkts 452 bytes 41584 Rx Pkts 452 bytes 41584 Lost 0Jitter 0 Latency 0The following sample output shows information for a phone that has two Cisco IP Phone 7914 Expansion Modules attached. The output shows this module as a subsidiary type in addition to the main 7960 type for the phone itself. Subtype 3 means that one Cisco IP Phone 7914 Expansion Module is attached to the main Cisco IP Phone 7960, and subtype 4 means that two are attached.
Router# show ephone 7914ephone-2 Mac:0007.0EA6.39F8 TCP socket:[2] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0IP:1.2.205.206 49278 Telecaster 7960 sub=4 keepalive 2723 max_line 34button 1: dn 21 number 60021 CH1 IDLEbutton 2: dn 22 number 60022 CH1 IDLEbutton 7: dn 11 number 60011 CH1 IDLE monitor-ringbutton 8: dn 12 number 60012 CH1 IDLE monitor-ringbutton 9: dn 13 number 60013 CH1 IDLE monitor-ringbutton 10: dn 14 number 60014 CH1 IDLE monitor-ringbutton 11: dn 15 number 60015 CH1 IDLE monitor-ringbutton 12: dn 16 number 60016 CH1 IDLE monitor-ringbutton 13: dn 17 number 60017 CH1 IDLE monitor-ringbutton 14: dn 18 number 60018 CH1 IDLE monitor-ringbutton 15: dn 19 number 60019 CH1 IDLE monitor-ringbutton 16: dn 20 number 60020 CH1 IDLE monitor-ringbutton 17: dn 39 number 60039 CH1 IDLE CH2 IDLE monitor-ringbutton 18: dn 40 number 60040 CH1 IDLE CH2 IDLE monitor-ringbutton 19: dn 23 number 60023 CH1 IDLE monitor-ringbutton 20: dn 24 number 60024 CH1 IDLE monitor-ringbutton 21: dn 25 number 60025 CH1 IDLE monitor-ringbutton 22: dn 26 number 60026 CH1 IDLE monitor-ringbutton 23: dn 27 number 60027 CH1 IDLE monitor-ringbutton 24: dn 28 number 60028 CH1 IDLE monitor-ringbutton 25: dn 29 number 60029 CH1 IDLE monitor-ringbutton 26: dn 30 number 60030 CH1 IDLE monitor-ringbutton 27: dn 31 number 60031 CH1 IDLE CH2 IDLE monitor-ringbutton 28: dn 32 number 60032 CH1 IDLE CH2 IDLE monitor-ringbutton 29: dn 33 number 60033 CH1 IDLE CH2 IDLE monitor-ringbutton 30: dn 34 number 60034 CH1 IDLE CH2 IDLE monitor-ringbutton 31: dn 35 number 60035 CH1 IDLE CH2 IDLE monitor-ringbutton 32: dn 36 number 60036 CH1 IDLE CH2 IDLE monitor-ringbutton 33: dn 37 number 60037 CH1 IDLE CH2 IDLE monitor-ringbutton 34: dn 38 number 60038 CH1 IDLE CH2 IDLE monitor-ringThe following sample output shows a phone that has a paging-dn and has received a page:
Router# show ephone 7910ephone-2 Mac:0087.0E76.B93C TCP socket:[4] activeLine:0 REGISTEREDmediaActive:1 offhook:0 ringing:0 reset:0 reset_sent:0 paging 1 debug:0IP:10.50.50.20 49231 Telecaster 7910 keepalive 112 max_line 2 dual-linebutton 1:dn 3 number 95021 CH1 IDLEpaging-dn 25Table 1 describes significant fields in the output.
Related Commands
show ephone-hunt
To display ephone-hunt configuration information, use the show ephone-hunt command in privileged EXEC mode.
show ephone-hunt [tag | summary]
Syntax Description
tag
The hunt-tag number configured with the ephone-hunt command. Range is from 1 to 10.
summary
Displays brief information regarding individual extension numbers.
Command Modes
Privileged EXEC
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
The show ephone-hunt and show ephone-hunt summary command display peer and sequential configuration information. The show ephone-hunt tag command outputs data regarding a specific hunt-tag configuration created by the ephone-hunt command. The show ephone-hunt and show ephone-hunt command provide expanded information regarding extension (list of numbers) and pilot numbers.
Examples
Table 2 describes significant fields in the output.
The following example provides output from the show ephone-hunt command with neither an argument nor a keyword:
Router# show ephone-huntGroup 1type: peerpilot number: 5000, peer-tag 20031; expanded-number 4085255000, peer-tag 20032list of numbers:5001, aux-number A5000A000, # peers 2, peer-tag:dn-tag [ 20030:36, 20029:1]5002, aux-number A5000A001, # peers 2, peer-tag:dn-tag [ 20034:37, 20033:2]5003, aux-number A5000A002, # peers 2, peer-tag:dn-tag [ 20036:38, 20035:3]5004, aux-number A5000A003, # peers 2, peer-tag:dn-tag [ 20038:39, 20037:4]5005, aux-number A5000A004, # peers 2, peer-tag:dn-tag [ 20040:40, 20039:5]final number: 5006preference: 0timeout: 180hops: 2E.164 register: yesGroup 2type: sequentialpilot number: 6000, peer-tag 20043list of numbers:5005, aux-number A6000A100, # peers 2, peer-tag:dn-tag [ 20042:40, 20041:5]5004, aux-number A6000A101, # peers 2, peer-tag:dn-tag [ 20045:39, 20044:4]5003, aux-number A6000A102, # peers 2, peer-tag:dn-tag [ 20047:38, 20046:3]5002, aux-number A6000A103, # peers 2, peer-tag:dn-tag [ 20049:37, 20048:2]5001, aux-number A6000A104, # peers 2, peer-tag:dn-tag [ 20051:36, 20050:1]final number: 5007preference: 5timeout: 3E.164 register: noThe following example provides output from the show ephone-hunt command for a specific hunt-tag configured with the ephone-hunt command:
Router# show ephone-hunt 2Group 2type: sequentialpilot number: 6000, peer-tag 20043list of numbers:5005, aux-number A6000A100, # peers 2, peer-tag:dn-tag [ 20042:40, 20041:5]5004, aux-number A6000A101, # peers 2, peer-tag:dn-tag [ 20045:39, 20044:4]5003, aux-number A6000A102, # peers 2, peer-tag:dn-tag [ 20047:38, 20046:3]5002, aux-number A6000A103, # peers 2, peer-tag:dn-tag [ 20049:37, 20048:2]5001, aux-number A6000A104, # peers 2, peer-tag:dn-tag [ 20051:36, 20050:1]final number: 5007preference: 5timeout: 3E.164 register: noThe following example shows a summary output:
Router# show ephone-hunt summaryGroup 1type: peerpilot number: 5000list of numbers:50015002500350045005final number: 5006preference: 0timeout: 180hops: 2E.164 register: yesGroup 2type: sequentialpilot number: 6000list of numbers:50055004500350025001final number: 5007preference: 5timeout: 3E.164 register: no
Related Commands
show ephone cfa
To display status and information on the registered phones that have call-forward-all set on one or more of their extensions (ephone-dns), use the show ephone cfa command in privileged EXEC mode.
show ephone cfa
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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.
Examples
The following is sample output from the show ephone cfa command.
Router# show ephone cfaephone-1 Mac:0007.0EA6.353A TCP socket:[2] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0IP:1.2.205.205 52491 Telecaster 7960 keepalive 14 max_line 6button 1: dn 11 number 60011 cfa 60022 CH1 IDLEbutton 2: dn 17 number 60017 cfa 60021 CH1 IDLETable 1 describes significant fields in this output.
Related Commands
show ephone dn
To display phone information for specified dn-tag or for all dn-tags, use the show ephone dn command in privileged EXEC mode.
show ephone dn [dn-tag]
Syntax Description
dn-tag
(Optional) Unique sequence number that is used during configuration to identify a particular extension (ephone-dn).
Command Modes
Privileged EXEC
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
Use this command to identify the phone on which a particular dn-tag has been assigned.
Examples
The following is sample output from the show ephone dn command.
Router# show ephone dn 2Tag 2, Normal or Intercom dnephone 2, mac-address 000A.3D7C.5323, line 1Table 1 describes significant fields in this output.
Related Commands
show ephone dnd
To display information on the registered phones that have do-not-disturb set on one or more of their extensions (ephone-dns), use the show ephone dnd command in privileged EXEC mode.
show ephone dnd
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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.
Examples
The following is sample output from the show ephone dnd command.
Router# show ephone dndephone-1 Mac:0007.0EA6.353A TCP socket:[1] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0IP:1.2.205.205 52486 Telecaster 7960 keepalive 2729 max_line 6 DnDbutton 1: dn 11 number 60011 CH1 IDLETable 1 describes significant fields in this output.
Related Commands
show ephone login
To display the login states of all local IP phones, use the show ephone login command in privileged EXEC mode.
show ephone login
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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
The show ephone login command displays whether an ephone has a personal identification number (PIN) and whether its owner has logged in.
Examples
The following is sample output from the show ephone login command. It shows that a PIN is enabled for ephone 1 and that its owner has not logged in. The other phones do not have PINs associated with them.
Router# show ephone loginephone 1 Pin enabled:TRUE Logged-in:FALSEephone 2 Pin enabled:FALSEephone 3 Pin enabled:FALSEephone 4 Pin enabled:FALSEephone 5 Pin enabled:FALSEephone 6 Pin enabled:FALSEephone 7 Pin enabled:FALSEephone 8 Pin enabled:FALSEephone 9 Pin enabled:FALSETable 3 describes significant fields in this output.
Related Commands
show ephone offhook
To display information and packet counts for the phones that are currently off hook, use the show ephone offhook command in privileged EXEC mode.
show ephone offhook
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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.
Examples
The following sample output is displayed when no phone is off hook:
Router# show ephone offhookNo ephone in specified type/condition.The following sample output displays information for a phone that is off hook:
Router# show ephone offhookephone-5 Mac:000A.8A2C.8C6E TCP socket:[20] activeLine:1 REGISTEREDmediaActive:0 offhook:1 ringing:0 reset:0 reset_sent:0 paging 0 debug:0IP:10.22.84.71 51228 Telecaster 7960 keepalive 43218 max_line 6button 1:dn 9 number 59943 CH1 SIEZE silent-ringbutton 2:dn 10 number 59943 CH1 IDLEbutton 3:dn 42 number A4400 auto dial A4500 CH1 IDLEbutton 4:dn 96 number 69943 auto dial 95259943 CH1 IDLEbutton 5:dn 75 number 49943 auto dial 49943 CH1 IDLEspeed dial 1:57514 marketingActive Call on DN 9 chan 1 :59943 0.0.0.0 0 to 0.0.0.0 2000 via 172.30.151.1G711Ulaw64k 160 bytes vadTx Pkts 0 bytes 0 Rx Pkts 0 bytes 0 Lost 0Jitter 0 Latency 0 callingDn -1 calledDn -1Username:user1 Password:newuserThe following sample output displays information for a phone that has just completed a call:
Router# show ephone offhookephone-5 Mac:000A.8A2C.8C6E TCP socket:[20] activeLine:1 REGISTEREDmediaActive:1 offhook:1 ringing:0 reset:0 reset_sent:0 paging 0 debug:0IP:10.22.84.71 51228 Telecaster 7960 keepalive 43224 max_line 6button 1:dn 9 number 59943 CH1 CONNECTED silent-ringbutton 2:dn 10 number 59943 CH1 IDLEbutton 3:dn 42 number A4400 auto dial A4500 CH1 IDLEbutton 4:dn 96 number 69943 auto dial 95259943 CH1 IDLEbutton 5:dn 75 number 49943 auto dial 49943 CH1 IDLEspeed dial 1:57514 marketingActive Call on DN 9 chan 1 :59943 10.23.84.71 22926 to 172.30.131.129 2000 via 172.30.151.1G711Ulaw64k 160 bytes no vadTx Pkts 0 bytes 0 Rx Pkts 0 bytes 0 Lost 0Jitter 0 Latency 0 callingDn -1 calledDn -1 (media path callID 19288 srcCallID 19289)Username:user1 Password:newuserSignificant fields in the output from this command are described in Table 1.
Related Commands
show ephone overlay
To display information for the registered phones that have overlay ephone-dns associated with them, use the show ephone overlay in privileged EXEC mode.
show ephone overlay
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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.
Examples
The following is sample output from the show ephone overlay command.
Router# show ephone overlayephone-1 Mac:0007.0EA6.353A TCP socket:[1] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0IP:10.2.225.205 52486 Telecaster 7960 keepalive 2771 max_line 6button 1: dn 11 number 60011 CH1 IDLE overlaybutton 2: dn 17 number 60017 CH1 IDLE overlaybutton 3: dn 24 number 60024 CH1 IDLE overlaybutton 4: dn 30 number 60030 CH1 IDLE overlaybutton 5: dn 36 number 60036 CH1 IDLE CH2 IDLE overlaybutton 6: dn 39 number 60039 CH1 IDLE CH2 IDLE overlayoverlay 1: 11(60011) 12(60012) 13(60013) 14(60014) 15(60015) 16(60016)overlay 2: 17(60017) 18(60018) 19(60019) 20(60020) 21(60021) 22(60022)overlay 3: 23(60023) 24(60024) 25(60025) 26(60026) 27(60027) 28(60028)overlay 4: 29(60029) 30(60030) 31(60031) 32(60032) 33(60033) 34(60034)overlay 5: 35(60035) 36(60036) 37(60037)overlay 6: 38(60038) 39(60039) 40(60040)Table 1 describes significant fields in this output. Table 4 describes a field that is not in that table.
Table 4 show ephone overlay Field Descriptions
overlay number
Displays the contents of an overlay set, including each dn-tag and its associated extension number.
Related Commands
show ephone phone-load
To display information about the phone firmware that is loaded on registered phones, use the show ephone phone-load command in privileged EXEC mode.
show ephone phone-load
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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.
Examples
The following is sample output from the show ephone phone-load command.
Router# show ephone phone-loadDeviceName CurrentPhoneload PreviousPhoneload LastReset=====================================================================SEP0002B9AFC49F 3.2(2.14) 3.2(2.14) TCP-timeoutSEP003094C2D0B0 3.2(2.14) 3.2(2.14) TCP-timeoutSEP000C30F03707 3.2(2.14) 3.2(2.14) TCP-timeoutSEP003094C2999F 3.2(2.14) 3.2(2.14) TCP-timeoutSEP000A8A2C8C6E 3.2(2.14) 3.2(2.14) InitializedSEP0002B9AFBB4D 3.2(2.14) 3.2(2.14) TCP-timeoutSEP00075078627F 3.2(2.14) 3.2(2.14) TCP-timeoutSEP0002FD659E59 3.2(2.14) 3.2(2.14) TCP-timeoutSEP00024BCCD626 3.2(2.14) CM-closed-TCPSEP0008215F88C1 3.2(2.14) 3.2(2.14) TCP-timeoutSEP000C30F0390C 3.2(2.14) 3.2(2.14) TCP-timeoutSEP003094C30143 3.2(2.14) 3.2(2.14) TCP-timeoutTable 5 describes significant fields in this output.
Related Commands
show ephone registered
To display the status of registered phones, use the show ephone registered command in privileged EXEC mode.
show ephone registered
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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.
Examples
The following is sample output from the show ephone registered command.
Router# show ephone registeredephone-2 Mac:000A.8A5C.5961 TCP socket:[1] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0IP:192.168.0.50 50349 Telecaster 7940 keepalive 23738 max_line 2button 1: dn 2 number 91450 CH1 IDLE CH2 IDLETable 1 describes significant fields in this output.
Related Commands
show ephone remote
To display nonlocal phones (phones with no Address Resolution Protocol, or ARP, entry), use the show ephone remote command in privileged EXEC mode.
show ephone remote
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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
Phones without ARP entries are suspected not to be on the local area network (LAN). Use the show ephone remote command to identify phones without ARP entries that might have operational issues.
Examples
The following is sample output that identifies ephone 2 as not having an ARP entry:
Router# show ephone remoteephone-2 Mac:0185.047C.993E TCP socket:[4] activeLine:0 REGISTEREDmediaActive:1 offhook:0 ringing:0 reset:0 reset_sent:0 paging 1 debug:0IP:10.50.50.20 49231 Telecaster 7910 keepalive 112 max_line 2 dual-linebutton 1:dn 3 number 95021 CH1 IDLEpaging-dn 25Table 1 describes significant fields in this output.
Related Commands
show ephone ringing
To display information on phones that are ringing, use the show ephone ringing command in privileged EXEC mode.
show ephone ringing
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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.
Examples
The following is sample output from the show ephone ringing command.
Router# show ephone ringingephone-1 Mac:0005.5E37.8090 TCP socket:[1] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:1 reset:0 reset_sent:0 paging 0 debug:0IP:10.50.50.10 49329 Telecaster 7960 keepalive 17602 max_line 6button 1:dn 1 number 95011 CH1 RINGING CH2 IDLEbutton 2:dn 2 number 95012 CH1 IDLETable 1 describes significant fields in this output.
Related Commands
show ephone summary
To display brief information about Cisco IP phones, use the show ephone summary command in privileged EXEC mode.
show ephone summary
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following sample output displays brief information for phones in a Cisco CallManager Express system:
Router# show ephone summaryephone-1 Mac:0003.E3E7.F627 TCP socket:[2] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0IP:20.0.0.2 Telecaster 7940 keepalive 30 1:1 CM Fallbackephone-2 Mac:0030.94C3.F43A TCP socket:[1] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0IP:20.0.0.3 Telecaster 7960 keepalive 30 1:3 CM Fallbackephone-3 Mac:0003.6B40.99DA TCP socket:[3] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0IP:1.2.168.200 Telecaster 7960 keepalive 30 1:2 CM FallbackMax Conferences 4 with 0 activeTable 1 describes significant fields in this output.
Related Commands
show ephone tapiclients
To display status of ephone Telephony Application Programming Interface (TAPI) clients, use the show ephone tapiclients command in privileged EXEC mode.
show ephone tapiclients
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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.
Examples
The following is sample output from the show ephone tapiclients command.
Router# show ephone tapiclientsephone-4 Mac:0007.0EA6.39F8 TCP socket:[2] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0IP:192.168.1.18 50291 Telecaster 7960 sub=3 keepalive 728 max_line 20button 1:dn 6 number 1004 CH1 IDLE CH2 IDLEbutton 2:dn 1 number 1000 CH1 IDLE sharedbutton 3:dn 2 number 1000 CH1 IDLE sharedbutton 7:dn 3 number 1001 CH1 IDLE CH2 IDLE monitor-ring sharedbutton 8:dn 4 number 1002 CH1 IDLE CH2 IDLE monitor-ring sharedbutton 9:dn 5 number 1003 CH1 IDLE CH2 IDLE monitor-ringbutton 10:dn 91 number A00 auto dial A01 CH1 IDLEspeed dial 1:2000 PAGE-STAFFspeed dial 2:2001 HUNT-STAFFpaging-dn 90Username:userB Password:ge30qeTapi client informationUsername:userB status:REGISTERED Socket :[5]Tapi Client IP address: 192.168.1.5 Port:2295Table 1 describes significant fields in this output.
Related Commands
show ephone telephone-number
To display information for the phone associated with a specified number, use the show ephone telephone-number command in privileged EXEC mode.
show ephone telephone-number number
Syntax Description
Command Modes
Privileged EXEC
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
Use this command to find the phone on which a particular telephone number appears.
Examples
The following is sample output from the show ephone telephone-number command.
Router# show ephone telephone-number 91400DP tag: 0, primaryTag 1, Normal or Intercom dnephone 1, mac-address 000A.0E51.19F0, line 1Table 1 describes significant fields in this output.
Related Commands
show ephone unregistered
To display information about unregistered phones, use the show ephone unregistered command in privileged EXEC mode.
show ephone unregistered
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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
There are two ways that an ephone can become unregistered. The first way is when an ephone is listed in the running configuration but no physical device has registered for that ephone. The second way is when an unknown device has registered at some time since the last router reboot but has since unregistered.
Examples
The following is sample output from the show ephone unregistered command.
Router# show ephone unregisteredephone-1 Mac:0007.0E81.10F0 TCP socket:[-1] activeLine:0 UNREGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0IP:0.0.0.0 0 Unknown 0 keepalive 0 max_line 0Table 1 describes significant fields in this output.
Related Commands
show ephone-dn
To display status and information or call statistics for one or all extensions (ephone-dns) in a Cisco CallManager Express (Cisco CME) system, use the show ephone-dn command in privileged EXEC mode.
show ephone-dn [dn-tag] [statistics]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
Table 6 describes significant fields in the output from this command.
The following sample output displays status and information for all ephone-dns:
Router# show ephone-dn50/0/1 CH1 DOWNEFXS 50/0/1 Slot is 50, Sub-unit is 0, Port is 1Type of VoicePort is EFXSOperation State is UPAdministrative State is UPNo Interface Down FailureDescription is not setNoise Regeneration is enabledNon Linear Processing is enabledNon Linear Mute is disabledNon Linear Threshold is -21 dBMusic On Hold Threshold is Set to -38 dBmIn Gain is Set to 0 dBOut Attenuation is Set to 0 dBEcho Cancellation is enabledEcho Cancellation NLP mute is disabledEcho Cancellation NLP threshold is -21 dBEcho Cancel Coverage is set to 8 msPlayout-delay Mode is set to adaptivePlayout-delay Nominal is set to 60 msPlayout-delay Maximum is set to 200 msPlayout-delay Minimum mode is set to default, value 40 msPlayout-delay Fax is set to 300 msConnection Mode is normalConnection Number is not setInitial Time Out is set to 10 sInterdigit Time Out is set to 10 sCall Disconnect Time Out is set to 60 sRinging Time Out is set to 180 sWait Release Time Out is set to 30 sCompanding Type is u-lawRegion Tone is set for USStation name None, Station number 91400Caller ID Info Follows:Standard BELLCORETranslation profile (Incoming):Translation profile (Outgoing):Digit Duration Timing is set to 100 ms50/0/2 CH1 IDLE CH2 IDLEEFXS 50/0/2 Slot is 50, Sub-unit is 0, Port is 2Type of VoicePort is EFXSOperation State is DORMANTAdministrative State is UPNo Interface Down FailureDescription is not setNoise Regeneration is enabledNon Linear Processing is enabledNon Linear Mute is disabledNon Linear Threshold is -21 dBMusic On Hold Threshold is Set to -38 dBmIn Gain is Set to 0 dBOut Attenuation is Set to 0 dBEcho Cancellation is enabledEcho Cancellation NLP mute is disabledEcho Cancellation NLP threshold is -21 dBEcho Cancel Coverage is set to 8 msPlayout-delay Mode is set to adaptivePlayout-delay Nominal is set to 60 msPlayout-delay Maximum is set to 200 msPlayout-delay Minimum mode is set to default, value 40 msPlayout-delay Fax is set to 300 msConnection Mode is normalConnection Number is not setInitial Time Out is set to 10 sInterdigit Time Out is set to 10 sCall Disconnect Time Out is set to 60 sRinging Time Out is set to 180 sWait Release Time Out is set to 30 sCompanding Type is u-lawRegion Tone is set for USStation name None, Station number 91450Caller ID Info Follows:Standard BELLCORETranslation profile (Incoming):Translation profile (Outgoing):Digit Duration Timing is set to 100 msThe following sample output displays voice quality statistics for the ephone-dn with dn-tag 2:
Router# show ephone-dn 2 statisticsDN 2 chan 1 incoming 0 answered 0 outgoing 2 answered 0 busy 0Far-end disconnect at: connect 0 alert 0 hold 0 ring 0Last 64 far-end disconnect cause codes28 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0local phone on-hookDN 2 chan 1 (91450) voice quality statistics for last callCall Ref 2 called callingTotal Tx Pkts 0 bytes 0 Rx Pkts 0 bytes 0 Lost 0Final Jitter 0 Latency 0 Lost 0Signal Level to phone 0 (-78 dB) peak 0 (-78 dB)Packets counted by router 0Table 6 describes significant fields in the output from this command.
The following sample output displays statistics for all extensions (ephone-dns) in the Cisco CME system. There are two ephone-dns (DN1 and DN3) in this example.
Router# show ephone-dn statisticsTotal Calls 103Stats may appear to be inconsistent for conference or shared line casesDN 1 chan 1 incoming 36 answered 21 outgoing 60 answered 30 busy 6Far-end disconnect at:connect 29 alert 18 hold 7 ring 15Last 64 far-end disconnect cause codes17 17 17 17 17 17 16 16 16 16 16 16 16 16 16 1616 16 16 16 65 16 65 65 65 65 16 65 65 65 16 1616 16 16 16 16 16 16 16 16 16 16 16 16 65 47 6547 47 16 16 16 16 16 16 16 16 16 16 16 16 16 16local phone on-hookDN 1 chan 1 (95011) voice quality statistics for last callCall Ref 103 called 91500 calling 95011Total Tx Pkts 0 bytes 0 Rx Pkts 0 bytes 0 Lost 0Final Jitter 30 Latency 0 Lost 0Signal Level to phone 0 (-78 dB) peak 0 (-78 dB)Packets counted by router 0DN 1 chan 2 incoming 0 answered 0 outgoing 1 answered 0 busy 0Far-end disconnect at:connect 0 alert 0 hold 0 ring 0Last 64 far-end disconnect cause codes0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0local phone on-hookDN 1 chan 2 (95011) voice quality statistics for last callCall Ref 86 called callingTotal Tx Pkts 0 bytes 0 Rx Pkts 0 bytes 0 Lost 0Final Jitter 0 Latency 0 Lost 0Signal Level to phone 0 (-78 dB) peak 0 (-78 dB)Packets counted by router 0DN 3 chan 1 incoming 0 answered 0 outgoing 1 answered 1 busy 0Far-end disconnect at:connect 0 alert 0 hold 0 ring 0Last 64 far-end disconnect cause codes0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0DN 3 chan 1 (95021) voice quality statistics for current callCall Ref 102 called 94011 calling 95021Current Tx Pkts 241 bytes 3133 Rx Pkts 3304 bytes 515023 Lost 0Jitter 30 Latency 0Worst Jitter 30 Worst Latency 0Signal Level to phone 201 (-39 dB) peak 5628 (-12 dB)Packets counted by router 3305Table 6 describes significant fields in the output from this command.
Table 6 show ephone-dn Field Descriptions
Administrative State
Administrative (configured) state of the voice port.
alert
The number of calls that were disconnected by the far-end device when the local IP phone was in the call alerting state (for example, because the far-end phone rang but was not answered and the far-end system decided to drop the call rather than let the phone ring for too long).
answered (incoming)
The number of incoming calls that were actually answered (the phone goes off hook when ringing).
answered (outgoing)
The number of outgoing call attempts that were answered by the far-end.
busy
The number of outgoing call attempts that got a busy response.
Call Disconnect Time Out
Not applicable to the Cisco IP phone.
called, calling
Extension numbers of called and calling parties.
Caller ID Info Follows
Information about the caller ID.
Call Ref
A unique per-call identifier used by the SCCP protocol. The Call Ref values are assigned sequentially within the Cisco CME-SCCP interface, so this value also indicates the total number of SCCP calls since the router was last rebooted.
chan
Channel number of an ephone-dn.
CODEC
Codec type.
Companding Type
Not applicable to the Cisco IP phone.
connect
The number of calls that were disconnected by the far-end device when the local IP phone was in the call connected state.
Connection Mode
Not applicable to the Cisco IP phone.
Connection Number
Not applicable to the Cisco IP phone.
Description
Not applicable to the Cisco IP phone.
Digit Duration Timing
Not applicable to the Cisco IP phone.
DN STATE
Ephone-dn dn-tag number and state of the phone line associated with an extension.
Echo Cancellation...
Not applicable to the Cisco IP phone.
Echo Cancel Coverage
Not applicable to the Cisco IP phone.
EFXS
Voice port type.
Far-end disconnect at...
See connect, alert, hold, and ring.
Final Jitter
The final voice packet receive jitter reported by the IP phone at the end of the call.
hold
The number of calls that were disconnected by the far-end device when the local IP phone was in the call hold state (for example, if the caller was left on hold for too long and got tired of waiting).
incoming
The number of incoming calls presented (the phone rings).
In Gain
Not applicable to the Cisco IP phone.
Initial Time Out
Amount of time the system waits for an initial input digit from the caller.
Interdigit Time Out
Amount of time the system waits for a subsequent input digit from the caller.
Last 64 far-end disconnect cause codes
See Table 7.
Latency
The final voice packet receive latency reported by the IP phone at the end of the call.
Lost
Number of lost packets.
Music On Hold Threshold
Not applicable to the Cisco IP phone.
No Interface Down Failure
State of the interface.
Noise Regeneration
Not applicable to the Cisco IP phone.
Non Linear...
Not applicable to the Cisco IP phone.
Operation State
Operational state of the voice port.
Out Attenuation
Not applicable to the Cisco IP phone.
outgoing
The number of outgoing call attempts.
Playout-delay Maximum
Not applicable to the Cisco IP phone.
Playout-delay...
Not applicable to the Cisco IP phone.
Port
Port number for the interface associated with the voice interface card.
Region Tone
Not applicable to the Cisco IP phone.
ring
The number of calls that were disconnected by the far-end device when the local IP phone was in the ringing state (for example, if the call was not answered and the caller hung up).
Ringing Time Out
Duration, in seconds, for which ringing to continue if a call is not answered. Set with the timeouts ringing command.
Rx Pkts, bytes
Number of packets and bytes received during the current or last call.
Signal Level to phone, peak
For G.711 calls only, this parameter indicates the most recent voice signal level in the voice IP packets sent from the router to the IP phone. This parameter is only valid for VoIP or PSTN G.711 calls to the IP phones. This parameter is not valid for calls between local IP phones, or calls that use codecs other than G.711. The peak field indicates the peak signal level seen during the entire call.
Slot
Slot used in the voice interface card for this port.
Station name
Station name.
Station number
Station number.
Sub-unit
Subunit used in the voice interface card for this port.
Tx Pkts, bytes
Number of packets and bytes transmitted during the current call or last call.
Type of VoicePort
Voice port type.
VAD
Voice activity detection.
Voice card specific info
Information specific to the voice card.
VPM STATE
State indication for the VPM software component.
VTSP STATE
State indication for the VTSP software component.
Wait Release Time Out
Time that a voice port stays in the call-failure state while the router sends a busy tone, reorder tone, or out-of-service tone to the port.
Table 7 lists the PSTN cause codes that can be sent as an ISDN cause information element (IE) and the corresponding SIP event for each. These are the far-end disconnect cause codes listed in the output for the show ephone-dn statistics command.
Related Commands
show ephone-dn callback
To display information about pending callbacks in a Cisco CallManager Express (Cisco CME) system, use the show ephone-dn callback command in privileged EXEC mode.
show ephone-dn callback
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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.
Examples
The following sample output shows a callback placed by ephone-dn 1 against ephone-dn 3. Ephone-dn 3 has its channel 1 on hold and has just seized dial tone on its channel 2.
Router# show ephone-dn callbackDN 3 (95021) CallBack pending to DN 1 (95021) for ephone-1 age 7 secondsState for DN 3 is CH1 HOLD CH2 SIEZEThe following sample output shows a callback placed by ephone-dn 1 against ephone-dn 3. Ephone-dn 3 has a call in progress on channel 1.
Router# show ephone-dn callbackDN 3 (95021) CallBack pending to DN 1 (95021) for ephone-1 age 8 secondsState for DN 3 is CH1 CONNECTEDSignificant fields in the output from this command are described in Table 8.
Related Commands
show ephone-dn
Displays status and information or call statistics for one ephone-dn or all ephone-dns in a Cisco CME system.
show ephone-dn loopback
To display information about loopback ephone-dns that have been created in a Cisco CallManager Express (Cisco CME) system, use the show ephone-dn loopback command in privileged EXEC mode.
show ephone-dn loopback
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example displays information for a loopback using ephone-dn 21 and ephone-dn 22:
Router# show ephone-dn loopbackLOOPBACK DN status (min 21, max 22):DN 21 51... Loopback to DN 22 CH1 IDLECallingDn -1 CalledDn -1 Called Calling G711Ulaw64kStrip NONE, Forward 2, prefix 10 retry 10 Media 0.0.0.0 0callID 0 srcCallID 0 ssrc 0 vector 0DN 22 11... Loopback to DN 21 CH1 IDLECallingDn -1 CalledDn -1 Called Calling G711Ulaw64kStrip NONE, Forward 2, prefix 50 retry 10 Media 0.0.0.0 0callID 0 srcCallID 0 ssrc 0 vector 0Significant fields in the output from this command are described in Table 9, in alphabetical order.
Related Commands
show ephone-dn summary
To display brief information about Cisco IP phone extensions (ephone-dns), use the show ephone-dn summary command in privileged EXEC mode.
show ephone-dn summary
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
Significant fields in the output from this command are described in Table 10, in alphabetical order.
Router# show ephone-dn summaryPORT DN STATE CODEC VAD VTSP STATE VPM STATE======== ========== ======== === ===================== =========50/0/1 DOWN - - - EFXS_ONHOOK50/0/2 DOWN - - - EFXS_ONHOOK50/0/3 DOWN - - - EFXS_ONHOOK50/0/4 INVALID - - - EFXS_INIT50/0/5 INVALID - - - EFXS_INIT50/0/6 INVALID - - - EFXS_INIT
Related Commands
show ephone-dn
Displays status and information or call statistics for one ephone-dn or all ephone-dns in a Cisco CME system.
show fb-its-log
To display information about the Cisco CallManager Express (Cisco CME) XML API configuration, statistics on XML API queries, and the XML API event logs, use the show fb-its-log command in privileged EXEC mode.
show fb-its-log [summary]
Syntax Description
summary
(Optional) Displays only the XML API configuration and the statistics for queries and logs, and not the logs themselves.
Command Modes
Privileged EXEC
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.
Examples
The following is sample output from the show fb-its-log summary command:
Router# show fb-its-log summaryIP Keyswitch Logs:(21:11:30 UTC Wed Jul 1 2003)---- Current Period ---extension events:4device events: 3overwrites:0missed:0deleted:0---- History ------overwrites:0missed:0deleted:8---- Threads ----max xml threads:2current thread:0read in process:FALSETable 11 describes the significant fields in this output.
The following is sample output from the show fb-its-log command:
Router# show fb-its-logIP Keyswitch Logs:(21:11:30 UTC Wed Jul 1 2003)---- Current Period ---extension events:4device events: 3overwrites:0missed:0deleted:0---- History ------overwrites:0missed:0deleted:8---- Threads ----max xml threads:2cuttent thread:0read in process:FALSE1 Time:21:11:06 UTC Wed Jul 1 2003Event:DN 1[2001] goes down2 Time:21:11:06 UTC Wed Jul 1 2003Event:DN 2[2003] goes down3 Time:21:11:06 UTC Wed Jul 1 2003Event:IP Phone 1[SEP003094C3F96A] unregistered4 Time:21:11:06 UTC Wed Jul 1 2003Event:IP Phone 1[SEP003094C3F96A] unregistered5 Time:21:11:54 UTC Wed Jul 2003Event:IP Phone 1[SEP003094C3F96A] registered6 Time:21:11:57 UTC Wed Jul 2003Event:DN 1[2001] goes up7 Time:21:11:57 UTC Wed Jul 2003Event:DN 2[2003] goes upTable 11 describes the significant fields in this output.
Related Commands
log table
Sets the maximum size of the table used to capture phone events used for the Cisco CME XML API.
show telephony-service admin
To display information about the Cisco CallManager Express (Cisco CME) system administrator, use the show telephony-service admin command in user EXEC or privileged EXEC mode.
show telephony-service admin
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC and privileged EXEC
Command History
Examples
The following is sample output from this command:
Router# show telephony-service adminadmin_username Adminadmin_password wordedit DN through Web: enabled.edit TIME through Web: enabled.Table 12 describes the significant fields in this output.
Related Commands
dn-webedit
Enables adding of extensions (ephone-dns) through the web interface.
time-webedit
Enables setting of time through the web interface.
show telephony-service all
To display detailed configuration for phones, voice ports, and dial peers in a Cisco CallManager Express (Cisco CME) system, use the show telephony-service all command in user EXEC or privileged EXEC mode.
show telephony-service all
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC and privileged EXEC
Command History
Examples
The following is sample output from this command:
Router# show telephony-service allCONFIG======ip source-address 10.0.0.1 port 2000max-ephones 24max-dn 24dialplan-pattern 1 408734....voicemail 11111transfer-pattern 510734....keepalive 30ephone-dn 1number 5001huntstopephone-dn 2number 5002huntstopcall-forward noan 5001 timeout 8ephone-dn 3number 5003huntstopephone 1mac-address 0030.94C3.37CBtype 0button 1:1speed-dial 1 5002speed-dial 2 5003cos 0!ephone 2mac-address 0030.94C3.F96Atype 0button 1:2 2:3 3:4speed-dial 1 5004speed-dial 2 5001cos 0!voice-port 50/0/1station-id number 5001!voice-port 50/0/2station-id number 5002timeout ringing 8!dial-peer voice 20025 potsdestination-pattern 5001huntstopport 50/0/1dial-peer voice 20026 potsdestination-pattern 5002huntstopcall-forward noan 5001port 50/0/2dial-peer voice 20027 potsdestination-pattern 5003huntstopport 50/0/3Table 13 describes significant fields in this output, in alphabetical order.
Related Commands
show telephony-service dial-peer
To display dial peer information for extensions in a Cisco CallManager Express (Cisco CME) system, use the show telephony-service dial-peer command in user EXEC or privileged EXEC mode.
show telephony-service dial-peer
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC and privileged EXEC
Command History
Usage Guidelines
The dial peers cannot be edited manually. To change values associated with dial peers, use the ephone-dn command.
Examples
The following is sample output from this command:
Router# show telephony-service dial-peerdial-peer voice 20025 potsdestination-pattern 5001huntstopport 50/0/1dial-peer voice 20026 potsdestination-pattern 5002huntstopcall-forward noan 5001port 50/0/2dial-peer voice 20027 potsdestination-pattern 5003huntstopport 50/0/3dial-peer voice 20028 potsdestination-pattern 5004huntstopport 50/0/4Table 14 describes significant fields in this output, in alphabetical order.
Related Commands
show telephony-service directory-entry
To display the entries made using the directory entry command, use the show telephony-service directory-entry command in user EXEC or privileged EXEC mode.
show telephony-service directory-entry
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC and privileged EXEC
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
This command lists directory entries that are made using the directory entry command but does not list entries that are made using the name and number commands in ephone-dn configuration mode.
Examples
The following is sample output from this command:
Router# show telephony-service directory-entrydirectory entry 1 4085550123 name Smith, JohnTable 15 describes significant fields in this output, in alphabetical order.
Related Commands
show telephony-service ephone
To display configuration for the Cisco IP phones, use the show telephony-service ephone command in user EXEC or privileged EXEC mode.
show telephony-service ephone
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC or privileged EXEC
Command History
Examples
The following is sample output from this command:
Router# show telephony-service ephoneephone 1mac-address 0030.94C3.37CBtype 0button 1:1speed-dial 1 5002speed-dial 2 5003cos 0!ephone 2mac-address 0030.94C3.F96Atype 0button 1:2 2:3 3:4speed-dial 1 5004speed-dial 2 5001cos 0!Table 16 describes significant fields in this output.
Related Commands
show telephony-service ephone-dn
To display information about extensions (ephone-dns) in a Cisco CallManager Express (Cisco CME) system, use the show telephony-service ephone-dn command in user EXEC or privileged EXEC mode.
show telephony-service ephone-dn
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC or privileged EXEC
Command History
Examples
The following is sample output from this command:
Router# show telephony-service ephone-dnephone-dn 1number 5001huntstopephone-dn 2number 5002huntstopcall-forward noan 5001 timeout 8ephone-dn 3number 5003huntstopephone-dn 4number 5004huntstopTable 17 describes significant fields in this output, in alphabetical order.
Related Commands
show telephony-service tftp-bindings
To display the current configuration files accessible to IP phones, use the show telephony-service tftp-bindings command in user EXEC or privileged EXEC mode.
show telephony-service tftp-bindings
Syntax Description
This command has no arguments or keywords.
Command Modes
User or privileged EXEC
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 with Cisco IOS Telephony Services V2.1, Cisco CallManager Express 3.0, or a later version.
This command provides a list of configuration files that are accessible to IP phones using TFTP, including the dictionary, language, and tone configuration files that are associated with the ISO-3166 codes that have been selected using the user-locale and network-locale commands.
Examples
The following is sample output from the show telephony-service tftp-bindings command when the ISO-3166 code for Germany has been selected for both language and tones:
Router(config)# show telephony-service tftp-bindings
tftp-server system:/its/SEPDEFAULT.cnf
tftp-server system:/its/SEPDEFAULT.cnf alias SEPDefault.cnf
tftp-server system:/its/XMLDefault.cnf.xml alias XMLDefault.cnf.xml
tftp-server system:/its/ATADefault.cnf.xml
tftp-server system:/its/XMLDefault7960.cnf.xml alias SEP00036B54BB15.cnf.xml
tftp-server system:/its/germany/7960-font.xml alias German_Germany/7960-font.xml
tftp-server system:/its/germany/7960-dictionary.xml alias German_Germany/7960-dictionary.xml
tftp-server system:/its/germany/7960-kate.xml alias German_Germany/7960-kate.xml
tftp-server system:/its/germany/SCCP-dictionary.xml alias German_Germany/SCCP-dictionary.xml
tftp-server system:/its/germany/7960-tones.xml alias Germany/7960-tones.xml
Related Commands
show telephony-service voice-port
To display configurations of virtual voice ports in a Cisco CallManager Express (Cisco CME) system, use the show telephony-service voice-port command in user EXEC or privileged EXEC mode.
show telephony-service voice-port
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC or privileged EXEC
Command History
Usage Guidelines
This command displays virtual voice-port configurations for a Cisco CME system. Each ephone-dn corresponds to a virtual voice port. For example, the ephone-dn with dn-tag 7 corresponds to virtual voice port 50/0/7. The virtual voice port provides the telephone line associated with the Cisco IP phone extension (ephone-dn).
Examples
The following is sample output from this command:
Router# show telephony-service voice-portvoice-port 50/0/1station-id number 5001!voice-port 50/0/2station-id number 5002timeout ringing 8!voice-port 50/0/3station-id number 5003!voice-port 50/0/4station-id number 5004!Table 18 describes significant fields in this output, in alphabetical order.
Related Commands
speed-dial
To create speed-dial definitions for a Cisco IP phone or analog phone that uses an analog telephone adaptor (ATA) in a Cisco CallManager Express (Cisco CME) system, use the speed-dial command in ephone configuration mode. To disable a speed-dial definition, use the no form of this command.
speed-dial speed-tag digit-string [label label-text]
no speed-dial speed-tag
Syntax Description
Defaults
No speed-dial definitions are created.
Command Modes
Ephone configuration
Command History
Usage Guidelines
The speed-tag argument in this command is a unique identifier for a speed-dial definition on the phone that is being configured. On Cisco IP phones, speed-dial definitions are assigned to available extension buttons that have not been assigned to extensions. Speed-dial definitions are assigned in the order of their identifier numbers.
For example, if you define speed-dial 1, it is assigned to the first phone button that is available after the buttons that are assigned to extensions. If you used two buttons for extensions on a phone, speed-dial 1 is assigned to the third physical button on the phone. When you define speed-dial 2, it is assigned to the fourth physical button on the phone.
For IP phones, speed-dial numbers can be assigned by the administrator using the digit-string argument and can be locked if the digit-string argument begins with a plus sign (+). Locked numbers cannot be changed at the phone. Speed-dial instances without speed-dial numbers (those defined with only a pound sign) and speed-dial instances with unlocked digit-string arguments can be changed by users at their IP phones.
If more speed-dial definitions are created than are supported by the IP phone setup, the extra speed-dial configurations are ignored.
Changes made to speed-dial buttons are saved in the router NVRAM configuration after a timer-based delay.
Analog phone users who use a Cisco ATA-186 or Cisco ATA-188 to connect to Cisco CME systems use a different method to access speed-dial numbers. Instead of pressing a speed-dial button, phone users with ATA devices press the asterisk (star) key and a speed-tag number (speed-dial identifier) to dial a speed-dial number. For instance, a phone user with a Cisco ATA-186 would press *1 to dial the number that has been programmed as speed-dial 1 on that ephone. Phones with ATA devices are limited to a maximum of nine speed-dial numbers that must be programmed by the system administrator. The numbers cannot be programmed from the phone. With phones that use ATA devices, system administrators must be sure to tell phone users when speed-dial numbers have been programmed for their phones.
This command must be followed by a quick reboot of the phone using the restart command.
Examples
The following example sets speed-dial button 2 to dial the head office at extension 5001 and locks the setting so that the phone user cannot change it at the phone:
Router(config)# ephone 23Router(config-ephone)# speed-dial 2 +5001 label "Head Office"Related Commands
system message
To set a text message for display on idle Cisco IP Phone 7940s and Cisco IP Phone 7960s in a Cisco CallManager Express (Cisco CME) system, use the system message command in telephony-service configuration mode. To return to the default, use the no form of this command.
system message text-message
no system message
Syntax Description
text-message
Alphanumeric string of up to approximately 30 characters to display when the phone is idle.
Defaults
The message "Cisco CallManager Express" is displayed.
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
The number of characters that can be displayed is not fixed because IP phones typically use a proportional (as opposed to a fixed-width) font. There is room for approximately 30 alphanumeric characters.
The display message is refreshed with a new message after any of the following events occurs:
•
•
•
Examples
The following example sets the message "ABC Company" to display instead of "Cisco CallManager Express" on idle Cisco IP Phone 7940s and Cisco IP Phone 7960s:
Router(config)# telephony-serviceRouter(config-telephony-service)# system message ABC CompanyRelated Commands
telephony-service
To enter telephony-service configuration mode to configure a Cisco CallManager Express (Cisco CME) system, use the telephony-service command in global configuration mode. To remove an existing Cisco CME configuration, use the no form of this command.
telephony-service [setup]
no telephony-service
Syntax Description
setup
(Optional) Uses the Cisco CME setup tool for interactive creation of a Cisco CME system configuration.
Defaults
No Cisco CME configuration is present.
Command Modes
Global configuration
Command History
Usage Guidelines
The telephony-service command is used to enter telephony-service configuration mode. Use telephony-service configuration mode to set systemwide parameters in a Cisco CME system.
The setup keyword starts the Cisco CME setup tool, which presents a question-and-answer dialog to gather information that is used to automatically configure a Cisco CME system. When you do not use the setup keyword, telephony-service configuration submode is opened and you can manually configure the Cisco CME system using command-line interface (CLI) commands.
The setup CLI keyword is not stored in the router NVRAM.
If you attempt to use the setup option for a system that already has a nonempty telephony-service configuration, the command is rejected. To use the setup option after an existing telephony-service configuration has been created, first remove the existing configuration using the no telephony-service command.
Table 19 shows a sample dialog with the Cisco CME setup tool and explains possible responses to the Cisco CME setup tool prompts.
Table 19 Cisco CME Setup Tool DIalog Prompts
Do you want to setup DHCP service for your IP phones? [yes/no]:
If you respond yes, you see the following prompts:
IP network for telephony-service DHCP Pool:
Subnet mask for DHCP network :
TFTP Server IP address (Option 150) :
Default Router for DHCP Pool :
•
•
Do you want to start telephony-service setup? [yes/no]:
•
•
Enter the IP source address for Cisco CallManager Express:
Enter the Skinny Port for Cisco CallManager Express: [2000]:
IP address on which the router provides Cisco CME services, usually the default gateway for the IP subnet that you are using for the IP phones, and the port for Skinny Client Control Protocol (SCCP) messages.
How many IP phones do you want to configure : [0]:
Enter the maximum number of IP phones that this Cisco CME system will support. This number can be increased later, to the maximum allowed for this version and your router.
Note
Do you want dual-line extensions assigned to phones? [yes for dual-line / no for single-line]:
•
•
What language do you want on IP phones?
0 English
1 French
2 German
3 Russian
4 Spanish
5 Italian
6 Dutch
7 Norwegian
8 Portuguese
9 Danish
10 Swedish
[0]:
Language for IP phone displays, selected from the list. The default is 0, English.
Which Call Progress tone set do you want on IP phones :
0 United States
1 France
2 Germany
3 Russia
4 Spain
5 Italy
6 Netherlands
7 Norway
8 Portugal
9 UK
10 Denmark
11 Switzerland
12 Sweden
13 Austria
14 Canada
[0]:
Locale for the tone set used to indicate call status or progress, selected from the list. The default is 0, United States.
What is the first extension number you want to configure :[0]:
Lowest number to use for extension numbers. Each additional extension that is created receives a number that is incremented by one. Extension numbers must be compatible with your telephone number plan and with PSTN numbering requirements if you use Direct Inward Dialing (DID) service.
Do you have Direct-Inward-Dial service for all your phones? [yes/no]:
•
•
If you answer yes to the previous question, you see the following prompt:
Enter the full E.164 number for the first phone:
Complete ten-digit telephone number, including area code, that corresponds to the first extension number.
Do you want to forward calls to a voice message service? [yes/no]:
•
•
If you answer yes to the previous question, you see the following prompt:
Enter the extension or pilot number of the voice message service:
Voice message service pilot number. This step can be ignored during the setup dialog and manually configured later.
Call forward No Answer Timeout: [18]:
Timeout, in seconds, after which to forward calls to voice mail if they are not answered. Default is 18.
Do you wish to change any of the above information? [yes/no]:
•
•
Examples
The following example enters telephony-service configuration mode for manual setup of a Cisco CME system and defines the maximum number of phones for that system as 12:
Router(config)# telephony-serviceRouter(config-telephony-service)# max-ephones 12The following example starts the Cisco CME setup tool:
Router(config)# telephony-service setuptime-format
To select a 12-hour clock or a 24-hour clock for the time display format on Cisco IP phones in a Cisco CallManager Express (Cisco CME) system, use the time-format command in telephony-service configuration mode. To return to the default, use the no form of this command.
time-format {12 | 24}
no time-format
Syntax Description
Defaults
12
Command Modes
Telephony-service configuration
Command History
Examples
The following example selects a 24-hour clock for the time display on Cisco IP phones:
Router(config)# telephony-serviceRouter(config-telephony-service)# time-format 24Related Commands
date-format
Selects a format to display the date on Cisco IP phones.
telephony-service
Enters telephony-service configuration mode.
timeout (ephone-hunt)
To define the number of seconds after which a call that is not answered is redirected to the next number in a Cisco CallManager Express (Cisco CME) ephone-hunt-group list, use the timeout command in ephone-hunt configuration mode. To return to the default timeout, use the no form of this command.
timeout seconds
no timeout seconds
Syntax Description
Defaults
180 seconds
Command Modes
Ephone-hunt 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.
Examples
The following example defines a no-answer timeout of 10 seconds for hunt group 25:
Router(config)# ephone-hunt 25 sequentialRouter(config-ephone-hunt)# timeout 10Related Commands
timeouts busy
To set the amount of time after which a call is disconnected from a busy signal, use the timeouts busy command in telephony-service configuration mode. To return to the default value, use the no form of this command.
timeouts busy seconds
no timeouts busy
Syntax Description
seconds
Number of seconds after connection before a call is disconnected from a busy signal. Range is from 0 to 30 seconds. Default is 10.
Defaults
10 seconds
Command Modes
Telephony-service configuration
Command History
Examples
The following example sets a busy timeout of 10 seconds:
Router(config)# telephony-serviceRouter(config-telephony-service)# timeouts busy 10Related Commands
timeouts interdigit (telephony-service)
To set the interdigit timeout value for all Cisco IP phones in a Cisco CallManager Express (Cisco CME) system, use the timeouts interdigit command in telephony-service configuration mode. To return to the default value, use the no form of this command.
timeouts interdigit seconds
no timeouts interdigit
Syntax Description
seconds
Interdigit timeout duration for Cisco IP phones, in seconds. Range is from 2 to 120. Default is 10.
Defaults
10 seconds
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
The interdigit timeout timer is activated when the caller enters a digit and is restarted each time the caller enters subsequent digits until the destination address is identified. This command specifies how long, in seconds, the system waits after a caller enters an initial digit or a subsequent digit of a dialed string. If the configured timeout value is exceeded before the destination address is identified, a tone sounds and the call is terminated. The default is 10 seconds.
To disable the timeouts interdigit timer, set the seconds value to zero.
Examples
The following example sets the interdigit timeout value to 5 seconds for all Cisco IP phones:
Router(config)# telephony-serviceRouter(config-telephony-service)# timeouts interdigit 5In this example, the 5 seconds also provides the elapsed time after which an incompletely dialed number times out. For example, if you dial nine digits (408555013) instead of the required ten digits (4085550134), you hear a busy tone after 5 "timeout" seconds.
Related Commands
telephony-service
Enters telephony-service configuration mode.
timeouts interdigit (voice-port)
Configures the interdigit timeout value for a specified voice port.
timeouts ringing (telephony-service)
To set the timeout value for ringing in a Cisco CallManager Express (Cisco CME) system, use the timeouts ringing command in telephony-service configuration mode. To reset the timeout value to the default value, use the no form of this command.
timeouts ringing seconds
no timeouts ringing
Syntax Description
seconds
Duration, in seconds, for which the Cisco CME system allows ringing to continue if a call is not answered. Range is from 5 to 60000. Default is 180.
Defaults
180 seconds
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.
Examples
The following example allows incoming calls to ring for 600 seconds:
Router(config)# telephony-serviceRouter(config-telephony-service)# timeouts ringing 600Related Commands
time-webedit (telephony-service)
To enable the system administrator to set time on the Cisco CallManager Express (Cisco CME) router through the web interface, use the time-webedit command in telephony-service configuration mode. To disable this feature, use the no form of this command.
time-webedit
no time-webedit
Syntax Description
This command has no arguments or keywords.
Defaults
Time-setting through the web interface is disabled.
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
The time-webedit command allows a local administrator of the Cisco CME router to change and set time through the web-based graphical user interface (GUI).
Note
Examples
The following example enables web editing of time:
Router(config)# telephony-serviceRouter(config-telephony-service)# time-webeditRelated Commands
dn-webedit
Enables adding of directory numbers through a web interface.
telephony-service
Enters telephony-service configuration mode.
transfer-mode
To specify the type of call transfer for an individual IP phone extension that uses the ITU-T H.450.2 standard, use the transfer-mode command in ephone-dn configuration mode. To remove this specification, use the no form of this command.
transfer-mode {blind | consult}
no transfer-mode
Syntax Description
blind
Transfers calls without consultation using a single phone line.
consult
Transfers calls with consultation using a second phone line, if available.
Defaults
The ephone-dn uses the transfer-system value that was set systemwide.
Command Modes
Ephone-dn 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
This command specifies the type of call transfer for an individual Cisco IP phone extension that is using the ITU-T H.450.2 protocol. It allows you to override the system default transfer-system setting (full-consult or full-blind) for that extension.
Call transfers that useH.450.2 can be blind or consultative. A blind transfer is one in which the transferring phone connects the caller to a destination extension before ringback begins. A consultative transfer is one in which the transferring party either connects the caller to a ringing phone (ringback heard) or speaks with the third party before connecting the caller to the third party.
You can specify blind or consultative transfer on a systemwide basis by using the transfer-system command. The systemwide setting can then be overridden for individual phone extensions by using the transfer-mode command. For example, in a Cisco CallManager Express (Cisco CME) network that is set up for consultative transfer, a specific extension with an auto-attendant that automatically transfers incoming calls to specific extension numbers can be set to use blind transfer, because auto-attendants do not use consultative transfer.
Use this command with Cisco IOS Telephony Services V2.1, Cisco CallManager Express 3.0, or a later version.
Examples
The following example sets blind mode for call transfers from extension 21354:
Router(config)# ephone-dn 21354Router(config-ephone-dn)# transfer-mode blindRelated Commands
transfer-pattern (telephony-service)
To allow transfer of telephone calls from Cisco IP phones to phones other than Cisco IP phones, use the transfer-pattern command in telephony-service configuration mode. To disable these transfers, use the no form of this command.
transfer-pattern transfer-pattern [blind]
no transfer-pattern
Syntax Description
Defaults
Transfer of calls is enabled only to local Cisco IP phones.
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
This command allows you to transfer calls to "other" phones—that is, to non-IP phones and phones outside of your network. A call is then established between the transferred party and the new recipient. By default, all Cisco IP phone extension numbers are allowed as transfer targets.
The blind keyword is valid only for systems that use Cisco IOS Telephony Services V2.1, Cisco CallManager Express 3.0, or a later version and applies only to consultative transfers made using the H.450.2 standard. The blind keyword forces calls that are transferred to numbers that match the transfer pattern to be executed as blind or full-blind transfers, overriding any settings made using the transfer-system and transfer-mode commands.
When defining transfers to non-local numbers, it is important to note that transfer-pattern digit matching is performed before translation-rule operations. Therefore, you should specify in this command the digits actually entered by phone users before they are translated. For more information, see the "Translation Rules" section in Chapter 3, "Setting Up Phones in a Cisco CME System" in the Cisco CallManager Express 3.0 System Administration Guide.
Examples
The following example sets a transfer pattern:
Router(config)# telephony-serviceRouter(config-telephony-service)# transfer-pattern 55501..A maximum of 32 transfer patterns can be entered. In this example, 55501.. (the two periods are wildcards) permits transfers to any number in the range 555-0100 to 555-0199.
Related Commands
transfer-system
To specify the call transfer method for IP phone extensions that use the ITU-T H.450.2 standard, use the transfer-system command in telephony-service configuration mode. To disable the call transfer method, use the no form of this command.
transfer-system {blind | full-blind | full-consult | local-consult}
no transfer-system
Syntax Description
Defaults
blind
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 with Cisco IOS Telephony Services V2.1, Cisco CallManager Express 3.0, or a later version.
Call transfers that use the H.450.2 standard can be blind or consultative. A blind transfer is one in which the transferring extension connects the caller to a destination extension before ringback begins. A consultative transfer is one in which the transferring party either connects the caller to a ringing phone (ringback heard) or speaks with the third party before connecting the caller to the third party. When H.450.2 call transfer is selected using the full-blind or full-consult keyword, the router must be configured with a Tool Command Language (Tcl) script that supports the H.450.2 protocol. The Tcl script is loaded on the router using the call application voice command.
You can specify blind or consultative transfer on a systemwide basis using the transfer-system command. The systemwide setting can then be overridden for individual extensions using the transfer-mode command. For example, in a system that is set up for consultative transfer, a specific extension with an auto-attendant that automatically transfers incoming calls to specific extension numbers can be set to use blind transfer, because auto-attendants do not use consultative transfer.
Examples
The following example sets full consultation as the call transfer method:
Router(config)# telephony-serviceRouter(config-telephony-service)# transfer-system full-consultRelated Commands
translate (ephone-dn)
To apply a translation rule in order to manipulate the digits that are dialed by users of Cisco IP phones, use the translate command in ephone-dn configuration mode. To disable the translation rule, use the no form of this command.
translate {called | calling} translation-rule-tag
no translate {called | calling}
Syntax Description
Defaults
No translation rule is applied.
Command Modes
Ephone-dn configuration
Command History
Usage Guidelines
This command allows you to select a preconfigured translation rule to modify the number dialed by a specific extension (Cisco IP phone destination number, or ephone-dn). A translation rule is a general-purpose digit-manipulation mechanism that performs operations such as automatically adding telephone area and prefix codes to dialed numbers. The translation rules are applied to the voice ports created by the ephone-dn. The called keyword translates the called number, and the calling keyword translates the calling number.
The translation rule mechanism inserts a delay into the dialing process when digits are entered that do not explicitly match any of the defined translation rules. This delay is set by the interdigit timeout. The translation-rule mechanism uses the delay to ensure that it has acquired all of the digits from the phone user before making a final decision that there is no translation-rule match available (and therefore no translation operation to perform). To avoid this delay, it is recommended that you include a dummy translation rule to act as a pass-through rule for digit strings that do not require translation. For example, a rule like "^5 5" that maps a leading 5 digit into a 5 would be used to prevent the translation rule delay being applied to local extension numbers that started with a 5.
Note
Examples
The following example applies translation rule 20 to numbers called by extension 46839:
Router(config)# translation-rule 20Router(config-translate)# rule 0 1234 2345 abbreviatedRouter(config-translate)# exitRouter(config)# ephone-dn 1Router(config-ephone-dn)# number 46839Router(config-ephone-dn)# translate called 20Related Commands
ephone-dn
Enters ephone-dn configuration mode.
rule
Defines a translation rule.
translation-rule
Creates a translation identifier and enters translation-rule configuration mode.
type (ephone)
To define a phone type or to define one or two add-on phone modules for a Cisco IP phone, use the type command in ephone configuration mode. To remove a definition, use the no form of this command.
type phone-type [addon 1 module-type [2 module-type]]
no type phone-type [addon 1 module-type [2 module-type]]
Syntax Description
Defaults
No phone type or add-on module is defined.
Command Modes
Ephone configuration
Command History
Usage Guidelines
Use this command with Cisco IOS Telephony Services V2.1, Cisco CallManager Express 3.0, or a later version.
The following guidelines apply to this command:
•
•
•
The only types of phones that accept add-on modules are the Cisco IP Phone 7940 and the Cisco IP Phone 7960.
This command must be followed by a phone reboot using the reset command.
Examples
The following example defines the IP phone with phone-tag 10 as a Cisco IP Phone 7960 with two attached Cisco IP Phone 7914 Expansion Modules:
Router(config)# ephone 10Router(config-ephone)# type 7960 addon 1 7914 2 7914The following example defines the IP phone with phone-tag 4 as a Cisco ATA device:
Router(config)# ephone 4Router(config-ephone)# mac 1234.87655.234Router(config-ephone)# type ataRelated Commands
url (telephony-service)
To provision uniform resource locators (URLs) for Cisco IP phones connected to the Cisco CallManager Express router, use the url command in telephony-service configuration mode. To remove a URL association, use the no form of this command.
url {authentication | directories | information | messages | proxy-server | services} url
no url {authentication | directories | information | messages | proxy-server | services}
Syntax Description
Defaults
The router automatically uses the local directory service.
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
The Cisco IP Phone 7940 and Cisco IP Phone 7960 can support four URLs in association with the four programmable feature buttons on those IP phones: Directories, Information, Messages, and Services. The fifth button, Settings, is managed entirely by the phone. Operation of these services is determined by the Cisco IP phone capabilities and the content of the referenced URL.
The purpose of the url command is to provision the URLs through the configuration file supplied by the Cisco CallManager Express router to the Cisco IP phones during phone registration.
You can disable the local directory by specifying the string none instead of a URL with the directories keyword, as shown in the following example:
Router(config-telephony-service)# url directories none
Note
This command must be followed by a complete phone reboot using the reset command.
Examples
The following example provisions the Information, Directories, and Services buttons:
Router(config)# telephony-serviceRouter(config-telephony-service)# url information http://1.4.212.4/CCMUser/GetTelecasterHelpText.aspRouter(config-telephony-service)# url directories http://1.4.212.11/localdirectoryRouter(config-telephony-service)# url services http://1.4.212.4/CCMUser/123456/urltest.htmlThe Messages button is configured by the voicemail command. This button acts like a speed-dial key to retrieve messages from a specified telephone number.
Related Commands
url idle
To specify a file to display on an IP phone that is not in use, use the url idle command in telephony-service configuration mode. To disable display of the file, use the no form of this command.
url idle url idle-timeout seconds
no url idle
Syntax Description
url
Uniform resource locator as defined in RFC 2396.
idle-timeout seconds
Time interval between display refreshes, in seconds. Range is from 0 to 300.
Defaults
No file is specified for display on idle phones.
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 with Cisco IOS Telephony Services V2.1, Cisco Call Manager Express 3.0, or a later version.
The file that is displayed must be encoded in XML using the Cisco XML DTD. For more information about Cisco DTD formats, refer to Cisco IP Phone Services Application Development Notes.
This command must be followed by a complete phone reboot using the reset command.
Examples
The following example specifies that the file logo.xml should be displayed on IP phones when they are not being used and that the display should be refreshed every 12 seconds:
Router(config)# telephony-serviceRouter(config-telephony-service)# url idle http://mycompany.com/files/logo.xml idle-timeout 12Related Commands
user-locale
To set the language for displays on the Cisco IP Phone 7940 and Cisco IP Phone 7960, use the user-locale command in telephony-service configuration mode. To disable the selected setting, use the no form of this command.
user-locale language-code
no user-locale language-code
Syntax Description
language-code
The following ISO-3166 codes are valid entries:
•
•
•
•
•
•
•
•
•
•
•
Defaults
The default code is US (United States).
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
Use this command with Cisco IOS Telephony Services V2.1, Cisco CallManager Express 3.0, or a later version.
The show telephony-service tftp-bindings command displays the locale that has been set using this command. This locale is currently associated with the dictionary and language files.
This command must be followed by a complete phone reboot using the reset command.
Examples
The following example sets the IP phone display language to French:
Router(config)# telephony-serviceRouter(config-telephony-service)# user-locale FRRelated Commands
username (ephone)
To assign a Cisco CallManager Express (Cisco CME) login account username and password to a phone user so that the user can log in to a web-based graphical user interface (GUI), use the username command in ephone configuration mode. To disable a username and password, use the no form of this command.
username username [password password]
no username username
Syntax Description
username
Username of the local Cisco IP phone user. Default is Admin.
password password
(Optional) Enables a password for the Cisco IP phone user.
Defaults
The default username for the administrator is Admin.
Command Modes
Ephone configuration
Command History
Usage Guidelines
The login account allows a phone user to access a web-based GUI to view information and change some personal settings for the phone user's own phone only. A login account is also required for users of Telephony Application Programming Interface (TAPI)-aware PC applications, which can register with the Cisco CME router and exercise remote-control operation of Cisco IP phones.
Note
Examples
The following example shows how to set the username and password:
Router(config)# ephone 1Router(config-ephone)# username smith password 9golfRelated Commands
vm-device-id (ephone)
To define a voice-messaging identification string, use the vm-device-id command in ephone configuration mode. To disable this feature, use the no form of this command.
vm-device-id id-string
no vm-device-id
Syntax Description
Defaults
No voice-mail identification string is defined.
Command Modes
Ephone configuration
Command History
Usage Guidelines
Use this command to define a voice-messaging device ID string. A voice-messaging port registers with a device ID instead of a MAC address. To distinguish among different voice-messaging ports, the value of the voice-messaging device ID is used. The voice-messaging device ID is configured to a Cisco IP phone port, which maps to a corresponding voice-messaging port.
Examples
The following example shows how to set the voice-messaging device ID to CiscoUM-VI1:
Router(config) ephone 1Router(config-ephone) vm-device-id CiscoUM-VI1Related Commands
voicemail (telephony-service)
Configures the telephone number that is speed-dialed when the Messages button on a Cisco IP phone is pressed.
vm-integration
To enter voice-mail integration configuration mode and enable voice-mail integration with dual tone multifrequency (DTMF) and analog voice-mail systems, use the vm-integration command in global configuration mode. To disable voice-mail integration, use the no form of this command.
vm-integration
no vm-integration
Syntax Description
This command has no arguments or keywords.
Defaults
No voice-mail integration is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
The vm-integration command is used to enter voice-mail integration configuration mode. Use voice-mail integration configuration mode to integrate a Cisco CME system with an analog voice-mail system.
Examples
The following example shows how to enter the voice-mail integration configuration mode:
Router(config) vm-integrationRouter(config-vm-integration) pattern direct 2 CGN *Related Commands
voicemail (telephony-service)
To define the telephone number that is speed-dialed when the Messages button on a Cisco IP phone is pressed, use the voicemail command in telephony-service configuration mode. To disable the Messages button, use the no form of this command.
voicemail phone-number
no voicemail
Syntax Description
Defaults
No phone number is configured, and the Messages button is disabled.
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
This command configures the telephone number that is speed-dialed when the Messages button on a Cisco IP phone is pressed. The same telephone number is configured for voice messaging for all Cisco IP phones connected to the router.
Examples
The following example sets the phone number 914085550100 as the speed-dial number that is dialed to retrieve messages when the Messages button is pressed:
Router(config)# telephony-serviceRouter(config-telephony-service)# voicemail 914085550100Related Commands
telephony-service
Enters telephony-service configuration mode.
vm-device-id (ephone)
Defines the voice-mail ID string.
web admin customer
To define a username and password for a Cisco CallManager Express (Cisco CME) customer administrator, use the web admin customer command in telephony-service configuration mode. To disable a customer administrator login, use the no form of this command.
web admin customer name username {password string | secret {0 | 5} string}
no web admin customer
Syntax Description
Defaults
A customer administrator named Customer with no password is defined.
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 with Cisco IOS Telephony Services V2.1, Cisco CallManager Express 3.0, or a later version.
Examples
The following example defines a customer administrator named user22 whose password is pw567890:
Router(config)# telephony-serviceRouter(config-telephony-service)# web admin customer name user22 password pw567890Related Commands
web admin system
To define a username and password for a Cisco CallManager Express (Cisco CME) system administrator, use the web admin system command in telephony-service configuration mode. To disable a system administrator login, use the no form of this command.
web admin system name username {password string | secret {0 | 5} string}
no web admin system
Syntax Description
Defaults
A system administrator named Admin with no password is defined.
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 with Cisco IOS Telephony Services V2.1, Cisco CallManager Express 3.0, or a later version.
Use the secret 0 keyword pair when entering a plain-text password string. This keyword pair instructs the system to encrypt the system administrator password with MD5. An encrypted version of the string is saved in the running configuration, as shown in the following example. The digit 5 that appears after the secret keyword in the running configuration indicates that the password that follows is shown in its encrypted version.
web admin system name jsmith secret 5 $1$TCyK$OU/NSQ/VtAU2ibHdi8UauExamples
The following example establishes a system administrator named user1 whose password will be encrypted in the running configuration:
Router(config)# telephony-serviceRouter(config-telephony-service)# web admin system name user1 secret 0 pw234567Related Commands
web customize load
To load and parse an eXtensible Markup Language (XML) file in router Flash memory to customize a Cisco CallManager Express GUI for a customer administrator, use the web customize load command in telephony-service configuration mode. To disable the customized GUI and use the system administrator GUI for the customer administrator, use the no form of this command.
web customize load filename
no web customize load
Syntax Description
Defaults
The standard system administrator GUI is used.
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 with Cisco IOS Telephony Services V2.1, Cisco CallManager Express 3.0, or a later version.
Examples
The following example specifies a file named cust_admin_gui.xml as the file that defines the GUI for Cisco CME customer administrators:
Router(config)# telephony-serviceRouter(config-telephony-service)# web customize load cust_admin_gui.xmlRelated Commands
xmlschema
To specify the URL for a Cisco CallManager Express (Cisco CME) XML API schema, use the xmlschema command in telephony-service configuration mode. To set the URL for the XML API schema to the default, use the no form of this command.
xmlschema schema-url
no xmlschema
Syntax Description
Defaults
srst-its.xsd
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.
Examples
The following example specifies a URL for an XML API schema:
Router(config)# telephony-serviceRouter(config-telephony-service)# xmlschema http://server2.example.com/schema/schema1.xsdRelated Commands
xmltest
To specify that the HTTP payload in XML API queries be interpreted as having form format, use the xmltest command in telephony-service configuration mode. To specify that the HTTP payload should be interpreted as plain text (no form) format, use the no form of this command.
xmltest
no xmltest
Syntax Description
This command has no arguments or keywords.
Defaults
Plain text (no form) format
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.
Examples
The following example specifies that the HTTP payload in XML API queries be interpreted as having form format:
Router(config)# telephony-serviceRouter(config-telephony-service)# xmltestRelated Commands
xmlthread
To set the maximum number of Cisco CallManager Express (Cisco CME) XML API queries, use the xmlthread command in telephony-service configuration mode. To set the maximum number of queries to the default, use the no form of this command.
xmlthread number
no xmlthread
Syntax Description
Defaults
number: 2
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.
Examples
The following example sets the maximum number of XML API queries to 5:
Router(config)# telephony-serviceRouter(config-telephony-service)# xmlthread 5Related Commands
Feedback