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 151 October 2006
Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169)
ini File Field Name
Web Parameter Name
Valid Range and Description
ProxyIP
ProxyIP
ProxyIP
[Redundant Proxy IP Address]
IP addresses of the redundant Proxies you are using.
Enter the IP address as FQDN or in dotted format notation (for example
192.10.1.255). You can also specify the selected port in the format: <IP
Address>:<port>.
Note 1: This parameter is available only if you select ‘Yes’ in the ‘Is Proxy
Used’ field.
Note 2: When port number is specified, DNS NAPTR/SRV queries aren’t
performed, even if ProxyDNSQueryType is set to 1 or 2.
Note ini file: The IP addresses of the redundant Proxies are defined by the
second, third and fourth repetition of the ini file parameter ‘ProxyIP’.
ProxyName
[Proxy Name]
Home Proxy Domain Name. If specified, the name is used as Request-URI in
REGISTER, INVITE and other SIP messages.
If the proxy name isn’t specified, the Proxy IP address is used instead.
EnableProxySRVQuery
[Enable Proxy SRV Queries]
This parameter is now obsolete. Please use the parameter
ProxyDNSQueryType.
EnableSRVQuery
[Enable SRV Queries]
This parameter is now obsolete. Please use the parameter DNSQueryType.
AlwaysSendToProxy
[Always Use Proxy]
0 = Use standard SIP routing rules (default).
1 = All SIP messages and Responses are sent to Proxy server.
Note: Applicable only if Proxy server is used.
SendInviteToProxy
[Send All INVITE to Proxy]
0 = INVITE messages, generated as a result of Transfer or Redirect, are sent
directly to the URI (according to the Refer-To header in the REFER message
or Contact header in 30x response) (default).
1 = All INVITE messages, including those generated as a result of Transfer or
Redirect are sent to Proxy.
Note: Applicable only if Proxy server is used and ‘AlwaysSendtoProxy=0’.
PreferRouteTable
[Prefer Routing Table]
Determines if the local Tel to IP routing table takes precedence over a Proxy
for routing calls.
0 = Only Proxy is used to route calls (default).
1 = The gateway checks the 'Destination IP Address' field in the 'Tel to IP
Routing' table for a match with the outgoing call. Only if a match is not found, a
Proxy is used.
Note: Applicable only if Proxy is not always used (‘AlwaysSendToProxy’ = 0,
‘SendInviteToProxy’ = 0).
EnableProxyKeepAlive
[Enable Proxy Keep Alive]
0 = Disable (default).
1 = Enable Keep alive with Proxy using OPTIONS.
2 = Enable Keep alive with Proxy using REGISTER.
If EnableProxyKeepAlive = 1, SIP OPTIONS message is sent every
ProxyKeepAliveTime. If EnableProxyKeepAlive = 2, SIP REGISTER message
is sent every RegistrationTime. Any response from the Proxy, either success
(200 OK) or failure (4xx response) is considered as if the Proxy is correctly
communicating.
Note 1: This parameter must be set to 1 (OPTIONS) when Proxy redundancy
is used.
Note 2: When EnableProxyKeepAlive = 2 (REGISTER), the homing
redundancy mode is disabled.
Note 3: When the active proxy doesn't respond to INVITE messages sent by
the gateway, the proxy is marked as offline. The behavior is similar to a Keep-
Alive (OPTIONS or REGISTER) failure.
ProxyKeepAliveTime
[Proxy Keep Alive Time]
Defines the Proxy keep-alive time interval (in seconds) between Keep-Alive
messages.
The default value is 60 seconds.
Note: This parameter is applicable only if EnableProxyKeepAlive = 1
(OPTIONS). When EnableProxyKeepAlive = 2 (REGISTER), the time interval
between Keep-Alive messages is determined by the parameter
RegistrationTime.