Find answers to your technical questions and learn how to use our products
Search suggestions:
Find answers to your technical questions and learn how to use our products
Search suggestions:
The following table details the LAN supported features for Server Edition Expansion System (V2) and Server Edition Expansion System (L) platforms.
Feature |
IP500 V2 LAN1 |
Linux LAN1 |
||
|---|---|---|---|---|
LAN1 |
LAN2 |
LAN1 |
LAN2 |
|
Interface Layer1 - Layer4 |
||||
Interface Support |
✓ |
✓ |
✓ |
✓ |
Physical<>logical interface mapping |
Fixed: ‘LAN’ |
Fixed: ‘WAN’ |
✓ |
✓ |
Speed |
10/100 |
10/100 |
10/100/ 1000 |
10/100/ 1000 |
Duplex |
Full/half |
Full/half |
Full/half |
Full/half |
802.1Q VLAN support Static o/g VLAN assignment via administration. IP500 V2 strips any received VLAN tag, all o/g packets have no VLAN tag |
– |
– |
✓ |
✓ |
DSCP/ToS Linux LAN2 uses LAN1 DSCP settings – any LAN2 settings are ignored |
✓ |
✓ |
✓ |
✓ |
Default gateway/route Linux via ignition or Web Control |
✓ |
✓ |
✓ |
✓ |
Proxy ARP IP500 V2 acts as an L3 router |
✓ |
✓ |
– |
– |
IP Multicast |
✓ |
✓ |
– |
– |
Inter LAN |
||||
Firewall A Linux ingress/egress firewall can be activated, with further controls for specific unsecure ports such as TFTP and HTTP. No differentiation between LAN1 and LAN2. |
✓ |
✓ |
✓ |
✓ |
IP Routes No configurable IP routing between Linux LAN interfaces. All received Linux LAN traffic that is not destined for the node is discarded except VoIP media which is allowed to traverse with NAT. |
✓ |
✓ |
– |
– |
NAT/NAPT |
✓ |
✓ |
– |
– |
PPP |
✓ |
✓ |
✓ |
– |
Clients |
||||
one-X Portal client – basic |
– |
– |
✓ |
✓ |
one-X Portal client – VM listen |
– |
– |
✓ |
- |
one-X Plugins |
– |
– |
✓ |
✓ |
SoftConsole |
✓ |
✓ |
✓ |
✓ |
Voicemail Pro – MAPI Link Two way MS Exchange VM Integration via MAPI or EWS. |
– |
– |
✓ |
✓ |
Voicemail Pro – SMTP One way IMAP/Exchange VM integration. |
– |
– |
✓ |
– |
Administration |
||||
IP Office Manager Also accessible via IPOSS remote tunnel (SSLVPN). |
✓ |
✓ |
✓ |
✓ |
Server Edition Manager Access should be the same LAN1/2 interface as the inter-node connections. |
✓ |
✓ |
✓ |
✓ |
SSA |
✓ |
✓ |
✓ |
✓ |
SysMon |
✓ |
✓ |
✓ |
✓ |
Web Manager Cannot launch other clients (including Manager and Linux Platform Management) when not accessed via LAN1. |
✓ |
✓ |
✓ |
✓ |
Voicemail Pro Client |
n/a |
n/a |
✓ |
✓ |
Linux Platform Management |
n/a |
n/a |
✓ |
✓ |
Protocols |
||||
DHCP Client and server |
✓ |
✓ |
✓ |
✓ |
BOOTP |
✓ |
✓ |
✓ |
– |
TFTP |
✓ |
✓ |
✓ |
✓ |
HTTP/S |
✓ |
✓ |
✓ |
✓ |
SCP |
– |
– |
✓ |
✓ |
FTP |
– |
– |
✓ |
✓ |
SFTP |
– |
– |
✓ |
✓ |
PPP |
✓ |
✓ |
– |
– |
IPsec |
✓ |
✓ |
– |
– |
VPN (L2TP/PPTP) |
✓ |
✓ |
– |
– |
RIPv2 |
✓ |
✓ |
– |
– |
SSLVPN |
✓ |
✓ |
✓ |
✓ |
NTP Client and server SNTP operation |
✓ |
✓ |
✓ |
✓ |
TIME RFC 868 |
✓ |
✓ |
– |
– |
TSPI CTI interface for TAPI and one-X Portal |
✓ |
✓ |
✓ |
✓ |
SNMP Traps and MIBs, v1 only |
✓ |
✓ |
✓ |
✓ |
SMDR |
✓ |
✓ |
✓ |
✓ |
DNS |
✓ |
✓ |
✓ |
– |
Syslog (UDP+TCP+TLS) |
✓ |
✓ |
✓ |
✓ |
Telephony |
||||
H.323 trunks (including SCN) LAN1 and LAN2 should not be mixed for SCN. Should be all LAN1 or all LAN2. This also includes SE Manager access. |
✓ |
✓ |
✓ |
✓ |
H.323 phones Phones must be configured with ‘local’ registrar IP address – e.g. not possible to access LAN2 registrar via LAN1. |
✓ |
✓ |
✓ |
✓ |
H.323 Remote worker phone |
✓ |
✓ |
✓ |
✓ |
IP DECT |
✓ |
✓ |
✓ |
✓ |
SIP trunks |
✓ |
✓ |
✓ |
✓ |
SIP phones |
✓ |
✓ |
✓ |
✓ |
STUN |
✓ |
✓ |
✓ |
✓ |
IP Office Softphone |
✓ |
✓ |
✓ |
✓ |