Hi Eric,

I think Giovanni recommends here to use a front OpenSIPS to split the incoming traffic across multiple FreeSWITCH boxes, where each FS box may host an individual queue - this means partitioning the overall Call Center, by running different queues on different FS boxes, not on a single one, to allow some better scalability.

Another option may be to us OpenSIPS as front-end running the call queuing part (see the call center module in OpenSIPS) for all the FS boxes.

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
  https://www.opensips.org/events/Summit-2022Athens/

On 6/9/22 5:07 PM, Peiffer Eric wrote:

Hi,

I'm new in freeswitch and I'm in charge to study the developmnet of a call center using freeswitch. I have read some books and documents about freeswitch scalability, and I have also read the document : "Giovanni_Maruzzelli-OpenSIPS_Summit2016-FreeSWITCH_HA.pdf", here in the link:

https://opensips.org/pub/events/2016-05-10_OpenSIPS-Summit_Amsterdam/Giovanni_Maruzzelli-OpenSIPS_Summit2016-FreeSWITCH_HA.pdf

FreeSWITCH High Availability and Scaling - openSIPS

12/36 OpenSIPS Summit 2016 - Amsterdam gmaruzz@OpenTelecom.IT Many FreeSWITCHes as ONE ALL FreeSWITCH Boxes are ACTIVE (and most other boxes are too) – HA Database: Keeps its own State – Distributed FileSystem: Has its own Configuration Writes and Reads Voice Mails – HA Load Balancers and Proxies: Manages NAT Handling (RTP Media and SIP Signaling)

opensips.org

In page 32 it is wrote that call center is a special case and the answer is partitioning. Can you tell me a little more about this solution?

Regards,

Eric