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 389 October 2006
Table I-12: acSS7LinkCongestionStateChangeAlarm Trap
Alarm:
acSS7LinkCongestionStateChangeAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.22
Default Severity
Major
Event Type:
communicationsAlarm
Probable Cause:
Other
Alarm Text:
*** SS7 *** Link %i is %s %s
Status Changes:
Condition:
SS7 link becomes congested (local or remote).
Alarm status: Major
<text> value: %i - <Link number>
%s – If link has MTP3 layer, then this string equals:
(SP %i linkset %i slc %i)
Where:
%i - <SP number>
%i - <Link-Set number>
%i - <SLC number>
Otherwise there is NO additional text.
%s - <congestion state>: { “UNCONGESTED”, “CONGESTED” }
Additional
Info1 varbind
CONGESTED
Condition:
Link becomes un-congested (local AND remote).
Alarm status: Cleared
Corrective Action:
Reduce SS7 traffic on that link.
Note:
This alarm is raised for any change in the remote or local congestion
status.
I.1.5 Log Traps (Notifications)
This section details traps that are not alarms. These traps are sent with the severity varbind
value of ‘indeterminate’. These traps don’t ‘clear’, they don’t appear in the alarm history or
active tables. One log trap that does send clear is
acPerformanceMonitoringThresholdCrossing.
Table I-13: acKeepAlive Log Trap
Trap:
acKeepAlive
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.16
Default Severity
Indeterminate
Event Type:
other (0)
Probable Cause:
other (0)
Trap Text:
Keep alive trap
Status Changes:
Condition:
The STUN client in is enabled and identified a NAT device or doesn’t locate the
STUN server.
The ini file contains the following line: ‘SendKeepAliveTrap=1’
Trap status: Trap is sent
Note:
Keep-alive is sent every 9/10 of the time defined in the parameter
NatBindingDefaultTimeout.