Chapter 3 CiscoIPPhone XML Objects
XML Considerations
Note All CiscoIPPhone element names and attribute names are case sensitive.
Mandatory Escape Sequences
By XML convention, the XML parser also requires that you provide escape values for a few special characters. Table
.
Table | Escape Sequences for Special Characters | |
|
|
|
Character | Name | Escape Sequence |
|
|
|
& | Ampersand | & |
|
|
|
“ | Quote | " |
|
|
|
' | Apostrophe | ' |
|
|
|
< | Left angle bracket | < |
|
|
|
> | Right angle bracket | > |
|
|
|
Escaping text can be tedious, but some authoring tools or scripting languages can automate this task.
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
The encoding value specified in the XML header must match one of the encodings provided by the IP Phone in its
Example
The following examples illustrate
<?xml version="1.0"
<?xml version="1.0"
For details on setting HTTP header encoding settings, see the “HTTP Encoding Header Setting” section on page
|
| Cisco Unified IP Phone Services Application Development Notes |
|
| |
|
|
| |||
|
|
|
| ||
|
|
|
|