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 236 Document #: LTRT-68805
9.8 Simple Network Time Protocol Support
The Simple Network Time Protocol (SNTP) client functionality generates requests and
reacts to the resulting responses using the NTP version 3 protocol definitions (according to
RFC 1305). Through these requests and responses, the NTP client is able to synchronize
the system time to a time source within the network, thereby eliminating any potential
issues should the local system clock 'drift' during operation. By synchronizing time to a
network time source, traffic handling, maintenance, and debugging actions become
simplified for the network administrator.
The NTP client follows a simple process in managing system time; the NTP client requests
an NTP update, receives an NTP response, and updates the local system clock based on a
configured NTP server within the network.
The client requests a time update from a specified NTP server at a specified update
interval. In most situations this update interval should be every 24 hours based on when
the system was restarted. The NTP server identity (as an IP address) and the update
interval are configurable parameters that can be specified either in the ini file
(NTPServerIP, NTPUpdateInterval respectively) or via an SNMP MIB object.
When the client receives a response to its request from the identified NTP server it must be
interpreted based on time zone, or location, offset that the system is to a standard point of
reference called the Universal Time Coordinate (UTC). The time offset that the NTP client
should use is a configurable parameter that can be specified either in the ini file
(NTPServerUTCOffset) or via an SNMP MIB object.
If required, the clock update is performed by the client as the final step of the update
process. The update is done in such a way as to be transparent to the end users. For
instance, the response of the server may indicate that the clock is running too fast on the
client. The client slowly robs bits from the clock counter in order to update the clock to the
correct time. If the clock is running too slow, then in an effort to catch the clock up, bits are
added to the counter, causing the clock to update quicker and catch up to the correct time.
The advantage of this method is that it does not introduce any disparity in the system time,
that is noticeable to an end user, or that could corrupt call timeouts and timestamps.
9.9 IP QoS via Differentiated Services (DiffServ)
DiffServ is architecture providing different types or levels of service for IP traffic. DiffServ
(according to RFC 2474) offers the capability to prioritize certain traffic types, depending on
their priority, thereby accomplishing a higher-level QoS at the expense of other traffic
types. By prioritizing packets, DiffServ routers can minimize transmission delays for time-
sensitive packets such as VoIP packets.
The gateway can be configured to set a different DiffServ value to IP packets according to
their class-of-service (Network, Premium Media, Premium Control, Gold and Bronze).
For the mapping of an application to its class-of-service, refer to Table
9-1 on page 238.
The DiffServ parameters are described in Table
6-1 on page 130.