1. 1 The Need for Enterprise Session Border Controller The E-SBC allows the enterprise to control its SIP implementation The Ingate SIParator ®

2.  Normalization of the SIP signaling  To insure interoperability with the service provider  NAT and Firewall traversal  To enable SIP to the enterprise  To permit placement of the PBX behind the firewall  Security through deep packet inspection  Avoid delivery of mal-formed packets  Control through authentication  Reduce opportunity for theft of services Intrusion Prevention / Detection  Protect against Denial of Service attacks  Disaster recovery  Eliminate single points of failure  Quality of Service  To deliver the highest quality voice  Performance metrics Encryption for private communications Why does the Enterprise need an SBC?

3. Over a Managed Line PSTN Public Internet SIP Trunking Provider Network GW SIP System Data & VoIP LAN Firewall IP- PBX Managed SIP Trunk Over the Public Internet PSTN Public Internet SIP Trunking Provider Network GW SIP System Data & VoIP LAN IP- PBX SIP Trunk over Internet Firewall Two Ways to Connect to a SIP Trunk

4. Confirmed Interoperability SIP Trunk Ingate SIParator ® -or- Ingate Firewall  Aastra  Aastra MX-One  Adtran Netvanta UC  Avaya CM & SM  Cisco Call Manager  Digium / Asterisk  Fonality  HP VCX  Innovaphone  Interactive Intelligence  Iwatsu  Microsoft OCS 2007  Mitel  NEC / Sphere  Nortel BCM / SCS / CS1K  Panasonic  SER  Shoretel  Siemens  SIP-Gear  Swyx Compliant with  360 Networks  Airespring  AT&T  BandTel  Bandwidth.com  Bell Canada  Broadvox  Cablevision  Cbeyond  Cellip  Cordia  Deltacom  Excel  Gamma  Global Crossing  IP-Only  Nectar  Level 3  Netlogic  NetSolutions  Nexvortex  Nuvox  OneCommunications  Paetec  Primus  Qwest  RNK Telecom  Skype  SoTel  TDC  Tele2  Toplink  Verizon  VoEX  VoIP Unlimited  Windstream  Voxbone More in pipeline..... Service providers IP-PBXs Carrier Equipment  Acme Packet  Broadsoft  GenBand  Sonus

5. Data LAN PSTN Public Internet SIP Trunking Provider GWGW IP-PBX Firewall SIP Trunking does not pass a SIP unaware NAT/firewall! … and the firewall cannot even be opened enough to make it work. SIP System NAT and Firewall Traversal Problem

6. Ingate SIP Proxy SIP Proxy/Registrar SIP Signaling 10.x.xx168.x.xx 1.Check the SIP signaling, packet inspection - Full flexibility to handle future threats 2.Rewrite for the different address spaces 3.Forward the signaling to the correct SIP proxy or client 4.Open ports (UDP/TCP) in the firewall for the media -Only for the duration of the call -Only between the exact endpoints 5.Media flows through the ports Media 6.Close ports after the call ITSP IP-Phone E-SBC Functions

7. Internet ITSP IP-PBX Mobile user Spammer Dynamically allow authenticated users Block non authenticated users Monitor traffic and block end-points with a un-normal behavior DOS Protection

8. Encrypted SIP signalling –Support for TLS Encrypted media –Support for SRTP (Sdescriptions) IP-Phone Ingate Firewall or SIParator IP-PBX / SIP Server Termination TLS, Pass through or Transcoding Encryption SRTP In the clear RTP __SRTP__ SRTP TLS SRTP In the clear

9. Security Encryption Termination / Transcoding Authentication SIP Filtering Flexible Control Near-End Traversal Firewall & NAT Sol. for Remote Workers SIP Proxy, ALG, B2BUA, Registrar Call Qualiity Statistics Extensive Diagnostic Tools Far-End NAT Traversal and STUN SIP Trunking Tool Set QoS, Taffic Mgmt IP-PBX Compatibility SIP Trunking Service Provider Compatibility ENUM Support SIP-ALG-only Firewalls can only do this much SIP Proxy, ALG, B2BUA, Registrar Extensive SIP Feature Set

10. Network Installation Options

11.  Eliminate interoperability issues  Resolve NAT traversal through the firewall  Security  Place the PBX in the private IP space  Authenticate to prevent theft of services  Protect against Denial of Service attacks  Eliminate single points of failure  Manage bandwidth for optimal voice experience  Measure quality of the voice  Encryption of Signaling and Media for privacy Why does the Enterprise need an SBC?

12. Please contact me at any time: Steve Johnson President Mail & SIP: steve@ingate.com Direct: 1-603-883-6569