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 168 Document #: LTRT-68805
Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169)
ini File Field Name
Web Parameter Name
Valid Range and Description
30 (default), 60, 90,
120
13
T.38
[t38fax]
N/A N/A N/A N/A
G.711A-law_VBD
[g711AlawVbd]
10, 20 (default), 30,
40, 50, 60, 80, 100,
120
Always 64 Dynamic
(0-120)
N/A
G.711U-law_VBD
[g711UlawVbd]
10, 20 (default), 30,
40, 50, 60, 80, 100,
120
Always 64 Dynamic
(0-120)
N/A
Note 1: The coder name is case-sensitive.
Note 2: If silence suppression is not defined (for a specific coder), the value
defined by the parameter EnableSilenceCompression is used.
Note 3: The value of several fields is hard-coded according to well-known
standards (e.g., the payload type of G.711 U-law is always 0). Other values
can be set dynamically. If no value is specified for a dynamic field, a default
value is assigned. If a value is specified for a hard-coded field, the value is
ignored.
Note 4: Only the ptime of the first coder in the defined coder list is declared in
INVITE / 200 OK SDP, even if multiple coders are defined.
Note 5: If the coder G.729 is selected and silence suppression is enabled (for
this coder), the gateway includes the string ‘annexb=no’ in the SDP of the
relevant SIP messages. If silence suppression is set to ‘Enable w/o
Adaptations’, ‘annexb=yes’ is included. An exception to this logic is when the
remote gateway is a Cisco device (IsCiscoSCEMode).
Note 6: Both GSM-FR and MS-GSM coders use Payload Type = 3. Using
SDP, it isn’t possible to differentiate between the two. Therefore, it is highly
recommended not to select both coders simultaneously.
Note 7: This parameter (CoderName_ID) can appear up to 20 times (five
coders in four coder groups).
For example:
CoderName_1 = g711Alaw64k,20,,,0
CoderName_1 = g711Ulaw64k,40
CoderName_1 = g7231,90,1,,1
CoderName_2 = g726,$$,2,,0