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 9. Networking Capabilities
Version 5.0 239 October 2006
9.10.2.1 Operation
Outgoing packets (from the gateway to the switch):
All outgoing packets are tagged, each according to its interface (control, media or
OAM). If the gateway’s native ID is identical to one of the other IDs (usually to the
OAM ID), this ID (e.g., OAM) is set to zero on outgoing packets
(VlanSendNonTaggedOnNative = 0). This method is called Priority Tagging (p tag
without Q tag). If the parameter VlanSendNonTaggedOnNative is set to 1, the
gateway sends regular packets (with no VLAN tag).
Incoming packets (from the switch to the gateway):
The switch sends all packets intended for the gateway (according to the switch’s
configuration) to the gateway without altering them. For packets whose VLAN ID is
identical to the switch’s PVID. In this case, the switch removes the tag and sends a
packet.
The gateway only accepts packets that have a VLAN ID identical to one of its
interfaces (control, media or OAM). Packets with a VLAN ID that is 0 or packets
without a tag are accepted only if the gateway’s native VLAN ID is identical to the
VLAN ID of one of its interfaces. In this case, the packets are sent to the relevant
interface. All other packets are rejected.
9.10.3 Getting Started with VLANS and Multiple IPs
By default, the gateway operates without VLANs and multiple IPs, using a single IP
address, subnet mask and default gateway IP address. This section provides an example
of the configuration required to integrate the gateway into a VLAN and multiple IPs network
using the Embedded Web Server (refer to Section
9.10.3.1) and ini file (refer to Section
9.10.3.2 on page 242). Table 9-2 below shows an example configuration that is
implemented in the following sections.
Table 9-2: Example of VLAN and Multiple IPs Configuration
Network
Type
IP Address Subnet Mask
Default
Gateway IP
Address
VLAN ID
External
Routing Rule
OAM 10.31.174.50 255.255.0.0 0.0.0.0 4 83.4.87.X
Control 10.32.174.50 255.255.0.0 0.0.0.0 5 130.33.4.6
Media 10.33.174.50 255.255.0.0 10.33.0.1 6 --
Note that since a default gateway is available only for the Media network, for the gateway
to be able to communicate with an external device / network on its OAM and Control
networks, IP routing rules must be used.
Note: The values provided in Sections 9.10.3.1 and 9.10.3.2 are sample
parameter values only and are to be replaced with actual values
appropriate to your system.