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 270 Document #: LTRT-68805
12.2.1 MTP2 Tunneling Technology
The SS7 tunneling technology is based on a pairing of remote and central gateways, as
shown in Figure
12-5. The remote gateways are configured to backhaul MTP layer 2
signaling over the IP network using standard M2UA protocol (over SCTP protocol). The
function of the M2TN entity is to transmit traffic and handle all management events
between MTP2 on the TDM side and M2UA's MGC (Media Gateway Controller) entity on
the IP side. Only the actual SS7 MSU (Message Signaling Unit) data is sent. Management
of the SS7 link is performed using M2UA without transporting the MTP2 LSSU (Link Status
Signaling Unit) and FISU (Fill in Signaling Unit) messages over IP. These messages, in
addition to MTP2 timing, are terminated and supported, respectively, by the remote and
central sides. Therefore, the MTP2 connections are not affected by the fact that they are
transported over IP.
Figure 12-5: Protocol Architecture for MTP2 Tunneling
12.2.2 SS7 Characteristics
Only standard protocols are used on external interfaces (MTP2 on PSTN side, and
M2UA over SCTP on IP side) - the M2TN application resides internally on the
gateway.
No extra signaling point codes are required; both endpoints are unaware that the SS7
connection is via IP.
Several links from multiple SS7 nodes can be concentrated into a single board on the
‘Central’ side (using several SCTP associations per gateway).
The gateways can handle SS7 MTP2 tunneling and voice concurrently (does not
require additional gateway or other server).
Voice and signaling can be transferred on the same E1/T1 trunk (F-Links).
IP traffic can be monitored via standard sniffing tools (e.g. protocol analyzers).
Note: Channels that are used for SS7 Tunneling mustn’t be defined in the Trunk
Group table.