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 63 October 2006
5.5 Protocol Management
Use this menu to configure the gateway’s SIP parameters and tables.
5.5.1 Protocol Definition Parameters
Use this submenu to configure the following gateway’s specific SIP protocol parameters:
General Parameters
Proxy & Registration Parameters
Coders (refer to Section 5.5.1.1 below)
DTMF & Dialing Parameters
5.5.1.1 Coders
From the Coders screen you can configure the first to fifth preferred coders (and their
attributes) for the gateway. The first coder is the highest priority coder and is used by the
gateway whenever possible. If the far end gateway cannot use the coder assigned as the
first coder, the gateway attempts to use the next coder and so forth.
¾ To configure the gateway’s coders, take these 9 steps:
1. Open the ‘Coders’ screen (Protocol Management menu > Protocol Definition
submenu > Coders option); the ‘Coders’ screen is displayed.
Figure 5-5: Coders Screen
2. From the Coder Name drop-down list, select the coder you want to use. For the full list
of available coders and their corresponding attributes, refer to the ini file parameter
‘CoderName’ (described in Table 6-7).
Note: Each coder can appear only once.
3. From the Packetization Time drop-down list, select the packetization time (in msec) for
the coder you selected. The packetization time determines how many coder payloads
are combined into a single RTP packet.
Note 1: If not specified, the ptime gets a default value.
Note 2: The ptime specifies the packetization time the gateway expects to receive.
The gateway always uses the ptime requested by the remote side for sending RTP
packets.
4. From the Rate drop-down list, select the bit rate (in kbps) for the coder you selected.
5. In the Payload Type field, if the payload type for the coder you selected is dynamic,
enter a value from 0 to 120 (payload types of ‘well-known’ coders cannot be modified).
The payload type identifies the format of the RTP payload.
Note: If not specified, a default is used.