|
|
Table Of Contents
Cisco Unified CME Commands: sast1 trustpoint through show fb-its-log
sdspfarm conference mute-on mute-off
semi-attended enable (voice register template)
show ephone attempted-registrations
Cisco Unified CME Commands: sast1 trustpoint through show fb-its-log
Last Updated: September 11, 2007First Published: February 27, 2006
This chapter contains commands to configure and maintain Cisco Unified Communications Manager Express (formally known as Cisco Unified CallManager Express). The commands are presented in alphabetical order. Some commands required for configuring Cisco Unified Communications Manager Express (Cisco Unified CME) may be found in other Cisco IOS command references. Use the command reference master index or search online to find these commands.
sast1 trustpoint
To specify the name of the SAST1 trustpoint, use the sast1 trustpoint command in CTL-client configuration mode. To return to the default, use the no form of this command.
sast1 trustpoint label
no sast1
Syntax Description
Command Default
No SAST1 trustpoint name is specified
Command Modes
CTL-client configuration
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)T
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
This command is used with Cisco Unified CME phone authentication.
The sast1 trustpoint and sast2 trustpoint commands are used to set up the System Administrator Security Token (SAST) credentials, which are used to sign the CTL file. The SAST1 and SAST2 certificates must be different from each other, but to conserve memory either one of them can use the same certificate as Cisco Unified CME. The CTL file is always signed by SAST1 credentials. The SAST2 credentials are included in the CTL file so that if the SAST1 certificate is compromised, the CTL file can be signed by SAST2 to prevent the phones from being reset to their factory defaults.
Examples
The following example names sast1tp as the SAST1 trustpoint.
Router(config)# ctl-clientRouter(config-ctl-client)# server capf 10.2.2.2 trustpoint capftrustRouter(config-ctl-client)# server cme 10.2.2.3 trustpoint cmetpRouter(config-ctl-client)# server tftp 10.2.2.4 trustpoint tftptpRouter(config-ctl-client)# sast1 trustpoint sast1tpRouter(config-ctl-client)# sast2 trustpoint sast2tpRouter(config-ctl-client)# regenerateRelated Commands
sast2 trustpoint
To specify the name of the SAST2 trustpoint, use the sast2 trustpoint command in CTL-client configuration mode. To return to the default, use the no form of this command.
sast2 trustpoint label
no sast2
Syntax Description
Command Default
No SAST2 trustpoint name is specified.
Command Modes
CTL-client configuration
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)T
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
This command is used with Cisco Unified CME phone authentication.
The sast1 trustpoint and sast2 trustpoint commands are used to set up the System Administrator Security Token (SAST) credentials, which are used to sign the CTL file. The SAST1 and SAST2 certificates must be different from each other, but to conserve memory either one of them can use the same certificate as Cisco CME. The CTL file is always signed by SAST1 credentials. The SAST2 credentials are included in the CTL file so that if the SAST1 certificate is compromised, the CTL file can be signed by SAST2 to prevent the phones from being reset to their factory defaults.
Examples
The following example names sast2tp as the SAST2 trustpoint.
Router(config)# ctl-clientRouter(config-ctl-client)# server capf 10.2.2.2 trustpoint capftrustRouter(config-ctl-client)# server cme 10.2.2.3 trustpoint cmetpRouter(config-ctl-client)# server tftp 10.2.2.4 trustpoint tftptpRouter(config-ctl-client)# sast1 trustpoint sast1tpRouter(config-ctl-client)# sast2 trustpoint sast2tpRouter(config-ctl-client)# regenerateRelated Commands
sdspfarm conference mute-on mute-off
To define mute-on and mute-off DTMF digits for use during conferencing, use the sdspfarm conference mute-on mute-off command in telephony-service configuration mode. To disable the mute-on and mute-off digits, use the no form of this command.
sdspfarm conference mute-on mute-on-digits mute-off mute-off-digits
no sdspfarm conference mute-on mute-on-digits mute-off mute-off-digits
Syntax Description
Command Default
No mute-on or mute-off digits are defined.
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
You must define mute-on and mute-off digits to mute or unmute your phone using the keypad during a conference. The mute-on digits and mute-off digits can be the same or different. You can mute and unmute your phone using the phone's mute button also. You must unmute the phone in the same way that you muted it, either with the keypad or the mute button.
Examples
The following example configures #5 as the buttons to press to mute and unmute the phone during a conference:
Router(config-telephony)# sdspfarm conference mute-on #5 mute-off #5sdspfarm tag
To permit a digital-signal-processor (DSP) farm to be to registered to Cisco CallManager Express (Cisco CME) and associate it with a Skinny Client Control Protocol (SCCP) client interface's MAC address, use the sdspfarm tag command in telephony-service configuration mode. To delete a tag generated by the sdspfarm tag command, use the no form of this command.
sdspfarm tag number device-name
no sdspfarm tag number device-name
Syntax Description
number
Declares a numeric name for a DSP farm. Number from 1 to 5.
device-name
The MAC address of the SCCP client interface that is preceded by the Message Transfer Part (MTP).
Defaults
No default behavior or values
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
DSP farms are sets of DSP resources used for conferencing and transcoding only. DSP farms do not include voice termination resources. Use the show interface command to find the MAC address of the SCCP client interface.
Examples
The following example declares tag 1 as the MAC address of mac000a.8aea.ca80. The show interface command is used to obtain the MAC address.
Router# show interface FastEthernet 0/0...FastEthernet0/0 is up, line protocol is upHardware is AmdFE, address is 000a.8aea.ca80 (bia 000a.8aea.ca80)...Router(config)# telephony-serviceRouter(config-telephony)# sdspfarm tag 1 mac000a.8aea.ca80Related Commands
sdspfarm transcode sessions
To specify the maximum number of transcoding sessions allowed per Cisco CallManager Express (Cisco CME) router, use the sdspfarm transcode sessions command in telephony-service configuration mode. To return to the default transcode session of 0, use the no form of this command.
sdspfarm transcode sessions number
no sdspfarm transcode sessions number
Syntax Description
Defaults
The default is 0.
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
The transcoding is allowed between G.711 and G.729. A session consists of two transcode streams. To configure this information, you must know how many digital-signal-processor (DSP) farms are configured on the network module (NM) farms in your Cisco CME router. DSP farms are sets of DSP resources used for conferencing and transcoding only. DSP farms do not include voice termination resources. To learn how many DSP farms have been configured on your Cisco CME router, use the show sdspfarm command.
Examples
The following example sets the maximum number of transcoding sessions allowed on the Cisco CME router to 20:
Router(config)# telephony-serviceRouter(config-telephony)# sdspfarm transcode sessions 20Related Commands
sdspfarm units
To specify the maximum number of digital-signal-processor (DSP) farms that are allowed to be registered to the Skinny Client Control Protocol (SCCP) server, use the sdspfarm units command in telephony-service configuration mode. To set the number of DSP farms to the default value of 0, use the no form of this command.
sdspfarm units number
no sdspfarm units number
Syntax Description
Defaults
The default number is 0.
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
DSP farms are sets of DSP resources used for conferencing and transcoding only. DSP farms do not include voice termination resources.
Examples
The following example configures a Cisco CME router to register one DSP farm:
Router(config)# telephony-serviceRouter(config-telephony)# sdspfarm units 1Related Commands
sdspfarm unregister force
To remove all transcoding streams associated with active calls, use the sdspfarm unregister force command in telephony-service configuration mode. To deactivate the removal of transcoding streams, use the no form of this command.
sdspfarm unregister force
no sdspfarm unregister force
Syntax Description
This command has no arguments or keywords.
Defaults
The default is transcoding streams are not removed.
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
If any of the SCCP server's associated streams are functioning in active calls, the default response for the sdspfarm unregister force command is to reject them. If no stream is used in a call, all of the transcoding streams associated with the DSP farm will be released, and SCCP server can recycle those streams for other DSP farms.
Examples
The following example removes all transcoding streams for active calls.
Router(config)# telephony-serviceRouter(config-telephony)# sdspfarm unregister forceRelated Commands
secondary start
To specify the ephone hunt group agent to receive parked calls that are forwarded to the secondary pilot number, use the secondary start command in ephone-hunt configuration mode. To disable this setting, use the no form of this command.
secondary start [current | next | list-position]
no secondary start [current | next | list-position]
Syntax Description
Command Default
No default behavior or values
Command Modes
Ephone-hunt configuration
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)T
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
When a call that has been parked by a hunt group agent meets either of these conditions, the hunt group agent to receive the call can be specified with the secondary start command:
•
The call is recalled from call park to the hunt group secondary pilot number.
•
Examples
The following example specifies that the third hunt group member (3031) will receive calls that are recalled or forwarded to the secondary group hunt pilot number (3001) after the calls have been parked by an ephone-dn.
ephone-hunt 17 sequentialpilot 3000 secondary 3001list 3011, 3021, 3031timeout 10final 7600secondary start 3Related Commands
ephone-hunt
Defines an ephone hunt group and enters ephone-hunt configuration mode.
list
Creates a list of extensions that are members of an ephone hunt group
secondary-dialtone
To activate a secondary dial tone when a Cisco IP phone user dials a defined public switched telephone network (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 access prefix is pressed. For example, if 8 is the access prefix and a person dials 8 555-0145, the secondary dial tone is turned off when the digit 5 is pressed.
Examples
The following example enables a secondary dial tone when a Cisco IP phone users press the digit 9 to get an outside line:
Router(config)# telephony-serviceRouter(config-telephony)# secondary-dialtone 9Related Commands
secure-signaling trustpoint
To specify the name of the PKI trustpoint with the certificate to use for TLS handshakes with IP phones on TCP port 2443, use the secure-signaling trustpoint command in telephony-service configuration mode. To return to the default, use the no form of this command.
secure-signaling trustpoint label
no secure-signaling trustpoint
Syntax Description
Command Default
No trustpoint is specified.
Command Modes
Telephony-service configuration
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)T
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
This command is used with Cisco Unified CME phone authentication to name the trustpoint that enables handshaking between Cisco Unified CME and a phone to ensure secure SCCP signaling on TCP port 2443.
Examples
The following example names server25, the CAPF server, as the trustpoint to enable secure SCCP signaling:
Router(config)# telephony-serviceRouter(config-telephony)# device-security-mode authenticated
Router(config-telephony)# secure-signaling trustpoint server25
Router(config-telephony)# tftp-server-credentials trustpoint server12
Router(config-telephony)# load-cfg-file slot0:Ringlist.xml alias Ringlist.xml sign create
Router(config-telephony)# exit
semi-attended enable (voice register template)
To enable call transfer at the alert call stage for Cisco IP Phone 7940s, Cisco IP Phone 7940Gs, Cisco IP Phones 7960s, and Cisco IP Phone and 7960Gs, use the semi-attended enable command in the voice register template mode. To disable call transfer, use the no form of this command.
semi-attended enable
no semi-attended enable
Syntax Description
This command has no arguments or keywords.
Defaults
Call transfer at the alert call stage is disabled
Command Modes
Voice register template
Command History
Examples
The following example shows how to enable call transfer at the alter call stage:
Router(config)# voice register template 1Router(config-register-temp)# semi-attend enableRelated Commands
voice register template
Enters voice register template configuration mode and defines a template of common parameters for SIP phones.
server
To specify the IP address of a presence server for sending presence requests from internal watchers to external presence entities, use the server command in presence configuration mode. To remove the server, use the no form of this command.
server ip-address
no server
Syntax Description
Command Default
A remote presence server is not used.
Command Modes
Presence configuration
Command History
12.4(11)XJ
This command was introduced.
12.4(15)T
This command was integrated into Cisco IOS Release 12.4(15)T.
Usage Guidelines
This command specifies the IP address of a presence server that handles presence requests when the watcher and presence entity (presentity) are not colocated. The router acts as the presence server and processes all presence requests and status notifications when a watcher and presentity are both internal. If a subscription request is for an external presentity, the request is sent to the remote server specified by this command.
Examples
The following example shows a presence server with IP address 10.10.10.1:
Router(config)# presenceRouter(config-presence)# allow subscribeRouter(config-presence)# server 10.10.10.1Related Commands
server (CTL-client)
To enter trustpoint information for the CAPF server, Cisco Unified CME router, or TFTP server into the router configuration, use the server command in CTL-client configuration mode. To return to the default, use the no form of this command.
server {capf | cme | cme-tftp | tftp} ip-address trustpoint label
no server {capf | cme | cme-tftp | tftp} ip-address
Syntax Description
Command Default
Trustpoint information about the CAPF server, Cisco Unified CME router, or TFTP server is not present in the security configuration.
Command Modes
CTL-client configuration
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)T
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
This command is used with Cisco Unified CME phone authentication. Cisco IOS software stores credential information in a trustpoint. The trustpoint label in this command names the specified PKI trustpoint.
Note
Examples
The following example defines trustpoint names and IP addresses for the CAPF server, the Cisco Unified CME router, and the TFTP server:
Router(config)# ctl-clientRouter(config-ctl-client)# server capf 10.2.2.2 trustpoint capftrustRouter(config-ctl-client)# server cme 10.2.2.3 trustpoint cmetpRouter(config-ctl-client)# server tftp 10.2.2.4 trustpoint tftptpRouter(config-ctl-client)# sast1 trustpoint sast1tpRouter(config-ctl-client)# sast2 trustpoint sast2tpRouter(config-ctl-client)# regenerateserver-security-mode
To change the security mode of the Cisco Unified CME phone authentication server, use the server-security-mode command in telephony-service configuration mode. To return to the default, use the no form of this command.
server-security-mode {non-secure | secure}
no server-security-mode {non-secure | secure}
Syntax Description
Command Default
When the CTL file is initially generated, the mode is set to secure.
Command Modes
Telephony-service configuration
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)T
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
This command is used with Cisco Unified CME phone authentication.
This command has no effect until the CTL file is initially generated by the CTL client. When the CTL file is successfully generated, the CTL client automatically sets the server security mode to secure. You can toggle the mode thereafter.
This command must be followed by the regenerate command in CTL-client configuration mode, which regenerates the CTL file. This is necessary because if the security mode is non-secure, its credentials are zeroed out in the CTL file. If the security mode is secure, the CTL file contains the server's credentials.
Examples
The following example changes the mode of the server to non-secure.
telephony-serviceserver-security-mode non-secureRelated Commands
regenerate
Creates a new CTLFile.tlv file after changes to the CTL client configuration.
service directed-pickup
To enable directed pickup in a Cisco Unified CME system, use the service directed-pickup command in telephony-service configuration mode. To globally disable the directed pickup feature and change the action of the PickUp soft key on IP phones, use the no form of this command.
service directed-pickup
no service directed-pickup
Syntax Description
This command has no arguments or keywords.
Command Default
Directed pickup is enabled.
Command Modes
Telephony-service configuration
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)T
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
This command is enabled by default.
To globally disable directed call pickup for all phone users, use the no form of this command. Using the no form of the command also changes the behavior of the PickUp soft key on all IP phones so that a user pressing it invokes local group pickup rather than directed call pickup.
To selectively remove the directed pickup function from one or more ephones, use the features blocked command in ephone-template mode. The features blocked command removes the PickUp soft key from IP phones and blocks directed call pickup on analog phones. When you use the features blocked command, it becomes part of an ephone template that you apply to one or more ephones on which you want the specified features to not appear as soft keys.
Examples
The following example globally disables directed call pickup.
telephony-serviceno service directed-pickupRelated Commands
features blocked
Prevents one or more features from being used on one or more ephones.
telephony-service
Enters telephony-service configuration mode.
service dnis dir-lookup
To allow the display of names associated with called numbers for incoming calls on IP phones, use the service dnis dir-lookup command in telephony-service configuration mode. To deactivate directory lookup, use the no form of this command.
service dnis dir-lookup
no service dnis dir-lookup
Defaults
The default is directory service lookup is inactive.
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
The service dnis dir-lookup command provides a called number to the name-lookup service to support display of the name associated with the called number for incoming calls to IP phones. The display name is obtained from the Cisco CME system's list of Cisco CME directory names created using the directory entry command in the telephony-service configuration mode.
Called numbers can be displayed for overlaid ephone-dn and for ephone-dns that are not overlaid. Secondary line are supported.
To allow a single ephone-dn to receive calls for multiple different called numbers (with different names), you must use wildcard "." characters in the number field for the ephone-dn.
To use the service dnis dir-lookup command in conjunction with the ephone-hunt command, you can configure the ephone-hunt group to use a pilot number that contains wildcard "." characters. This allows the ephone-hunt group to receive calls from different numbers. Individual ephone-dns that are configured as members of the hunt group with the ephone-hunt list command must not have wildcard characters in their number fields.
If the service dnis dir-lookup command is used at the same time as the service dnis overlay command, the directory-lookup service takes precedence in resolving the name for the called number.
Examples
The following is an example of an overlaid ephone-dn configuration, where the service dnis dir-lookup command allows one of three directory entry names to be displayed on three IP phones when a call is placed to a number declared in the directory entry command.
telephony-serviceservice dnis dir-lookupdirectory entry 1 0001 name dept1directory entry 2 0002 name dept2directory entry 3 0003 name dept3ephone-dn 1number 0001ephone-dn 2number 0002ephone-dn 2number 0002ephone 1button 1o1,2,3ephone 2button 1o1,2,3ephone 3button 1o1,2,3The following is an example of an ephone-dn configuration in which the overlay function is not in use. There are three IP phones, each with two buttons. Button 1 receives calls from user1, user2, and user3; button 2 receives calls from user4, user5, and user6.
telephony-serviceservice dnis dir-lookupdirectory entry 1 5550001 name user1directory entry 2 5550002 name user2directory entry 3 5550003 name user3directory entry 4 5550010 name user4directory entry 5 5550011 name user5directory entry 6 5550012 name user6ephone-dn 1number 555000.ephone-dn 2number 5552001.ephone 1button 1:1button 2:2mac-address 1111.1111.1111ephone 2button 1:1button 2:2mac-address 2222.2222.2222The following is an example of a hunt-group configuration. There are three phones, each with two buttons, and each button is assigned two numbers. When a person calls 5550341, Cisco CME matches the hunt-group pilot secondary number (555....) and rings button 1 on one of the two phones and displays "user1." The selection of the phone is dependent on the ephone-hunt command settings. For more information about hunt groups, refer to the "Ephone Hunt Groups" section of the Cisco CallManager Express 3.3 System Administrator Guide.
telephony-serviceservice dnis dir-lookupmax-redirect 20directory entry 1 5550341 name user1directory entry 2 5550772 name user2directory entry 3 5550263 name user3directory entry 4 5550150 name user4ephone-dn 1number 1001ephone-dn 2number 1002ephone-dn 3number 1003ephone-dn 4number 1004ephone 1button 1o1,2button 2o3,4mac-address 1111.1111.1111ephone 2button 1o1,2button 2o3,4mac-address 2222.2222.2222ephone-hunt 1 peerpilot 1000 secondary 555....list 1001, 1002, 1003, 1004final 5556000hops 5preference 1timeout 20no-regThe following is an example of a secondary-line configuration. Ephone-dn 1 can accept calls from extension 1001 and from 5550000, 5550001, and 5550002.
telephony-serviceservice dnis dir-lookupdirectory entry 1 5550000 name doctor1directory entry 2 5550001 name doctor2directory entry 3 5550002 name doctor3ephone-dn 1number 1001 secondary 555000.ephone 1button 1:1mac-address 2222.2222.2222Related Commands
service dnis overlay
To allow incoming calls to an ephone-dn overlay to display called ephone-dn names, use the service dnis overlay command in telephony-service configuration mode. To deactivate the service dialed number identification service (DNIS) overlay, use the no form of this command.
service dnis overlay
no service dnis overlay
Defaults
The ephone-dn names in an ephone-dn overlay are not displayed on IP phones.
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
The service dnis overlay command allows phone users to determine which ephone-dn within an overlay set is being called. Up to ten ephone-dns are allowed per overlay set. When an incoming call is presented under a service dnis overlay command configuration, the phone displays the name of the individual ephone-dn according to the name command configured under the ephone-dn configuration mode. Note that for an ephone-dn name to be displayed on IP phones, you must first assign ephone-dn names with the name command in ephone-dn configuration mode.
The number of the first ephone-dn listed in the button command is the default display for all phones using the same set of overlaid ephone-dns. Calls to the first ephone-dn display the caller ID. Calls to the remaining ephone-dns display ephone-dn names. For example, if there are three phones with one overlay set containing five ephone-dns, the first ephone-dn's number listed is the default display for all three phones. A call to the first ephone-dn displays the caller ID on all phones until the call is picked up. When the call is answered by phone 1, the displays in phone 2 and phone 3 return to the default display. Calls to the last four ephone-dns display ephone-dn names.
If the service dnis overlay command is used at the same time as the service dnis dir-lookup command, the service dnis dir-lookup command takes precedence in determining the name to be displayed.
Examples
The following is an overlay configuration for two phones with button 1 assigned to pick up three 800 numbers from three ephone-dns that have been assigned names. The default display for button 1 is 18005550100. A call to 18005550100 displays the caller ID. Calls to 18005550001 and 18005550002 display "name1" and "name2," respectively.
telephony-serviceservice dnis overlayephone-dn 1name mainnumbernumber 18005550100ephone-dn 2name name1number 18005550001ephone-dn 3name name2number 18005550002ephone 1button 1o1,2,3ephone 2button 1o1,2,3Related Commands
name
Associates a name with a Cisco CME extension (ephone-dn).
service dnis dir-lookup
Allows directory entry lookup for the display of directory entry names on IP phones.
service dss
To enable DSS (Direct Station Select) in a Cisco Unified CME system, use the service dss command in telephony-service configuration mode. To globally disable the DSS feature, use the no form of this command.
service dss
no service dss
Syntax Description
This command has no arguments or keywords.
Command Default
DSS service is disabled.
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
This command enables phone users to quickly transfer calls to an extension selected by a speed-dial or monitor line button without having to press the Transfer button. If this command is enabled, a user can transfer a call when the call is in the connected state by simply pressing a speed-dial or monitor line button to select the transfer destination. The transfer action is automatically implied by CME if the service dss command is enabled.
This feature is supported only on phones on which monitor-line buttons for speed dial or speed-dial line buttons are configured.
Using the no form of the command changes the behavior of the speed-dial line button on all IP phones so that a user pressing a speed-dial button in the middle of a connected call will play out the speed-dial digits into the call without transferring the call. If the service dss command is disabled, the phone user must press the Transfer button before pressing the speed-dial line button or monitor line button to transfer the call.
For Cisco Unified CME 4.0 and earlier, the transfer-system full-consult dss command is used to select between blind transfers and consult transfers for the DSS case.
Examples
The following example globally enables directed call pickup.
telephony-serviceservice dssRelated 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 display, use the no form of this command.
service local-directory [authenticate]
no service local-directory [authenticate]
Syntax Description
Command Default
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 this ITS router:
Router(config)# telephony-serviceRouter(config-telephony-service)# no service local-directoryRelated Commands
service phone
To modify the vendorConfig parameters in the configuration file, use the service phone command in telephony-service or ephone-template configuration mode. To disable a setting, use the no form of this command.
service phone parameter-name parameter-value
no service phone parameter-name parameter-value
Syntax Description
parameter-name
Name of the vendorConfig parameter in the configuration file. For valid parameter names, see Table 12.
Note
parameter-value
Value for the vendorConfig parameter. For valid parameter values and defaults, see Table 12.
Command Default
The vendorConfig parameter defaults are enabled.
Command Modes
Telephony-service configuration (config-telephony)
Ephone-template configuration (config-ephone-template)Command History
Usage Guidelines
This command in telephony-service configuration mode modifies vendorConfig parameters in the configuration file for phones in a Cisco Unified CME system.
In Cisco Unified CME 4.0 and later versions, support for creating configuration files at a per-phone level was added and this command in ephone-template configuration mode creates an ephone-template of vendorConfig parameters which can be applied to an individual Cisco Unified IP phone in Cisco Unified CME.
If you use an ephone template to apply this command to a phone and you also use this command in telephony-service configuration mode for the same phone, the value that you set in ephone-template configuration mode has priority.
The vendorConfig section of a configuration file is read by a phone's firmware when that Cisco Unified IP phone is booted. Only the vendorConfig parameters supported by the currently loaded firmware are available. The number and type of parameters may vary from one firmware version to the next.
The IP phone that downloads the configuration file will implement only those parameters that it can support and ignore configured parameters that it cannot implement. For example, a Cisco Unified IP Phone 7970G does not have a backlit display and cannot implement Backlight parameters regardless of whether they are configured.
After modifying the vendorConfig parameters, you must use the create cnf command to generate a new configuration file. After generating the configuration file, use the reset command to reboot the IP phones to be configured and download the configuration.
Use the show telephony-service tftp-binding command to view the SEP*.cnf.xml files that are associated with individual phones. The following example entry from a Sep*.conf.xml file disables the PC port on a phone:
<vendorConfig><pcPort>1</pcPort></vendorConfig>Table 12 lists the basic vendorConfig parameters in alphabetical order.
Note
Examples
The following example shows how to configure multiple service phone parameters. This configuration is applied only in as much as IP phone firmware supports each parameter.
Router(config)# telephony-service
Router(config-telephony)# service phone disableSpeaker true
Router(config-telephony)# service phone disableSpeakerAndHeadset true
Router(config-telephony)# service phone forwardingDelay 1
Router(config-telephony)# service phone garp 1
Router(config-telephony)# service phone pcPort 1
Router(config-telephony)# service phone voiceVlanAccess 0
Router(config-telephony)# service phone settingsAccess 1
Router(config-telephony)# service phone videoCapability 1
Router(config-telephony)# service phone daysDisplayNotActive 1,7
Router(config-telephony)# service phone displayOnTime 07:30
Router(config-telephony)# service phone displayOnDuration 10:00
Router(config-telephony)# service phone displayIdleTimeout 01:00
Router(config-telephony)# service phone daysBacklightNotActive 1,7
Router(config-telephony)# service phone backlightOnTime 07:30
Router(config-telephony)# service phone backlightOnDuration 10:00
Router(config-telephony)# service phone backlightIdleTimeout 01:00
Router(config-telephony)# create cnf-files
Router(config-telephony)# reset all
The following example shows how to set the default values for backlighting the phone display for all Cisco Unified IP phones with backlight capabilities in Cisco Unified CME.Router(config)# telephony-service
Router(config-telephony)# service phone daysBacklightNotActive 1,7
Router(config-telephony)# service phone backlightOnTime 07:30
Router(config-telephony)# service phone backlightOnDuration 10:00
Router(config-telephony)# service phone backlightIdleTimeout 01:00
Router(config-telephony)# create cnf-files
Router(config-telephony)# reset all
The following example shows how to set the Backlighting parameters so that there is no backlighting of the phone display for all Cisco Unified IP phones with backlight capabilities until there is user interaction with the phone. The backlightIdleTimeout parameter is configured so that the backlight will switch off again after 60 seconds of inactivity.
Router(config)# telephony-service
Router(config-telephony)# service phone daysBacklightNotActive 1,2,3,4,5,6,7
Router(config-telephony)# service phone backlightOnTime 07:30
Router(config-telephony)# service phone backlightOnDuration 10:00
Router(config-telephony)# service phone backlightIdleTimeout 00.01
Router(config-telephony)# create cnf-files
Router(config-telephony)# reset all
The following example shows how to set the Display parameters so that the phone display for all Cisco Unified IP phones with luminous displays are blank on Sunday (1), Monday (2), and Saturday (7):
Router(config)# telephony-service
Router(config-telephony)# service phone daysDisplayNotActive 1,2,7
Router(config-telephony)# create cnf-files
Router(config-telephony)# reset all
The following example shows how to disable the PC port on an individual IP phone (ephone 15) using an ephone template:
Router(config)# ephone-template 8
Router(config-ephone-template)# service phone pcPort 1
Router(config-ephone-template)# exit
Router(config)# ephone 15
Router(config-ephone)# ephone-template 8
Router(config-ephone)# exit
Router(config)# telephony-service
Router(config-telephony)# create cnf-files
Router(config-telephony)# exit
Router(config)# ephone 15
Router(config-ephone)# reset
Related Commands
session-server
To specify a session manager to manage and monitor Register and Subscribe messages during a feature-server session, use the session-server command in voice register dn configuration mode, voice register pool configuration mode, or ephone-dn configuration mode. To return to the default, use the no form of this command.
session-server session-server-tag [, ...session-server-tag]
no session-server session-server-tag
Syntax Description
Command Default
Session manager is not assigned.
Command Modes
Ephone-dn configuration (ephone-dn)
Voice register dn configuration (voice-register-dn)
Voice register pool configuration (voice-register-pool)Command History
12.4(11)XW2
Cisco Unified CME 4.2
This command was introduced.
Usage Guidelines
Cisco Unified CME 4.2 and later versions provide a general interface for interoperating with external feature servers, such as the Cisco Unified CCX application on Cisco CRS, including call monitoring and device monitoring based on SIP presence and dialog event package. A session manager in Cisco Unified CME can manage and monitor Register and Subscribe messages.
Before configuring this command, a session manager must already configured in Cisco Unified CME by using the voice register session-server command.
Use the session-server command in voice register pool configuration mode to specify that Register and Subscribe messages for an external feature-server route point must contain a Cisco-referenceID field. Registration or subscription will be granted only for the specified route point. The route point for which Register and Subscribe messages are to be managed by this session manager must already be configured as a SIP endpoint in Cisco Unified CME. Typically, the configuration for the route point is provided from the feature server. If the configuration for the route point is deleted or must be modified, it can be reconfigured directly in Cisco Unified CME by using Cisco IOS commands. Each route point can be managed by only one session manager. Each session manager can manage multiple route points.
Use the session-server command in ephone-dn configuration mode or in voice register dn configuration mode to specify that Subscribe messages for a directory number must contain a Cisco-referenceID field. Registration or subscription will be granted only for the specified directory number. The directory number for which Subscribe messages are to be monitored by this session manager must already be configured in Cisco Unified CME. Each directory number can be monitored by up to eight session managers. Each session manager can subscribe for multiple directory numbers.
Examples
The following example shows the configuration for specifying that session manager 1 can control a route point (voice register pool) for an external feature server:
voice register pool 1session-server 1The following example shows the configuration specifying which session managers can monitor Register and Subscribe messages to directory numbers associated with Cisco Unified CCX agent phones. Notice that several session managers (1, 3, 5, and 7) can subscribe for both directory numbers.
ephone-dn 1session-server 1,2,3,4,5,6,7,8.ephone-dn 2session-server 1,3,5,7Related Commands
session-transport
To specify the transport layer protocol that a SIP phone uses to connect to Cisco Unified CME, use the session-transport command in voice register pool or voice register template configuration mode. To reset to the default value, use the no form of this command.
session-transport {tcp | udp}
no session-transport
Syntax Description
tcp
Transmission Control Protocol (TCP) is used.
udp
User Datagram Protocol (UDP) is used. This is the default.
Command Default
UDP is the default protocol.
Command Modes
Voice register pool configuration
Voice register template configurationCommand History
Usage Guidelines
This command sets the transport layer protocol parameter in the phone's configuration file.
If you use a voice register template to apply a command to a phone and you also use the same command in voice register pool configuration mode for the same phone, the value that you set in voice register pool configuration mode has priority.
This command is not supported on the Cisco Unified IP Phone 7905, 7912, 7940, or 7960.
Note
Examples
The following example sets the transport layer protocol to TCP for SIP phone 10:
Router(config)# voice register pool 10Router(config-register-pool)# session-transport tcpRelated Commands
create profile
Generates the configuration profile files required for SIP phones.
show sip-ua status
Displays the status of SIP call service on a SIP gateway.
show capf-server
To display CAPF server configuration and session information, use the show capf-server command in privileged EXEC configuration mode.
show capf-server {auth-string | sessions | summary}
Syntax Description
auth-string
Display authentication strings for ephones.
sessions
Display information about active CAPF sessions.
summary
Display CAPF server configuration details.
Command Modes
Privileged EXEC
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)T
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
This command is used with Cisco Unified CME phone authentication.
Examples
The following example output displays CAPF server parameters:
Router# show capf-server summaryCAPF Server Configuration DetailsTrustpoint for TLS With Phone: cmeserverTrustpoint for CA operation: iosraSource Address: 10.1.1.1Listening Port: 3804Phone Key Size: 1024Phone KeyGen Retries: 100Phone KeyGen Timeout: 120 minutesDevice Authentication Mode: Auth-StringThe following example output displays the authentication strings that have been defined for the phones with the listed MAC addresses:
Router# show capf-server auth-stringAuthentication Strings for configured EphonesMac-Addr Auth-String-------- -----------000CCE3A817C 7012001121116BDD 922000D299D50DF 9182000ED7B10DAC 3114000F90485077 33280013C352E7F1 0678The following example output displays active sessions between phones (identified by their MAC addresses) and the CAPF server. The phone ID field lists standard phone identifications, which include the letters "SEP" plus the MAC addresses of the phones. Table 13 defines the session states that can appear in the output.
Router# show capf-server sessionsActive CAPF SessionsPhone ID StateSEP000CCE3A817C AWAIT-KEYGEN-RES
show credentials
To display the credentials settings that have been configured for use during Cisco Unified CME phone authentication communications or secure Cisco Unified SRST fallback, use the show credentials command in privileged EXEC mode.
show credentials
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Cisco Unified CME
This command displays the credentials settings on a Cisco Unified CME router that has been configured with a CTL provider to be used with Cisco Unified CME phone authentication.
Cisco Unified SRST
This command displays the credentials settings on the Cisco Unified SRST router that are supplied to Cisco Unified CallManager for use during secure SRST fallback.
Examples
The following is sample output from the show credentials command:
Router# show credentialsCredentials IP: 10.1.1.22Credentials PORT: 2445Trustpoint: srstcaTable 14 describes the fields in the sample output.
Related Commands
show ctl-client
To display information about the certificate trust list (CTL) client, use the show ctl-client command in privileged EXEC configuration mode.
show ctl-client
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)TC
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
This command is used with Cisco Unified CME phone authentication.
Examples
The following example displays trustpoints and IP addresses known to the CTL client.
Router# show ctl-clientCTL Client Information-----------------------------SAST 1 Certificate Trustpoint: cmeserverSAST 1 Certificate Trustpoint: sast2List of Trusted Servers in the CTLCME 10.1.1.1 cmeserverTFTP 10.1.1.1 cmeserverCAPF 10.1.1.1 cmeservershow ephone
To display information about registered Cisco Unified 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 13.
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 4444ephone-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 5555ephone-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 3333The 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:10.0.0.2 51671 Telecaster 7940 keepalive 28 max_line 2button 1: dn 1 number 4444Active Call on DN 1:3001 10.0.0.51 31808 to 10.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 Unified 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 Unified IP Phone 7914 Expansion Module is attached to the main Cisco Unified IP Phone 7960 or 7960G, 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:10.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 13 describes significant fields in the output.
Related Commands
show ephone attempted-registrations
To display the log of ephones that unsuccessfully attempt to register with Cisco Unified CME, use the show ephone attempted-registrations command in privileged EXEC mode.
show ephone attempted-registrations
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)T
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
The no auto-reg-ephone command blocks the automatic registration of ephones whose MAC addresses are not explicitly listed in the configuration. When automatic registration is blocked, Cisco Unified CME records the MAC addresses of phones that attempt to register but cannot because they are blocked.
Use the show ephone attempted-registrations command to view the list of phones that have attempted to register but have been blocked. The clear telephony-service ephone-attempted-registrations command clears the list.
Examples
The following example displays ephones that unsuccessfully attempted to register with Cisco Unified CME:
Router# show ephone attempted-registrationsAttempting Mac address:Num Mac Address DateTime DeviceType-----------------------------------------------------------------------------1 C863.8475.5417 22:52:05 UTC Thu Apr 28 2005 SCCP Gateway (AN)2 C863.8475.5408 22:52:05 UTC Thu Apr 28 2005 SCCP Gateway (AN).....25 000D.28D7.7222 22:26:32 UTC Thu Apr 28 2005 Telecaster 796026 000D.BDB7.A9EA 22:25:59 UTC Thu Apr 28 2005 Telecaster 7960...47 C863.94A8.D40F 22:52:17 UTC Thu Apr 28 2005 SCCP Gateway (AN)48 C863.94A8.D411 22:52:18 UTC Thu Apr 28 2005 SCCP Gateway (AN)49 C863.94A8.D400 22:52:15 UTC Thu Apr 28 2005 SCCP Gateway (AN)Table 16 describes the significant fields shown in the display.
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
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 IDLEThe show ephone command 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
Usage Guidelines
Use this command to identify the phone on which a particular dn-tag has been assigned.
Examples
The following is sample output for the two appearances of DN 5:
Router# show ephone dn 5Tag 5, Normal or Intercom dnephone 1, mac-address 0030.94C3.CAA2, line 2ephone 2, mac-address 0030.94c2.9919, line 3The show ephone command 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
Usage Guidelines
This command does not apply to Cisco Unified SRST.
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 IDLEThe show ephone command 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
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 17 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
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:newuserThe show ephone command describes significant fields in this output.
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
Usage Guidelines
This command does not apply to Cisco Unified SRST.
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)The show ephone command describes significant fields in this output. Table 18 describes a field that is not in that table.
Table 18 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
Examples
The following is sample output that displays the phone firmware versions for all phones in the system:
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 19 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
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 IDLEbutton 2: dn 0 --button 3: dn 0 --button 4: dn 0 --button 5: dn 0 --button 6: dn 0 --The show ephone command describes significant fields in this output.
Related Commands
show ephone remote
To display nonlocal phones (phones with no Address Resolution Protocol [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
Usage Guidelines
Phones without ARP entries are suspected not to be on the 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 25The show ephone command 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
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 IDLEThe show ephone command 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 is sample output from the show ephone summary command:
Router# show ephone summaryephone-1 Mac:0030.94C3.37CB TCP socket:[-1] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0IP:10.1.1.1 Telecaster 7910 keepalive 45 1:1sp1:5002 sp2:5003ephone-2 Mac:0030.94C3.F96A TCP socket:[-1] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0IP:10.1.1.2 Telecaster 7960 keepalive 45 1:2 2:3 3:4sp1:5004 sp2:5001ephone-3 Mac:0030.94C3.F946 TCP socket:[-1] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0IP:10.2.1.2 Telecaster 7960 keepalive 59ephone-4 Mac:0030.94C3.F43A TCP socket:[-1] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0IP:10.2.1.1 Telecaster 7960 keepalive 59Max 48, Registered 1, Unregistered 0, Deceased 0, Sockets 1Max Conferences 4 with 0 active (4 allowed)Skinny Music On Hold StatusActive MOH clients 0 (max 72), Media Clients 0No MOH file loadedThe show ephone command 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
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:2295The show ephone command 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
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 1The show ephone command 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
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 been registered for that ephone. The second way is when an unknown device was registered at some time after 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 0The show ephone command describes significant fields in this output.
Related Commands
show ephone-dn
To display status and information for a Cisco IP phone destination number or for extensions (ephone-dns) in a Cisco Unified CallManager Express (Cisco Unified CME) or Cisco Unified Survivable Remote Site Telephony (SRST) environment, use the show ephone-dn command in privileged EXEC mode.
show ephone-dn [dn-tag]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
Cisco Unified CME
The following Cisco Unified CME 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 msCisco Unified SRST
The following SRST sample output displays status and information for all ephone-dns:
Router# show ephone-dn 750/0/7 INVALIDEFXS 50/0/7 Slot is 50, Sub-unit is 0, Port is 7Type 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 defaultPlayout-delay Nominal is set to 60 msPlayout-delay Maximum is set to 200 msPlayout-delay Minimum mode is set to default, value 4 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 8 sWait Release Time Out is set to 30 sCompanding Type is u-lawRegion Tone is set for USStation name None, Station number NoneCaller ID Info Follows:Standard BELLCOREVoice card specific Info Follows:Digit Duration Timing is set to 100 msTable 20 describes significant fields in the output from this command.
The following table 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 Unified CallManager Express (Cisco Unified CME) or a Cisco Unified Survivable Remote Site Telephony (Cisco Unified SRST) environment, 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
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 22.
Related Commands
show ephone-dn
Displays status and information for a Cisco IP phone destination number or for extensions (ephone-dns) in a Cisco Unified CME or a Cisco Unified SRST environment.
show ephone-dn conference
To display information about ad hoc and meet-me conferences in a Cisco Unified CallManager Express (Cisco Unified CME) environment, use the show ephone-dn conference command in privileged EXEC mode.
show ephone-dn conference [ad-hoc | meetme | number number]
Syntax Description
ad-hoc
(Optional) Ad hoc conferences.
meetme
(Optional) Meet-me conferences.
number number
(Optional) Conference telephone or extension number.
Command Modes
Privileged EXEC
Command History
Examples
The following sample output displays information for the 1234 conference number. There are three directory numbers and six inactive parties.
Router# show ephone-dn conference number 1234type active inactive number==================================Meetme 0 6 1234DN tags: 31, 32, 33Table 23 describes the significant fields shown in the display.
Related Commands
show ephone-dn
Displays status and information for a Cisco IP phone destination number or for extensions (ephone-dns) in a Cisco Unified CME or a Cisco Unified SRST environment.
show ephone-dn loopback
To display information about loopback ephone-dns that have been created in a Cisco Unified CallManager Express (Cisco Unified CME) or a Cisco Unified Survivable Remote Site Telephony (Cisco Unified SRST) environment, 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 24, in alphabetical order.
Related Commands
show ephone-dn park
To display information about call-park slots in the system, use the show ephone-dn park command in privileged EXEC mode.
show ephone-dn park
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows information for a single call-park slot that uses an ephone-dn identifier of 50 and an extension number of 1560.
Router#show ephone-dn parkDN 50 (1560) park-slot state IDLENotify to () timeout 15 limit 20Table 25 describes the significant fields shown in the display.
Related Commands
park-slot
Creates a floating extension (ephone-dn) at which calls can be temporarily held (parked).
show ephone-dn statistics
To display call statistics for a Cisco IP destination or for extensions (ephone-dns) in a Cisco Unified CallManager Express (Cisco Unified CME) or a Cisco Unified Survivable Remote Site Telephony (Cisco Unified SRST) environment, 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
The following sample output displays statistics for all extensions (ephone-dns) in a Cisco Unified 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 3305The 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 0The show ephone-dn command describes significant fields in the output from this command.
Related Commands
show ephone-dn
Displays status and information for a Cisco IP phone destination number or for extensions (ephone-dns) in a Cisco Unified CME or a Cisco Unified SRST environment.
show ephone-dn summary
To display brief information about Cisco IP phone destination numbers or for extensions (ephone-dns) in a Cisco Unified CallManager Express (Cisco Unified CME) or a Cisco Unified Survivable Remote Site Telephony (Cisco Unified SRST) environment, 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
The following is example output from the show ephone-dn summary command:
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_INITTable 26 describes significant fields in the output from this command.
Related Commands
show ephone-dn
Displays status and information for a Cisco IP phone destination number or for extensions (ephone-dns) in a Cisco Unified CME or a Cisco Unified SRST environment.
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 IDLEThe show capf-server command describes significant fields in this output.
Related Commands
show ephone-hunt
To display ephone-hunt configuration information and current status and statistics information, use the show ephone-hunt command in privileged EXEC mode.
show ephone-hunt [tag | summary]
Syntax Description
tag
(Optional) Hunt-group number that was used to identify a hunt group in the ephone-hunt command. Range is 1 to 100.
summary
(Optional) Displays hunt group configuration information.
Command Modes
Privileged EXEC
Command History
12.2(15)ZJ
Cisco CME 3.0
This command was introduced.
12.3(4)T
Cisco CME 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 commands display information for peer, sequential, and last-idle ephone hunt groups. Using the tag argument outputs data for a specific ephone hunt group.
The output is dependent on call activity. If there is no activity, no data is displayed.
Examples
The following examples are contained in this section:
•
•
Verbose Output
The following is sample output from the show ephone-hunt command when no argument or keyword has been entered. The sample contains information for a peer hunt group, a sequential hunt group, and a longest-idle hunt group. See Table 28 for descriptions of significant fields in the output.
Router# show ephone-huntGroup 1type: peerpilot number: 450, peer-tag 20123list of numbers:451, aux-number A450A0900, # peers 5, logout 0, down 1peer-tag dn-tag rna login/logout up/down[20122 42 0 login up ][20121 41 0 login up ][20120 40 0 login up ][20119 30 0 login up ][20118 29 0 login down]452, aux-number A450A0901, # peers 4, logout 0, down 0peer-tag dn-tag rna login/logout up/down[20127 45 0 login up ][20126 44 0 login up ][20125 43 0 login up ][20124 31 0 login up ]453, aux-number A450A0902, # peers 4, logout 0, down 0peer-tag dn-tag rna login/logout up/down[20131 48 0 login up ][20130 47 0 login up ][20129 46 0 login up ][20128 32 0 login up ]477, aux-number A450A0903, # peers 1, logout 0, down 0peer-tag dn-tag rna login/logout up/down[20132 499 0 login up ]preference: 0preference (sec): 7timeout: 3, 3, 3, 3max timeout : 10hops: 4next-to-pick: 1E.164 register: yesauto logout: nostat collect: noGroup 2type: sequentialpilot number: 601, peer-tag 20098list of numbers:123, aux-number A601A0200, # peers 1, logout 0, down 0peer-tag dn-tag rna login/logout up/down[20097 56 0 login up ]622, aux-number A601A0201, # peers 3, logout 0, down 0peer-tag dn-tag rna login/logout up/down[20101 112 0 login up ][20100 111 0 login up ][20099 110 0 login up ]623, aux-number A601A0202, # peers 3, logout 0, down 0peer-tag dn-tag rna login/logout up/down[20104 122 0 login up ][20103 121 0 login up ][20102 120 0 login up ]*, aux-number A601A0203, # peers 1, logout 0, down 1peer-tag dn-tag rna login/logout up/down[20105 0 0 - down]*, aux-number A601A0204, # peers 1, logout 0, down 1peer-tag dn-tag rna login/logout up/down[20106 0 0 - down]final number: 5255348preference: 0preference (sec): 9timeout: 5, 5, 5, 5, 5max timeout : 40fwd-final: orig-phoneE.164 register: yesauto logout: nostat collect: noGroup 3type: longest-idlepilot number: 100, peer-tag 20142list of numbers:101, aux-number A100A9700, # peers 3, logout 0, down 3on-hook time stamp 7616, off-hook agents=0peer-tag dn-tag rna login/logout up/down[20141 132 0 login down][20140 131 0 login down][20139 130 0 login down]*, aux-number A100A9701, # peers 1, logout 0, down 1on-hook time stamp 7616, off-hook agents=0peer-tag dn-tag rna login/logout up/down[20143 0 0 - down]102, aux-number A100A9702, # peers 2, logout 0, down 2on-hook time stamp 7616, off-hook agents=0peer-tag dn-tag rna login/logout up/down[20145 142 0 login down][20144 141 0 login down]all agents down!preference: 0preference (sec): 7timeout: 100, 100, 100hops: 0E.164 register: yesauto logout: nostat collect: noSummary Output
The following example shows summary output. See Table 28 for descriptions of significant fields in the 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: noAgent Status Control Conditions
A portion of the show ephone-hunt command output displays the ready and not-ready agent status of extensions in hunt groups. An extension that is ready is available to receive hunt-group calls. An extension that is in not-ready status blocks hunt-group calls. An agent toggles an extension from ready to not ready and back to ready using the HLog soft key or a FAC.
The following examples display some output that reports different agent status not-ready conditions within a hunt group. In the hunt group used for these examples, there are four users: agent1 and agent4 share extension 8001, agent2 is on extension 8002, and agent3 is on extension 8003.
In the show ephone-hunt output, "logout 0" means that all instances of the extension are in ready status. Any number greater than zero next to "logout' indicates that at least one ephone using the extension has activated not-ready status.
If agent1 is in not-ready status, the show ephone-hunt command will display the following output. The logout value for extension 8001 is 1 because one phone is in not-ready status.
Router# show ephone-hunt...list of numbers:8001, aux-number A8000A100, # peers 2, logout 1 ...8002, aux-number A8000A101, # peers 1, logout 0...8003, aux-number A8000A102, # peers 1, logout 0....If agent1 and agent2 place their phones in not-ready status, the show ephone-hunt command will display the following output:
Router# show ephone-hunt...list of numbers:8001, aux-number A8000A100, # peers 2, logout 1...8002, aux-number A8000A101, # peers 1, logout 1...8003, aux-number A8000A102, # peers 1, logout 0...If all agents place their phones in not-ready status, the show ephone-hunt command displays the following output. Note that the logout value of 2 for extension 8001 indicates that both ephone-dns with that extension number (agent1 and agent4) are in not-ready status.
Router# show ephone-hunt...list of numbers:8001, aux-number A8000A100, # peers 2, logout 2...8002, aux-number A8000A101, # peers 1, logout 1...8003, aux-number A8000A102, # peers 1, logout 1...all agents logout!Automatic Agent Status Not-Ready Parameters
The show ephone-hunt command displays the parameters that have been set using the auto logout command, which is used for the Automatic Agent Status Not-Ready feature. Table 27 shows the possible values of the auto logout field. Table 28 describes other fields in the output.
Router# show ephone-hunt 1Group 1type:sequentialpilot number:8888, peer-tag 20029list of numbers:8001, aux-number A8888A000, # peers 1, logout 0, down 0peer-tag:dn-tag [ 20028:1]8003, aux-number A8888A001, # peers 1, logout 0, down 0peer-tag:dn-tag [ 20030:3]preference:0preference (sec):9timeout:5E.164 register:yesauto logout:nostat collect:yes
Table 28 describes significant fields shown in show ephone-hunt command displays.
Table 28 show ephone-hunt Field Descriptions
auto logout
Indicates whether the Automatic Agent Status Not-Ready feature has been enabled. See the "Automatic Agent Status Not-Ready Parameters" section.
aux-number
Auxiliary number used to generate dial peers for a hunt group. This number is generated by the list command.
description
Description string entered for the ephone hunt group. This value is set using the description (ephone-hunt) command.
dn-tag
Directory number (DN) sequence number.
E.164 register
Displays whether a pilot number registers with an H.323 gatekeeper. This value is set by the no-reg command.
final number
Last number in the ephone-hunt group, after which a call is no longer redirected. This value is set by the final command.
fwd-final
Final destination of an unanswered call that has been transferred into a hunt group: orig-phone means calls are returned to the transferring phone, and final means calls are sent to the final number specified in the configuration. This value is set by the fwd-final command.
hops
Number of hops before a call proceeds to the final number. This value is set by the hops command.
list of numbers
Extension numbers that are group members of the specified ephone hunt group. This value is set by the list command.
login/logout
Ready status of the agent: login means ready and accepting calls, and logout means not-ready and blocking hunt-group calls.
logout
Number of agents in the not-ready state (not accepting hunt-group calls).
max timeout
Maximum combined timeout for the no-answer periods for all ephone-dns in the ephone-hunt list. This value is set by the max-timeout command.
next-to-pick
(Peer hunt groups only) List number of the agent whose phone will ring when the next call comes in to the hunt group. (For example, if the order of agents in the list command is 451, 452, 453, 454, the list number 2 represents extension 452.)
off-hook agents
Number of agents who are currently off-hook.
on-hook time stamp
(Longest-idle hunt groups only) The last on-hook time of the agent, which is used to determine which agent to ring next time.
peers
Displays the number of ephone-dn dial peers.
peer-tag
Dial-peer sequence number.
pilot number
Number that callers dial to reach the ephone hunt group.
preference
Preference order set by the preference (ephone-hunt) command for the primary pilot number.
preference (sec)
Preference order set by the preference (ephone-hunt) command for the secondary pilot number.
rna
Number of unanswered hunt group calls (ring-no-answer) by this agent, used for the Automatic Agent Status Not-Ready feature.
stat collect
Indicates whether statistic are being Cisco Unified CME B-ACD data is being collected. See the statistics collect command.
timeout
Number of seconds after which a call that is not answered at one number is redirected to the next number in the hunt-group list. Multiple values in this field refer to the timeouts for the hops between ephone-dns in a hunt group as they appear in the list command. This value is set by the timeout command.
type
Type of ephone hunt group: longest-idle, peer, or sequential.
up/down
Dial peer is up or down.
Related Commands
show ephone-hunt statistics
To display ephone-hunt statistics information, use the show ephone-hunt statistics command in privileged EXEC mode.
show ephone-hunt tag statistics {last hours hours | start day time [to day time]}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The show ephone-hunt statistics last and show ephone-hunt statistics commands provide expanded information regarding extension (list of numbers) and pilot numbers.
The output is dependent on call activity. If there is no activity, no data is displayed.
If your Cisco Unified CME system is configured with the basic automatic call distribution (B-ACD) and auto-attendant service, you can enable the collection of call statistics per ephone hunt group with the statistics collect command. Additional data is displayed for all agents combined and for individual agents. The additional data includes statistics such as: the number of calls received, the amount of time the calls waited to be answered, and the amount of time the calls spend on hold or in a queue.
The statistics collect command can be used to obtain other call statistics, such as direct calls to hunt group pilot numbers. For more information, see the " Cisco Unified CME Basic Automatic Call Distribution and Auto-Attendant Service" chapter in the Cisco Unified CME B-ACD and TCL Call-Handling Applications guide.
Once you have enabled statistics collection, you can use the show ephone-hunt statistics command to display call statistics, or you can use the hunt-group report every hours and hunt-group report url commands to transfer the statistics to files using TFTP.
Note
Examples
The following sample output displays call statistics for the past hour for hunt group 2, which is associated with a Cisco Unified CME B-ACD service:
Router#show ephone-hunt 2 stat last 1 hThu 02:00 - 03:00Max Agents: 3Min Agents: 3Total Calls: 9Answered Calls: 7Abandoned Calls: 2Average Time to Answer (secs): 6Longest Time to Answer (secs): 13Average Time in Call (secs): 75Longest Time in Call (secs): 161Average Time before Abandon (secs): 8Calls on Hold: 2Average Time in Hold (secs): 16Longest Time in Hold (secs): 21Per agent statistics:Agent: 8004From Direct Call:Total Calls Answered : 3:Average Time in Call (secs) : 70Longest Time in Call (secs) : 150Total Calls on Hold : 1:Average Hold Time (secs) : 21Longest Hold Time (secs) : 21From Queue:Total Calls Answered : 3Average Time in Call (secs) : 55Longest Time in Call (secs) : 78Total Calls on Hold : 2:Average Hold Time (secs) : 19Longest Hold Time (secs) : 26Agent: 8006From Direct Call:Total Calls Answered : 3:Average Time in Call (secs) : 51Longest Time in Call (secs) : 118Total Calls on Hold : 1:Average Hold Time (secs) : 11Longest Hold Time (secs) : 11From Queue:Total Calls Answered : 1Average Time in Call (secs) : 4Longest Time in Call (secs) : 4Agent: 8044From Direct Call:Total Calls Answered : 1:Average Time in Call (secs) : 161Longest Time in Call (secs) : 161From Queue:Total Calls Answered : 1Average Time in Call (secs) : 658Longest Time in Call (secs) : 658Queue related statistics:Total calls presented to the queue: 5Calls answered by agents: 5Number of calls in the queue: 0Average time to answer (secs): 2Longest time to answer (secs): 3Number of abandoned calls: 0Average time before abandon (secs): 0Calls forwarded to voice mail: 0Calls answered by voice mail: 0Table 28 describes significant fields shown in show ephone-hunt command displays.
Related Commands
show fb-its-log
To display information about the Cisco CallManager Express (Cisco CME) eXtensible Markup Language (XML) application program interface (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:FALSEThe 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 30 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.
Posted: Tue Sep 11 11:23:22 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
