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 318 Document #: LTRT-68805
15.7.2 SNMP v3 USM Users
You can define up to 10 User-based Security Model (USM) users (USM users are referred
to as “v3 users”). Each v3 user can be associated with an authentication type (none, MD5,
or SHA-1) and a privacy type (none, DES, 3DES, or AES).
Table 15-3: SNMP v3 Security Levels
Security Level Authentication Privacy
noAuthNoPriv(1)
None None
authNoPriv(2)
MD5 or SHA-1 None
authPriv(3)
MD5 or SHA-1 DES, 3DES, AES128, AES192, or
AES256
Each SNMP v3 user must be associated with one of the predefined groups listed in the
following table:
Table 15-4: SNMP v3 Predefined Groups
Group Get Access Set Access Send Traps Security Level
ReadGroup1
Yes No Yes noAuthNoPriv(1)
ReadWriteGroup1
Yes Yes Yes noAuthNoPriv(1)
TrapGroup1
No No Yes noAuthNoPriv(1)
ReadGroup2
Yes No Yes authNoPriv(2)
ReadWriteGroup2
Yes Yes Yes authNoPriv(2)
TrapGroup2
No No Yes authNoPriv(2)
ReadGroup3
Yes No Yes authPriv(3)
ReadWriteGroup3
Yes Yes Yes authPriv(3)
TrapGroup3
No No Yes authPriv(3)
15.7.2.1 Configuring SNMP v3 users via the ini File
Use the SNMPUsers ini table to add, modify, and delete SNMPv3 users. For a description
of the SNMPUsers table ini file parameters, refer to Section
6.11 on page 148.
Note: The SNMPUsers ini table is a hidden parameter. Therefore, when you
perform a “Get ini File” operation using the Web interface, the table will not
be included in the generated file.
You can enter keys in the form of a text password or in the form of a localized key in hex
format. If using a text password, then it should be at least eight characters in length. Below
is an example of a localized key format:
26:60:d8:7d:0d:4a:d6:8c:02:73:dd:22:96:a2:69:df