 |
Everything You Need to Get Started
AnyFirewall Engine provides a rich and flexible application
programming interface (API) to provide seamless NAT and
firewall traversal for your applications. It is a complete SDK
with:
- 4 C/C++ library providing flexible API.
- Sample client applications illustrating how to use the
Engine for VoIP applications using third-party SIP stack and RTP library.
- Developer reference documentation.
- Technical support for integration and customization.
- Access to Eyeball AnyFirewall Server - a carrier-grade STUN and TURN
server.
Supported Platforms:
AnyFirewall Engine supports major fixed and mobile device platforms, including
Android, iOS, Linux, OS X, Windows, and Windows Phone, and fixed and mobile
networks, including cable, DSL, 3G, LTE, 4G, and WiFi.
AnyFirewall Engine Stack Diagram
Standards Compliance and Certification:
-
Compliant with IETF, 3GPP, and CableLabs standards STUN,
TURN, and ICE
-
Compliant with Microsoft standards MS-STUN, MS-TURN, and
MS-ICE
-
AnyFirewall Engine and Server are the reference
STUN/TURN/ICE software for CableLabs PacketCable 2.0 certification
-
TLS security
-
Supports any application protocol including Jingle, RTP,
SIP, XMPP, and more
-
Supports any data or media format including G.711, G.729,
H.263, H.264, MPEG-4, and more
High Performance:
-
~300 KB footprint for integration into embedded systems and
mobile devices
-
Peer-to-peer media transport over UDP-enabled networks for
low latency and high scalability
-
Scalable to tens of millions of subscribers
Standards and Protocols
- RFC 5389: Session Traversal Utilities for NAT(STUN)
- RFC 5766: Traversal Using Relays around
- NAT (TURN)
- : Relay Extensions to
Session Traversal Utilities for NAT (STUN)
- RFC 5245: Interactive Connectivity Establishment (ICE): A Protocol for
Network Address Translator (NAT) Traversal for Offer/Answer Protocols
- RFC 6314:NAT Traversal Practices for Client-Server SIP
- IETF draft mmusic-ice-tcp-15: TCP Candidates with Interactive
Connectivity Establishment
- RFC 5626: Managing Client Initiated Connections in the Session
Initiation Protocol
- RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)
- RFC 3581: An Extension to the Session Initiation Protocol (SIP) for
Symmetric Response Routing
- UPNP Forum specification: Internet Gateway Device (IGD) Standardized
Device Control Protocol V 1.0
- CableLabs specification: PacketCable 2.0 NAT and Firewall Traversal
Technical Report (PKT-TR-NFT-V02-061013)
|
|
 |
|
|
|
