SIP Director Overview

1. SIP Director Overview

2. Agenda • VoIP Market Trends • The Need for SIP ADC • SIP Director Solution Overview • SIP Director Deployment Examples • Advantages of SIP-Enabled ADC • SIP Director Feature Overview • Summary

3. VoIP Market Trends

4. VoIP Market Trends • The VoIP revolution is where HTTP was in the late 90’s • VoIP is becoming mainstream for voice communication – Fixed, Mobile and Web 2.0 • VoIP deployment is rapidly ramping up with SIP as the de-facto standard • SIP enables new exciting collaboration services (Voice + Video + Messaging)

5. IP Convergence IP Convergence • Emerging applications and services enabled by IP convergence include: • Voice over IP • Voice Mail service • Voice/Video Conferencing • IVR • Instant Messaging • Presence/Location services • Data Collaboration • 3G Cellular Services • Call Centers • All services are enabled by SIP

6. VoIP Market Trends • Consolidation of VoIP and Web Business Apps Collaborative Apps HTTP SIP PLM CRM Instant Messaging Unified Messaging ERP HCM Meeting Place IPCC Procurement SCM IP Phone Video Delivery

7. Business Apps Collaborative Apps HTTP SIP PLM CRM Instant Messaging Unified Messaging ERP HCM Meeting Place IPCC Procurement SCM IP Phone Video Delivery VoIP Market Trends • Consolidation of VoIP and Web

8. VoIP Market Trends • Consolidation of VoIP and Web SIP & HTTP Services

9. The Need for SIP ADC

10. The Need for SIP ADC • NG environment is heterogeneous & diversified – solutions don’t come “out-of-box” • Carriers often require rapid deployment of new services in order to be successful • SIP ADC is required to ensure reliable, scalable, fast and secure deployment (as required for Web apps) • SIP ADC factors out these capabilities supporting the ITU 3 tiered SIP load-balancing architecture

11. ITU-OCAF 3 Tiered SIP Load-Balancing OCAF – Open Communication Architecture Forum CGOE – Carrier Grade Open Environment (Rec. Y.CGOE)

12. The Need for SIP Specific ADC • Heritage of PSTN Robustness • Needs to be as robust as current PSTN network • Real-Time • Delay sensitive – signaling and media • Must provide good service experience • Direct Tie to Billing • Requires keeping track of call from start to end • Requires different levels of persistency • Multiple Transports • Interoperability issues with UDP / TCP / TLS

13. The Need for SIP Specific ADC • Routing / Forwarding by Content (L7 info.) • Message content defines routing decisions, Not IP routing • 2-way communication • SIP message flow is different than 1-way client server • Request / Reply handling is independent of the connection • Long sessions • Requires keeping persistency for a long time – Memory • Complex scenarios – Transfer, Forward, 3PCC • Multi-stream Communication • Requires to relate between signaling and media • Standard extensions and Convergence • SIP continues to evolve – new extensions

14. SIP Director Solution Overview

15. Radware Background 10 years of leadership in Web service availability and load balancing Key patents - Global load balancing and Traffic redirection, Multi-Homing, Behavioral security,… Experience and technology are leveraged for guaranteeing SIP service delivery

16. Radware’s SIP Director • Ensures the reliable delivery of SIP services in carrier environment through simplified integration providing: • High Availability • Scalability & Performance • Interoperability • Flexibility & Simplicity • Security • Reduced time-to-market • Factors out operational, architectural and development capabilities SIP Service Delivery Guaranteed !

17. ‘Out-of-the-box’ configurable • capabilities for scalable, fast • and reliable implementation • Simplified Installation and/or • integration • Header modifications • Rule based Routing • Transport conversion • RFC compliant (3261,…) • NAT/FW Traversal Rule Based Configuration SIP Stateless Proxy • Local / Global LB • SIP multi-parameter • persistency (Policy based) • for In/Outbound calls • SIP level Health Monitoring SIP level LB Security (Hardening) • Admission Control • Flood protection • SIP intrusion prevention • TLS/TCP offload • TCP Proxy: • - Connection mgmt: • Aliasing, Conn. Reuse • - Splitting / Multiplexing Acceleration • IP Virtualization • IP + port Load Balancing • L4-L7 web switching IP level LB What Do We Factor Out? Radware’s Differentiation Classical ADC

