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 320 Document #: LTRT-68805
Note: A row with the same security level (authPriv) must already exist in the
usmUserTable (see the usmUserTable for details).
¾ To delete the read-write, authPriv SNMPv3 user (v3admin1), take
these 3 steps:
1. If v3admin1 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 v3admin1, GroupName
ReadWriteGroup1, and SecurityModel usm.
3. Delete the row in the usmUserTable for v3admin1.
15.7.3 Trusted Managers
By default, the agent accepts ‘get’ and ‘set’ requests from any IP address, as long as the
correct community string is used in the request. Security can be enhanced via the use of
Trusted Managers. A Trusted Manager is an IP address from which the SNMP Agent
accepts and processes ‘get’ and ‘set’ requests. An EM can be used to configure up to five
Trusted Managers.
Note: If Trusted Managers are defined, all community strings work from all
Trusted Managers. That is, there is no way to associate a community string
with particular trusted managers.
The concept of trusted managers is considered to be a weak form of security and is
therefore, not a required part of SNMPv3 security, which uses authentication and privacy.
However, the board’s SNMP agent applies the trusted manager concept as follows:
There is no way to configure trusted managers for only a SNMPv3 user. An SNMPv2c
community string must be defined.
If specific IPs are configured as trusted managers (via the community table), then only
SNMPv3 users on those trusted managers are given access to the agent’s MIB
objects.
15.7.3.1 Configuration of Trusted Managers via ini File
To set the Trusted Mangers table from start-up, write the following in the ini file:
SNMPTRUSTEDMGR_X = D.D.D.D
where X is any integer between 0 and 4 (0 sets the first table entry, 1 sets the second, and
so on), and D is an integer between 0 and 255.
15.7.3.2 Configuration of Trusted Managers via SNMP
To configure Trusted Managers, the EM must use the SNMP-COMMUNITY-MIB, the
snmpTargetMIB and the snmpTargetMIB.
The procedure below assumes that there is at least one configured read-write community,
are currently no Trusted Managers, and the TransportTag for columns for all
snmpCommunityTable rows are currently empty.