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 322 Document #: LTRT-68805
15.7.4 SNMP Ports
The SNMP Request Port is 161 and the Trap Port is 162. These ports can be changed by
setting parameters in the device ini file. The parameter name is:
SNMPPort = <port_number>
Valid UDP port number; default = 161
This parameter specifies the port number for SNMP requests and responses. Usually, it
should not be specified. Use the default.
15.7.5 Multiple SNMP Trap Destinations
An agent can send traps to up to five managers. For each manager, set the manager’s IP
address, receiving port number, and enable sending traps to that manager.
The user also has the option of associating a trap destination with a specific SNMPv3 USM
user. Traps are then sent to that trap destination using the SNMPv3 format and the
authentication and privacy protocol configured for that user..
To configure the trap managers table use:
The Embedded Web Server (refer to Section 5.6.9.1 on page 103).
The ini file (refer to Section 15.7.5.2 below).
SNMP (refer to Section 15.7.5.3 on page 324).
15.7.5.1 Configuring Trap Manager via Host Name
One of the five available SNMP managers can be defined using a FQDN. In the current
version, this option can only be configured via the ini file (SNMPTrapManagerHostName).
The gateway tries to resolve the host name at start up. Once the name is resolved (IP is
found), the resolved IP address replaces the last entry in the trap manager table (defined
by the parameter SNMPManagerTableIP_x) and the last trap manager entry of
snmpTargetAddrTable in the snmpTargetMIB. The port is 162 (unless specified otherwise),
the row is marked as ‘used’ and the sending is ‘enabled’.
When using 'host name' resolution, any changes made by the user to this row in either
MIBs are overwritten by the gateway when a resolving is redone (once an hour).
Note that several traps may be lost until the resolving is complete.
15.7.5.2 Configuring Trap Managers via the ini File
In the IPmedia 2000 ini file, the parameters below can be set to enable or disable the
sending of SNMP traps. Multiple trap destinations can be supported on the device by
setting multiple trap destinations in the ini file.
SNMPManagerTrapSendingEnable_<x>: indicates whether or not traps are to be
sent to the specified SNMP trap manager. A value of ‘1’ means that it is enabled, while
a value of ‘0’ means disabled. <x> represents a number 0, 1, 2 which is the array
element index. Currently, up to five SNMP trap managers can be supported.
SNMPManagerTrapUser_<x>: indicates to send an SNMPv2 trap using the trap user
community string configured with the SNMPTrapCommunityString parameter. The
user may instead specify an SNMPv3 user name.
Figure
15-1 presents an example of entries in a device's ini file regarding SNMP. The
device can be configured to send to multiple trap destinations. The lines in the file below
are commented with the ‘;’ at the beginning of the line. All of the lines below are
commented since the first line character is a semi-colon.