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 214 Document #: LTRT-68805
8.5 ThroughPacket™
The gateway supports a proprietary method to aggregate RTP streams from several
channels to reduce the bandwidth overhead caused by the attached Ethernet, IP, UDP and
RTP headers, and to reduce the packet / data transmission rate. This option reduces the
load on network routers and can typically save 50% (e.g., for G.723) on IP bandwidth.
ThroughPacket™ is accomplished by aggregating payloads from several channels that are
sent to the same destination IP address into a single IP packet.
ThroughPacket™ can be applied to the entire gateway or, using IP Profile, to specific IP
destinations (refer to Section
5.5.6.3 on page 80). Note that ThroughPacket™ must be
enabled on both gateways.
To enable ThroughPacket™ set the parameter ‘RemoteBaseUDPPort’ to a nonzero value.
Note that the value of ‘RemoteBaseUDPPort’ on the local gateway must equal the value of
‘BaseUDPPort’ of the remote gateway. The gateway uses these parameters to identify and
distribute the payloads from the received multiplexed IP packet to the relevant channels.
In ThroughPacket™ mode, the gateway uses a single UDP port for all incoming
multiplexed packets and a different port for outgoing packets. These ports are configured
using the parameters ‘L1L1ComplexTxUDPPort’ and ‘L1L1ComplexRxUDPPort’.
When ThroughPacket™ is used, Call statistics aren’t available (since there is no RTCP
flow).