Cisco Unified IP Phone Services Application Development Notes for Cisco Unified Communications Manager and Multiplatform Phones

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

• Preface
• Custom Client Services Overview
• New and Changed Information
• CiscoIPPhone XML Objects
• Component APIs
• Internal URI Features
• HTTP Requests and Header Settings
• Troubleshooting Cisco Unified IP Phone Service Applications
• Cisco IP Phone Services Software Development Kit (SDK)
• IP Phone Service Administration and Subscription
• CiscoIPPhone XML Object Quick Reference
• Device Capability Query via CTI Feature
• Index

Book Title

Cisco Unified IP Phone Services Application Development Notes for Cisco Unified Communications Manager and Multiplatform Phones

Troubleshooting Cisco Unified IP Phone Service Applications

• PDF - Complete Book (3.6 MB)PDF - This Chapter (1.01 MB) View with Adobe Reader on a variety of devices

Results

Chapter: Troubleshooting Cisco Unified IP Phone Service Applications

• Troubleshooting Cisco Unified IP Phone Service Applications
• Troubleshooting Tips
• XML Parsing Errors
• Error Messages

Troubleshooting Cisco Unified IP Phone Service Applications

Troubleshooting Tips

The following tips apply to troubleshooting Cisco Unified IP Phone service applications:

• Microsoft Internet Explorer 5 or higher can display the XML source with its default style sheet.
• Understand that standard IP troubleshooting techniques are important for HTTP errors.
• Externally verify name resolution (Phone has DNS set).
• If DNS is suspected, use IP addresses in URLs.
• Browse the URL in question with Microsoft Internet Explorer or download and verify with another web browser.
• Use a logged telnet session to verify that the desired HTTP headers are returned (telnet to the server on port 80, and then enter: get /path/page).

XML Parsing Errors

The following tips apply to troubleshooting XML parsing errors in Cisco Unified IP Phone services applications:

• Verify the object tags (the object tags are case sensitive).
• Verify that "&" and the other four special characters are used according to the restrictions while inside the XML objects.
• Validate XML applications developed prior to Cisco Unified IP Phone Firmware Release 8.3(2) against the more recent XML parser. Some of examples of the types of errors you might encounter include:
  • CiscoIPPhoneMenu Object: If the field is missing for a , the original parser would stop rendering from that onwards. The new parser will display a blank line in the menu list and continue to render any subsequent definitions.
  • CiscoIPPhoneDirectory Object: If the field is not present, the old original parser would not display the directory entry, the new parser will display the directory entry, but there will be no associated with it.
  • CiscoIPPhoneInput Object: The URL and QueryStringParam fields are mandatory. The original parser would not report an error on the missing URL and on submit request would display a "Host not Found" message. If the QueryStringParam field is missing, the updated parser will report an error.
  • SoftKeyItem: The Position field is mandatory. If the Position field is not present, the updated XML parser will report an error.

  Error Messages

  The following error messages may appear on the prompt line of the Cisco Unified IP Phone display:

  • XML Error[4] = XML Parser error (Invalid Object)
  • XML Error[5] = Unsupported XML Object (not supported by this phone model)
  • HTTP Error[8] = Unknown HTTP Error
  • HTTP Error[10] = HTTP Connection Failed

  The Cisco Unified IP Phone 6900 Series supports the following error messages:

  cfg file directoryURL or servicesURL is empty

  DNS query fails

  Server response 503

  Socket cannot be created or the connection fails

  XML Error [4]: Parse Error

  Does not match XML schema

  Downloaded content is over 196608 bytes

  No services configured

  HTTP message body is empty

  Filename too long!

  file name length is over 127 characters.