On Tue, 9 Aug 2016 at 11:05 James Bensley <[email protected]> wrote:
> I've had good success at a former job with > https://integrics.com/enswitch/ which is a multi-tenant PBX. > > Its Asterix under the hood for call routing with their custom > application over the top for all the jazzy features. So its Asterix + > MySQL (you can use MariaDB) + Apache so you can virtuaise it and scale > it. > > So you can pay for support but still extend Asterix as you please. We > built a custom hand set provisioning tool, added custom call features > directly in Asterix etc. > I try not to put my oar in to things much when it comes to VoIP discussions generally since many of my employers' customers inhabit the same lists... and it looks bad when you bad mouth products they use.[1] However, it's worth noting that if you're going to be using Asterisk and selling the product to your customers who will in turn rely solely on your product for telephony, you need to make sure you're very aware and up to speed on the legal aspects. >From what I've seen implemented, read up on and inevitably replaced, it's incredibly difficult to build a solution using Asterisk that would be able to survive the test of general condition 4.[2] Forget the shiny web UI, the billing interfaces, systems operations, etc; if you can't maintain an call and lose half your network, you're setting yourself up for a number of very big (and potentially expensive) headaches. ...just my 2p ~ Rich [1] As many who know me will attest, mentioning asterisk in my presence generally earns a scowl or some form of muttering... [2] Out litmus tests for GC4 includes dropping the power on one-half of a disparately located platform.
