As someone who has numerous voipo accounts, I have some experience with this.

We have setup dozens of new accounts just in the past few months.

The installs are all over the country, from California, Colorado, Texas, Illinois, Delaware, Florida, New York, etc.

They all have mostly identical equipment (pbx phones and routers), but a wide variety of local internet providers... Comcast Cable, AT&T DSL, Verizon Fios, etc.

Many of our locations have high call volumes, and at various time have had the problems described by original poster above... mostly outbound calls failing, but also toll free issues, voipo to voipo issues, and some inbound issues.

For example, on failed outbound calls, our equipment logs show "forking errors" coming from IPs (servers) on voipo's network, or voipo's host network, or whatever.

We've purchased new routers and hired an outside consultant to check our network, etc. Everything was solid and setup correctly.

Next, we thought it might be our voip equipment, since it was all the same. But even switching the equipment in a test location did not help.

So then we tested one of our locations with a different voip provider. We set things up so we could dial 9 to use voipo and dial 8 to use the alternate voip provider.

I hate to say it, but sure enough, the various calling problems literally vanished by using the other provider... and no other changes required.

As a result of the positive results, we've begun switching accounts over to the alternate voip provider.

In each case, the problems went away simply by switching to the alternate provider. It didn't matter what type of equipment, internet, city or state, etc.

Honestly, there are still features about voipo that we prefer over the other provider, and we do like voipo's people.

But as the original poster said, ultimately, the features and service simply have to work correctly, or what's the point?

Hopefully voipo can identify the deficiencies in their setup, carrier, whatever, and resolve them soon.