c03.fm
A31003-S2000-R102-16-7620, 02/2016
Provisioning Service, Developer’s Guide
27
Nur für den internen Gebrauch
Basic Communication Procedures
Phone Message Structure
Examples
<Item name="e164">49897223290</Item>
- E.164 number of the phone
<Item name="device-type">OpenStage 60</Item>
- type of phone
<Item index="1" name="ldap-server-address">ldap.mycompany.com</Item>
-
DNS name (or IP address) of the first LDAP server to be queried
<Item name="reg-addr">192.168.1.117</Item>
- IP address of the SIP server
(registrar) at which the phone is registered or shall be registrated
3.3
Phone Message Structure
3.3.1
Initial Message From the Phone
When the phone initiates an interaction with the provisioning service, it will include at least the
following data items in its message:
3.3.2
Root Element
The root element of any message from the phone to the provisioning service is
WorkpointMessage
. For the corresponding XML schema, please refer to Section 3.5.1.2,
Item
Description
contact-me-uri
The provisioning service must send its contact-me messages to this
fully qualified URI in order to start an interaction with the phone.
mac-addr
Contains the phone’s MAC address, which is eligible as a unique
identifier for the phone.
e164
This is the E.164 number of the phone. It can be used as additional
or alternative identifier in case an identification by the
mac-addr
alone should fail.
The
E.164
item can be rewritten by the provisioning service. If so, the
new value will be used by the phone for subsequent interactions.
Table 3-1
