|
|
Table Of Contents
CiscoUnified CME Commands: Debug
debug ephone extension-assigner
CiscoUnified CME Commands: Debug
Last Updated: July 19, 2007First Published: February 27, 2006
This chapter contains commands to configure and maintain Cisco Unified Communications Manager Express (formally known as Cisco Unified CallManager Express). The commands are presented in alphabetical order. Some commands required for configuring Cisco Unified Communications Manager Express (Cisco Unified CME) may be found in other Cisco IOS command references. Use the command reference master index or search online to find these commands.
debug callmonitor
To collect and display debugging traces for call monitor, use the debug callmonitor command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug callmonitor {all | core | detail | errors | events | hwconf | info | xml}
no debug command {all | core | detail | errors | events | hwconf | info | xml}
Syntax Description
Command Default
There is no default for this command.
Command Modes
Privileged EXEC
Command History
Examples
The following example is partial output from this command:
Router# debug callmonitor allSyslog logging: enabled (11 messages dropped, 2 messages rate-limited,0 flushes, 0 overruns, xml disabled, filtering disabled)No Active Message Discriminator.No Inactive Message Discriminator.Console logging: disabledMonitor logging: level debugging, 0 messages logged, xml disabled,filtering disabledBuffer logging: level debugging, 444378 messages logged, xml disabled,filtering disabledLogging Exception size (4096 bytes)Count and timestamp logging messages: disabledPersistent logging: disabledTrap logging: level informational, 461 message lines loggedLog Buffer (1000000 bytes):Jun 4 22:30:24.222: //CMM/INFO:Jun 4 22:30:24.222: //CMM/INFO:Jun 4 22:30:24.222: //CMM/INFO:cmm_notify_trigger() 15, callID 99685, 5114016, 1884814040, 1632257208Jun 4 22:30:24.222: //CMM/INFO: target_node 0Jun 4 22:30:24.222: //CMM/INFO:Lineinfo node Search FAILEDJun 4 22:30:24.222: //CMM/INFO:create_lineinfo_nodeJun 4 22:30:24.222: //CMM/INFO: target_node 66AF3714Jun 4 22:30:24.222: //CMM/INFO: - dn 4016Jun 4 22:30:24.222: //CMM/INFO: CallEntry 709C3FB8Jun 4 22:30:24.222: //CMM/INFO: dstCallID -1Jun 4 22:30:24.222: //CMM/INFO: line_info 66AF3720, dn 4016Jun 4 22:30:24.222: //CMM/INFO: * cmm_crs_proc_tr_rpt_origJun 4 22:30:24.222: //CMM/INFO: callID = 99685, CG 5114016, GCID =05591A85-122211DC-8645A1CA-4B604A7AJun 4 22:30:24.222: //CMM/INFO:increase_gcid_ref_count 99685 0Jun 4 22:30:24.222: //CMM/INFO:find_gcidinfo_nodeJun 4 22:30:24.222: //CMM/INFO: target_node 0Jun 4 22:30:24.222: //CMM/INFO: Gcidinfo node Search FAILEDJun 4 22:30:24.222: //CMM/INFO:create_gcidinfo_nodeJun 4 22:30:24.222: //CMM/INFO: target_node 6544A9CCJun 4 22:30:24.222: //CMM/INFO: - gcid 05591A85-122211DC-8645A1CA-4B604A7AJun 4 22:30:24.222: //CMM/INFO: count = 1Jun 4 22:30:24.222: //CMM/INFO:insert_ssptrs_to_gcid for line_info 66AF3720 (dn 4016), GCID 05591A85-122211DC-8645A1CA-4B604A7AJun 4 22:30:24.222: ss_ptr list :-Jun 4 22:30:24.222: ss_ptr list :-Jun 4 22:30:24.222: //CMM/INFO:Jun 4 22:30:24.222: //CMM/INFO:Jun 4 22:30:24.222: //CMM/INFO:cmm_notify_trigger() 1, callID 99685, 5114016, 16, 1695547392Jun 4 22:30:24.222: //CMM/INFO: target_node 66AF3714Jun 4 22:30:24.222: //CMM/INFO: - dn 4016Jun 4 22:30:24.222: //CMM/INFO: CallEntry 709C3FB8Jun 4 22:30:24.222: //CMM/INFO: dstCallID -1Jun 4 22:30:24.222: //CMM/INFO: line_info 66AF3720, dn 4016Jun 4 22:30:24.222: //CMM/INFO: * cmm_crs_proc_tr_call_origJun 4 22:30:24.222: //CMM/INFO: orig --> callID 99685, line_info 66AF3720, call_inst 655AF384, gcid 05591A85-122211DC-8645A1CA-4B604A7AJun 4 22:30:24.222: //CMM/INFO:is_sccp_endpoint DN 4016Jun 4 22:30:24.222: //CMM/INFO:Jun 4 22:30:24.222: sccp endpoint TRUEJun 4 22:30:24.222: //CMM/INFO:find_gcidinfo_nodeJun 4 22:30:24.222: //CMM/INFO: target_node 6544A9CCJun 4 22:30:24.222: //CMM/INFO: - gcid 05591A85-122211DC-8645A1CA-4B604A7AJun 4 22:30:24.222: //CMM/INFO:cmm_send_dialog_notify sub_info 0Jun 4 22:30:24.222: ss_ptr list :-Jun 4 22:30:24.222: //CMM/INFO: <== DIALOG MGR ==>Jun 4 22:30:24.222: //CMM/INFO: :: CMM_EV_CALL_CONN_ORIGINATEDJun 4 22:30:24.222: //CMM/INFO: - Gcid 05591A85-122211DC-8645A1CA-4B604A7AJun 4 22:30:24.222: //CMM/INFO: - Calling 4016Jun 4 22:30:24.222: //CMM/INFO: - CalledJun 4 22:30:24.222: //CMM/INFO: - ConnAddr 4016Jun 4 22:30:24.222: //CMM/INFO: - Type 0Jun 4 22:30:24.222: //CMM/INFO: - parentGcid 00000000-00000000-00000000-00000000Jun 4 22:30:24.222: //CMM/INFO:find_gcidinfo_nodeJun 4 22:30:24.222: //CMM/INFO: target_node 6544A9CCJun 4 22:30:24.222: //CMM/INFO: - gcid 05591A85-122211DC-8645A1CA-4B604A7AJun 4 22:30:24.222: //CMM/DETAIL: type: CMM_EV_CALL_CONN_ORIGINATED, filter analyzing.... [4016, , 4016]Jun 4 22:30:24.222: //CMM/INFO:find_gcidinfo_nodeJun 4 22:30:24.222: //CMM/INFO: target_node 6544A9CCJun 4 22:30:24.222: //CMM/INFO: - gcid 05591A85-122211DC-8645A1CA-4B604A7AJun 4 22:30:24.222: //CMM/DETAIL:gcid is not part of conference. [4016, , 4016] checking originateFilter...Jun 4 22:30:24.222: //CMM/DETAIL:originateFilter[callid=99685, pdn=16, pchan=1] is not set. [4016, , 4016] is not filteredJun 4 22:30:24.222: //CMM/INFO:find_gcidinfo_nodeJun 4 22:30:24.222: //CMM/INFO: target_node 6544A9CCJun 4 22:30:24.222: //CMM/INFO: - gcid 05591A85-122211DC-8645A1CA-4B604A7AJun 4 22:30:24.222: //CMM/INFO:cmm_send_dialog_notify sub_info 0Jun 4 22:30:24.222: ss_ptr list :-Jun 4 22:30:24.222: //CMM/INFO: <== DIALOG MGR ==>Jun 4 22:30:24.222: //CMM/INFO: :: CMM_EV_CALL_CONN_ACTIVEJun 4 22:30:24.222: //CMM/INFO: - Gcid 05591A85-122211DC-8645A1CA-4B604A7AJun 4 22:30:24.222: //CMM/INFO: - Calling 4016Jun 4 22:30:24.222: //CMM/INFO: - CalledJun 4 22:30:24.222: //CMM/INFO: - ConnAddr 4016Jun 4 22:30:24.222: //CMM/INFO: - LastRedirectAddrJun 4 22:30:24.222: //CMM/INFO: - Type 0Jun 4 22:30:24.222: //CMM/INFO: - parentGcid 00000000-00000000-00000000-00000000Jun 4 22:30:24.222: //CMM/INFO:find_gcidinfo_nodeJun 4 22:30:24.222: //CMM/INFO: target_node 6544A9CCJun 4 22:30:24.222: //CMM/INFO: - gcid 05591A85-122211DC-8645A1CA-4B604A7AJun 4 22:30:24.222: //CMM/DETAIL: type: CMM_EV_CALL_CONN_ACTIVE, filter analyzing.... [4016, , 4016]Jun 4 22:30:24.222: //CMM/DETAIL:called number is not specified. [4016, , 4016]Jun 4 22:30:24.222: //CMM/DETAIL:originateFilter[callid=99685, pdn=16, pchan=1] is not set, [4016, , 4016] is not filteredJun 4 22:30:25.670: //CMM/INFO:Jun 4 22:30:25.670: //CMM/INFO:Jun 4 22:30:25.670: //CMM/INFO:cmm_notify_trigger() 14, callID 99686, 8101, 1902058375, 0Jun 4 22:30:25.670: //CMM/INFO: target_node 65DB15E4Jun 4 22:30:25.670: //CMM/INFO: - dn 8101...Related Commands
debug capf-server
To collect debug information about the CAPF server, use the debug capf-server command in privileged EXEC mode. To disable collection of debug information, use the no form of this command.
debug capf-server {all | error | events | messages}
no debug capf-server
Syntax Description
all
Collect all CAPF information available.
error
Collect only information about CAPF errors.
events
Collect only information about CAPF status events.
messages
Collect only CAPF system messages.
Command Default
Collection of CAPF debug information is disabled.
Command Modes
Privileged EXEC
Command History
12.4(4)XC
This command was introduced.
12.4(9)T
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
This command is used with Cisco Unified CallManager Express phone authentication.
Examples
The following example shows debug messages for the CAPF server.
Router# debug capf-server all001891: .Jul 21 18:17:07.014: %IPPHONE-6-UNREGISTER_NORMAL: ephone-1:SEP000E325C9A43 IP:10.10.10.194 Socket:3 DeviceType:Phone has unregistered normally.001892: .Jul 21 18:17:20.495: New Connection from phone, socket 1001893: .Jul 21 18:17:20.495: Created New Handshake Process001894: .Jul 21 18:17:20.499: SSL Handshake Error -6983001895: .Jul 21 18:17:21.499: SSL Handshake Error -6983001896: .Jul 21 18:17:22.555: SSL Handshake Successful001897: .Jul 21 18:17:22.555: ephone_capf_send_auth_req:001898: .Jul 21 18:17:22.555: ephone_capf_ssl_write: 12 bytes001899: .Jul 21 18:17:22.711: ephone_capf_ssl_read: Read 35 bytes001900: .Jul 21 18:17:22.711: ephone_capf_handle_phone_msg: msgtype 2001901: .Jul 21 18:17:22.711: ephone_capf_process_auth_res_msg: SEP000E325C9A43 AuthMode 2001902: .Jul 21 18:17:22.711: ephone_capf_send_delete_cert_req_msg: SEP000E325C9A43001903: .Jul 21 18:17:22.711: ephone_capf_ssl_write: 8 bytes001904: .Jul 21 18:17:23.891: ephone_capf_ssl_read: Read 12 bytes001905: .Jul 21 18:17:23.891: ephone_capf_handle_phone_msg: msgtype 14001906: .Jul 21 18:17:23.891: certificate delete successful for SEP000E325C9A43001907: .Jul 21 18:17:24.695: ephone_capf_release_session: SEP000E325C9A43001908: .Jul 21 18:17:24.695: ephone_capf_send_end_session_msg: SEP000E325C9A43001909: .Jul 21 18:17:24.695: ephone_capf_ssl_write: 12 bytes001910: .Jul 21 18:17:25.095: %IPPHONE-6-REG_ALARM: 22: Name=SEP000E325C9A43 Load=7.2(2.0) Last=Reset-Reset001911: .Jul 21 18:17:25.099: %IPPHONE-6-REGISTER: ephone-1:SEP000E325C9A43 IP:10.10.10.194 Socket:2 DeviceType:Phone has registered.001912: .Jul 21 18:18:05.171: %IPPHONE-6-UNREGISTER_NORMAL: ephone-1:SEP000E325C9A43 IP:1.1.1.127 Socket:2 DeviceType:Phone has unregistered normally.001913: .Jul 21 18:18:18.288: New Connection from phone, socket 1001914: .Jul 21 18:18:18.288: Created New Handshake Process001915: .Jul 21 18:18:18.292: SSL Handshake Error -6983001916: .Jul 21 18:18:19.292: SSL Handshake Error -6983001917: .Jul 21 18:18:20.348: SSL Handshake Successful001918: .Jul 21 18:18:20.348: ephone_capf_send_auth_req:001919: .Jul 21 18:18:20.348: ephone_capf_ssl_write: 12 bytes^Z001920: .Jul 21 18:18:20.492: ephone_capf_ssl_read: Read 35 bytes001921: .Jul 21 18:18:20.492: ephone_capf_handle_phone_msg: msgtype 2001922: .Jul 21 18:18:20.492: ephone_capf_process_auth_res_msg: SEP000E325C9A43 AuthMode 2001923: .Jul 21 18:18:20.492: ephone_capf_send_PhKeyGenReq_msg: SEP000E325C9A43 KeySize 1024001924: .Jul 21 18:18:20.492: ephone_capf_ssl_write: 13 bytes001925: .Jul 21 18:18:20.540: ephone_capf_ssl_read: Read 8 bytes001926: .Jul 21 18:18:20.540: ephone_capf_handle_phone_msg: msgtype 17001927: .Jul 21 18:18:20.540: ephone_capf_process_req_in_progress: SEP000E325C9A43 delay 0sh001928: .Jul 21 18:18:21.924: %SYS-5-CONFIG_I: Configured from console by user1 on consoledebug cch323 video
To provide debugging output for video components within the H.323 subsystem, use the debug cch323 video command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cch323 video
no debug cch323 video
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.4(4)XC
This command was introduced.
12.4(9)T
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
Use this command to enable a debugging trace for the video component in an H.323 network.
Examples
Originating Gateway Example
The following is sample output of the debugging log for an originating Cisco Unified CallManager Express (Cisco Unified CME) gateway after the debug cch323 video command was enabled:
Router# show logSyslog logging: enabled (11 messages dropped, 487 messages rate-limited,0 flushes, 0 overruns, xml disabled, filtering disabled)Console logging: disabledMonitor logging: level debugging, 0 messages logged, xml disabled,filtering disabledBuffer logging: level debugging, 1144 messages logged, xml disabled,filtering disabledLogging Exception size (4096 bytes)Count and timestamp logging messages: disabledTrap logging: level informational, 1084 message lines loggedLog Buffer (6000000 bytes):Jun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_get_peer_info: EntryJun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_get_peer_info: Have peerJun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_set_pref_codec_list: First preferred codec(bytes)=16(20)Jun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_get_peer_info: Flow Mode set to FLOW_THROUGHJun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_get_caps_chn_info: No peer leg setup paramsJun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_get_caps_chn_info: Setting CCH323_SS_NTFY_VIDEO_INFOJun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_set_h323_control_options_outgoing: h245 sm mode = 8463Jun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_set_h323_control_options_outgoing: h323_ctl=0x20Jun 13 09:19:42.010: //103030/C7838B198002/H323/cch323_rotary_validate: No peer_ccb availableTerminating Gateway Example
The following is sample output of the debugging log for a terminating Cisco Unified Survivable Remote Site Telephony (Cisco Unified SRST) gateway after the debug cch323 video command was enabled:
Router# show logSyslog logging: enabled (11 messages dropped, 466 messages rate-limited,0 flushes, 0 overruns, xml disabled, filtering disabled)Console logging: disabledMonitor logging: level debugging, 0 messages logged, xml disabled,filtering disabledBuffer logging: level debugging, 829 messages logged, xml disabled,filtering disabledLogging Exception size (4096 bytes)Count and timestamp logging messages: disabledTrap logging: level informational, 771 message lines loggedLog Buffer (200000 bytes):Jun 13 09:19:42.011: //103034/C7838B198002/H323/setup_ind: Receive bearer cap infoXRate 24, rateMult 12Jun 13 09:19:42.011: //103034/C7838B198002/H323/cch323_set_h245_state_mc_mode_incoming: h245 state m/c mode=0x10F, h323_ctl=0x2FJun 13 09:19:42.015: //-1/xxxxxxxxxxxx/H323/cch245_event_handler: callID=103034Jun 13 09:19:42.019: //-1/xxxxxxxxxxxx/H323/cch245_event_handler: Event CC_EV_H245_SET_MODE: data ptr=0x465D5760Jun 13 09:19:42.019: //-1/xxxxxxxxxxxx/H323/cch323_set_mode: callID=103034, flow Mode=1 spi_mode=0x6Jun 13 09:19:42.019: //103034/C7838B198002/H323/cch323_do_call_proceeding: set_mode NOT called yet...saved deferred CALL_PROCJun 13 09:19:42.019: //103034/C7838B198002/H323/cch323_h245_connection_sm: state=0, event=0, ccb=4461B518, listen state=0Jun 13 09:19:42.019: //103034/C7838B198002/H323/cch323_process_set_mode: Setting inbound leg mode flags to 0x10F, flow-mode to FLOW_THROUGHJun 13 09:19:42.019: //103034/C7838B198002/H323/cch323_process_set_mode: Sending deferred CALL_PROCJun 13 09:19:42.019: //103034/C7838B198002/H323/cch323_do_call_proceeding: set_mode called so we can proceed with CALLPROCJun 13 09:19:42.027: //103034/C7838B198002/H323/cch323_h245_connection_sm: state=1, event=2, ccb=4461B518, listen state=1Jun 13 09:19:42.027: //103034/C7838B198002/H323/cch323_send_cap_request: Setting mode to VIDEO MODEJun 13 09:19:42.031: //103034/C7838B198002/H323/cch323_h245_cap_ind: Masks au=0xC data=0x2 uinp=0x32Related Commands
debug cme-xml
To generate debug messages for the Cisco Unified CallManager Express XML application, use the debug cme-xml command in privileged EXEC mode. To disable debugging, use the no form of the command.
debug cme-xml
no debug cme-xml
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC
Command History
12.4(4)XC
This command was introduced.
12.4(9)T
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
The show fb-its-log command displays the contents of the XML event table.
Examples
The following example shows the progress of an XML request that has been sent to Cisco Unified CallManager Express:
Router# debug cme-xml*Aug 5 06:27:25.727: CME got a raw XML message.*Aug 5 06:27:25.727: doc 0x63DB85E8, doc->doc_type 3, req 0x655FDCD0*Aug 5 06:27:25.727: CME extracted a XML document*Aug 5 06:27:25.727: Response buffer 0x63DCFD58, len = 4096*Aug 5 06:27:25.727: First Tag ID SOAP_HEADER_TAG_ID 58720257*Aug 5 06:27:25.727: First Attribute ID SOAP_ENV_ATTR 50331649*Aug 5 06:27:25.727: cme_xml_process_soap_header*Aug 5 06:27:25.727: cme_xml_process_soap_body*Aug 5 06:27:25.731: cme_xml_process_axl*Aug 5 06:27:25.731: cme_xml_process_request*Aug 5 06:27:25.731: cme_xml_process_ISgetGlobal*Aug 5 06:27:25.731: CME XML sent 811 bytes response.Related Commands
debug credentials
To set debugging on the credentials service that runs between the Cisco Unified CME CTL provider and CTL client or between the Cisco Unified SRST router and Cisco Unified CallManager, use the debug credentials command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug credentials
no debug credentials
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Cisco Unified CME
Use this command with Cisco Unified CME phone authentication to monitor a CTL provider as it provides credentials to the CTL client.
Cisco Unified SRST
Use this command to monitor Cisco Unified CallManager while it requests certificates from the Cisco Unified SRST router. It sets debugging on the credentials service that runs between the SRST router and Cisco Unified CallManager
Examples
Cisco Unified CME
The following sample output displays the CTL provider establishing a TLS session with the CTL client and providing all the relevant credentials for the services that are running on this router to the CTL client.
Router# debug credentialsCredentials server debugging is enabledMay 25 12:08:17.944: Credentials service: Start TLS Handshake 1 10.5.43.174 4374May 25 12:08:17.948: Credentials service: TLS Handshake returns OPSSLReadWouldBlockErrMay 25 12:08:18.948: Credentials service: TLS Handshake returns OPSSLReadWouldBlockErrMay 25 12:08:19.948: Credentials service: TLS Handshake returns OPSSLReadWouldBlockErrMay 25 12:08:20.964: Credentials service: TLS Handshake completesCisco Unified SRST
The following is sample output showing the credentials service that runs between the Cisco Unified SRST router and Cisco Unified CallManager. The credentials service provides Cisco Unified CallManager with the certificate from the SRST router.
Router# debug credentialsCredentials server debugging is enabledRouter#May 25 12:08:17.944: Credentials service: Start TLS Handshake 1 10.5.43.174 4374May 25 12:08:17.948: Credentials service: TLS Handshake returns OPSSLReadWouldBlockErrMay 25 12:08:18.948: Credentials service: TLS Handshake returns OPSSLReadWouldBlockErrMay 25 12:08:19.948: Credentials service: TLS Handshake returns OPSSLReadWouldBlockErrMay 25 12:08:20.964: Credentials service: TLS Handshake completesTable 2 describes the significant fields shown in the display.
Related Commands
debug ctl-client
To collect debug information about the CTL client, use the debug ctl-client command in privileged EXEC configuration mode. To disable collection of debug information, use the no form of this command.
debug ctl-client
no debug ctl-client
Syntax Description
This command has no arguments or keywords.
Command Default
Collection of CTL client debug information is disabled.
Command Modes
Privileged EXEC
Command History
12.4(4)XC
This command was introduced.
12.4(9)T
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 shows debug messages for the CTL client:
Router# debug ctl-client001954: .Jul 21 18:23:02.136: ctl_client_create_ctlfile:001955: .Jul 21 18:23:02.272: create_ctl_record: Function 0 Trustpoint cisco1001956: .Jul 21 18:23:02.276: create_ctl_record: record added for function 0001957: .Jul 21 18:23:02.276: create_ctl_record: Function 0 Trustpoint sast2001958: .Jul 21 18:23:02.280: create_ctl_record: record added for function 0001959: .Jul 21 18:23:02.280: create_ctl_record: Function 1 Trustpoint cisco1001960: .Jul 21 18:23:02.284: create_ctl_record: record added for function 1001961: .Jul 21 18:23:02.284: create_ctl_record: Function 3 Trustpoint cisco1001962: .Jul 21 18:23:02.288: create_ctl_record: record added for function 3001963: .Jul 21 18:23:02.288: create_ctl_record: Function 4 Trustpoint cisco1001964: .Jul 21 18:23:02.292: create_ctl_record: record added for function 4001965: .Jul 21 18:23:02.424: ctl_client_create_ctlfile: Signature length 128001966: .Jul 21 18:23:02.640: CTL File Created Successfullydebug ephone alarm
To set SkinnyStation alarm messages debugging for the Cisco IP phone, use the debug ephone alarm command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone alarm [mac-address mac-address]
no debug ephone alarm [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone alarm command shows all the SkinnyStation alarm messages sent by the Cisco IP phone. Under normal circumstances, this message is sent by the Cisco IP phone just before it registers, and the message has the severity level for the alarm set to "Informational" and contains the reason for the phone reboot or re-register. This type of message is entirely benign and does not indicate an error condition.
If the mac-address keyword is not used, the debug ephone alarm command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following example shows a SkinnyStation alarm message that is sent before the Cisco IP phone registers:
Router# debug ephone alarmphone keypad resetCM-closed-TCPCM-bad-stateRelated Commands
debug ephone blf
To display debugging information for Busy Lamp Field (BLF) presence features, use the debug ephone blf command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ephone blf [mac-address mac-address]
no debug ephone blf [mac-address mac-address]
Syntax Description
Command Modes
Privileged EXEC
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
Use this command for troubleshooting BLF speed-dial and BLF call-list features for phones in a presence service.
Examples
The following is sample output from the debug ephone blf command.
Router# debug ephone blfEPHONE BLF debugging is enabled*Sep 4 07:18:26.307: skinny_asnl_callback: subID 16 type 4*Sep 4 07:18:26.307: ASNL_RESP_NOTIFY_INDICATION*Sep 4 07:18:26.307: ephone-1[1]:ASNL notify indication message, feature index 4, subID [16]*Sep 4 07:18:26.307: ephone-1[1]:line status 6, subID [16]*Sep 4 07:18:26.307: ephone-1[1]:StationFeatureStatV2Message sent, status 2*Sep 4 07:18:26.307: skinny_asnl_callback: subID 23 type 4*Sep 4 07:18:26.307: ASNL_RESP_NOTIFY_INDICATION*Sep 4 07:18:26.307: ephone-2[2]:ASNL notify indication message, feature index 2, subID [23]*Sep 4 07:18:26.311: ephone-2[2]:line status 6, subID [23]*Sep 4 07:18:26.311: ephone-2[2]:StationFeatureStatV2Message sent, status 2*Sep 4 07:18:28.951: skinny_asnl_callback: subID 16 type 4*Sep 4 07:18:28.951: ASNL_RESP_NOTIFY_INDICATION*Sep 4 07:18:28.951: ephone-1[1]:ASNL notify indication message, feature index 4, subID [16]*Sep 4 07:18:28.951: ephone-1[1]:line status 1, subID [16]*Sep 4 07:18:28.951: ephone-1[1]:StationFeatureStatV2Message sent, status 1*Sep 4 07:18:28.951: skinny_asnl_callback: subID 23 type 4*Sep 4 07:18:28.951: ASNL_RESP_NOTIFY_INDICATION*Sep 4 07:18:28.951: ephone-2[2]:ASNL notify indication message, feature index 2, subID [23]*Sep 4 07:18:28.951: ephone-2[2]:line status 1, subID [23]*Sep 4 07:18:28.951: ephone-2[2]:StationFeatureStatV2Message sent, status 1Related Commands
debug ephone ccm-compatible
To display Cisco CallManager notification updates for calls between Cisco CallManager and Cisco CallManager Express, use the debug ephone ccm-compatible command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone ccm-compatible [mac-address mac-address]
no debug ephone ccm-compatible [mac-address mac-address]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays call flow notification information for all calls between Cisco CallManager and Cisco CallManager Express, but it is most useful for filtering out specific information for transfer and forward cases. For basic call information, use the debug ephone state command.
If you do not specify the mac-address keyword, the debug ephone ccm-compatible command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the no form of this command with the mac-address keyword.
Debugging can be enabled or disabled on any number of Cisco IP phones. Cisco IP phones that have debugging enabled are listed in the debug field of the show ephone command output. When debugging is enabled for a Cisco IP phone, debug output is displayed for all phone extensions (virtual voice ports) associated with that phone.
Examples
The following sample output displays call flow notifications between Cisco CallManager and Cisco CallManager Express:
Router# debug ephone ccm-compatible*May 1 04:30:02.650:ephone-2[2]:DtAlertingTone/DtHoldTone - mediaActive reset during CONNECT*May 1 04:30:02.654:ephone-2[2]:DtHoldTone - force media STOP state*May 1 04:30:02.654://93/xxxxxxxxxxxx/CCAPI/ccCallNotify:(callID=0x5D,nData->bitmask=0x00000007)*May 1 04:30:02.654://93/xxxxxxxxxxxx/VTSP:(50/0/3):-1:0:5/vtsp_process_event:vtsp:[50/0/3 (93), S_CONNECT, E_CC_SERVICE_MSG]*May 1 04:30:02.654://93/xxxxxxxxxxxx/VTSP:(50/0/3):-1:0:5/act_service_msg_down:.*May 1 04:30:02.658:dn_callerid_update DN 3 number= 12009 name= CCM7960 in state CONNECTED*May 1 04:30:02.658:dn_callerid_update (incoming) DN 3 info updated to*May 1 04:30:02.658:calling= 12009 called= 13003 origCalled=*May 1 04:30:02.658:callingName= CCM7960, calledName= , redirectedTo =*May 1 04:30:02.658:ephone-2[2][SEP003094C2999A]:refreshDisplayLine for line 1DN 3 chan 1*May 1 04:30:03.318:ephone-2[2]:DisplayCallInfo incoming call*May 1 04:30:03.318:ephone-2[2]:Call Info DN 3 line 1 ref 24 called 13003 calling 12009 origcalled 13003 calltype 1*May 1 04:30:03.318:ephone-2[2]:Original Called Name UUT4PH3*May 1 04:30:03.318:ephone-2[2]:CCM7960 calling*May 1 04:30:03.318:ephone-2[2]:UUT4PH3Related Commands
debug ephone detail
To set detail debugging for the Cisco IP phone, use the debug ephone detail command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone detail [mac-address mac-address]
no debug ephone detail [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone detail command includes the error and state levels.
If the mac-address keyword is not used, the debug ephone detail command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following is sample output of detail debugging of the Cisco IP phone with MAC address 0030.94c3.8724. The sample is an excerpt of some of the activities that takes place during call setup, connected state, active call, and the call being disconnected.
Router# debug ephone detail mac-address 0030.94c3.8724Ephone detail debugging is enabled1d04h: ephone-1[1]:OFFHOOK..1d04h: Skinny Call State change for DN 1 SIEZE..1d04h: ephone-1[1]:SetCallState line 1 DN 1 TsOffHook..1d04h: ephone-1[1]:SetLineLamp 1 to ON..1d04h: ephone-1[1]:KeypadButtonMessage 5..1d04h: ephone-1[1]:KeypadButtonMessage 0..1d04h: ephone-1[1]:KeypadButtonMessage 0..1d04h: ephone-1[1]:KeypadButtonMessage 2..1d04h: ephone-1[1]:Store ReDial digit: 5002.SkinnyTryCall to 5002 instance 1..1d04h: ephone-1[1]:Store ReDial digit: 50021d04h: ephone-1[1]:SkinnyTryCall to 5002 instance 1..1d04h: Skinny Call State change for DN 1 ALERTING..1d04h: ephone-1[1]:SetCallState line 1 DN 1 TsRingOut..1d04h: ephone-1[1]:SetLineLamp 1 to ON1d04h: SetCallInfo calling dn 1 dn 1calling [5001] called [5002]..1d04h: ephone-1[1]: Jane calling1d04h: ephone-1[1]: Jill..1d04h: SkinnyUpdateDnState by EFXS_RING_GENERATEfor DN 2 to state RINGING..1d04h: SkinnyGetCallState for DN 2 CONNECTED..1d04h: ephone-1[1]:SetLineLamp 3 to ON1d04h: ephone-1[1]:UpdateCallState DN 1 state 4 calleddn 2..1d04h: Skinny Call State change for DN 1 CONNECTED..1d04h: ephone-1[1]:OpenReceive DN 1 codec 4:G711Ulaw64k duration 10 ms bytes 80..1d04h: ephone-1[1]:OpenReceiveChannelAck 1.2.172.21 port=201801d04h: ephone-1[1]:Outgoing calling DN 1 Far-ephone-2 called DN 21d04h: SkinnyGetCallState for DN 1 CONNECTED..1d04h: ephone-1[1]:SetCallState line 3 DN 2 TsOnHook..1d04h: ephone-1[1]:SetLineLamp 3 to OFF..1d04h: ephone-1[1]:SetCallState line 1 DN 1 TsOnHook..1d04h: ephone-1[1]:Clean Up Speakerphone state1d04h: ephone-1[1]:SpeakerPhoneOnHook1d04h: ephone-1[1]:Clean up activeline 11d04h: ephone-1[1]:StopTone sent to ephone1d04h: ephone-1[1]:Clean Up phone offhook state1d04h: SkinnyGetCallState for DN 1 IDLE1d04h: called DN -1, calling DN -1 phone -11d04h: ephone-1[1]:SetLineLamp 1 to OFF1d04h: UnBinding ephone-1 from DN 11d04h: UnBinding called DN 2 from DN 11d04h: ephone-1[1]:ONHOOK1d04h: ephone-1[1]:SpeakerPhoneOnHook1d04h: ephone-1[1]:ONHOOK NO activeline.Related Commands.
debug ephone error
To set error debugging for the Cisco IP phone, use the debug ephone error command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone error [mac-address mac-address]
no debug ephone error [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone error command cancels debugging at the detail and state level.
If the mac-address keyword is not used, the debug ephone error command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following is sample output of error debugging for the Cisco IP phone with MAC address 0030.94c3.8724:
Router# debug ephone error mac-address 0030.94c3.8724EPHONE error debugging is enabledsocket [2] send ERROR 11Skinny Socket [2] retry failureRelated Commands
debug ephone extension-assigner
To display status messages produced by the extension assigner application, use the debug ephone extension-assigner command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone extension-assigner
no debug ephone extension-assigner
Syntax Description
This command has no arguments or keywords.
Command Default
Debug ephone extension-assigner is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays status messages produced by the extension assigner application, including messages related to the functions performed by the following Tcl commands:
•
phone query—Verifies whether the ephone tag has been assigned a MAC address.
•
•
Before using this command, you must load the Tcl script for the extension assigner application.
Examples
The following is sample output of extension assigner debugging as the extension assigner application queries phones for their status and issues commands to assign or unassign extension numbers.
*Jun 9 19:08:10.627: ephone_query: inCallID=47, tag=4, ephone_tag=4*Jun 9 19:08:10.627: extAssigner_IsEphoneMacPreset: ephone_tag = 4, ipKeyswitch.max_ephones = 96*Jun 9 19:08:10.627: extAssigner_IsEphoneMacPreset: ephone_ptr->mac_addr_str = 000B46BDE075, MAC_EXT_RESERVED_VALUE = 02EAEAEA0000*Jun 9 19:08:10.627: SkinnyGetActivePhoneIndexFromCallid: callID = 47*Jun 9 19:08:10.627: SkinnyGetActivePhoneIndexFromCallid: vdbPtr->physical_interface_type (26); CV_VOICE_EFXS (26)*Jun 9 19:08:10.627: SkinnyGetActivePhoneIndexFromCallid: vdbPtr->type (6); CC_IF_TELEPHONY (6)*Jun 9 19:08:10.627: SkinnyGetActivePhoneIndexFromCallid: htsp->sig_type (26); CV_VOICE_EFXS (26)*Jun 9 19:08:10.627: SkinnyGetActivePhoneIndexFromCallid: dn = 4, chan = 1*Jun 9 19:08:10.627: ephone_query: EXTASSIGNER_RC_SLOT_ASSIGNED_TO_CALLING_PHONE*Jun 9 19:08:22.763: ephone_unassign: inCallID=47, tag=4, ephone_tag=4*Jun 9 19:08:22.763: extAssigner_IsEphoneMacPreset: ephone_tag = 4, ipKeyswitch.max_ephones = 96*Jun 9 19:08:22.763: extAssigner_IsEphoneMacPreset: ephone_ptr->mac_addr_str = 000B46BDE075, MAC_EXT_RESERVED_VALUE = 02EAEAEA000*Jun 9 19:08:22.763: is_ephone_auto_assigned: button-1 dn_tag=4*Jun 9 19:08:22.763: is_ephone_auto_assigned: NO*Jun 9 19:08:22.763: SkinnyGetActivePhoneIndexFromCallid: callID = 47*Jun 9 19:08:22.763: SkinnyGetActivePhoneIndexFromCallid: vdbPtr->physical_interface_type (26); CV_VOICE_EFXS (26)*Jun 9 19:08:22.767: SkinnyGetActivePhoneIndexFromCallid: vdbPtr->type (6); CC_IF_TELEPHONY (6)*Jun 9 19:08:22.767: SkinnyGetActivePhoneIndexFromCallid: htsp->sig_type (26); CV_VOICE_EFXS (26)*Jun 9 19:08:22.767: SkinnyGetActivePhoneIndexFromCallid: dn = 4, chan = 1*Jun 9 19:08:29.795: ephone-4[8]:fStationOnHookMessage: Extension Assigner request restart, cmd=2, new mac=02EAEAEA0004, ephone_tag=4*Jun 9 19:08:30.063: %IPPHONE-6-UNREGISTER_NORMAL: ephone-4:SEP000B46BDE075 IP:5.5.0.1 Socket:8 DeviceType:Phone has unregistered normally.*Jun 9 19:08:30.063: ephone-4[8][SEP000B46BDE075]:extAssigner_assign: new mac=02EAEAEA0004, ephone-tag=4*Jun 9 19:08:30.063: extAssigner_simple_assign: mac=02EAEAEA0004, tag=4*Jun 9 19:08:30.063: ephone_updateCNF: update cnf_file ephone_tag=4*Jun 9 19:08:30.063: extAssigner_assign: restart again (mac=02EAEAEA0004) ephone_tag=4*Jun 9 19:08:30.131: %IPPHONE-6-REG_ALARM: 23: Name=SEP000B46BDE075 Load=8.0(2.0) Last=Reset-Restart*Jun 9 19:08:30.135: %IPPHONE-6-REGISTER_NEW: ephone-7:SEP000B46BDE075 IP:5.5.0.1 Socket:10 DeviceType:Phone has registered.*Jun 9 19:08:30.503: %IPPHONE-6-UNREGISTER_NORMAL: ephone-7:SEP000B46BDE075 IP:5.5.0.1 Socket:10 DeviceType:Phone has unregistered normally.*Jun 9 19:08:43.127: %IPPHONE-6-REG_ALARM: 22: Name=SEP000B46BDE075 Load=8.0(2.0) Last=Reset-Reset*Jun 9 19:08:43.131: %IPPHONE-6-REGISTER: ephone-7:SEP000B46BDE075 IP:5.5.0.1 Socket:13 DeviceType:Phone has registered.Related Commands
debug ephone state
Sets state debugging for Cisco IP phones.
debug voip application script
Displays status messages produced by voice over IP application scripts.
debug ephone keepalive
To set keepalive debugging for the Cisco IP phone, use the debug ephone keepalive command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone keepalive [mac-address mac-address]
no debug ephone keepalive [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone keepalive command sets keepalive debugging.
If the mac-address keyword is not used, the debug ephone keepalive command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following is sample output of the keepalive status for the Cisco IP phone with MAC address 0030.94C3.E1A8:
Router# debug ephone keepalive mac-address 0030.94c3.E1A8EPHONE keepalive debugging is enabled for phone 0030.94C3.E1A81d05h: ephone-1 Set interface FastEthernet0/0 ETHERNET1d05h: ephone-1[1]:Keepalive socket[1] SEP003094C3E1A81d05h: ephone-1 Set interface FastEthernet0/0 ETHERNET1d05h: ephone-1[1]:Keepalive socket[1] SEP003094C3E1A81d05h: Skinny Checking for stale sockets1d05h: ephone-1 Set interface FastEthernet0/0 ETHERNET1d05h: ephone-1[1]:Keepalive socket[1] SEP003094C3E1A81d05h: ephone-1 Set interface FastEthernet0/0 ETHERNET1d05h: ephone-1[1]:Keepalive socket[1] SEP003094C3E1A81d05h: Skinny active socket list (3/96): 1 2 4Related Commands
debug ephone loopback
To set debugging for loopback calls, use the debug ephone loopback command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ephone loopback [mac-address mac-address]
no debug ephone loopback [mac-address mac-address]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone loopback command sets debugging for incoming and outgoing calls on all loopback-dn pairs or on the single loopback-dn pair that is associated with the IP phone that has the MAC address specified in this command.
If you enable the debug ephone loopback command and the debug ephone pak command at the same time, the output displays packet debug output for the voice packets that are passing through the loopback-dn pair.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with that Cisco IP phone.
Examples
The following example contains two excerpts of output for a call that is routed through a loopback. The first excerpt is output from the show running-config command and displays the loopback configuration used for this example. The second excerpt is output from the debug ephone loopback command.
Router# show running-config...ephone-dn 14number 1514!!ephone-dn 42number 17181..loopback-dn 43 forward 4no huntstop!!ephone-dn 43number 19115..loopback-dn 42 forward 4!...A loopback call is started. An incoming call to 1911514 (ephone-dn 43) uses the loopback pair of ephone-dns to become an outgoing call to extension 1514. The number in the outgoing call has only four digits because the loopback-dn command specifies forwarding of four digits. The outgoing call uses ephone-dn 42, which is also specified in the loopback-dn command under ephone-dn 43. When the extension at 1514 rings, the following debug output is displayed:
Router# debug ephone loopbackMar 7 00:57:25.376:Pass processed call info to special DN 43 chan 1Mar 7 00:57:25.376:SkinnySetCallInfoLoopback DN 43 state IDLE to DN 42 state IDLEMar 7 00:57:25.376:Called Number = 1911514 Called Name =Mar 7 00:57:25.376:Calling Number = 8101 Calling Name =orig Called Number =Copy Caller-ID info from Loopback DN 43 to DN 42Mar 7 00:57:25.376:DN 43 Forward 1514Mar 7 00:57:25.376:PredictTarget match 1514 DN 14 is idleMar 7 00:57:25.380:SkinnyUpdateLoopbackState DN 43 state RINGING calledDn -1Mar 7 00:57:25.380:Loopback DN 42 state IDLEMar 7 00:57:25.380:Loopback DN 43 calledDN -1 callingDn -1 G711Ulaw64kMar 7 00:57:25.380:SkinnyUpdateLoopbackState DN 43 to DN 42 signal OFFHOOKMar 7 00:57:25.380:SetDnCodec Loopback DN 43 codec 4:G711Ulaw64k vad 0 size 160Mar 7 00:57:25.380:SkinnyDnToneLoopback DN 42 state SIEZE to DN 43 state RINGINGMar 7 00:57:25.380:TONE ON DtInsideDialToneMar 7 00:57:25.380:SkinnyDnToneLoopback called number = 1911514Mar 7 00:57:25.380:DN 43 Forward 1514Mar 7 00:57:25.380:DN 42 from 43 Dial 1514Mar 7 00:57:25.384:SkinnyDnToneLoopback DN 42 state ALERTING to DN 43 state RINGINGMar 7 00:57:25.384:TONE OFFMar 7 00:57:25.384:SkinnyDnToneLoopback DN 42 state ALERTING to DN 43 state RINGINGMar 7 00:57:25.384:TONE OFFMar 7 00:57:25.384:SkinnyUpdateLoopbackState DN 42 state ALERTING calledDn -1Mar 7 00:57:25.384:Loopback DN 43 state RINGINGMar 7 00:57:25.384:Loopback Alerting DN 42 calledDN -1 callingDn -1 G711Ulaw64kMar 7 00:57:25.388:ephone-5[7]:DisplayCallInfo incoming callMar 7 00:57:25.388:SkinnyDnToneLoopback DN 42 state ALERTING to DN 43 state RINGINGMar 7 00:57:25.388:TONE ON DtAlertingToneMar 7 00:57:25.388:SkinnyDnToneLoopback DN 42 to DN 43 deferred alerting by DtAlertingToneMar 7 00:57:25.388:EFXS_STATE_ONHOOK_RINGING already done for DN 43 chan 1Mar 7 00:57:25.388:Set prog_ind 0 for DN 42 chan 1...When extension 1514 answers the call, the following debug output is displayed:
...Mar 7 00:57:32.158:SkinnyDnToneLoopback DN 42 state ALERTING to DN 43 state RINGINGMar 7 00:57:32.158:TONE OFFMar 7 00:57:32.158:dn_support_g729 true DN 42 chan 1 (loopback)Mar 7 00:57:32.158:SetDnCodec Loopback DN 43 codec 4:G711Ulaw64k vad 0 size 160Mar 7 00:57:32.158:SkinnyUpdateLoopbackState DN 42 state CALL_START calledDn 14Mar 7 00:57:32.158:Loopback DN 43 state RINGINGMar 7 00:57:32.158:SkinnyUpdateLoopbackState DN 42 to DN 43 deferred alerting by CALL_START already sentMar 7 00:57:32.158:SetDnCodec reassert defer_start for DN 14 chan 1Mar 7 00:57:32.158:Delay media until loopback DN 43 is readyMar 7 00:57:32.158:SkinnyUpdateLoopbackCodec check for DN 14 chan 1 from DN 42 loopback DN 43Mar 7 00:57:32.158:SkinnyUpdateLoopbackCodec DN chain is 14 1, other=42, lb=43, far=-1 1, final=43 1Mar 7 00:57:32.158:SkinnyUpdateLoopbackCodec DN 14 chan 1 DN 43 chan 1 codec 4 matchMar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 42 state CONNECTED calledDn 14Mar 7 00:57:32.162:Loopback DN 43 state RINGINGMar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 42 to DN 43 signal ANSWERMar 7 00:57:32.162:Loopback DN 42 calledDN 14 callingDn -1 G711Ulaw64kMar 7 00:57:32.162:Loopback DN 43 calledDN -1 callingDn -1 incoming G711Ulaw64kMar 7 00:57:32.162:ephone-5[7][SEP000DBDBEF37D]:refreshDisplayLine for line 1 DN 14 chan 1Mar 7 00:57:32.162:dn_support_g729 true DN 43 chan 1 (loopback)Mar 7 00:57:32.162:SetDnCodec Loopback DN 42 codec 4:G711Ulaw64k vad 0 size 160Mar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 43 state CALL_START calledDn -1Mar 7 00:57:32.162:Loopback DN 42 state CONNECTEDMar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 43 has defer_dn 14 chan 1 setMar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 43 has defer_dn 14 chan 1:-invoke SkinnyOpenReceiveMar 7 00:57:32.162:SkinnyUpdateLoopbackCodec check for DN 14 chan 1 from DN 42 loopback DN 43Mar 7 00:57:32.162:SkinnyUpdateLoopbackCodec DN chain is 14 1, other=42, lb=43, far=-1 1, final=43 1Mar 7 00:57:32.162:SkinnyUpdateLoopbackCodec DN 14 chan 1 DN 43 chan 1 codec 4 matchMar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 43 state CALL_START calledDn -1Mar 7 00:57:32.162:Loopback DN 42 state CONNECTEDMar 7 00:57:32.454:SkinnyGetDnAddrInfo DN 43 LOOPBACKupdate media address to 10.0.0.6 25390 from DN 14Mar 7 00:57:33.166:ephone-5[7]:DisplayCallInfo incoming call...When the called extension, 1514, goes back on-hook, the following debug output is displayed:
...Mar 7 00:57:39.224:Loopback DN 42 disc reason 16 normal state CONNECTEDMar 7 00:57:39.224:SkinnyUpdateLoopbackState DN 42 state CALL_END calledDn -1Mar 7 00:57:39.224:Loopback DN 43 state CONNECTEDMar 7 00:57:39.224:SkinnyUpdateLoopbackState DN 42 to DN 43 signal ONHOOKMar 7 00:57:39.236:SkinnyDnToneLoopback DN 42 state IDLE to DN 43 state IDLEMar 7 00:57:39.236:TONE OFFMar 7 00:57:39.236:SkinnyDnToneLoopback DN 43 state IDLE to DN 42 state IDLEMar 7 00:57:39.236:TONE OFFTable 3 describes the significant fields shown in the display.
Related Commands
debug ephone message
To enable message tracing between ephones, use the debug ephone message command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone message [detail]
no debug ephone message
Syntax Description
detail
(Optional) Displays signaling connection control protocol (SCCP) messages sent and received between ephones in the Cisco Unified CallManager Express (Cisco Unified CME) system.
Command Modes
Privileged EXEC
Command History
12.4(4)XC
This command was introduced.
12.4(9)T
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
The debug ephone message command enables message tracing between ephones.
The debug ephone command debugs all ephones associated with a Cisco Unified CME router.
You can enable or disable debugging on any number of ephones. To see the ephones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a ephone, the debug output is displayed for the directory numbers associated with the ephone.
Examples
The following is sample output for the debug ephone message command for ephones:
Router# debug ephone messageEPHONE skinny message debugging is enabled*Jul 17 12:12:54.883: Received message from phone 7, SkinnyMessageID = StationKeepAliveMessageID*Jul 17 12:12:54.883: Sending message to phone 7, SkinnyMessageID = StationKeepAliveAckMessageIDThe following command disables ephone message debugging:
Router# no debug ephone messageEPHONE skinny message debugging is disabledRelated Commands
debug ephone moh
To set debugging for music on hold (MOH), use the debug ephone moh command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ephone moh [mac-address mac-address]
no debug ephone moh [mac-address mac-address]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Always use the no moh command before modifying or replacing the MOH file in Flash memory.
When a configuration using the multicast moh command is used and the debug ephone moh command is enabled, if you delete or modify the MOH file in the router's Flash memory, the debug output can be excessive and can flood the console. The multicast MOH configuration should be removed before using the no moh command when the debug ephone moh command is enabled.
Examples
The following sample output shows MOH activity prior to the first MOH session. Note that if you enable multicast MOH, that counts as the first session.
Router# debug ephone mohMar 7 00:52:33.817:MOH AU fileMar 7 00:52:33.817:skinny_open_moh_play set type to 3Mar 7 00:52:33.825: 2E73 6E64 0000 0018 0007 3CCA 0000 0001Mar 7 00:52:33.825: 0000 1F40 0000 0001 FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825:Mar 7 00:52:33.825:AU file processing Found .sndMar 7 00:52:33.825:AU file data start at 24 end at 474338Mar 7 00:52:33.825:AU file codec Media_Payload_G711Ulaw64kMar 7 00:52:33.825:MOH read file header type AU start 24 end 474338Mar 7 00:52:33.825:MOH pre-read block 0 at write-offset 0 from 24Mar 7 00:52:33.833:MOH pre-read block 1 at write-offset 8000 from 8024Mar 7 00:52:33.845:Starting read server with play-offset 0 write-offset 16000Table 4 describes the significant fields shown in the display.
Related Commands
moh (telephony-service)
Generates an audio stream from a file for MOH in a Cisco CME system.
multicast moh
Uses the MOH audio stream as a multicast source in a Cisco CME system.
debug ephone mwi
To set message waiting indication (MWI) debugging for the Cisco IOS Telephony Service router, use the debug ephone mwi command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone mwi
no debug ephone mwi
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone mwi command sets message waiting indication debugging for the Cisco IOS Telephony Service router. Because the MWI protocol activity is not specific to any individual Cisco IP phone, setting the MAC address keyword qualifier for this command is not useful.
Note
Examples
The following is sample output of the message waiting indication status for the Cisco IOS Telephony Service router:
Router# debug ephone mwiRelated Commands
debug ephone pak
To provide voice packet level debugging and to print the contents of one voice packet in every 1024 voice packets, use the debug ephone pak command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone pak [mac-address mac-address]
no debug ephone pak [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone pak command provides voice packet level debugging and prints the contents of one voice packet in every 1024 voice packets.
If the mac-address keyword is not used, the debug ephone pak command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following is sample output of packet debugging for the Cisco IP phone with MAC address 0030.94c3.8724:
Router# debug ephone pak mac-address 0030.94c3.8724EPHONE packet debugging is enabled for phone 0030.94c3.872401:29:14: ***ph_xmit_ephone DN 3 tx_pkts 5770 dest=10.2.1.1 orig len=32pakcopy=0 discards 27 ip_enctype 0 0 last discard: unsupported payload type01:29:14: to_skinny_duration 130210 offset -30 last -40 seq 0 adj 001:29:14: IP: 45B8 003C 0866 0000 3F11 3F90 2800 0001 0A02 010101:29:14: TTL 63 TOS B8 prec 501:29:14: UDP: 07D0 6266 0028 000001:29:14: sport 2000 dport 25190 length 40 checksum 001:29:14: RTP: 8012 16AF 9170 6409 0E9F 000101:29:14: is_rtp:1 is_frf11:0 vlen:0 delta_t:160 vofr1:0 vofr2:0scodec:11 rtp_bits:8012 rtp_codec:18 last_bad_payload 1901:29:14: vencap FAILED01:29:14: PROCESS SWITCH01:29:15: %SYS-5-CONFIG_I: Configured from console by console01:29:34: ***SkinnyPktIp DN 3 10.2.1.1 to 40.0.0.1 pkts 4880 FAST sw01:29:34: from_skinny_duration 15091001:29:34: nw 3BBC2A8 addr 3BBC2A4 mac 3BBC2A4 dg 3BBC2C4 dgs 2A01:29:34: MAC: 1841 080001:29:34: IP: 45B8 0046 682E 0000 3E11 E0BD 0A02 0101 2800 000101:29:34: TTL 62 TOS B8 prec 501:29:34: UDP: 6266 07D0 0032 000001:29:34: sport 25190 dport 2000 length 50 checksum 001:29:34: RTP: 8012 55FF 0057 8870 3AF4 C39401:29:34: RTP: rtp_bits 8012 seq 55FF ts 578870 ssrc 3AF4C39401:29:34: PAYLOAD:01:29:34: 1409 37C9 54DE 449C 3B42 0446 3AAB 182E01:29:34: 56BC 5184 58E5 56D3 13BE 44A7 B8C401:29:34:01:29:37: ***ph_xmit_ephone DN 3 tx_pkts 6790 dest=10.2.1.1 orig len=32pakcopy=0 discards 31 ip_enctype 0 0 last discard: unsupported payload type01:29:37: to_skinny_duration 153870 offset -150 last -40 seq 0 adj 001:29:37: IP: 45B8 003C 0875 0000 3F11 3F81 2800 0001 0A02 010101:29:37: TTL 63 TOS B8 prec 501:29:37: UDP: 07D0 6266 0028 000001:29:37: sport 2000 dport 25190 length 40 checksum 001:29:37: RTP: 8012 1AAF 9173 4769 0E9F 000101:29:37: is_rtp:1 is_frf11:0 vlen:0 delta_t:160 vofr1:0 vofr2:0Related Commands
debug ephone qov
To display quality of voice (QOV) statistics for calls when preset limits are exceeded, use the debug ephone qov command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ephone qov [mac-address mac-address]
no debug ephone qov [mac-address mac-address]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Once enabled, the debug ephone qov command produces output only when the QOV statistics reported by phones exceed preset limits. Phones are polled every few seconds for QOV statistics on VoIP calls only, not on local PSTN calls. An output report is produced when limits are surpassed for either or both of the following:
•
•
To receive a QOV report at the end of each call regardless of whether the QOV limits have been exceeded, enable the debug ephone alarm command in addition to the debug ephone qov command.
The debug ephone statistics command displays the raw statistics that are polled from phones and used to generate QOV reports.
Examples
The following sample output describes QOV statistics for a call on ephone 5:
Router# debug ephone qovMar 7 00:54:57.329:ephone-5[7]:QOV DN 14 chan 1 (1514) ref 4 called=1514 calling=8101Mar 7 00:54:57.329:ephone-5[7][SEP000DBDBEF37D]:Lost 91 Jitter 0 Latency 0Mar 7 00:54:57.329:ephone-5[7][SEP000DBDBEF37D]:previous Lost 0 Jitter 0 Latency 0Mar 7 00:54:57.329:ephone-5[7][SEP000DBDBEF37D]:Router sent 1153 pkts, current phone got 1141received by all (shared) phones 0Mar 7 00:54:57.329:ephone-5[7]:worst jitter 0 worst latency 0Mar 7 00:54:57.329:ephone-5[7]:Current phone sent 1233 packetsMar 7 00:54:57.329:ephone-5[7]:Signal Level to phone 3408 (-15 dB) peak 3516 (-15 dB)Table 5 describes the significant fields shown in the display.
Related Commands
debug ephone alarm
Displays alarm messages for IP phones.
debug ephone statistics
Displays call statistics for IP phones.
debug ephone raw
To provide raw low-level protocol debugging display for all Skinny Client Control Protocol (SCCP) messages, use the debug ephone raw command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone raw [mac-address mac-address]
no debug ephone raw [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone raw command provides raw low-level protocol debug display for all SCCP messages. The debug display provides byte level display of Skinny TCP socket messages.
If the mac-address keyword is not used, the debug ephone raw command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following is sample output of raw protocol debugging for the Cisco IP phone with MAC address 0030.94c3.E1A8:
Router# debug ephone raw mac-address 0030.94c3.E1A8EPHONE raw protocol debugging is enabled for phone 0030.94C3.E1A81d05h: skinny socket received 4 bytes on socket [1]0 0 0 01d05h:1d05h: SkinnyMessageID = 01d05h: skinny send 4 bytes4 0 0 0 0 0 0 0 0 1 0 01d05h: socket [1] sent 12 bytes OK (incl hdr) for ephone-(1)1d06h: skinny socket received 4 bytes on socket [1]0 0 0 01d06h:1d06h: SkinnyMessageID = 01d06h: skinny send 4 bytes4 0 0 0 0 0 0 0 0 1 0 01d06h: socket [1] sent 12 bytes OK (incl hdr) for ephone-(1)Related Commands
debug ephone register
To set registration debugging for the Cisco IP phone, use the debug ephone register command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone register [mac-address mac-address]
no debug ephone register [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone register command sets registration debugging for the Cisco IP phones.
If the mac-address keyword is not used, the debug ephone register command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following is sample output of registration debugging for the Cisco IP phone with MAC address 0030.94c3.8724:
Router# debug ephone register mac-address 0030.94c3.8724Ephone registration debugging is enabled1d06h: New Skinny socket accepted [1] (2 active)1d06h: sin_family 2, sin_port 50778, in_addr 10.1.0.211d06h: skinny_add_socket 1 10.1.0.21 507781d06h: ephone-(1)[1] StationRegisterMessage (2/3/12) from 10.1.0.211d06h: ephone-(1)[1] Register StationIdentifier DeviceName SEP003094C3E1A81d06h: ephone-(1)[1] StationIdentifier Instance 1 deviceType 71d06h: ephone-1[-1]:stationIpAddr 10.1.0.211d06h: ephone-1[-1]:maxStreams 01d06h: ephone-(1) Allow any Skinny Server IP address 10.1.0.6...1d06h: ephone-1[1]:RegisterAck sent to ephone 1: keepalive period 30.Related Commands
debug ephone sccp-state
To set debugging for the SCCP call state, use the debug ephone sccp-state command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone sccp-state [mac-address mac-address]
no debug ephone sccp-state [mac-address mac-address]
Syntax Description
Command Default
Debugging is not enabled for SCCP state.
Command Modes
Privileged EXEC
Command History
12.4(4)XC
This command was introduced.
12.4(9)T
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
This command is used with Cisco Unified CallManager Express (Cisco Unified CME).
This command outputs only the debug messages that correspond to SCCP messages sent to IP phones to indicate the SCCP phone call state, such as RingIn, OffHook, Connected, and OnHook. These debug messages are also included in the output for the debug ephone detail command among other information.
Examples
The following example sets SCCP state debugging for one Cisco Unified CME phone with the MAC address of 678B.AEF9.DAB5.
Router# debug ephone sccp-state mac-address 678B.AEF9.DAB5EPHONE SCCP state message debugging is enabledfor ephones 000B.BEF9.DFB5*Mar 8 06:38:45.863: %ISDN-6-CONNECT: Interface Serial2/0/0:22 is now connected to 4085254871 unknown*Mar 8 06:38:50.487: ephone-2[13]:SetCallState line 4 DN 60(60) chan 1 ref 100 TsRingIn *Mar 8 06:38:52.399: ephone-2[13]:SetCallState line 4 DN 60(-1) chan 1 ref 100 TsOffHook *Mar 8 06:38:52.399: ephone-2[13]:SetCallState line 4 DN 60(-1) chan 1 ref 100 TsConnected*Mar 8 06:38:58.415: %ISDN-6-CONNECT: Interface Serial2/0/0:22 is now connected to 4085254871 unknown*Mar 8 06:38:59.963: ephone-2[13]:SetCallState line 4 DN 60(-1) chan 1 ref 100 TsOnHook *Mar 8 06:38:59.975: %ISDN-6-DISCONNECT: Interface Serial2/0/0:22 disconnected from 4085254871 , call lasted 7 secondsRelated Commands
debug ephone detail
Sets detail debugging for one or all Cisco Unified IP phones.
debug ephone state
To set state debugging for the Cisco IP phone, use the debug ephone state command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone state [mac-address mac-address]
no debug ephone state [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone state command sets state debugging for the Cisco IP phones.
If the mac-address keyword is not used, the debug ephone state command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following is sample output of state debugging for the Cisco IP phone with MAC address 0030.94c3.E1A8:
Router# debug ephone state mac-address 0030.94c3.E1A8EPHONE state debugging is enabled for phone 0030.94C3.E1A81d06h: ephone-1[1]:OFFHOOK1d06h: ephone-1[1]:SIEZE on activeline 01d06h: ephone-1[1]:SetCallState line 1 DN 1 TsOffHook1d06h: ephone-1[1]:Skinny-to-Skinny call DN 1 to DN 2 instance 11d06h: ephone-1[1]:SetCallState line 1 DN 1 TsRingOut1d06h: ephone-1[1]:Call Info DN 1 line 1 ref 158 called 5002 calling 50011d06h: ephone-1[1]: Jane calling1d06h: ephone-1[1]: Jill1d06h: ephone-1[1]:SetCallState line 3 DN 2 TsRingIn1d06h: ephone-1[1]:Call Info DN 2 line 3 ref 159 called 5002 calling 50011d06h: ephone-1[1]: Jane calling1d06h: ephone-1[1]: Jill1d06h: ephone-1[1]:SetCallState line 3 DN 2 TsCallRemoteMultiline1d06h: ephone-1[1]:SetCallState line 1 DN 1 TsConnected1d06h: ephone-1[1]:OpenReceive DN 1 codec 4:G711Ulaw64k duration 10 ms bytes 801d06h: ephone-1[1]:OpenReceiveChannelAck 1.2.172.21 port=240101d06h: ephone-1[1]:StartMedia 1.2.172.22 port=246121d06h: DN 1 codec 4:G711Ulaw64k duration 10 ms bytes 801d06h: ephone-1[1]:CloseReceive1d06h: ephone-1[1]:StopMedia1d06h: ephone-1[1]:SetCallState line 3 DN 2 TsOnHook1d06h: ephone-1[1]:SetCallState line 1 DN 1 TsOnHook1d06h: ephone-1[1]:SpeakerPhoneOnHook1d06h: ephone-1[1]:ONHOOK1d06h: ephone-1[1]:SpeakerPhoneOnHook1d06h: SkinnyReportDnState DN 1 ONHOOKRelated Commands
debug ephone statistics
To set call statistics debugging for the Cisco IP phone, use the debug ephone statistics command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone statistics [mac-address mac-address]
no debug ephone statistics [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone statistics command provides a debug monitor display of the periodic messages from the Cisco IP phone to the router. These include transmit-and-receive packet counts and an estimate of drop packets. The call statistics can also be displayed for live calls using the show ephone command.
If the mac-address keyword is not used, the debug ephone statistics command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following is sample output of statistics debugging for the Cisco IP phone with MAC address 0030.94C3.E1A8:
Router# debug ephone statistics mac-address 0030.94C3.E1A8EPHONE statistics debugging is enabled for phone 0030.94C3.E1A81d06h: Clear Call Stats for DN 1 call ref 1621d06h: Clear Call Stats for DN 1 call ref 1621d06h: Clear Call Stats for DN 1 call ref 1621d06h: Clear Call Stats for DN 2 call ref 1631d06h: ephone-1[1]:GetCallStats line 1 ref 162 DN 1: 50011d06h: ephone-1[1]:Call Stats for line 1 DN 1 5001 ref 1621d06h: ephone-1[1]:TX Pkts 0 bytes 0 RX Pkts 0 bytes 01d06h: ephone-1[1]:Pkts lost 4504384 jitter 0 latency 01d06h: ephone-1[1]:Src 0.0.0.0 0 Dst 0.0.0.0 0 bytes 80 vad 0 G711Ulaw64k1d06h: ephone-1[1]:GetCallStats line 1 ref 162 DN 1: 50011d06h: STATS: DN 1 Packets Sent 01d06h: STATS: DN 2 Packets Sent 01d06h: ephone-1[1]:Call Stats found DN -1 from Call Ref 1621d06h: ephone-1[1]:Call Stats for line 0 DN -1 5001 ref 1621d06h: ephone-1[1]:TX Pkts 275 bytes 25300 RX Pkts 275 bytes 253001d06h: ephone-1[1]:Pkts lost 0 jitter 0 latency 0Related Commands
debug ephone video
To set video debugging for ephones, use the debug ephone video command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone video
no debug ephone video
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging is disabled for ephone video.
Command Modes
Privileged EXEC
Command History
12.4(4)XC
This command was introduced.
12.4(9)T
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
The debug ephone video command sets ephone video traces, which provide information about different video states for the call, including video capabilities selection, start, and stop.
The debug ephone command debugs all ephones that are registered to the Cisco Unified CallManager Express (Cisco Unified CME) system.
You can enable or disable debugging on any number of ephones. To see the ephones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a ephone, the debug output is displayed for the directory numbers associated with the ephone.
Examples
The following is sample output for the debug ephone video command for ephones:
Router# debug ephone video*Mar 13 16:10:02.703: SkinnyVideoCodecMatch_Caps2Caps: match capability: tx_idxcap = 4, tx_idxpref = 3,*Mar 13 16:10:02.703: rx_idxcap = 0, rx_idxpref = 0, videoBitRate = 7040 tx_mpi = 1*Mar 13 16:10:04.711: ephone-19[1][SEPFFFA00000019]:checkToOpenMultiMedia: dn=19, chan=1*Mar 13 16:10:04.711: ephone-19[1]:skinnyDP[19].s2s = 0*Mar 13 16:10:04.711: ephone-19[1]:s2s is not set - hence not video capable*Mar 13 16:10:04.719: ephone-19[1][SEPFFFA00000019]:SkinnyStartMultiMediaTransmission: chan 1 dn 19*Mar 13 16:10:04.723: ephone-19[1]:Accept OLC and open multimedia channel*Mar 13 16:10:04.723: ephone-19[1][SEPFFFA00000019]:SkinnyOpenMultiMediaReceiveChannel: dn 19 chan 1*Mar 13 16:10:04.967: ephone-19[1][SEPFFFA00000019]:fStationOpenReceiveChannelAckMessage: MEDIA_DN 19 MEDIA_CHAN 1*Mar 13 16:10:04.967: ephone-19[1]:fStationOpenMultiMediaReceiveChannelAckMessage:*Mar 13 16:10:04.967: ephone-19[1]:Other_dn == -1sk3745-2#*Mar 13 16:10:14.787: ephone-19[1]:SkinnyStopMedia: Stop Multimedia*Mar 13 16:10:14.787: ephone-19[1][SEPFFFA00000019]:SkinnyCloseMultiMediaReceiveChannel: passThruPartyID = 0, callReference = 23*Mar 13 16:10:14.787: ephone-19[1]:SkinnyStopMultiMediaTransmission: line 1 chan 1 dn 19Related Commands
debug ephone vm-integration
To display pattern manipulation information used for integration with voice-mail applications, use the debug ephone vm-integration command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone vm-integration [mac-address mac-address]
no debug ephone vm-integration [mac-address mac-address]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays the voice-mail integration patterns that were created using the pattern commands in vm-integration configuration mode. The patterns are used to forward calls to a voice-mail number that is set with the voicemail command.
If you do not specify the mac-address keyword, the debug ephone vm-integration command debugs all Cisco IP phones that are registered to the router. To remove debugging for Cisco IP phones, enter the no form of this command with the mac-address keyword.
Examples
The following sample output shows information for the vm-integration tokens that have been defined:
Router# debug ephone vm-integration*Jul 23 15:38:03.294:ephone-3[3]:StimulusMessage 15 (1) From ephone 2*Jul 23 15:38:03.294:ephone-3[3]:Voicemail access number pattern check*Jul 23 15:38:03.294:SkinnyGetCallState for DN 3 chan 1 IDLE*Jul 23 15:38:03.294:called DN -1 chan 1, calling DN -1 chan 1 phone -1 s2s:0*Jul 23 15:38:03.294:dn number for dn 3 is 19003*Jul 23 15:38:03.294:Updated number for token 1 is 19003*Jul 23 15:38:03.294:CDN number for dn 3 is*Jul 23 15:38:03.294:Updated number for token 2 is*Jul 23 15:38:03.294:Updated number for token 0 is*Jul 23 15:38:03.294:Update is 219003**Jul 23 15:38:03.294:New Voicemail number is 19101219003*Table 6 describes the significant fields shown in the display.
Related Commands
debug mwi relay errors
To debug message waiting indication (MWI) relay errors, use the debug mwi relay errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mwi relay errors
no debug mwi relay errors
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug mwi relay errors command provides a debug monitor display of any error messages, when MWI Relay Server (Cisco IOS Telephony Server) is trying to do MWI Relay to extensions on remote Cisco IOS Telephony Service (ITS).
Examples
The following examples show errors when MWI Relay Server tries to do an MWI Relay to extension 7004, but location of 7004 is not known to the MWI Relay Server:
Router# debug mwi relay errorsmwi-relay error info debugging is on01:46:48: MWI-APP: mwi_notify_status: No ClientID (7004) registeredRelated Commands
debug ephone mwi
Sets MWI debugging for the Cisco IOS Telephony Service router.
debug mwi relay events
Sets MWI relay events debugging for the Cisco IOS Telephony Service router.
debug mwi relay events
To set message waiting indication (MWI) relay events debugging, use the debug mwi relay events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mwi relay events
no debug mwi relay events
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug mwi relay events command provides a debug monitor display of events, when MWI Relay Server (Cisco IOS Telephony Server) is trying to do MWI Relay to extensions on remote Cisco IOS Telephony Services (ITS).
Examples
The following debugging messages are shown when the MWI Relay server tries to send MWI Information to remote client 7001 and the location of 7001 is known by the MWI Relay Server:
Router# debug mwi relay eventsmwi-relay events info debugging is on01:45:34: mwi_notify_status: Queued event for mwi_app_queue01:45:34: MWI-APP: mwi_app_process_event:01:45:34: MWI-APP: mwi_app_process_event: MWI Event for ClientID(7001)@(1.8.17.22)Related Commands
debug ephone mwi
Sets MWI debugging for the Cisco IOS Telephony Service router.
debug mwi relay errors
Sets MWI relay errors debugging for the Cisco IOS Telephony Service router.
debug voice register errors
To display debug information on voice register module errors during registration in a Cisco Unified CallManager Express (Cisco Unified CME) or Cisco Unified Session Initiation Protocol (SIP) Survivable Remote Site Telephony (SRST) environment, use the debug voice register errors command in privileged EXEC mode. To disable debugging, use the no form of the command.
debug voice register errors
no debug voice register errors
Syntax Description
This command has no arguments or keywords
Command Default
Disabled
Command Modes
Privileged EXEC mode
Command History
Usage Guidelines
Registration errors include failure to match pools or any internal errors that happen during registration.
Examples
Cisco Unified CME
The following is sample output for this command for a registration request with authentication enabled:
...*May 6 18:07:26.971: VOICE_REG_POOL: Register request for (4901) from (10.5.49.83)*May 6 18:07:26.971: VOICE_REG_POOL: key(9499C07A000036A3) added to nonce table*May 6 18:07:26.975: VOICE_REG_POOL: Contact doesn't match any pools*May 6 18:07:26.975: //4/89D7750A8005/SIP/Error/ccsip_spi_register_incoming_registration: Registration Authorization failed with authorization header=...
If there are no voice register pools configured for a particular registration request, the message "Contact doesn't match any pools" is displayed.
When authentication is enabled and if the phone requesting registration cannot be authenticated, the message "Registration Authorization failed with authorization header" is displayed.
Cisco Unified SIP SRST
The following is sample output from this command:
Router# debug voice register errors*Apr 22 11:52:54.523 PDT: VOICE_REG_POOL: Contact doesn't match any pools*Apr 22 11:52:54.539 PDT: VOICE_REG_POOL: Register request for (33015) from (10.2.152.39)*Apr 22 11:52:54.539 PDT: VOICE_REG_POOL: Contact doesn't match any pools.*Apr 22 11:52:54.559 PDT: VOICE_REG_POOL: Register request for (33017) from (10.2.152.39)*Apr 22 11:53:04.559 PDT: VOICE_REG_POOL: Maximum registration threshold for pool(3) hit
If there are no voice register pools configured for a particular registration request, the message "Contact doesn't match any pools" is displayed.
If the max registrations command is configured, when registration requests reach the maximum limit, the "Maximum registration threshold for pool (x) hit" message is displayed for the particular pool.
Table 7 describes the significant fields shown in the display.
Related Commands
debug voice register events
Displays debug information on voice register module events during SIP phone registrations in a Cisco Unified CME or Cisco Unified SIP SRST environment.
debug voice register events
To display debug information on voice register module events during Session Initiation Protocol (SIP) phone registrations in a Cisco Unified CallManager Express (Cisco Unified CME) or Cisco Unified SIP Survivable Remote Site Telephony (SRST) environment, use the debug voice register events command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug voice register events
no debug voice register events
Syntax Description
This command has no arguments or keywords
Command Default
Disabled
Command Modes
Privileged EXEC mode
Command History
Usage Guidelines
Using the debug voice register events command should suffice to view registration activity.
Registration activity includes matching of pools, registration creation, and automatic creation of dial
peers. For more details and error conditions, you can use the debug voice register errors command.
Cisco Unified CME
The following example shows output from this command:
*May 6 18:07:27.223: VOICE_REG_POOL: Register request for (4901) from (1.5.49.83)*May 6 18:07:27.223: VOICE_REG_POOL: Contact matches pool 1 number list 1*May 6 18:07:27.223: VOICE_REG_POOL: key(4901) contact(10.5.49.83) add to contact table*May 6 18:07:27.223: VOICE_REG_POOL: No entry for (4901) found in contact table*May 6 18:07:27.223: VOICE_REG_POOL: key(4901) contact(10.5.49.83) added to contact tableVOICE_REG_POOL pool->tag(1), dn->tag(1), submask(1)*May 6 18:07:27.223: VOICE_REG_POOL: Creating param container for dial-peer 40001.*May 6 18:07:27.223: VOICE_REG_POOL: Created dial-peer entry of type 0*May 6 18:07:27.223: VOICE_REG_POOL: Registration successful for 4901, registration id is 2...The phone number 4901 associated with voice register pool 1, voice register dn 1, registered successfully. A dynamic normal (type 0) VoIP dial peer has been created for entry 4901. The dial peer can be verified using the show voice register dial-peers and show sip-ua status registrar commands.
Cisco Unified SIP SRST
The following is sample output from this command:
Router# debug voice register eventsApr 22 10:50:21.731 PDT: VOICE_REG_POOL: Contact matches pool 1Apr 22 10:50:21.731 PDT: VOICE_REG_POOL: key(91011) contact(192.168.0.2) add to contact tableApr 22 10:50:21.731 PDT: VOICE_REG_POOL: key(91011) exists in contact tableApr 22 10:50:21.731 PDT: VOICE_REG_POOL: contact(192.168.0.2) exists in contact table, ref updatedApr 22 10:50:21.731 PDT: VOICE_REG_POOL: Created dial-peer entry of type 1Apr 22 10:50:21.731 PDT: VOICE_REG_POOL: Registration successful for 91011, registration id is 257The phone number 91011 registered successfully, and type 1 is reported in the debug, which means that there is a preexisting VoIP dial peer.
Apr 22 10:50:38.119 PDT: VOICE_REG_POOL: Register request for (91021) from (192.168.0.3)Apr 22 10:50:38.119 PDT: VOICE_REG_POOL: Contact matches pool 2Apr 22 10:50:38.123 PDT: VOICE_REG_POOL: key(91021) contact(192.168.0.3) add to contact tableApr 22 10:50:38.123 PDT: VOICE_REG_POOL: key(91021) exists in contact tableApr 22 10:50:38.123 PDT: VOICE_REG_POOL: contact(192.168.0.3) exists in contact table, ref updatedApr 22 10:50:38.123 PDT: VOICE_REG_POOL: Created dial-peer entry of type 1Apr 22 10:50:38.123 PDT: VOICE_REG_POOL: Registration successful for 91021, registration id is 258A dynamic VoIP dial peer has been created for entry 91021. The dial peer can be verified using the show voice register dial-peers and show sip-ua status registrar commands.
Apr 22 10:51:08.971 PDT: VOICE_REG_POOL: Register request for (95021) from (10.2.161.50)Apr 22 10:51:08.971 PDT: VOICE_REG_POOL: Contact matches pool 3Apr 22 10:51:08.971 PDT: VOICE_REG_POOL: key(95021) contact(10.2.161.50) add to contact tableApr 22 10:51:08.971 PDT: VOICE_REG_POOL: No entry for (95021) found in contact tableApr 22 10:51:08.975 PDT: VOICE_REG_POOL: key(95021) contact(10.2.161.50) added to contact tableApr 22 10:51:08.979 PDT: VOICE_REG_POOL: Created dial-peer entry of type 0Apr 22 10:51:08.979 PDT: VOICE_REG_POOL: Registration successful for 95021, registration id is 259Apr 22 10:51:09.019 PDT: VOICE_REG_POOL: Register request for (95012) from (10.2.161.50)Apr 22 10:51:09.019 PDT: VOICE_REG_POOL: Contact matches pool 3Apr 22 10:51:09.019 PDT: VOICE_REG_POOL: key(95012) contact(10.2.161.50) add to contact tableApr 22 10:51:09.019 PDT: VOICE_REG_POOL: No entry for (95012) found in contact tableApr 22 10:51:09.023 PDT: VOICE_REG_POOL: key(95012) contact(10.2.161.50) added to contact tableApr 22 10:51:09.027 PDT: VOICE_REG_POOL: Created dial-peer entry of type 0Apr 22 10:51:09.027 PDT: VOICE_REG_POOL: Registration successful for 95012, registration id is 260Apr 22 10:51:09.071 PDT: VOICE_REG_POOL: Register request for (95011) from (10.2.161.50)Apr 22 10:51:09.071 PDT: VOICE_REG_POOL: Contact matches pool 3Apr 22 10:51:09.071 PDT: VOICE_REG_POOL: key(95011) contact(10.2.161.50) add to contact tableApr 22 10:51:09.071 PDT: VOICE_REG_POOL: No entry for (95011) found in contact tableApr 22 10:51:09.075 PDT: VOICE_REG_POOL: key(95011) contact(10.2.161.50) added to contact tableApr 22 10:51:09.079 PDT: VOICE_REG_POOL: Created dial-peer entry of type 0Apr 22 10:51:09.079 PDT: VOICE_REG_POOL: Registration successful for 95011, registration id is 261Apr 22 10:51:09.123 PDT: VOICE_REG_POOL: Register request for (95500) from (10.2.161.50)Apr 22 10:51:09.123 PDT: VOICE_REG_POOL: Contact matches pool 3Apr 22 10:51:09.123 PDT: VOICE_REG_POOL: key(95500) contact(10.2.161.50) add to contact tableApr 22 10:51:09.123 PDT: VOICE_REG_POOL: No entry for (95500) found in contact tableApr 22 10:51:09.127 PDT: VOICE_REG_POOL: key(95500) contact(10.2.161.50) added to contact tableApr 22 10:51:09.131 PDT: VOICE_REG_POOL: Created dial-peer entry of type 0Apr 22 10:51:09.131 PDT: VOICE_REG_POOL: Registration successful for 95500, registration id is 262*Apr 22 11:52:54.523 PDT: VOICE_REG_POOL: Contact doesn't match any pools*Apr 22 11:52:54.539 PDT: VOICE_REG_POOL: Register request for (33015) from (10.2.152.39)*Apr 22 11:52:54.539 PDT: VOICE_REG_POOL: Contact doesn't match any pools*Apr 22 11:52:54.559 PDT: VOICE_REG_POOL: Register request for (33017) from (10.2.152.39)Table 8 describes the significant fields shown in the display.
Related Commands
Posted: Thu Jul 19 11:06:14 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
