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 304 Document #: LTRT-68805
Run-time test (Periodic): Used for monitoring the gateway during run-time.
The Periodic Test is performed every hour after startup, even when there is full traffic
on the gateway; quality is not degraded. The following hardware components are
being tested:
• TSA.
• PSTN framers (when they are used).
• Missing DSP’s.
• Conference channels (where they are supported).
• If an error is detected, an error message is sent to the Syslog.
Warning: To continue regular operation, the Detailed test must be disabled. Set
the parameter EnableDiagnostics to 0 and reset the gateway.
14.2 Syslog Support
Syslog protocol is an event notification protocol that enables a machine to send event
notification messages across IP networks to event message collectors- also known as
Syslog servers. Syslog protocol is defined in the IETF RFC 3164 standard.
Since each process, application and operating system was written independently, there is
little uniformity to Syslog messages. For this reason, no assumption is made on the
contents of the messages other than the minimum requirements of its priority.
Syslog uses UDP as its underlying transport layer mechanism. By default, UDP port 514 is
assigned to Syslog, but this can be changed (using the SyslogServerPort parameter).
The Syslog message is transmitted as an ASCII (American Standard Code for Information
Interchange) message. The message starts with a leading ‘<’ ('less-than' character),
followed by a number, which is followed by a ‘>’ ('greater-than' character). This is optionally
followed by a single ASCII space.
The number described above is known as the Priority and represents both the Facility and
Severity as described below. The Priority number consists of one, two, or three decimal
integers.
For example:
<37> Oct 11 16:00:15 mymachine su: 'su root' failed for lonvick on
/dev/pts/8
Note that when NTP is enabled, a timestamp string [hour:minutes:seconds] is added to all
Syslog messages (for information on NTP, refer to Section
9.8 on page 236).
14.2.1 Syslog Servers
Users can use the provided Syslog server (ACSyslog08.exe) or other third-party Syslog
servers.
Examples of Syslog servers available as shareware on the Internet:
Kiwi Enterprises: www.kiwisyslog.com
The US CMS Server: uscms.fnal.gov/hanlon/uscms_server/
TriAction Software: www.triaction.nl/Products/SyslogDaemon.asp
Netal SL4NT 2.1 Syslog Daemon: www.netal.com
A typical Syslog server application enables filtering of the messages according to priority,
IP sender address, time, date, etc.