Basic Communication Procedures
Nur für den internen Gebrauch
A31003-S2000-R102-16-7620 02/2016
30
Provisioning Service, Developer’s Guide
c03.fm
Provisioning Service Message Structure
3.4
Provisioning Service Message Structure
3.4.1
Initiation
Before issuing XML messages to the phone, the provisioning service must announce to the
phone that it desires an interaction with it. For details, see Section 1.4.4.2, "Contact-me
Messages".
3.4.2
Action Type
Any message from the provisioning service must contain the Action element. It determines the
activity the phone should perform. The possible actions are listed in the following table:
>
In case a firewall/DMZ should prevent the provisioning service from initiating an in-
teraction with the phone, please refer to Section 3.1.2.2, "Provisioning Service Lo-
cated Behind A Firewall".
>
The character encoding of the XML data sent to the phone should be UTF-8 in order
to allow for special characters, such as german umlaut.
Content Value
Description
ReadAllItems
The phone will deliver its whole set of items. However, this does
not include certificates.
WriteItems
The phone is requested to modify its current settings for those
items which are contained in the message.
Please note that this request will be denied when the phone is in a
call (for details, please see Section 3.6.4, "Modify Phone Set-
tings").
ReadItems
The provisioning service asks the phone to deliver the values of a
certain subset of items.
Restart
The provisioning service asks the phone to restart.
FileDeployment
The phone is requested to download a file from an FTP or HTTPS
server denoted by the items contained in the message.
SoftwareDeployment
The phone is requested to download a firmware image from a FTP
or HTTPS Server denoted by the items contained in the message.
