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 56 Document #: LTRT-68805
5.2.1 User Accounts
To prevent unauthorized access to the Embedded Web Server, two user accounts are
available, a primary and secondary. Each account is composed of three attributes:
username, password and access level. The username and password enable access to the
Embedded Web Server itself; the access level determines the extent of the access (i.e.,
availability of screens and read / write privileges). Note that additional accounts can be
defined using a RADIUS server (refer to Section
13.3 on page 294).
Table
5-1 lists the available access levels and their privileges.
Table 5-1: Available Access Levels and their Privileges
Access Level
Numeric
Representation*
Privileges
Security Administrator
200
Read / write privileges for all screens
Administrator
100
Read-only privilege for security-related screens and
read / write privileges for the others
User Monitor
50
No access to security-related and file-loading
screens and read-only access to the others
No Access
0
No access to any screen
* The numeric representation of the access level is used only to define accounts in a RADIUS server (the
access level ranges from 1 to 255).
The access level mechanism operation is as follows (for both Web and RADIUS accounts):
Each Web screen features two (hard-coded) minimum access levels, read and write. The
read access level determines whether the screen can be viewed. The write access level
determines whether the information in the screen can be modified.
When a user tries to access a specific Web screen, his access level is compared with the
access levels of the screen:
If the access level of the user is less than the screen’s read access level, the screen
cannot be viewed.
If the access level of the user is equal to or greater than the screen’s read access
level but less than the write access level, the screen is read only.
If the access level of the user is equal to or greater than the screen’s write access
level, the screen can be modified.
The default attributes for the two accounts are shown in Table
5-2 below:
Table 5-2: Default Attributes for the Accounts
Account / Attribute Username
(Case-Sensitive)
Password
(Case-Sensitive)
Access Level
Primary Account Admin Admin Security Administrator*
Secondary Account User User User Monitor
* The access level of the primary account cannot be changed; all other account-attributes can be modified.
The first time a browser request is made, users are requested to provide their account’s
username and password to obtain access. If the Embedded Web Server is left idle for more
than five minutes, the session expires and the user is required to re-enter his username
and password.