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 112 Document #: LTRT-68805
5.7.3 Activating the Internal Syslog Viewer
The Message Log screen displays Syslog debug messages sent by the gateway.
Note that it is not recommended to keep a ‘Message Log’ session open for a prolonged
period (refer to the Note below). For prolong debugging use an external Syslog server,
refer to Section
14.2 on page 304.
Refer to the Debug Level parameter ‘GwDebugLevel’ (described in Table
6-2) to determine
the Syslog logging level.
¾ To activate the Message Log, take these 4 steps:
1. In the General Parameters screen under Advanced Parameters submenu
(accessed from the Protocol Management menu), set the parameter ‘Debug Level’ to
5. This parameter determines the Syslog logging level, in the range 0 to 5, where 5 is
the highest level.
2. Open the ‘Message Log’ screen (Status & Diagnostics menu > Message Log); the
‘Message Log’ screen is displayed and the Log is activated.
Figure 5-41: Message Log Screen
3. Select the messages, copy them and paste them into a text editor such as Notepad.
Send this txt file to our Technical Support for diagnosis and troubleshooting.
4. To clear the screen of messages, click on the submenu Message Log; the screen is
cleared and new messages begin appearing.
Tip: Do not keep the ‘Message Log’ screen minimized for a prolonged period as
a prolonged session may cause the gateway to overload. As long as the
screen is open (even if minimized), a session is in progress and messages
are sent. Closing the screen (and accessing another) stops the messages
and terminates the session.