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 316 Document #: LTRT-68805
15.7.1 SNMP Community Names
By default, the device uses a single, read-only community string of ‘public’ and a single
read-write community string of ‘private’.
The following community strings can be defined:
Up to five read-only community strings
Up to five read-write community strings
A single trap community string
Each community string must be associated with one of the following predefined SNMP
groups:
Table 15-2: SNMP Predefined Groups
Group Get Access Set Access Can Send Traps
ReadGroup
Yes No Yes
ReadWriteGroup
Yes Yes Yes
TrapGroup
No No Yes
15.7.1.1 Configuration of Community Strings via the Web
For detailed information on configuration the community strings via the Embedded Web
Server, refer to Section
5.6.9.2 on page 104.
15.7.1.2 Configuration of Community Strings via the ini File
The following ini file parameters are used to configure community strings:
SNMPReadOnlyCommunityString_<x> = '#######'
SNMPReadWriteCommunityString_<x> = '#######'
Where <x> is a number from 0 to 4. The '#' character represents any alphanumeric
character. The maximum length of the string is 20 characters.
15.7.1.3 Configuration of Community Strings via SNMP
To configure read-only and read-write community strings, the EM must use the
snmpCommunityMIB. To configure the trap community string, the EM must also use the
snmpVacmMIB and the snmpTargetMIB.
¾ To add a read-only community string (v2user), take these 2 steps:
1. Add a new row to the snmpCommunityTable with CommunityName v2user.
2. Add a row to the vacmSecurityToGroupTable for SecurityName v2user, GroupName
ReadGroup and SecurityModel snmpv2c.
¾ To delete the read-only community string (v2user), take these 3
steps:
1. If v2user is being used as the trap community string, follow the procedure for changing
the trap community string. (See below.)
2. Delete the snmpCommunityTable row with CommunityName v2user.
3. Delete the vacmSecurityToGroupTable row for SecurityName v2user, GroupName
ReadGroup and SecurityModel snmpv2c.