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 309 October 2006
viewed with a MIB Browser, which is a traditional SNMP management tool incorporated
into virtually all Network Management Systems.
The act of compiling the MIB allows the manager to know about the special objects
supported by the agent and access these objects as part of the standard object set.
15.2 Carrier Grade Alarm System
The basic alarm system has been extended to a carrier-grade alarm system. A carrier-
grade alarm system provides a reliable alarm reporting mechanism that takes into account
EMS outages, network outages, and transport mechanism such as SNMP over UDP.
A carrier-grade alarm system is characterized by the following:
The device has a mechanism that allows a manager to determine which alarms are
currently active in the device. That is, the device maintains an active alarm table.
The device has a mechanism to allow a manager to detect lost alarm raise and clear
notifications [sequence number in trap, current sequence number MIB object].
The device has a mechanism to allow a manager to recover lost alarm raise and clear
notifications [maintains a log history].
The device sends a cold start trap to indicate that it is starting. This allows the EMS to
synchronize its view of the device's active alarms.
When the SNMP alarm traps are sent, the carrier-grade alarm system does not add or
delete alarm traps as part of the feature. This system provides the mechanism for viewing
of history and current active alarm information.
15.2.1 Active Alarm Table
The device maintains an active alarm table to allow a manager to determine which alarms
are currently active in the device. Two views of the active alarm table are supported by the
agent:
acActiveAlarmTable in the enterprise acAlarm
alarmActiveTable and alarmActiveVariableTable in the IETF standard ALARM-MIB
(rooted in the AC tree)
The acActiveAlarmTable is a simple, one-row per alarm table that is easy to view with a
MIB browser.
The ALARM-MIB is currently a draft standard and therefore has no OID assigned to it. In
the current software release, the MIB is rooted in the experimental MIB subtree. In a future
release, after the MIB has been ratified and an OID assigned, it is to move to the official
OID.
15.2.2 Alarm History
The device maintains a history of alarms that have been raised and traps that have been
cleared to allow a manager to recover any lost, raised or cleared traps. Two views of the
alarm history table are supported by the agent:
acAlarmHistoryTable in the enterprise acAlarm
nlmLogTable and nlmLogVariableTable in the standard NOTIFICATION-LOG-MIB
As with the acActiveAlarmTable, the acAlarmHistoryTable is a simple, one-row-per-alarm
table that is easy to view with a MIB browser.