User guide

51
PROVISIONING – UPGRADE AND CONFIGURATION
Check server cert. Enable authentication with certicate.
Certicate Here you can upload a certicate to the Konftel 300IP to be used
for authentication when using Device management.
Root certicate The public key in the root certicate is used to verify other certi-
cates when using Device management.
Private key Here you can upload a private key to the Konftel 300IP to be used
for authentication when using Device management.

Read more about certicates on page 22.
Setting up a Device management server
This is a description of a manual method to create the conguration les.

Select Settings > Provisioning.

Enable Device management and enter the server information.
Creating a global conguration le

Congure one phone with the basic conguration.

Click on Export to create a conguratuion le.

If necessary, edit the xml le in a suitable editor.

Some parameters can’t be entered via the web interface (update frequency, page-
name, and letype).

To avoid confusion, it may be wise to delete the local information from the le (eg.
account information).

Save the le with the name kt300ip.xml on the File server address specied above.
Creating local conguration les

Save a copy of the conguration le for each conference phone on your location with
content only in the elements that shall be unique for each conference phone (eg.
account information).
The default name for each le is kt300ip-<MAC>.xml, where <MAC> is the MAC ad-
dress of the specic conference phone.

Place the conguration les on the File server address specied above.
Firmware binary

Place the rmware binary le on the Provisioning server.

Create a Firmware metadata le according to page 49 and place it on the File server
address specied above.

Depending on the server used, and the security settings, there might be necessary
to add the le type .kt to the MIME settings on the server. This is easily checked by
trying to download the kt le from a web browser.