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 317 October 2006
¾ To add a read-write community string (v2admin), take these 2
steps:
1. Add a new row to the snmpCommunityTable with CommunityName v2admin.
2. Add a row to the vacmSecurityToGroupTable for SecurityName v2admin, GroupName
ReadWriteGroup and SecurityModel snmpv2c.
¾ To delete the read-write community string (v2admin), take these 2
steps:
1. If v2admin is being used as the trap community string, follow the procedure for
changing the trap community string. (Refer to the procedure below.)
2. Delete the snmpCommunityTable row with a CommunityName of v2admin and
GroupName of ReadWriteGroup.
¾ To change the only read-write community string from v2admin to
v2mgr, take these 4 steps:
1. Follow the procedure above to add a read-write community string to a row for v2mgr.
2. Set up the EM so that subsequent ‘set’ requests use the new community string,
v2mgr.
3. If v2admin is being used as the trap community string, follow the procedure to change
the trap community string (see below).
4. Follow the procedure above to delete a read-write community name in the row for
v2admin.
¾ To change the trap community string, take these 3 steps:
1. Add a row to the vacmSecurityToGroupTable with these values:
• SecurityModel = 2
• SecurityName = the new trap community string
• GroupName = TrapGroup, ReadGroup or ReadWriteGroup
• The SecurityModel and SecurityName objects are row indices
2. Modify the SecurityName field in the sole row of the snmpTargetParamsTable.
3. Remove the row from the vacmSecurityToGroupTable with SecurityName = the old
trap community string.
Notes:
• The procedure above assumes that a row already exists in the
snmpCommunityTable for the new trap community string. The trap
community string can be part of the TrapGroup, ReadGroup, or
ReadWriteGroup. If the trap community string is used solely for
sending traps (recommended), then it should be made part of the
TrapGroup.
• You must add GroupName and RowStatus on the same set.