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

SIP User's Manual 15. SNMP-Based Management
Version 5.0 319 October 2006
The following example configuration creates three SNMPv3 USM users:
[ SNMPUsers ]
FORMAT SNMPUsers_Index = SNMPUsers_Username, SNMPUsers_AuthProtocol,
SNMPUsers_PrivProtocol, SNMPUsers_AuthKey, SNMPUsers_PrivKey, SNMPUsers_Group;
SNMPUsers 0 = v3user, 0, 0, -, -, 0;
SNMPUsers 1 = v3admin1, 1, 0, myauthkey, -, 1;
SNMPUsers 2 = v3admin2, 2, 1, myauthkey, myprivkey, 1;
[ \SNMPUsers ]
The example above creates the following three v3 users:
The user "v3user" is defined for a security level of noAuthNoPriv(1) and is associated
with ReadGroup1.
The user "v3admin1" is defined for a security level of authNoPriv(2) with
authentication protocol MD5. The authentication text password is “myauthkey” and the
user will be associated with ReadWriteGroup2.
The user "v3admin2" is defined for a security level of authPriv(3) with authentication
protocol SHA-1 and privacy protocol DES. The authentication text password is
“myauthkey”, the privacy text password is “myprivkey”, and the user will be associated
with ReadWriteGroup3.
15.7.2.2 Configuring SNMP v3 Users via SNMP
To configure SNMP v3 users, the EM must use the standard snmpUsmMIB and the
snmpVacmMIB.
¾ To add a read-only, noAuthNoPriv SNMPv3 user (v3user), take
these 3 steps:
1. Clone the row with the same security level. After the clone step, the status of the row
is notReady(3).
2. Activate the row (i.e., set the row status to active(1)).
3. Add a row to the vacmSecurityToGroupTable for SecurityName v3user, GroupName
ReadGroup1, and SecurityModel usm(3).
Note: A row with the same security level (noAuthNoPriv) must already exist in the
usmUserTable. (See the usmUserTable for details).
¾ To delete the read-only, noAuthNoPriv SNMPv3 user (v3user), take
these 3 steps:
1. If v3 user is associated with a trap destination, follow the procedure for associating a
different user to that trap destination. (See below.)
2. Delete the vacmSecurityToGroupTable row for SecurityName v3user, GroupName
ReadGroup1, and SecurityModel usm.
3. Delete the row in the usmUserTable for v3user.
¾ To add a read-write, authPriv SNMPv3 user (v3user), take these 4
steps:
1. Clone the row with the same security level.
2. Change the authentication key and privacy key.
3. Activate the row. That is, set the row status to active(1).
4. Add a row to the vacmSecurityToGroupTable for SecurityName v3admin1,
GroupName ReadWriteGroup3, and SecurityModel usm(3).