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 11. Advanced System Capabilities
Version 5.0 251 October 2006
11.4 Startup Process
The startup process (illustrated in Figure 11-3 on page 252) begins when the gateway is
reset (physically or from the Web / SNMP) and ends when the operational software is
running. In the startup process, the network parameters, software and configuration files
are obtained.
After the gateway powers up or after it is physically reset, it broadcasts a BootRequest
message to the network. If it receives a reply (from a BootP server), it changes its network
parameters (IP address, subnet mask and default gateway address) to the values
provided. If there is no reply from a BootP server and if DHCP is enabled (DHCPEnable =
1), the gateway initiates a standard DHCP procedure to configure its network parameters.
After changing the network parameters, the gateway attempts to load the cmp and various
configuration files from the TFTP server’s IP address, received from the BootP/DHCP
servers. If a TFTP server’s IP address isn’t received, the gateway attempts to load the
software (cmp) file and / or configuration files from a preconfigured TFTP server (refer to
Section
11.3 on page 249). Thus, the gateway can obtain its network parameters from
BootP or DHCP servers and its software and configuration files from a different TFTP
server (preconfigured in ini file).
If BootP/DHCP servers are not found or when the gateway is reset from the Web / SNMP,
it retains its network parameters and attempts to load the software (cmp) file and / or
configuration files from a preconfigured TFTP server.
If a preconfigured TFTP server doesn’t exist, the gateway operates using the existing
software and configuration files loaded on its non-volatile memory.
Note that after the operational software runs, if DHCP is configured, the gateway attempts
to renew its lease with the DHCP server.
Notes:
• Though DHCP and BootP servers are very similar in operation, the
DHCP server includes some differences that could prevent its operation
with BootP clients. However, many DHCP servers, such as Windows
™
NT DHCP server, are backward-compatible with BootP protocol and can
be used for gateway configuration.
• The time duration between BootP/DHCP requests is set to 1 second by
default. This can be changed by the BootPDelay ini file parameter. Also,
the number of requests is 3 by default and can be changed by
BootPRetries ini file parameter. (Both parameters can also be set using
the BootP command line switches).