Filter
Top Products
5-67
Cisco IP Phone Services Application Development Notes
OL-5375-01
Chapter 5 HTTP Client Requests and Header Settings
Accept Header
These parameters get separated by commas as shown in the following example of
a Cisco IP Phone 7970 header:
x-CiscoIPPhoneDisplay: 298, 168, 12, C
Note The pixel resolutions advertised by the device define the area of the display
accessible by the phone services; not the actual resolution of the display.
x-CiscoIPPhoneSDKVersion
This Cisco-proprietary header contains the version of the IP Phone Services SDK
the requesting phone supports. Knowing the supported SDK version helps in
understanding, among other things, which URIs get supported. Support for
individual URIs (unlike the XML objects) does not get explicitly enumerated in
an HTTP header. The developer therefore must check the
<<Supported URIs
Matrix>>
in the IP Phone Services SDK, so the developer application will know,
based on the Phone Model Name and supported SDK version, whether a specific
URI (or specific feature/version of a URI) gets supported.
Refer to the
<<Supported URIs Matrix>> to find out which IP phone models
support the URIs that are documented in this SDK.
Note Beginning with the IP Phone Services SDK 3.3(3), the SDK version number
matches the minimum Cisco CallManager software that is required to support it.
For example, SDK version 3.3(4) gets supported only on Cisco CallManager
version 3.3(4) or later.
Accept Header
The Accept header represents a standard HTTP header that is used to inform web
servers about the content-handling capabilities of the client.
Cisco IP Phones include proprietary content-types to indicate which XML objects
are supported. These proprietary content-types all begin with x-CiscoIPPhone, to
indicate Cisco IP Phone XML objects, followed by a slash "/", followed by either
a specific XML object or a "*" to indicate all objects.