FreeSWITCH(es) Beyond the single machine: special cases and differences between single domain and multi tenant

Transcription

1 SCALING FreeSWICH(es) Beyond the single machine: special cases and differences between single domain and multi tenant Giovanni Maruzzelli

2 SI Scaling FreeSWICHes SI roxy Media UD Media roxy C Signaling LS W BR Signaling C UD LS C C BR W K A L I V D g in l na g ia d Si e M DB File File DB R L I C A I O N SI roxy Media GSQL BDR + GlusterFS Media roxy FreeSWICH Servers Farm GSQL BDR + GlusterFS 2/24

3 SI and NA Client is behind NA, not directly reachable by server Client sends from its own I:port a RGISR request to Location Server I:port, and in doing so it opens a pinhole in the NA, waiting for server's answer NA pinhole is only able to receive packets from same I:port couple (Client/Server) it was open by, and for a limited period of time (30 seconds?) Location Server sends periodically from same I:port an OIONS message to Client I:port, Client answers, and in doing so it maintains the pinhole open When there is an incoming call for Client, Server sends the INVI from same I:port to Client I:port 3/24

4 SI Load Balancing and roxies SI roxy UD Media roxy C LS WB RC Signaling Signaling C UD LS C BR W K A L I V D SI roxy Media roxy 4/24

5 Where to put the SI Registrar ON LB (SI roxy) MACHIN, directly interacting with Clients RGISR and NA Keepalive (OIONS) are high volume, low load transactions One robust box (in active-passive HA) will be able to serve tens of thousands clients his is the most straightforward topology RGISRAION is then Forwarded to FreeSWICH MACHINS, load balanced by LB FreeSWICHes are made aware of registration (eg, where the phone is) created and deleted No registration traffic, no NA keepalive traffic 5/24

6 SI Call Distribution: DISACHR & LOAD BALANCR SI roxy can be used for relaying requests to multiple boxes using static algorithms (eg: round robin or weighted) or dynamic algorithms (that take care of actual number of active calls on each machine) All proxy's algorithms are able to ping destinations, retry on failed destination, disable the failed box from list, and reenable it when is back in order 6/24

7 SI Load Balancing and roxies SI roxy UD Media roxy C LS WB RC Signaling Signaling C UD LS C BR W K A L I V D g il n na g Si SI roxy Media roxy 7/24

8 SI Media Relaying SI (signaling) proxy has nothing to do with media flow, it does not touch R It can modify SI headers, and SD bodies, so clients behind restrictive NAs will use a third party as a relay, and it can pass commands to that relay (eg: so the relay knows which client must be relayed to which) Original relay software is Rtpproxy More recent and advanced (eg: kernel space, etc): Mediaroxy Rtpngine All of them can scale indefinitely 8/24

9 SI Load Balancing and roxies SI roxy Media UD Media roxy C LS WB RC Signaling Signaling C UD LS C BR W K A L I V D S g in l a n ig D (U ) C ia d e M ) D (U SI roxy Media Media roxy 9/24

10 Adapted from: pass-through proxy by Stanislav Sinyagin 10/24

11 Standard Calls (one to one, straightforward) Registered hone to Registered hone (eg Internal Calls ) Registered hone to IS gw (eg Outbound Calls ) IS s to Registered hone (eg Inbound DID Calls ) 11/24

12 Special Cases (must be managed) Load Balancing is predicated on a server farm of equivalent and equipollent (eg: interchangeable) servers here are cases for which this is not true: Conferences Call Queues Call ark Unpark Call/Group ickup (Intercept) And so on, and so on (quot. Zizek) 12/24

13 Conferences, Call Queues, Call arks (must be local to one FS machine) Conferences are multiple calls media streams switched or mixed together (think multitrack video/audio editing software), result stream is then broadcasted to all participants Call Queues are stacks of incoming live calls, all of them listening to Music on Hold, waiting to be dispatched to answering agents. It is possible to inject streams to single callers (eg You are 3 rd in line, your average waiting time is 9 minutes ) Call arks are named stalls where you put a call, and after a while you or someone else pick it up 13/24

14 Special Cases (hash on destination) 14/24

15 SI Scaling FreeSWICHes SI roxy Media UD Media roxy C Signaling LS W BR Signaling C UD LS C C BR W K A L I V D g in l na g ia d Si e M SI roxy Media Media roxy FreeSWICH Servers Farm 15/24

16 Call/Group ickups Someone answered a call, you are in his same group, he stares at you, you press *8 and pickup the call A call is ringing on a phone a desk away on your same group, you press *4X and answer the call hose two cases are to be managed at FreeSWICH dialplan level, inserting into a DB table info on call groups belonging 16/24

17 Special Cases (Multi enancy) Multi enant = Multiple SI/WebRC domains, managed independently Farm is partitioned on Domains by the roxy, each domain goes to a particular machine his solves the conferencing-queues-transferpickup issues (eg locality of calls/users) High Availability by one or more SAR machines, ready to take the role of the failed machine 17/24

18 Special Cases (hash on domain) 18/24

19 FreeSWICHes' Farm artitioned FreeSWICH 01 FreeSWICH 02 FreeSWICH 03 K A LI V D FreeSWICH 04 FreeSWICH SAR 19/24

20 Signaling, Again (resence, BLF, Messaging) ALL UR SIGNALING AR BLONG O SI ROXY resence SUBSCRIB UBLISH NOIFY vent: State (Available, Busy, Do Not Disturb, Away) Blinking Field Lamp (BLF) SUBSCRIB UBLISH NOIFY vent: Dialog (Idle, Ringing, Calling, in a call) Messaging MSSAG (SIML) 20/24

21 OpenSIS nhancements Clustering roxies Mid-Registar Balancing on FreeSWICH Load 21/24

22 22/24

23 23/24

24 hank You QUSIONS? Giovanni Maruzzelli 24/24