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

SIP User's Manual 6. Gateway's ini File Configuration
Version 5.0 133 October 2006
Table 6-1: Networking Parameters (continues on pages 130 to 138)
ini File Field Name
Web Parameter Name
Valid Range and Description
SyslogServerIP
[Syslog Server IP Address]
IP address (in dotted format notation) of the computer you are using to run the
Syslog Server.
The Syslog Server is an application designed to collect the logs and error
messages generated by the VoIP gateway.
Note: Use the SyslogServerPort parameter to define the Syslog server's port.
For information on the Syslog server, refer to Section
14.2 on page 304.
SyslogServerPort
[Syslog Server Port]
Defines the UDP port of the Syslog server.
The valid range is 0 to 65,535. The default port value is 514.
For information on the Syslog server, refer to Section
14.2 on page 304.
EnableSyslog
[Enable Syslog]
Sends the logs and error message generated by the gateway to the Syslog
Server.
0 = Disable (logs and errors are not sent to the Syslog Server -- default).
1 = Enable.
Note1: If you enable Syslog (i.e, EnableSyslog = 1), you must enter an IP
address and a port number using SyslogServerIP and SyslogServerPort
parameters.
Note 2: Syslog messages may increase the network traffic.
Note 3: To configure the Syslog logging levels use the parameter
‘GwDebugLevel’.
BaseUDPport
[RTP Base UDP Port]
Lower boundary of UDP port used for RTP, RTCP (Real-Time Control Protocol)
(RTP port + 1) and T.38 (RTP port + 2). The upper boundary is the Base UDP
Port + 10 * (number of gateway’s channels).
The range of possible UDP ports is 6,000 to 64,000.
The default base UDP port is 6000.
For example:
If the Base UDP Port is set to 6000 (the default) then:
The first channel uses the following ports: RTP 6000, RTCP 6001 and T.38
6002;
the second channel uses: RTP 6010, RTCP 6011 and T.38 6012, etc.
Note: If RTP Base UDP Port is not a factor of 10, the following message is
generated: ‘invalid local RTP port’.
For detailed information on the default RTP/RTCP/T.38 port allocation, refer to
Section
E.3 on page 366.
RemoteBaseUDPPort
[Remote RTP Base UDP
Port]
Determines the lower boundary of UDP ports used for RTP, RTCP and T.38 by
a remote gateway. If this parameter is set to a non-zero value,
ThroughPacket™ is enabled. 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.
The valid range is the range of possible UDP ports: 6,000 to 64,000.
The default value is 0 (ThroughPacket™ is disabled).
Note: To enable ThroughPacket™ the parameters ‘L1L1ComplexTxUDPPort’
and ‘L1L1ComplexRxUDPPort’ must be set to a non-zero value.
For detailed information on ThroughPacket™, refer to Section
8.4 on page 212.
L1L1ComplexTxUDPPort
[RTP Multiplexing Local UDP
Port]
Determines the local UDP port used for outgoing multiplexed RTP packets
(applies to the ThroughPacket™ mechanism).
The valid range is the range of possible UDP ports: 6,000 to 64,000.
The default value is 0 (ThroughPacket™ is disabled).
This parameter cannot be changed on-the-fly and requires a gateway reset.