> 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. >
I would replace the word Asterisk with the words "software based product" in the above paragraph. > 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] > ^^^ This applies to any software stack solution. It is your own due diligence to test and adopt any solution. Whether it's Asterisk or not. It is fair to say that there have a lot of bad Asterisk solutions out there, but it's not supposed to be used for everything. It's usually provided as the A in a LAMP stack but there's so much more needed if selling a landline replacement service, as Richard points out. > 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. > Again, not specific to Asterisk or its known weaknesses - http://mcfunley.com/choose-boring-technology I'm the opposite. Asterisk has its place and should only be bashed when you've experienced it. I think Richard has experienced it though :) Gavin. -- Kind Regards, Gavin Henry. Managing Director. Winner of the Best Business ITSP (Medium Enterprise) 2016! http://www.surevoip.co.uk/2016-best-provider
