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 I. SNMP Traps
Version 5.0 383 October 2006
I SNMP Traps
This section provides information on proprietary SNMP traps currently supported by the
gateway. There is a separation between traps that are alarms and traps that are not (logs).
Currently all have the same structure made up of the same 11 varbinds (Variable Binding)
(1.3.6.1.4.1.5003.9.10.1.21.1).
The source varbind is composed of a string that details the component from which the trap
is being sent (forwarded by the hierarchy in which it resides). For example, an alarm from
an SS7 link has the following string in its source varbind:
acBoard#1/SS7#0/SS7Link#6
In this example, the SS7 link number is specified as 6 and is part of the only SS7 module in
the device that is placed in slot number 1 (in a chassis) and is the module to which this trap
relates. For devices where there are no chassis options the slot number of the gateway is
always 1.
I.1 Alarm Traps
The following tables provide information on alarms that are raised as a result of a
generated SNMP trap. The component name (described in each of the following headings)
refers to the string that is provided in the ‘acBoardTrapGlobalsSource’ trap varbind. To
clear a generated alarm the same notification type is sent but with the severity set to
‘cleared’.
I.1.1 Component: Board#<n>
The source varbind text for all the alarms under this component is Board#<n> where n is
the slot number when the board resides in a chassis (for TP-260 and TP-1610, <n> = 1).
Table I-1: acBoardFatalError Alarm Trap
Alarm:
acBoardFatalError
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.1
Default Severity
Critical
Event Type:
equipmentAlarm
Probable Cause:
underlyingResourceUnavailable (56)
Alarm Text:
Board Fatal Error: <text>
Status Changes:
Condition:
Any fatal error
Alarm status: Critical
<text> value: A run-time specific string describing the fatal error
Condition:
After fatal error
Alarm status: Status stays critical until reboot. A clear trap is not sent.
Corrective Action:
Capture the alarm information and the Syslog clause, if active. Contact your first-
level support group. The support group will likely want to collect additional data
from the device and perform a reset.