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 certificate.
Certificate
Here you can upload a certificate to the Avaya B179 to be used for
authentication when using Device management.
Root certificate
The public key in the root certificate is used to verify other certificates
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 configuration files.
Select Settings > Provisioning.
Enable Device management and enter the server information.
Creating a global configuration file
Configure one phone with the basic configuration.
Click on Export to create a configuratuion file.
If necessary, edit the xml file in a suitable editor.
Some parameters can’t be entered via the web interface (update frequency, pagename,
and filetype).
To avoid confusion, it may be wise to delete the local information from the file (eg. ac-
count information).
Save the file with the name avayab179.xml on the File server address specified above.
Creating local configuration files
Save a copy of the configuration file 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 file is avaya-<MAC>.xml, where <MAC> is the MAC address of
the specific conference phone.
Place the configuration files on the File server address specified above.