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 234 Document #: LTRT-68805
9.4.2 PPPoE Overview
PPPoE is a method of sending the Point-to-Point Protocol over Ethernet network. PPPoE
provides the ability to connect a network of hosts over a simple bridging access device to a
remote Access Concentrator. Access control, billing and type of service can be done on a
per-user, rather than a per-site, basis.
A common use of the PPPoE is in the ADSL market: The home PC is connected to a
modem via Ethernet, and the PC uses the PPPoE to ‘simulate’ as if it was directly
connected to the remote host on a point-to-point connection.
Since PPPoE frames are sent over Ethernet, each PPP session must learn the Ethernet
address of the remote peer, as well as establish a unique session identifier. The PPPoE
standard describes a discovery protocol that provides this. A PPPoE session begins with a
discovery phase. Only after this discovery is completed can the PPP state machine start
(with LCP, Authentication etc, as described above).
Each of the Ethernet frames carrying PPP session has a standard Ethernet header
followed by PPPoE header, and is sent with the remote host Ethernet MAC address
(except for the very first one, in the discovery phase, which is broadcasted to all hosts).
Further information on the transmission of PPPoE is available on the IETF website
(http://www.ietf.org/rfc/rfc2516.txt).
9.4.3 PPPoE in AudioCodes Gateways
The AudioCodes gateway contains a PPPoE client embedded in its software. When
correctly configured (see ini file parameters) the gateway can try to connect to a remote
PPPoE Access Concentrator.
When restarting the gateway after several BOOTP attempts, if PPPoE is enabled (see ini
file parameter EnablePPPoE), the gateway tries to initiate a PPP session.
The gateway initiates a PPPoE discovery phase to discover a PPPoE Access
Concentrator. It does this by broadcasting a discovery initialization packet (PADI). If an
Access Concentrator exists and replies, the gateway tries to connect to this Access
Concentrator. If this initial connection succeeds, then the PPP LCP phase starts - each
side of the PPPoE connection sends LCP configuration requests to configure the PPP link.
The gateway PPPoE client supports both PAP and CHAP authentications. The type of
authentication protocol used is according to the request from the authentication server. In
the LCP configuration phase, the server requires a specific authentication (none, PAP, or
CHAP are supported). The ini file parameters PPPoEUserName, PPPoEPassword, and
PPPoEServerName are used to configure the authentication parameters. If the Access
Concentrator is configured to operate in PAP, the PPPoEUserName and PPPoEPassword
are used as Username and Password (in this case, the PPPoEServerName parameter is
not used). If the Access Concentrator is configured to operate in CHAP, the
PPPoEUserName parameter functions as Client Name (sent in the CHAP response
packet), while the PPPoEPassword functions as the shared secret (calculated along with
the challenge to produce the response). In this case, the PPPoEServerName is the name
of the server. Some hosts can be configured to authenticate to multiple servers. In such
hosts, the server name is used to identify the "secret" that should be used.
Note: The AudioCodes gateway, being a PPPoE client, requests no authentication.
After the gateway has been authenticated, it needs to configure a network layer protocol.
The gateway uses the IP protocol. Therefore, the used NCP will be IPCP (IP Configuration
Protocol). In this phase, if the ini file parameter PPPoEStaticIPAddress is defined, the
gateway requests the remote host to assign this address for its use.