Specifications

3-31
Cisco Unified IP Phone Services Application Development Notes
OL-22505-01
Chapter 3 CiscoIPPhone XML Objects
Application Event Handlers
XML Encoding
Because the phone firmware can support multiple encodings, the XML encoding should always be set in
the XML header.
If the XML encoding header is not specified, the phone will default to the encoding specified by the
current user locale.
Note This behavior is NOT compliant with XML standards, which specify UTF-8 as the default encoding, so
any UTF-8 encoded XML object must have the encoding explicitly set for the phone to parse it correctly.
The encoding value specified in the XML header must match one of the encodings provided by the IP
Phone in its Accept-Charset HTTP request header, as shown in the example below.
Example
The following examples illustrate UTF-8 and ISO-8859-1 encoding, respectively:
<?xml version="1.0" encoding="utf-8" ?>
<?xml version="1.0" encoding="iso-8859-1" ?>
For details on setting HTTP header encoding settings, see the “HTTP Encoding Header Setting” section
on page 6-6.
Application Event Handlers
The Application Manager API (see “Application” section on page 5-20) includes an Application
Management Event Handler which is supported by any displayable object, which are noted in the
following table. The unsupported objects are not contained in a standard application context and are
handled differently by the Application Manager API:
For information on phone models that support Application Event Handlers, see Supported Phone Models
section in Component APIs chapter.
Supported Unsupported
CiscoIPPhoneMenu CiscoIPPhoneStatus
CiscoIPPhoneText CiscoIPPhoneStatusFile
CiscoIPPhoneInput
CiscoIPPhoneDirectory
CiscoIPPhoneImage
CiscoIPPhoneImageFile
CiscoIPPhoneGraphicMenu
CiscoIPPhoneGraphicFileMenu
CiscoIPPhoneIconMenu
CiscoIPPhoneIconFileMenu