Outbound Calls - 1 ring, then dead air - Wife ready to kill me.....

[GreenLantern]

My company has several hundred numbers/accounts with voipo, using equipment from a lot of different brands (grandstream, obi, linksys, cisco, polycom, asterisk, and about a dozen others).

Most of our accounts work fine. But a scattering of our numbers suffer from the one-ring-then-dead issue over and over, resulting in a disproportionately high volume of our support tickets. We have to first perform internal troubleshooting to make sure it isn't a device, network, or user issue. It usually isn't, so then we have to log and submit call examples so voipo can perform "route treatments". After going through the support ticket process, that dialed number then works, but a day later we may run into a different number requiring yet another route treatment.

My understanding is that voipo uses multiple carriers for routing calls. Which carrier is used depends on origination and destination, plus (I assume) the relative cost of the various carriers... lowest cost having priority. That is, unless they perform some kind of manual override (route treatment), causing a more reliable carrier to be used.

I believe that a few weeks ago, one carrier was removed from the voipo routing "pool" due to poor performance. But it sounds like there is at least one more flakey carrier out there that is still causing problems.

Either that, or there's simply a flaw/bug in the voipo network somewhere, causing certain routes to be unreliable.

I would think that some kind of intelligence could be written into the system, for example not allowing the same route to be used within a short time on a redial. Or to take note of 2 or more attempts to call a number within a short period of time, then an automatic route treatment could be applied. Combine that with elimination of flakey routes/carriers, and voipo could be much more robust and reliable.

Hopefully, the issue can be hunted down and dealt with, because (IMO) this is really the single largest negative issue with voipo at this time.

[Ansextra]

I would have to agree that this is the single largest negative issue with Voipo (at least to me). It seems as if I run into at least one number that rings once and dies almost daily. It is at the point that when I dial a new number I find myself holding my breath waiting for the second ring. I've opened numerous tickets and have had the infamous "routing treatment" successfully done every time but the thing about phone service is that I expect to be connected when I dial a number. It wouldn't be so bad if I could call right back and get connected a second time but I can't even do that. If a number doesn't work it just doesn't work until the "routing treatment" is done. Unless I am on IM with someone it is impossible to ask them to call me back as I have no way to ask them to do that. All in all this is EXTREMELY frustrating. Phones need to connect when a number is dialed. Once in a while I understand that there can be issues but the frequency with which this happens makes it unacceptable.

[racerdude]

I've also had to do numerous routing treatment requests but my issue is slightly different, in my case some outgoing calls only stay connected for 20-30 seconds before dropping. I've done extensive troubleshooting with my router and ATA and even swapped both of them but still have the problem. Routing treatments always correct the issue, but it sometimes happens a few days later to the same number. Fortunately it doesn't happen with all outgoing calls, but like you mentioned its frustrating when it does because I have to call the person back from a different phone when it happens until the support ticket is answered.

I also agree that this is the biggest negative issue with Voipo.

[racerdude]

This issue is still happening:

http://www.dslreports.com/forum/r297...reatment-Blues