Mobicents vs FreeSwitch to replace our Twilio-based IVR and webrtc call

511 views
Skip to first unread message

CoderForFun

unread,
Mar 21, 2014, 10:48:59 AM3/21/14
to mobicent...@googlegroups.com
Hi everyone,

   In our company we've our IVR based on Twilio.

   The service is great, but we want a solution on which we've control, e.g. we don't want to rely on third
party SaaS company (that can stop the service, change prices, etc...)

   We're quite new to SIP and phone-system, but with Twilio we was able to setup an IVR and outbound calls from browser (through WebRTC) with ease.

   We would like to move to Mobicents or FreeSwitch. We prefer the first option, as our infrastructure is 90% build on top of Java.

   Basically, we want to use a SIP provider like FlowRoute, AnveoDirect or DIDLogic to have DID numbers forwarded to the Mobicents/FreeSwitch for inbound.
   For outbound we need to use Softphone + Browser with WebRTC with oubound managed by our solution.

   Basically we want to change Twilio with our inhouse solution, and use SIP providers for inbound DIDs and outbound termination. WebRTC is really important (even with Flash fallback). We don't have to support all browser, Firefox and Chrome are ok.

   We have no experience with both Mobicents nor FreeSwitch, so we must start from scratch, and any feedback that can help us in making the right choice is *really* appreciated.

    If may help, we use CentOS for deployment. We also considered RestComm, but we're a little start-up and can't keep with price tags for now, it also more intended for providing services like Twilio, while we want to use the service internally.

Best
Mark

  

Ivelin Ivanov

unread,
Mar 21, 2014, 3:57:41 PM3/21/14
to mobicents-public

Hi Mark,

Many companies use Restcomm for internal IVR apps the way you intend to. 

You have several options:

Open source version:

AWS AMI which starts at $30/mo:

Enterprise grade Java binary, which you can obtain from Telestax:

The difference between the Open Source vs Enterprise option is summarized here:


​Regards,​

---
​--​

Ivelin Ivanov 
Co-Founder, Telestax, Inc. 
Founder, Mobicents
+1 (512) 782-9359
@ivelini




--
You received this message because you are subscribed to the Google Groups "mobicents-public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobicents-publ...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

CoderForFun

unread,
Mar 22, 2014, 12:04:42 PM3/22/14
to mobicent...@googlegroups.com

@Ivanon

Yes, RestComm is probably the first option we considered, but in general AGPL doesn't fit well, and enterprise-grade version is oversized. I guess that price tag is a little bit expensive for business that are not Telco, or in general for which the voice features are not the core business.
Anyway we've scheduled a try for opensource version, may be it is ok for our purpose, even if we must investigate AGPL implications better.

To have an idea, how much effert is needed to build a IVR + webrtc outbound call manager using Mobicents SIP Servlet, wrt RestComm ? Which is the most related example to look at, to have an idea of the complexity involved ?

We have been advised to look at FreeSwitch, but how doest Mobicents compare to freeswitch ? I mean in terms of stability and standards (SIP) compliance ? WebRTC (mature and production-level) is a required feature to consider, as well as support for different SIP providers like FlowRoute, etc...

Thank you Ivanov for the feedback. I think that these information are really precious for all readers that are not experts, and need an advice to evalutate these solutions better.

@Wladimir
Thank you. We may be interested, but a general feedback/advice is really appreciated to better understand the proposed direction (not only for me, but for all readers), as well as an extimation of the costs involved for both evaluation and implementation.

Thanks again,
M
Reply all
Reply to author
Forward
0 new messages