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 4. Getting Started
Version 5.0 53 October 2006
4.3 Configuring the Gateway's Basic Parameters
To configure the gateway's basic parameters use the Embedded Web Server’s ‘Quick
Setup’ screen (shown in Figure
4-1 below). Refer to Section 5.3 on page 58 for information
on accessing the ‘Quick Setup’ screen.
Figure 4-1: Quick Setup Screen
¾ To configure basic SIP parameters, take these 10 steps:
1. If the gateway is connected to a router with NAT (Network Address Translation)
enabled, perform the following procedure. If it isn’t, leave the ‘NAT IP Address’ field
undefined.
• Determine the ‘public’ IP address assigned to the router (by using, for instance,
router Web management). Enter this public IP address in the ‘NAT IP Address’
field.
• Enable the DMZ (Demilitarized Zone) configuration on the residential router for
the LAN port where the gateway gateway is connected. This enables unknown
packets to be routed to the DMZ port.
2. Under ‘SIP Parameters’, enter the gateway's domain name in the field ‘Gateway
Name’. If the field is not specified, the gateway's IP address is used instead (default).
3. When working with a Proxy server, set ‘Working with Proxy’ field to ‘Yes’ and enter the
IP address of the primary Proxy server in the field ‘Proxy IP address’. When no Proxy
is used, the internal routing table is used to route the calls.
4. Enter the Proxy name in the field ‘Proxy Name’. If Proxy name is used, it replaces the
Proxy IP address in all SIP messages. This means that messages is still sent to the
physical Proxy IP address but the SIP URI contains the Proxy name instead.