you can just remove the features you don’t want from the client
On Mar 12, 2018, at 9:17 AM, Rick Jarvis <rick@magicmail.mooo.com> wrote:
What is the best way to remove all call control abilities from the web client, and have just audio between FS and browser? Let me explain what I mean and why:
My app server (running on Node) controls all call handling by ESL to FreeSWITCH. As the service is multi-tenant I need to consider security, but all the multi-tenant stuff is on the app server, and I’m trying to avoid the complexities of having multiple domains etc on FS as I would then need to build a way of syncing this with the app server.
So, ideally, the browser would connect to FS (via Verto, as I think it is Verto that handles all the clever re-connection stuff?), and would share its call uuid with the app server, which would then handle all the call transfer / conferencing etc using ESL to FS.
The sticking point is that I want to make sure that a user can’t instruct Verto to transfer the call to a guessed conference name. At the moment, I have a rather elaborate system of using a randomly generated auth code, which the app server keeps in Redis, and adds to the name of the conference. But the complexities of this are proving problematic in my code.
I hope this makes sense, I definitely consider myself to still be very new to webrtc/verto etc, despite having been playing with it for many months now!
Hoping for some ideas or guidance.
Thanks R