User's Manual

Avaya B179 SIP Conference Phone Installation and Administration Guide
59
File server address DM server address if not provided by DHCP option.
HTTPS protocol Default is auto, but can be set to SSLv2 or SSLv3 if open-ssl auto
detection fails.
Check server cert. Enable authentication with certicate.
Certicate Here you can upload a certicate to the Avaya B179 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 Avaya B179 to be used for
authentication when using Device management.
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, pagename,
and letype).

To avoid confusion, it may be wise to delete the local information from the le (eg. ac-
count information).

Save the le with the name avayab179.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 avaya-<MAC>.xml, where <MAC> is the MAC address of
the specic conference phone.

Place the conguration les on the File server address specied above.