Sangoma (FreePBX) to Acquire Digium (Asterisk) for $28M
sangoma.com
sangoma.com
[1] https://www.freepbx.org/sangoma-completes-the-acquisition-of... [2] https://www.dialogic.com/2018-01-09-sangoma-announces-sixth-... [3] http://www.marketwired.com/press-release/sangoma-announces-t...
The industry needed this consolidation 10 years ago.
Glad to see it’s finally happening. So much talent has left the space now that it absolutely had to happen.
Sangoma is a great company and I’m sure they will do a great job.
Most of the talent I know took a step to the right (like myself) and are working with WebRTC. It's all the same stuff! Just more signalling layers on top of RTP channel management. I quite often end up doing SIP over WebRTC with things like sip.js (still backing onto Asterisk and FreeSWITCH) and XMPP over WebRTC with jitsi-meet.
Does that mean they are doing a good job creating yet another monopoly? Seriously courageous. Are there other players left?
So Long Asterisk, And Thanks For All The Fish!
That said, I never really saw Dialogic as in the SMB space, certainly not their hardware division.
We must have had over 300 D480SC-2T1 boards in service at peak. Absolute workhorses. Their cPCI offerings were never as stable but 16 T1s or 1000 SIP ports in a single slot was extremely attractive. I recall them having issues with their supply chain for the high-density SIP boards in conjunction with field failures that pushed us towards their software product, HMP.
Dialogic’s HMP product was more stable and ultimately cheaper at scale (for SIP anyway; never had good luck with their T1 interface boards on HMP). Funny they didn’t sell that division off. Perhaps it’s still profitable or maybe Sangoma was simply uninterested as it isn’t really aligned with the Asterisk/FreeSWITCH ecosystem.
Wonder how much of that stuff is still running. You left a year after me so I suppose you wouldn’t know ;)
As others have stated, their features are now found in many low cost proprietary solutions.
No reason to pay a tax to use open source unless you believe in it.
Agree to disagree. I cut my teeth on freepbx; love it, miss it, constantly yell at my customers digium appliances in disappointment that they don't live up to their sibling. I rolled my old MSP over to it without any hassle and afaik they're still running it a few years later and I know none of them have touched it for admin. Rolled it on my VPS for my own consulting needs and it's pain free.
It's quite a legacy application and is not easily scalable nor made highly available.
The world is also moving to hosted communications (Twilio, etc) so there is less and less need for a local PBX, thus less demand for Asterisk.
You scale horizontally using proxies (kamailio dispatchers), (what you would call "reverse proxies in the http world), and use external storage / database / logic.
Correct, but don't forget many hosted communications services use asterisk internally.
Twilio did use Asterisk in the past, although I believe they have switched to something else.
Personally I wouldn't use it; I'd just write some quick code with Twilio (using Twilio functions or a companion app running on Heroku for the business logic) and let them handle it. Less maintenance overhead.
irl maintenance is pretty straightforward. I do it as a side thing to my main job.
I tried _hard_ to make FreeSWITCH work for me in an SMB environment, but I ended up with such a bad taste from the poor QA that I eventually had to call it all a false start and go back to Asterisk.
Going back to around that time period, there was a project started called Asterisk SCF (internally called Hydra, I couldn't remember if it was made public but it's in the list archives: http://lists.digium.com/pipermail/asterisk-scf-dev/). Asterisk SCF was going to be new software (written in C++) that supported scalability as a primary feature. I still wonder if Digium had continued funding it what would have happened, but eventually development was halted: http://www.digium.com/blog/2012/09/14/asterisk-scf-pause/.
All that to say I'm happy for Digium's success, but still think an acquisition could have occurred far sooner with a product based on Asterisk SCF.
they were selling T1/T3 hardware for years before asterisk was a thing. does seem like they pivoted to the voice stuff after asterisk, though.
There is really no other option in the FOSS community for small-to-medium phone systems, as Asterisk-based systems are rivaled mainly by 3CX (proprietary) in the industry which is somewhat expensive and significantly less-configurable than the open source options.
The email ecosystem had the same problem where anyone could send an email from any address but managed to solve it by adding new standards on top of old ones to verify senders. I hope something similar can happen for SIP.
Progress does seem very slow
If you were talking about PGP signatures, ignore my previous words :)
The issue you see in SIP predates voice over IP. PSTN suffers from the very same issue.
You can do an awful lot of things with SIP that are unthinkable or plain unlikely with PSTN. SIP can be encrypted (OK the RTP streams can) You can use IAX2 for those times when NAT and SIPnRTP are too hard (hint: try Symmetric RTP - fixes many NAT related problems)
Don't confuse SIP with something it isn't! SIP is a comms mechanism and a damn good one, considering how old it is. When you deploy SIP, you also have the option of using all of the very latest funky security stuff around it to support it thanks to the fact that it runs over UDP/IP or TCP/IP.
The email ecosystem had the same problem where anyone could send an email from any address - I'm not sure that you can call this a problem. I could call myself Mr Donald Trump, in fact my real name could even be Mr Donald Trump but it wont really make me POTUS but you need some way to tell the difference. Comms is tricky and safe comms in the modern world is very tricky. How far should a comms protocol go in ensuring that the source is who the recipient thinks it is? Or is that really a job for another protocol/system perhaps with some hooks of some sort?