User`s manual

Mediant 2000 & TP-1610 & TP-260
SIP User's Manual 264 Document #: LTRT-68805
Figure 11-10: Example of a Software Upgrade Key File Containing Multiple S/N Lines
11.7.2.2 Loading the Software Upgrade Key Using BootP/TFTP
¾ To load the Software Upgrade Key file using BootP/TFTP, take
these 5 steps:
1. Place the file in the same location you’ve saved the device’s cmp file. Note that in
order to load the Software Upgrade Key via TFTP server, the extension of the key file
must be ini.
2. Start the BootP/TFTP configuration utility and from the Services menu in the main
screen, choose option Clients; the Client Configuration screen is displayed (refer to
Figure D-4 on page 359).
3. From the drop-down list in the INI File field, select the Software Upgrade Key file
instead of the device’s ini file. Note that the device’s cmp file must be specified in the
Boot File field.
4. Configure the initial BootP/TFTP parameters required, and click OK (refer to Appendix
D on page 353).
5. Reset the device; the device’s cmp and Software Upgrade Key files are loaded to the
device.
11.7.3 Verifying that the Key was Successfully Loaded
After installing the key, you can determine in the Embedded Web Server’s read-only ‘Key
features:’ panel (Software Update menu > Software Upgrade Key) (refer to Figure
11-9)
that the features and capabilities activated by the installed string match those that were
ordered.
You can also verify that the key was successfully loaded to the device by accessing the
Syslog server. For detailed information on the Syslog server, refer to Section
14.2 on page
304. When a key is successfully loaded, the following message is issued in the Syslog
server:
‘S/N___ Key Was Updated. The Board Needs to be Reloaded with ini file\n’
11.7.4 Troubleshooting an Unsuccessful Loading of a Key
If the Syslog server indicates that a Software Upgrade Key file was unsuccessfully loaded
(the SN_ line is blank), take the following preliminary actions to troubleshoot the issue:
 Open the Software Upgrade Key file and check that the S/N line of the specific device
whose key you want to update is listed in it. If it isn’t, contact AudioCodes.
 Verify that you’ve loaded the correct file and that you haven’t loaded the device’s ini
file or the CPT ini file by mistake. Open the file and ensure that the first line is
[LicenseKeys].
 Verify that you didn’t alter in any way the contents of the file.