Table of Contents
Advertisement
c03.fm
Basic Communication Procedures
Basic Message Flow
3.1.2
Provisioning Service Driven Interaction
3.1.2.1
No Firewall
A typical reason for contacting the phone is the modification of one or more configuration set-
tings. The message flow might proceed as follows:
In an initial HTTP request, the provisioning service sends a contact-me message to the phone.
The phone responds to this request, and afterwards transmits a basic set of data items contain-
ing configuration settings to the provisioning service.
Now, the provisioning service sends a list of data items that have to be changed. If the phone
is ready, it will confirm the action and execute the commands or configuration changes. If the
phone is busy, it will send an appropriate message to the provisioning service (see Section
3.3.4, "Reason for Contact"). Starting with V3R3 the provisioning service sends a CleanUp with
a 'send-solicited' item. The phones reaction will be to schedule an automatic solicited connec-
tion to the provisioning service when the busy condition is cleared.
If the phone is downgraded then any receipt of a Send-solicited item in a CleanUp action from
the provisioning service will result in the pre-existing behaviour. If the provisioning service has
been upgraded to expect the 'Send-solicited'-feature is supported then it is the responsibility of
the provisioning service to ensure that the use of 'send-solicited' is restricted to the defined
DCMP use when a phone with an prior bind is involved.
In order to make sure that the desired changes have been made, the provisioning service
should send a read request for the modified data. Hereupon, the phone sends back the modi-
fied items. Finally, the provisioning service terminates the interaction with a CleanUp message.
22
Nur für den internen Gebrauch
A31003-S2000-R102-16-7620 02/2016
Provisioning Service, Developer's Guide
Advertisement
Table of Contents
