[Freeswitch-users] Hardware for Freeswitch setup

[Kristian Kielhofner]

With your setup I see two things about WebRTC to consider from a
performance perspective:

1) Codec
2) SRTP

WebRTC endpoints (more than likely) will be using Opus. Even though
they support PCMU and PCMA the use of these codecs is ill-advised
considering the likely state of the endpoint and network. WebRTC also
mandates the use of SRTP.

Both of these have a potentially significant impact on your system
because you will be recording. This means that your system will have
to decrypt the SRTP stream and transcode it to store to common
recording formats (such as WAV). Even still, with the kind of volume
and applications you're describing Mike's comments earlier were spot
on.

For other applications and uses there are all kinds of additional
things to consider (like the impact of ICE negotiation on CPS, for
example).

On Wednesday, June 4, 2014, Oscar Franzen <oscar.franzen at advisa.se> wrote:
>
> Thanks!
>
> I forgot to mention that we want to use WebRTC in the near future as well. Is there anything special I have to consider for that?
>
> So you basically think the IO for recordings is going to be the main bottleneck?
> I am not entirely sure I can do transcoding at the storage server but I'll look into it.
>
> As I understand it FSW has to do some sort of transcoding when mixing two channels to record them? Is it possible / would you recommend   to record to g711 (I think this is the used codec)? And then later transcode it to mp3 for long time storage?
>
> What other bottlenecks am I looking at? What are some usual performance problems and when do you usually encounter them?
> My initial idea was to go with a modern multi core Intel Xeon processor and multiple network interfaces. Is the next thing to focus on storage performance?
>
> Oscar
>
>
> On Wed, Jun 4, 2014 at 9:27 PM, Guillermo Ruiz Camauer <grcamauer at gmail.com> wrote:
>
> I would concentrate on the disk side of things with a good stripe or RAID of SSDs.  Or, just add enough RAM (say 64GB) and make a large enough tmpfs/RAMdisk partition to store your recordings before transcoding and shipping them off to the storage server.  Just make sure to have UPS backed power.
>   Can the transcoding be done on the storage server (they usually have lots of spare CPU cycles)?  Separate network adapters for VoIP and storage would also be good.
> I would go with a CPU with 4 cores.
>
> Testing will always be the final answer.
>
> Guillermo
>
>
> On Wed, Jun 4, 2014 at 3:30 PM, Michael Jerris <mike at jerris.com> wrote:
>
> Not a whole lot of cpu from any modern non embedded processor can probably handle this.  Test to see exactly how it behaves with your exact requirements. Sound card would do nothing at all for transcoding, thats all cpu.
>
> Mike
>
> On Jun 4, 2014, at 6:20 PM, Oscar Franzen <oscar.franzen at advisa.se> wrote:
>
> Hi!
>
> I'm looking for some help with hardware for a production setup of freeswitch. I need at least 150 concurrent calls, but would prefer to buy a server which can handle more to facilitate growth.
>
> I am looking at using the same codec (i think it is g711) for both legs of the call. I want to record all calls. Either to whatever codec and then transcode them separately or directly to mp3/ogg. I am going to use ESL to control FSW and also listen to most events over the socket.
>
> What would you recommend for hardware? Is it recommended to buy a sound card for transcoding or just buy enough CPU? I will probably run from SSD, record to same SSD or other local disk and continuously move recordings to external (network) storage.
>
> So:
> 150 concurrent calls
> ~10 initiations/second
> mod_event_socket - for control and events
> A limited amount of eavesdropping
> recording (either to original codec or ogg/mp3)
> Some "standard" modules.
>
> Regards
> Oscar
>
>
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
>
> 
> 
>
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
>
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
>
>
>
> --
> Guillermo Ruiz Camauer
>
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
>
> Regards
> Oscar Franzén
> Developer
>
>
>
> Advisa
> oscar.franzen at advisa.se
> Mobil: 070-720 45 81
> Besöksadress: Kungsgatan 30, Stockholm
> www.advisa.se
>
> –––––––––––––––––––––––––––
> Informationen i detta meddelande är konfidentiell och endast avsedd för den/de angivna mottagarna. Om Du inte är en avsedd mottagare, ber vi Dig att inte läsa, kopiera eller använda informationen i meddelandet  samt att inte heller vidaresända informationen eller delge den till annan. Vi ber Dig även att omedelbart meddela  avsändaren att Du erhållit meddelandet felaktigt samt att därefter genast radera det från Ditt system. Advisa ansvarar inte för eventuella personliga åsikter eller värderingar i detta meddelande.