Getting Started
Nur für den internen Gebrauch
A31003-S2000-R102-16-7620 02/2016
12
Provisioning Service, Developer’s Guide
c01.fm
Network Communication
1.4
Network Communication
This chapter contains the elementary HTTP/HTTPS communication required for interaction
between the phone and the provisioning service. For a high-level description of the possible
interactions, please refer to Section 3, "Basic Communication Procedures".
1.4.1
Protocols
When the provisioning service wants to start communicating with a phone, it has to send a spe-
cial contact-me message. This message, as well as the response from the phone, is transmit-
ted via HTTP (clear text, not encrypted).
All further communication between the provisioning service and the phone consists of messag-
es in XML format, which are transmitted using HTTP v1.1 over TLS (HTTPS).
1.4.2
Ports
On the phone side, the destination port for messages to the provisioning server can be freely
chosen. The address and port number of the provisioning service are defined under
Network
> Update service
in the phone’s web interface or provided by DHCP (see Section 2.2, "Ex-
For sending contact-me messages to the phone in order to initiate an interaction, the provision-
ing service must use port 8085 as destination port.
>
To prevent communication problems in the HTTP layer, please consider the follow-
ing:
●
The keep-alive timeout in the provisioning server should be set to 10.
●
The provisioning server must be set to use HTTP 1.1.
●
With phone firmware V2R2 and lower, the provisioning server must not use
HTTP chunked encoding. This problem is solved with firmware version V3.
>
OpenStage phones and OpenScape Desk Phone IP expect the interface on port
18443 to be TLS-encrypted (HTTPS). Therefore, the provisioning server needs to
configure SSL/TLS on this listener port. In Default Mode OpenStage phones and
OpenScape Desk Phone IP do not authenticate the server, any certificate is suit-
able. In Secure Mode OpenStage phones and OpenScape Desk Phone IP requires
certificates supported by provisioning service. All further requests of this device are
performed on port 18444. For information on importing or creating a suitable TLS
web server certificate, please refer the relevant documentation for your web server.
