Hello FreePBX Community.
I am interested and trying to setup FreePBX as a websocket proxy between Odoo V19 Enterprise and Twilio Voice. I’m interested in hiring someone experienced in configuring such a connection.
I need the bare minimum from FreePBX in order to accomplish the bridge between Odoo and Twilio.
What was the result of using their plugin? VoIP WebRTC FreePBX | Odoo Apps Store
Which parts of the added value from the GUI configuration, or dialplan subroutines, do you intend to use, compared with doing this directly, with Asterisk?
Odoo is a CRM application that their last few versions now have WebRTC client. The client, like any other VoIP client, needs to register to a system that will be the WebRTC server. Twilio SIP Trunking doesn’t support being a WebRTC server.
In order to use the WebRTC client in Odoo something like FreePBX (or Asterisk) needs to be in between Odoo and Twilio.
The whole doing it via FreePBX vs Asterisk directly is more about the level of the user implementing the solution. They could either deploy FreePBX which has all this already configured and a GUI to easily set it up. Or they could deploy straight Asterisk and then write the entire solution themselves. The former has a lower threshold vs the latter and makes more sense for those that need the low threshold.
I’m assuming that the person commissioning the work has no experience with either FreePBX or Asterisk, and that about six lines of dialplan would be necessary for two way calling. With FreePBX, you would need to do a fair bit of configuration to make it generate/use 100s of lines of dialplan, to achieve the same effect, and with the problem that, if it does break, they will still be exposed to the details of that dialplan.
Well the reason I asked about the plugin is Odoo already provides FreePBX integration, there’s no solution to create outside of installing a plugin. Either the OP is aware of the plugin or not since it appears to be a recently released plugin.
So really this is an install FreePBX, create Twilio trunk, install/configure Odoo plug and off to the races. This may not be as big of a project the OP original thought it would be and the OP could save some money DIYing it since it’s a basic setup.
Hello everyone. Thanks again for all the replies and suggestions here, and my apologies for the delayed response. I wasn’t receiving notifications for forum replies, so I didn’t realize there had been follow-ups until recently.
I wanted to share an update: I do now have Odoo > FreePBX > Twilio SIP fully working for both termination and origination calling. I’m able to make and receive calls successfully using the Odoo WebRTC client, with media flowing correctly through FreePBX and Twilio for termination and origination. That part of the stack now seems solid. I do have a need for my Odoo users (which is just myself and my brother currently) to have multiple extensions available to them inside Odoo since I’m setting up an Odoo Multi-company environment for the two small businesses. But that is an Odoo issue not a FreePBX issue.
There is also still one remaining challenge around iOS audio behavior in the browser/WebRTC context, which I’m continuing to work through separately, but from a PBX/SIP perspective things are behaving as expected.
In regards to Straight Asterisk vs FreePBX, yes I agree this setup could certainly be managed by just Asterisk, but I don’t think I’m very constrained on the power of my machine, so knowing that I don’t see the harm in running FreePBX. Happy to hear otherwise if that is not true.
At this point, I’d actually be interested in hiring someone experienced with FreePBX to do a quick review of my DIY installation — mainly to:
sanity check my SIP / RTP / WebRTC configuration
review NAT and firewall assumptions
look over security hardening and best practices
identify any obvious optimizations or “gotchas” I may have missed
If anyone here offers that kind of service, or can recommend someone reputable, I’d be happy to connect offline.
Thanks again to everyone who took the time to responding and I’m looking forward to more helpful community feedback to get this across the finish line.