18. SIP Director Deployment Examples

19. SIP Director Target Applications • Radware provides SIP solutions for: • SIP Application & Feature Servers - Voice mail, Voice & Video Conferencing, IVR, Ring-back Tone, Media Servers, Presence/Location Services, Call Centers • SIP Core Network Solutions – IMS x-CSCF and SoftSwitches • SIP Border Elements – SBC clusters, Media Gateways, Trunk Gateways

20. Deployment example of SIP Director in IMS

21. Rule Based Configuration SIP Director Customizable SIP Stateless Proxy SIP level LB 0-Minute DDoS & Anomalies Farm 1 VIP Farm 2 VIP Security (Hardening) Acceleration Invite App 2 Invite App 1 SIP Level Floods , Anomalies & Vulnerabilities IP level LB SIP Director as an ADC for Application Servers SIP Application Server Farm 2 SIP Application Server Farm 1 SIP Director Benefits for AS Load balancing High availability: Health monitoring & global redundancy Scalability & Performance Outbound persistency ROI: TLS offload, NAT traversal & global load balancing Multi-Parameter Persistency (Condition based) - For ingress/egress calls - Application specific SIP APP Level Health Monitoring

22. UDP G.711 G.711 G.711 G.711 G.723 G.723 G.723 G.729 G.729 G.729 TLS G.729 TCP G.723 SIP Border Network Bottlenecks SBC Overloaded: - SBC Cluster LB - TLS/TCP/UDP Conversion - Real-time X-Coding ROI/Usage Issues for high-touch resources - Need dynamic resource usage adaptation - Need ‘pay as you grow’ model IP SBC Farm IP IPBX - SIP Trunking SIP Peering New requirements at the network border lead to a new eco’-system

23. SIP Director UDP G.711 Health Monitoring Resources Monitoring Real-Time x-coding farm Virtualized Access Farm • SBC Farm • offloaded • Common codec • - Transcoding G.711 G.723 G.711 G.711 G.711 Farm VIP G.729 0-Minute DDoS & Anomalies TLS TCP The Role of SIP Director On-Demand ‘High-Touch’ Resources On-Demand codecs IP SBC Farm IP IPBX - SIP Trunking SIP Peering

24. Main Benefits for Border Elements • Business benefits - CapEx – Lower investments in costly components due to better utilization of high-touch resources (‘On-Demand’) - New revenue generation – Collect additional IP minutes via extending x-coding and transport capabilities • Architectural/Operational/Development benefits - Simplify the design, add dynamic resources usage optimization (‘On-Demand’ across GLOBAL resource pools) - Virtualized service environment - Global distribution of load and resources - Reuse of common functions simplifies new feature development

25. IP PBX Trunking TDM Peering SIP Director as an ADC for GWs SIP Director SIP Director Benefits for GWs Load balancing ROI: Global GW virtualization, least cost routing, global resilience & load balancing High availability: Health monitoring Outbound persistency Scalability & Performance IP TDM Global GW farms

26. Advantages of SIP-Enabled ADC

27. SIP-Enabled ADC Characteristics • Functions as a SIP Proxy • Part of SIP message routing • Simplified network installation and integration

28. Advantages of functioning as a SIP Proxy Request and Response Routing SIP Director • Requests and Responses routed based on SIP routing rules (RFC 3261 and its extensions) • NAT traversal support - No firewall or NAT issues Other ADCs • Routing is based on Call-ID and IP routing mechanisms • Request received on port 5060 may result in response from any port number  Might be blocked by Firewall or NAT

