90 likes | 194 Views
Comparison of Acme Packet's SBC to SIP firewall/ALGs, highlighting its fully state-aware, at layers 2-7 capabilities to inspect and modify application layer header info. Acme Packet SBC can terminate, initiate, and re-initiate signaling & SDP, offering static & dynamic ACLs. Unlike Firewalls with SIP ALGs, Acme Packet SBC maintains single sessions, is fully state-aware at layers 3 & 4 only, inspects and modifies only application layer addresses, and supports static ACLs only. Explore security, application reach, regulatory, availability, and SLA assurance scenarios in this comprehensive comparison.
E N D
The leader in session border control for trusted, first class interactive communications
Back-to-back user agent Fully state-aware atlayers 2-7 Inspects and modifies any application layer header info (SIP, SDP, etc.) Can terminate, initiate,re-initiate signaling & SDP Static & dynamic ACLs Summary comparison:SBCs vs. Firewalls with SIP ALGs IP PBXUC server IP PBXUC server SBC Firewall with SIP ALG Data center Data center SIP trunking SIP trunking • Maintains single session • Fully state-aware atlayers 3 & 4 only • Inspects and modifies only application layer addresses (SIP, SDP, etc.) • Unable to terminate, initiate, re-initiate signaling & SDP • Static ACLs only Acme Packet
SBC vs. firewall w/ SIP ALG comparison Security scenarios Acme Packet
SBC vs. firewall w/ SIP ALG comparison Application reach, regulatory scenarios Acme Packet
SBC vs. firewall w/ SIP ALG comparison Availability scenarios Acme Packet
SBC vs. firewall w/ SIP ALG comparisonSLA assurance scenarios Acme Packet
The leader in session border control for trusted, first class interactive communications