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 13. Security
Version 5.0 291 October 2006
The figure below is an example of a host file:
Figure 13-8: Example of a Host File
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# Location: C:\WINDOWS\SYSTEM32\DRIVERS\ETC\hosts
#
127.0.0.1 localhost
10.31.4.47 ACL_280152
13.2.3 Secured Telnet
To enable the embedded Telnet server on the gateway, set the parameter
TelnetServerEnable (described in Table
6-3 on page 143) to 1 (standard mode) or 2 (SSL
mode); no information is transmitted in the clear when SSL mode is used.
If the Telnet server is set to SSL mode, a special Telnet client is required on your PC to
connect to the Telnet interface over a secured connection; examples include C-Kermit for
UNIX, Kermit-95 for Windows, and AudioCodes' acSSLTelnet utility for Windows (that
requires prior installation of the free OpenSSL toolkit). Contact AudioCodes to obtain the
acSSLTelnet utility.
13.2.4 Server Certificate Replacement
The gateway is supplied with a working SSL configuration consisting of a unique self-
signed server certificate. When the gateway is upgraded to a later firmware version, a
unique self-signed server certificate is created. If an organizational Public Key
Infrastructure (PKI) is used, you may wish to replace this certificate with one provided by
your security administrator.
¾ To replace the gateway's self-signed certificate, take these 9 steps:
1. Your network administrator should allocate a unique DNS name for the gateway (e.g.,
dns_name.corp.customer.com). This name is used to access the device, and should
therefore be listed in the server certificate.
2. Open the ‘Certificate’ screen (Advanced Configuration menu > Security Settings
submenu > Certificates option); the ‘Certificates’ screen is displayed (Figure 13-9).