48-34
Cisco ASA 5500 Series Configuration Guide using the CLI
Chapter48 Configuring the Cisco Phone Proxy
Troubleshooting the Phone Proxy
Solution
Step1 Verify that DNS lookup is configured on the ASA.
Step2 If DNS lookup is configured, determine whether you can ping the FQDN for the Cisco UCM from the
ASA.
Step3 If ASA cannot ping the Cisco UCM FQDN, check to see if there is a problem with the DNS server.
Step4 Additionally, use the name command to associate a name with an IP address with the FQDN. See the
command reference for information about using the name command.
Non-configuration File Parsing Error
Problem The ASA receives a file other than an IP phone configuration file from the Cisco UCM and
attempts to parse it. The following error appears in the debug output (debug phone-proxy tftp):
PP: 192.168.10.5/49357 requesting SK72f64050-7ad5-4b47-9bfa-5e9ad9cd4aa9.xml.sgn
PP: opened 0x193166
.......
PP: Beginning of element tag is missing, got !
PP: error parsing config file
PP: Error modifying config file, dropping packet
Solution The phone proxy should parse only the IP phone configuration file. When the phone proxy
TFTP state gets out of state, the phone proxy cannot detect when it is attempting to parse a file other
than the IP phone configuration file and the error above appears in the ASA output from the debug
phone-proxy tftp command.
Perform the following actions to troubleshoot this problem:
Step1 Reboot the IP phone.
Step2 On the ASA, enter the following command to obtain the error information from the first TFTP request
to the point where the first error occurred.
hostname# debug phone-proxy tftp
Step3 Capture the packets from the IP phone to the ASA. Make sure to capture the packets on the interface
facing the IP phone and the interface facing the Cisco UCM. See Debugging Information from the
Security Appliance, page 48-27.
Step4 Save this troubleshooting data, open a case with TAC and give them this information.
Cisco UCM Does Not Respond to TFTP Request for Configuration File
Problem When the ASA forwards the TFTP request to the Cisco UCM for the IP phone configuration
file, the Cisco UCM does not respond and the following errors appear in the debug output (debug
phone-proxy tftp):
PP: 192.168.10.5/49355 requesting SEP001562106AF3.cnf.xml.sgn
PP: opened 0x17ccde
PP: 192.168.10.5/49355 requesting SEP001562106AF3.cnf.xml.sgn