Basic Communication Procedures
Nur für den internen Gebrauch
A31003-S2000-R102-16-7620 02/2016
28
Provisioning Service, Developer’s Guide
c03.fm
Phone Message Structure
3.3.3
Message Element
The root element contains another container element,
Message
. It has a mandatory attribute
named
nonce
; its task is to prevent replay attacks. Any reply by the provisioning service con-
tains this attribute. With the optional attribute
maxItems
, the phone can define the maximum
number of items allowed in one single message document from the provisioning service. If the
reply requires a greater number of items, it must be fragmented (see Section 3.7, "Message
Fragmentation").If
maxItems
is set to -1, there is no limitation.
3.3.4
Reason for Contact
The
ReasonForContact
element indicates the motivation for sending a message to the pro-
visioning service. See the following table for possible values:
Content Value
Description
start-up
On each startup or reset, the phone sends a message to the pro-
visioning service with
reason
set to this value. This can be viewed
as a registration with the provisioning service.
local-changes
Some configuration changes have been made locally, that is, by
the local phone menu or by the phone’s web interface.
inventory-changes
Some inventory-related items have changed, due to a new side-
car or adaptor that has been connected.
status
The phone communicates the status of a file transfer initiated ear-
lier by the provisioning service (see Section 3.6.7, "File Provision-
ing").
solicited
The phone has received a contact-me message from the provi-
sioning service and is calling back for further actions.
reply-to
This message is a reply to a particular message from the provision-
ing service. As it is part of a complex interaction between phone
and provisioning service, it is recommended to establish an HTTP
session by using cookies. If so, OpenStage phones will present a
valid session-cookie along with this message.
Further specifications can be given via the attributes
action
and
status
, and, if applicable, via
fragment
(see next table).
clean-up
If the phone recognizes any problem, either due to its internal state
or due to a corrupted reply from the provisioning service, it will end
the interaction deliberately by sending this value.
Further specifications can be given via the ItemList, e.g.
<Item
name="cleanup-reason"> password retries exceed-
ed</Item>
when number of retries for PIN entry at the device in
Secure Mode has exceeded.
