User's Manual

For more information about provisioning parameters for the IP Deskphone, see
Create the SIP provisioning file on the provisioning server on page 34.
2. The IP Deskphone config file must include a [LICENSING] section to enable the IP
Deskphone to download the licence file. Add [LICENSING] section to the IP
Deskphone .cfg file.
Examples of IP Deskphone cfg files are 1120eSIP.cfg, 1140eSIP.cfg, 1165eSIP.cfg,
1220eSIP.cfg, and 1230eSIP.cfg.
The [LICENSING] section specifies a wild card filename which uses the IP
Deskphone MAC address as the filename with the ipctoken prefix and cfg suffix.
For example:
[FW]
DOWNLOAD_MODE AUTO
VERSION 3.00.xx.yy
PROTOCOL TFTP
FILENAME SIP 1140_e03.02.xx.yy.bin
...
[LICENSING]
DOWNLOAD_MODE AUTO
VERSION 000001
FILENAME ipctoken*.cfg
3. Place the IP Deskphone license file on the provisioning server.
The generated license file must be named ipctokenMAC.cfg, where MAC is the 12-
character MAC address of the IP Deskphone.
For example, for an IP Deskphone with MAC address “000f1fd304f8”, the license
file will be named “ ipctoken000f1fd304f8.cfg”.
4. Start the provisioning server so the IP Deskphone can retrieve the .cfg files when
the server starts.
When the new license file is downloaded to the phone from the provisioning server, it overwrites
the existing license file and reboots the phone to activate the new license.
Network Locked license file download
If a Network Locked license file is to be used, the same license file can be installed on all
phones. In this case, the wildcard “*” is not used in the FILENAME, as the filename is fixed
and does not contain the MAC address of each phone.
Use the following procedure to download a Network Locked license file from the provisioning
or TFTP server.
Downloading a Network Locked license file:
1. Configure the IP Deskphone with a provisioning IP address so it can access a
provisioning server. For more information about provisioning parameters for the IP
Licensing
286 SIP Software for Avaya 1100 Series IP Deskphones-Administration November 2012
Comments? infodev@avaya.com