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
Mediant 2000 & TP-1610 & TP-260
SIP User's Manual 222 Document #: LTRT-68805
8.11 Proxy or Registrar Registration Example
REGISTER sip:servername SIP/2.0
VIA: SIP/2.0/UDP 212.179.22.229;branch=z9hG4bRaC7AU234
From: <sip:GWRegistrationName@sipgatewayname>;tag=1c29347
To: <sip:GWRegistrationName@sipgatewayname>
Call-ID: mailto:10453@212.179.22.229
Seq: 1 REGISTER
Expires: 3600
Contact: sip:GWRegistrationName@212.179.22.229
Content-Length: 0
The ‘servername’ string is defined according to the following rules:
The ‘servername’ is equal to ‘RegistrarName’ if configured. The ‘RegistrarName’ can
be any string.
Otherwise, the ‘servername’ is equal to ‘RegistrarIP’ (either FQDN or numerical IP
address), if configured.
Otherwise the ‘servername’ is equal to ‘ProxyName’ if configured. The ‘ProxyName’
can be any string.
Otherwise the ‘servername’ is equal to ‘ProxyIP’ (either FQDN or numerical IP
address).
The parameter ‘GWRegistrationName’ can be any string. If the parameter is not defined,
the parameter ‘UserName’ is used instead.
The ‘sipgatewayname’ parameter (defined in the ini file or set from the Web browser), can
be any string. Some Proxy servers require that the ‘sipgatewayname’ (in REGISTER
messages) is set equal to the Registrar / Proxy IP address or to the Registrar / Proxy
domain name.
REGISTER messages are sent to the Registrar’s IP address (if configured) or to the
Proxy’s IP address. A single message is sent once per gateway, or messages are sent per
B-channel according to the parameter ‘AuthenticationMode’. The registration request is
resent according to the parameter ‘RegistrartionTimeDivider’. For example, if
‘RegistrationTimeDivider = 70’ (%) and Registration Expires time = 3600, the gateway
resends its registration request after 3600 x 70% = 2520 sec. The default value of
‘RegistrartionTimeDivider’ is 50%.
If registration per B-channel is selected, on gateway startup, the gateway sends
REGISTER requests according to the maximum number of allowed SIP dialogs (configured
by the parameter NumberOfActiveDialogs). After each received response, the subsequent
REGISTER request is sent.