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 164 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
TxDTMFOption
[DTMF RFC2833 Negotiation]
Determines a single or several preferred transmit DTMF negotiation methods.
0 (Not Supported) = No negotiation, DTMF digits are sent according to the
parameters ‘DTMFTransportType’ and ‘RFC2833PayloadType’ (default).
1 (INFO Nortel) = Sends DTMF digits according to IETF <draft-choudhuri-sip-
info-digit-00>.
2 (NOTIFY) = Sends DTMF digits according to <draft-mahy-sipping-signaled-
digits-01>.
3 (INFO Cisco) = Sends DTMF digits according to Cisco format.
4 (RFC 2833).
Note 1: DTMF negotiation methods are prioritized according to the order of
their appearance.
Note 2: When out-of-band DTMF transfer is used (1, 2 or 3), the parameter
‘DTMFTransportType’ is automatically set to 0 (DTMF digits are erased from
the RTP stream).
Note 3: When RFC 2833 (4) is selected, the gateway:
• Negotiates RFC 2833 Payload Type (PT) using local and remote SDPs.
• Sends DTMF packets using RFC 2833 PT according to the PT in the
received SDP.
• Expects to receive RFC 2833 packets with the same PT as configured by
the parameter ‘RFC2833PayloadType’.
• Uses the same PT for send and receive if the remote party doesn’t include
the RFC 2833 DTMF PT in its SDP.
Note 4: When TxDTMFOption is set to 0, the RFC 2833 PT is set according to
the parameter ‘RFC2833PayloadType’ for both transmit and receive.
ini file note: The DTMF transmit methods are defined using a repetition of the
same (TxDTMFOption) parameter (up to five options can be provided).
DisableAutoDTMFMute
Enables / disables the automatic mute of DTMF digits when out-of-band DTMF
transmission is used.
0 = Auto mute is used (default).
1 = No automatic mute of in-band DTMF.
When ‘DisableAutoDTMFMute=1’, the DTMF transport type is set according to
the parameter ‘DTMFTransportType’ and the DTMF digits aren’t muted if out-
of-band DTMF mode is selected (’TxDTMFOption =1, 2 or 3’). This enables the
sending of DTMF digits in-band (transparent of RFC 2833) in addition to out-
of-band DTMF messages.
Note: Usually this mode is not recommended.
EnableReasonHeader
[Enable Reason Header]
Enables or disables the usage of the SIP Reason header.
Valid options include:
0 = Disable
1 = Enable (default)
EnableSemiAttendedTransf
er
[Enable Semi-Attended
Transfer]
Determines the gateway behavior when a Transfer is initiated while still in
Alerting state.
Valid options include:
0 = Send REFER with Replaces (default).
1 = Send CANCEL, and after a 487 response is received, send REFER
without Replaces.
3xxBehavior
[3xx Behavior]
Determines the gateway’s behavior when a 3xx response is received for an
outgoing INVITE request. The gateway can either use the same call identifiers
(CallID, branch, to and from tags) or change them in the new initiated INVITE.
0 (forward) = Use different call identifiers for a redirected INVITE message
(default).
1 (redirect) = Use the same call identifiers.