FATPipe Web Redirect: Web requests from remote |
locations will obtain authorisation from the ICAS |
server at the main location and if allowed, all further |
traffic related to that request will be handled on local |
Internet lines. |
| |
Symphony works with any combination of private |
and public lines. Any changes to network architecture |
vis-a-vis line types would have minimal impact on |
Symphony's ability to provide the same benefits to |
customers. |
| |
Basic Firewall: Allows administrators to block any |
inbound or outbound traffic. |
| |
Ability to work with 2-16 WAN connections at any |
location including wireless and local cable without |
BGP programming. No ISP cooperation is required. |
| |
Failover across a public Internet connection and a |
private link from a hub location to 2000 other |
locations that will also have a public and private link. |
| |
Stateful Failover: In the event of unit failure, all |
existing connections are taken over by the standby box |
and there is no need to re-establish sessions, |
resulting in zero session loss. |
| |
An automatic unit failover option is available to |
customers that want a standby unit to backup |
the active SYMPHONY unit at the CPE. |
| |
MPSec: FATPipe's patented Multi-Path security |
provides up to nine times more security, making it |
virtually impossible to trap data flow and organise |
information in correct sequence. |
| |
Fault Tolerance for Remote VPN Users: |
FATPipe Symphony provides redundancy for remote |
VPN clients using IPSEC and PPTP, ensuring |
connectivity even when a WAN line fails. |
| |
SmartDNS: FATPipe's patent-pending technology |
intelligently balances and fails over IP load across |
all available lines for inbound IP traffic resulting in |
efficient delivery of information and inbound redundancy. |
| |
Reverse Mapping: Allows companies to conserve |
IP addresses and direct application traffic to specific |
servers. |
| |
Enhanced Route Control Tools: Symphony |
improved routing options give |
Administrators greater control over IP traffic |
delivery, allowing them to define routing |
criteria based on application and provider. |
| |
Compression: Traffic between locations can |
be compressed. The main location MUST |
use the 4U appliance with hardware |
compression. The branch locations can use |
a 4U device with hardware compression or |
a 1U device with software compression. |
| |
VPN: IPSec encryption can handle upto |
2000 VPN Sessions to the remote location. |
| |