User`s manual
Table Of Contents
- Mediant 2000 & TP-1610 & TP-260/UNI SIP User’s Manual Version 5.0
- Table of Contents
- List of Figures
- List of Tables
- Notices
- 1. Overview
- 2. Physical Description
- 3. Installation
- 4. Getting Started
- 5. Web Management
- Computer Requirements
- Protection and Security Mechanisms
- Accessing the Embedded Web Server
- Getting Acquainted with the Web Interface
- Protocol Management
- Advanced Configuration
- Status & Diagnostic
- Software Update Menu
- Maintenance
- Logging Off the Embedded Web Server
- 6. Gateway's ini File Configuration
- Secured ini File
- Modifying an ini File
- The ini File Content
- The ini File Structure
- The ini File Example
- Networking Parameters
- System Parameters
- Web and Telnet Parameters
- Security Parameters
- RADIUS Parameters
- SNMP Parameters
- SIP Configuration Parameters
- Voice Mail Parameters
- ISDN and CAS Interworking-Related Parameters
- Number Manipulation and Routing Parameters
- E1/T1 Configuration Parameters
- Channel Parameters
- Configuration Files Parameters
- 7. Using BootP / DHCP
- 8. Telephony Capabilities
- Working with Supplementary Services
- Configuring the DTMF Transport Types
- Fax & Modem Transport Modes
- Event Notification using X-Detect Header
- ThroughPacket™
- Dynamic Jitter Buffer Operation
- Configuring the Gateway’s Alternative Routing (based on Conn
- Call Detail Report
- Supported RADIUS Attributes
- Trunk to Trunk Routing Example
- Proxy or Registrar Registration Example
- SIP Call Flow Example
- SIP Authentication Example
- 9. Networking Capabilities
- 10. Advanced PSTN Configuration
- 11. Advanced System Capabilities
- 12. Special Applications
- 13. Security
- 14. Diagnostics
- 15. SNMP-Based Management
- SNMP Standards and Objects
- Carrier Grade Alarm System
- Cold Start Trap
- Third-Party Performance Monitoring Measurements
- TrunkPack-VoP Series Supported MIBs
- Traps
- SNMP Interface Details
- SNMP Manager Backward Compatibility
- Dual Module Interface
- SNMP NAT Traversal
- SNMP Administrative State Control
- AudioCodes’ Element Management System
- 16. Configuration Files
- Appendix A. Selected Technical Specifications
- Appendix B. Supplied SIP Software Kit
- Appendix C. SIP Compliance Tables
- Appendix D. The BootP/TFTP Configuration Utility
- Appendix E. RTP/RTCP Payload Types and Port Allocation
- Appendix F. RTP Control Protocol Extended Reports (RTCP-XR)
- Appendix G. Accessory Programs and Tools
- Appendix H. Release Reason Mapping
- Appendix I. SNMP Traps
- Appendix J. Installation and Configuration of Apache HTTP Server
- Appendix K. Regulatory Information

Mediant 2000 & TP-1610 & TP-260
SIP User's Manual 262 Document #: LTRT-68805
11.7 Software Upgrade Key
The gateways are supplied with a Software Upgrade Key already pre-configured for each
of its TrunkPack Modules (TPM).
Users can later upgrade their gateway's features, capabilities and quantity of available
resources by specifying what upgrades they require, and purchasing a new key to match
their specification.
The Software Upgrade Key is sent as a string in a text file, to be loaded onto the gateway.
Stored in the device’s non-volatile flash memory, the string defines the features and
capabilities allowed by the specific key purchased by the user. The device allows users to
utilize only these features and capabilities. A new key overwrites a previously installed key.
Note: The Software Upgrade Key is an encrypted key. Each TPM utilizes a
unique key. The Software Upgrade Key is provided by AudioCodes only.
11.7.1 Backing up the Current Software Upgrade Key
Back up your current Software Upgrade Key before loading a new key to the device. You
can always reload this backed-up key to restore your device capabilities to what they
originally were if the ‘new’ key doesn’t comply with your requirements.
¾ To backup the current Software Upgrade Key, take these 5 steps:
1. Access the devices Embedded Web Server (refer to Section 5.3 on page 58).
2. Click the Software Update button.
3. Click the Software Upgrade Key tab; the Software Upgrade Key screen is displayed
(shown in Figure 11-9).
4. Copy the string from the 'Current Key' field and paste it in a new file.
5. Save the text file with a name of your choosing.
11.7.2 Loading the Software Upgrade Key
After receiving the Software Upgrade Key file (do not modify its contents in any way),
ensure that its first line is [LicenseKeys] and that it contains one or more lines in the
following format:
S/N<Serial Number of TPM> = <long Software Upgrade Key>
For example: S/N370604 = jCx6r5tovCIKaBBbhPtT53Yj...
One S/N must match the S/N of your device. The device’s S/N can be viewed in the
‘Device Information’ screen (refer to Section
5.7.4 on page 113).
You can load a Software Upgrade Key using:
The Embedded Web Server (refer to Section 11.7.2.1).
The BootP/TFTP configuration utility (refer to Section 11.7.2.2 on page 264).
AudioCodes’ EMS (refer to Section 15.10 on page 326 and to AudioCodes’ EMS
User’s Manual or EMS Product Description).