User's Manual 116 Document #: LTRT-12809
Mediant 800 MSBR
traffic is sent from this interface to an unknown destination (i.e., not in the
same subnet and not defined for any static routing rule), it is forwarded to
this default gateway.
Notes: For valid configuration, see 'Multiple Interface Table Configuration
Rules' on page 117.
Web/EMS: VLAN ID
CLI: vlan-id
[InterfaceTable_VlanI
D]
Defines a VLAN ID for the interface.
Note: For valid configuration, see 'Multiple Interface Table Configuration
Rules' on page 117.
Web/EMS: Interface
Name
CLI: name
[InterfaceTable_Interf
aceName]
Defines a name for this interface. This name is used in various
configuration tables to associate this network interface with other
configuration entities such as Media Realms. It is also displayed in
management interfaces (Web, CLI, and SNMP) for clarity where it has no
functional use.
The valid value is a string of up to 16 characters.
Note: For valid configuration, see 'Multiple Interface Table Configuration
Rules' on page 117.
Web/EMS: Primary
DNS Server IP
address
CLI: primary-dns
[InterfaceTable_Prim
aryDNSServerIPAddr
ess]
(Optional) Defines the primary DNS server's IP address (in dotted-decimal
notation), which is used for translating domain names into IP addresses
for the interface.
By default, no IP address is defined.
Web/EMS: Secondary
DNS Server IP
address
CLI: secondary-dns
[InterfaceTable_Seco
ndaryDNSServerIPAd
dress]
(Optional) Defines the secondary DNS server's IP address (in dotted-
decimal notation), which is used for translating domain names into IP
addresses for the interface.
By default, no IP address is defined.
WAN Interface Name
[WanInterfaceName]
Assigns a WAN interface to the VoIP traffic (i.e., SIP signaling and media /
RTP interfaces). The available WAN interface options depends on the
hardware configuration (e.g., Ethernet, T1, or SHDSL) and/or whether
VLANs are defined for the WAN interface (see Virtual LAN Interface
(VLAN) on page
597. If VLANs are configured, for example, for the
Ethernet WAN interface (see Data Settings on page 531), then you can
select the WAN VLAN on which you want to run these SIP signaling
and/or media interfaces.
The WAN interface can be assigned to SIP signaling and media interfaces
in the SIP Interface table (see Configuring SIP Interface Table on page
207) and Media Realm table (see Configuring Media Realms on page
174), where the WAN interface is denoted as "WAN".
Once this association is set, VoIP traffic is sent via the WAN and incoming
traffic is identified as coming from the WAN. The device also automatically
configures the required port forwarding and static NAT rules.
Notes:
For this parameter to take effect, a device reset is required.
If you do not assign the WAN interface to SIP and media interfaces,
then the WAN interface may not be used for VoIP traffic. In such
scenarios, the VoIP traffic can be sent and received within the LAN, or
sent to the WAN via a third-party LAN router. If a third-party router is
To Next Page
Loading...
