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 5. Web Management
Version 5.0 55 October 2006
5 Web Management
The Embedded Web Server is used both for gateway configuration, including loading of
configuration files, and for run-time monitoring. The Embedded Web Server can be
accessed from a standard Web browser, such as Microsoft™ Internet Explorer,
Netscape™ Navigator, etc. Specifically, users can employ this facility to set up the gateway
configuration parameters. Users also have the option to remotely reset the gateway and to
permanently apply the new set of parameters.
5.1 Computer Requirements
To use the Embedded Web Server, the following is required:
A computer capable of running your Web browser.
A network connection to the VoIP gateway.
One of the following compatible Web browsers:
• Microsoft™ Internet Explorer™ (version 6.0 and higher).
• Netscape™ Navigator™ (version 7.2 and higher).
Note: The browser must be Java-script enabled. If java-script is disabled, access
to the Embedded Web Server is denied.
5.2 Protection and Security Mechanisms
Access to the Embedded Web Server is controlled by the following protection and security
mechanisms:
User accounts (refer to Section 5.2.1 below).
Read-only mode (refer to Section 5.2.2 below).
Disabling access (refer to Section 5.2.3 below).
Secured HTTP connection (HTTPS) (refer to Section 13.2.2 on page 290).
Limiting access to a predefined list of IP addresses (refer to Section 5.6.8.2 on page
100).
Managed access using a RADIUS server (refer to Section 13.3 on page 294).