AudioCodes Media Pack MP-112, Руководство пользователя

Страница: 463 / 486

Version 5.8 463 September 2009
SIP User's Manual 10. Networking Capabilities
•
One IPv4 interface with "Application Types" OAMP, one other or more IPv4
interfaces with "Application Types" CONTROL, and one or more IPv4 interfaces
with "Application Types" MEDIA (with VLANs).
•
One IPv4 interface with "Application Types" OAMP & MEDIA, one other or more
IPv4 interfaces with "Application Types" MEDIA & CONTROL.
•
Other configurations are also possible while keeping to the above-mentioned rule.

Only one interface may have a Gateway definition for each address family (IPv4). This
Gateway address must be in the same subnet as this interface; other routing rules may
be specified in the Routing Table. Refer to the Routing Table section below, for more
details.

Apart from the interface having the default gateway defined, the Gateway column for
all other interfaces must be set to "0.0.0.0" for IPv4.

The Interface Name column may have up to 16 characters. This column allows the
user to name each interface with an easier name to associate the interface with. This
column must have a unique value to each interface and must not be left blank.

For IPv4 interfaces, the "Interface Mode" column must be set to "IPv4 Manual"
(numeric value 10).

When defining more than one interface of the same address family, VLANs must be
enabled (the VlanMode should be set to 1).

VLANs become available only when booting the device from flash. When booting using
BootP/DHCP protocols, VLANs are disabled to allow easier maintenance access. In
this scenario, multiple network interface capabilities are not available.

The 'Native' VLAN ID may be defined using the 'VlanNativeVlanId' parameter. This
relates untagged incoming traffic as if reached with a specified VLAN ID. Outgoing
traffic from the interface which VLAN ID equals to the 'Native' VLAN ID are tagged with
VLAN ID 0 (priority tag).

Quality of Service parameters specify the priority field for the VLAN tag (IEEE 802.1p)
and the DiffServ field for the IP headers. These specifications relate to service classes.

When booting using BootP/DHCP protocols, the address received from the
BootP/DHCP server acts as a temporary OAMP address, regardless of the address
specified in the Multiple Interface table. This configured address becomes available
when booting from flash.

Network Configuration changes are offline. The new configuration should be saved
and becomes available at the next startup.
Upon system start up, the Multiple Interface table is parsed and passes comprehensive
validation tests. If any errors occur during this validation phase, the device sends an error
message to the Syslog server and falls back to a "safe mode", using a single interface and
no VLANs. Please be sure to follow the Syslog messages that the device sends in system
startup to see if any errors occurred.
Note: When configuring the device using the Web interface, it is possible to perform
a quick validation of the configured Multiple Interface table and VLAN
definitions, by clicking the
Done button in the Multiple Interface Table Web
page. It is highly recommended to perform this when configuring Multiple
Interfaces and VLANs, using the Web Interface to ensure the configuration is
complete and valid.