Spectralink 84-Series Series Wireless Telephones Administration Guide
1725-86984-000_P.docx
September 2016 49
You can create as many configuration files as you want and your configuration files can contain
any combination of parameters you put in them. You can put all parameters into one file or, for
example, you can put SIP server parameters in one file and handset features parameters in
another file. Configuration file variances are explained in the Spectralink 84-Series Wireless
Telephone Deployment Guide.
For large-scale deployments, the centralized provisioning method using configuration files is
strongly recommended. For smaller scale deployments, the Web Configuration Utility or local
interface may be used, but administrators need to be aware that settings made using these
methods will override settings made using configuration files.
For instructions on how to encrypt your configuration files, see Encrypting Configuration Files.
Shortcut Method to Deploy Spectralink Handsets with a Provisioning Server
The following steps are a shortcut method for provisioning procedure. Please use the
Spectralink 84-Series Wireless Telephone Deployment Guide for detailed instructions for each
of these steps.
To deploy handsets with a provisioning server using a shortcut method:
1 Obtain a list of MAC addresses for the handsets you want to deploy.
The MAC address is a 12-digit hexadecimal number on a label on the back of the
handset and on the outside of the shipping box. It is also available on the Status menu.
2 Create a per-handset <MACaddress>-ext.cfg file.
Do NOT use these names for a per-handset configuration file
Do NOT use the following file names as your per-handset file name:
<MACaddress>-phone.cfg,
<MACaddress>-Web.cfg,
<MACaddress>-app.log,
<MACaddress>-boot.log, or
<MACaddress>-license.cfg.
These file names are used by the handset itself to store user preferences
(overrides) and logging information.
Add handset registration parameters to the file, for example reg.1.address,
reg.1.label, and reg.1.type.
3 Create a per-site site<location>.cfg file.
For example, add the SIP server or feature parameters like
voIpProt.server.1.address and feature.corporateDirectory.enabled.
To Next Page
Loading...
