Specifications

PA-001011-03-04 Aastra July 2014
235
8 Troubleshooting XML Applications
8.1 Introduction
The following figure shows the HTTP call flows when the phone is performing an XML operation.
Figure 99: HTTP flow for XML applications
When the phone performs an HTTP GET there are many potential sources of error such as:
Server is not reachable
Answer
Network is down
Cannot display
Server is down
Cannot display
HTTP server application is down
Cannot display
URI can not be resolved (DNS issue)
Cannot display
Server is reachable
Answer
Wrong file name on the server
File not found
Parsing error of the XML answer
Cannot display
Timeout reached before getting an answer
Connect Timeout
URI can not be parsed (wrong format)
Invalid URI
Most of the time, an error will translate into a “Cannot display” which is not very helpful to find the
origin of the problem as well as very frustrating for the XML developer.
The most common error is a XML parsing error and often the most difficult one to fix.
Note: Using the php classes provided in the toolkit is a good way to limit the number of
parsing errors as the object are built following the XSD scheme.
When the server performs a PUSH to the phone, the common errors are: