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 310 Document #: LTRT-68805
15.3 Cold Start Trap
The gateway's technology supports a cold start trap to indicate that the device is starting.
This allows the manager to synchronize its view of the device's active alarms. Two different
traps are sent at start-up:
The standard coldStart trap - iso(1).org(3).dod(6).internet(1). snmpV2(6).
snmpModules(3). snmpMIB(1). snmpMIBObjects(1). snmpTraps(5). coldStart(1) - sent
at system initialization.
The enterprise acBoardEvBoardStarted which is generated at the end of system
initialization. This is more of an ‘application-level’ cold start sent after the entire
initializing process is complete and all the modules are ready.
15.4 Third-Party Performance Monitoring Measurements
Performance measurements are available for a third-party performance monitoring system
(or EMS) through an SNMP interface. These measurements can be polled at scheduled
intervals by an external poller or utility in a media server or other off-device system.
The device provides two types of performance measurements:
Gauges: Gauges represent the current state of activities on the device. Gauges,
unlike counters, can decrease in value, and like counters, can increase. The value of a
gauge is the current value or a snapshot of the current activity on the device.
Counters: Counters always increase in value and are cumulative. Counters, unlike
gauges, never decrease in value unless the off-device system is reset. The counters
are then zeroed.
Performance measurements are provided by several proprietary MIBs that are located
under the acPerformance sub tree:
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).audioCodes(5003).acPerformance(
10)
Two formats of performance monitoring MIBs are available:
Old format (obsolete as of version 4.6):
Each MIB is composed of a list of single MIB objects, each relates to a separate
attribute within a gauge or a counter. All counters and gauges provide the current time
value only.
• acPerfMediaGateway: a generic-type of PM MIB that covers:
♦ Control protocol
♦ RTP stream
♦ System packets statistics
• acPerfMediaServices: media services devices specific performance MIB.
• acPerfH323SIPGateway: holds statistics on Tel to IP and vice versa.
New format:
The following MIBs feature an identical structure. Each includes two major sub-trees.
• Configuration sub tree – enables configuration of general attributes of the MIB
and specific attributes of the monitored objects.
• Data sub tree
The monitoring results are presented in tables. Each table includes one or two indices.
When there are two indices, the first index is a sub-set in the table (e.g., trunk number) and
the second (or a single where there is only one) index represents the interval number
(present - 0, previous - 1 and the one before - 2).
The MIBs include:
acPMMedia: for media (voice) related monitoring (e.g., RTP, DSP’s).
acPMControl: for Control-Protocol related monitoring (e.g., connections, commands).