29. F1 Notify (CallID 1) F2 Notify (CallID 1) Proprietary Presence Scenario of a Messaging Company Proprietary F3 Notify (CallID 1) F4 Notify (CallID 1) F7 200 OK (CallID 1) Server 1 receives Notify messages and consults with proprietary backend server Backend server distributes Notify message based on internal policy through Server 2 Result - Routing Mismatch F8 200 OK (CallID 1) F5 200 OK (CallID 1) F6 200 OK (CallID 1) LB Call-ID mapping F5 F3 F1 1 1 1 S2 S1 S1 Advantages of functioning as a SIP Proxy Cont’ C1 C2 LB S1 S2 B Call-ID 1 is mapped to S1 Routing Mismatch

30. Advantages of functioning as a SIP Proxy Cont’ SIP Proxy Vs. Default GW SIP Director • Since it is a SIP Proxy only SIP signaling traffic is routed through it • Media doesn’t go through proxy Other ADCs • Must function as a default GW to ensure SIP signaling is routed through it • This results in routing of all traffic through it including overhead of media • Not enough to identify traffic based on default destination port 5060

31. Advantages of functioning as a SIP Proxy Cont’ TCP Splitting SIP Director • Can distribute SIP messages between backend servers regardless of TCP connection on which they were received • Supports connection reuse and aliasing Other ADCs • Not capable of splitting SIP messages received on one connection to a few connections/servers • This means that LB can’t spread load between backend servers

32. S1 UA-A SIP Director • Call between UA-B & UA-C using a TCP connection for each UA • Both TCP connections are mapped on LB to S2 • First TCP connection is dropped • UA-B sends BYE for both calls using the available connection for both messages • Call between UA-A & UA-B using a TCP connection for each UA • Both TCP connections are mapped on LB to S1 Since it functions as a SIP Proxy it supports TCP splitting in SIP level It may split messages from one connection to a few servers It may forward a few messages received on multiple TCP connections on one connections Result: Each message is routed correctly to the handling server UA-B S2 • Since LB doesn’t support TCP splitting it sends both BYEs to S2 • Result – Persistency mismatch UA-C S3 TCP Splitting Proxy Common LBs Servers Farm

33. Advantages of functioning as a SIP Proxy Cont’ Aging • Based on SIP mechanism – Session Timer and Response • Not based on IP rules or BYE requests User Persistency • Contact, From & To headers based on message type (REG/INV) • Expires header in Register request Replaces • Follows logic of complex call scenarios such as transfer and 3PCC NAT Traversal Support • Keeps pin-hole open with keep alive messages • Transparent if backend server supports NAT traversal

34. S1 Alice SUBSCRIBE Alice@example.com Call-ID: 123 Subscribe sent to Alice from Server 1 Bob S2 Load balancer maps Call-ID 123 to Server 1 LB Call-ID mapping Subscribe Alice@example.com Call-ID: 123 S3 123 S1 Complex Persistency Scenario demonstrates the need for flexible persistency based on varying message parts SUBSCRIBE – Request URI PUBLISH – P-Asserted-Identity Common LBs base persistency on Call-ID not supporting multiple & varying parameters Advantages of functioning as a SIP Proxy Cont’ Common LBs Presence Servers Farm

35. S1 Alice SIP Director Since it functions as a SIP Proxy it manages persistency based on SIP Rules SIP Director would relate Request URI of SUBSCRIBE with P-Asserted-Identity of PUBLISH Result: Both messages are routed to same server Common LB sees this as a new call Bob S2 LB Call-ID mapping S3 123 S1 999 S2 Advantages of functioning as a SIP Proxy Cont’ Common LBs Presence Server Farms PUBLISH P-Asserted-Identity: Alice@example.com Call-ID: 999

36. TLS support • SIP Director support: • High performance, HW-based TLS acceleration • Mutually-Authenticated TLS support for increased security • Conversion from SIPS <-> SIP & Transport=TLS • Certificates – Imported or self signed (supports OCSP) • Benefits • Out-of-box TLS support – preserving UDP based investment • Increased interoperability • Scalability - Performance acceleration for TLS

