Eyeball has developed AnyFirewall Technology to
ensure seamless traversal of media across different NATs,
firewalls, UPnP gateways, & web proxies. This comprises of two
AnyFirewall Engine (AFE) - the industry's
leading firewall and NAT traversal SDK offering the most
comprehensive implementation of STUN, TURN and ICE.
AnyFirewall Server (AFS) - a carrier-grade STUN
and TURN server ready for licensing and mass deployment.
Here are a few highlights about Eyeball’s NAT
Developed using industry standard protocols:
IETF standards of STUN RFC5389, TURN RFC5766, ICE RFC5245,
ICE-TCP , nat-behaviour-discovery and UPNP.
100% call completion: In addition to
implementing ICE for NAT/Firewall traversal, UPnP and HTTP Proxy
tunneling are provided to ensure 100% call completion.
High peer-to-peer call completion rate: More
than 95% of calls are completed peer-to-peer in UDP-enabled
Small SDK footprint: The standard footprint is
less than 300kB, but smaller footprints are available for embedded
devices and other environments where available memory is limited.
Multiple platforms: AFE is available on Microsoft
Windows, Linux, Android, iPhone/iOS, Neutrino, J2ME, and Windows 7, with other platform support available upon request.
Easy to integrate: The AFE socket API is based on the
standard Berkeley socket API, which is used in most operating systems. This
allows AFE to be integrated quickly into existing products.
Complete solution: TheSTUN TURN Server - AnyFirewall Server(a
standards-based STUN/TURN relay server) and the AnyFirewall Engine (a
standards-based ICE client) provide a complete solution for NAT traversal.
Service scalability: A singleSTUN TURN Server - AnyFirewall Serversupports
more than 10,000 concurrent calls at one time, with more calls supported by
simply adding another server.
Product maturity: Eyeball has been a leader in NAT
traversal solutions for over 5 years. Our products are field tested by millions
of end-users all over the world.
Sections 5.1 and 5.2 presents AnyFirewall Engine and Server
solutions respectively and section 5.3 provides a typical call completion
scenario using the solution.