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 158 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
EnableHistoryInfo
[Enable History-Info Header]
Enables usage of the History-Info header.
Valid options include:
0 = Disable (default)
1 = Enable
UAC Behavior:
Initial request: The History-Info header is equal to the Request URI. If a
PSTN Redirect number is received, it is added as an additional History-Info
header with an appropriate reason.
Upon receiving the final failure response, the gateway copies the History-
Info as is, adds the reason of the failure response to the last entry, and
concatenates a new destination to it (if an additional request is sent).
The order of the reasons is as follows:
- Q.850 Reason
- SIP Reason
- SIP Response code
Upon receiving the final (success or failure) response, the gateway
searches for a Redirect reason in the History-Info (i.e., 3xx/4xx SIP
Reason). If found, it is passed to ISDN, according to the following table:
SIP Reason Code ISDN Redirecting Reason
302 – Moved Temporarily Call Forward Universal (CFU)
408 – Request Timeout
480 – Temporarily Unavailable
487 – Request Terminated
Call Forward No Answer (CFNA)
486 – Busy Here
600 – Busy Everywhere
Call Forward Busy (CFB)
If history reason is a Q.850 reason, it is translated to the SIP reason
(according to the SIP-ISDN tables) and then to ISDN Redirect reason
according to the table above.
UAS Behavior:
History-Info is sent in the final response only.
Upon receiving a request with History-Info, the UAS checks the policy in
the request. If 'session', 'header', or 'history' policy tag is found, the (final)
response is sent without History-Info. Otherwise, it is copied from the
request.
SIPSubject
[Subject]
Defines the value of the Subject header in outgoing INVITE messages. If not
specified, the Subject header isn’t included (default).
The maximum length of the subject is limited to 50 characters.
MultiPtimeFormat
[Multiple Packetization Time
Format]
Determines whether the 'mptime' attribute is included in the outgoing SDP.
Valid options include:
0 = Disable (default)
1 = Enable (includes the mptime attribute in the outgoing SDP -- PacketCable
defined format)
The 'mptime' attribute enables the gateway to define a separate Packetization
period for each negotiated coder in the SDP. The 'mptime' attribute is only
included if this parameter is enabled, even if the remote side includes it in the
SDP offer.
Upon reception, each coder receives its 'ptime' value in the following
precedence:
1. From 'mptime' attribute.
2. From 'ptime' attribute.
3. Default value.