37. SIP Director Feature Overview

38. Carriers & Service Providers Architectural Benefits

39. Carriers & Service Providers Cont’ Architectural Benefits

40. Carriers & Service Providers Cont’ Architectural Benefits

41. Carriers & Service Providers Cont’ Architectural Benefits

42. SIP: INVITE SIP: INVITE Local Load Balancing • SIP Characteristic: • No standard way for load balancing of high load of traffic between servers • Radware Solution: • SIP Director monitors capacity and availability of servers • Layer 7 policies allow dispatch and load balancing of SIP traffic based on any SIP data • Message Splitting – distribute SIP messages of a single TCP/TLS connection to multiple servers SIP Server Farms

43. SIP: Register SIP: Invite SIP message dispatching • SIP Characteristic: • Multiple SIP services may be provided via the same URI (& VIP) to users with different capabilities and service requests • Radware Solution: • Layer 7 policies allow to dispatch SIP traffic based on any SIP message data (Method, Request URI, SIP headers, SDP data) SIP Registrars Farm SIP Proxies

44. Invite SIP: bob@b.com From : alice@a.com To: bob@b.com Call-ID: 1223023@a.com Persistency • SIP Characteristic: • Persistency is required to allow SIP server to see both session initiation and session termination (SIP is used for session signaling only and not for the actual data transfer). • Persistency is critical for SIP services, such as accounting and billing, which are based on session duration. • Radware Solution: • Layer 7 SIP persistency Call-ID = 1223023@a.com Server 1 SIP Proxies

45. BYE From : alice@a.com To: bob@b.com Call-ID: 1223023@a.com Persistency • SIP Characteristic: • Persistency is required to allow SIP server to see both session initiation and session termination (SIP is used for session signaling only and not for the actual data transfer). • Persistency is critical for SIP services, such as accounting and billing, which are based on session duration. • Radware Solution: • Layer 7 SIP persistency Call-ID = 1223023@a.com Server 1 SIP Proxies

46. Persistency • Different types of Layer 7 persistency are required: • Dynamic Call-ID persistency • Call-ID entries can be aged when BYE or Cancel SIP messages are received for that call • The SIP Director monitors the expiration of the call • User name / number Persistency • For Registration– guaranteeing registration persistency • For Registration & Call setups – guaranteeing incoming call dispatch to the same server • Multi-party call (Conference-ID): • All calls of the conference will be dispatched to the same server • User defined persistency • Any header parameter can be used for message persistency

47. INVITE Outbound SIP traffic Persistency • SIP Characteristic: • SIP servers (Gateways, B2BUA) open connections as part of their regular operation (call control, value-added services: presence, voice mail announcements, notifications) • Radware Solution: • Call-ID learning on server request to ensure return traffic reaches the correct server Call-ID = 1223023@a.com Server 1 SIP Server

48. BYE Outbound SIP traffic Persistency • SIP Characteristic: • SIP servers (Gateways, B2BUA) open connections as part of their regular operation (call control, value-added services: presence, voice mail announcements, notifications) • Radware Solution: • Call-ID learning on server request to ensure return traffic reaches the correct server Call-ID = 1223023@a.com Server 1 SIP Proxies

49. SIPS: Invite (TLS) SIP: Invite (UDP) Interoperability • Protocol Conversion – SIP/TLS SIP/TCP  SIP/UDP • Scheme Conversion – SIPS  SIP • Interoperability - Proxy / Server / B2BUA / Gateway and any Client device • Save TTM – Security (TLS) supported on-the-fly SIP Proxy 1 SIP Proxy 2

50. Clean Environment VoIP P2P VoIP Web Mail… P2P Web Egress Traffic Bandwidth Management Rules Effective Traffic Shaping Network Resources Guarantee Using BWM Rules Prioritized Traffic 1 2 3 4 Queuing