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

[voipinit]

Hertz,

I had to request a routing fix when I was with Packet8.

[Tlbaker]

Yes, I am having the same problem. Calls ring, then go busy while call is still ring on other phone. Does not ring and goes straight to call cutting off part of the opening conversation. Etc etc etc. What is happening?? It was working fine before.

[Razzy]

I realize this is an old thread but I don't give a crap. I have the same issue for a while and nothing is fixed yet. Anyone else having this issue??

[VOIPoTim]

I realize this is an old thread but I don't give a crap. I have the same issue for a while and nothing is fixed yet. Anyone else having this issue??

Contact us at support@voipo.com and we'll be able to help you. If it rings then goes to dead air, the most likely issue is that the audio stream is being blocked by your router/modem. Support can help you setup port forwarding on your router to always allow our traffic through to the VOIPO device and that'll likely resolve your issue.

[ggmorton]

I realize this is an old thread but I don't give a crap. I have the same issue for a while and nothing is fixed yet. Anyone else having this issue??

Yes, I see this issue a lot with only 1 phone number (my parents) which is to a rural phone company in TN.

They have made route changes, and it works for a while. Then it is back to the same problem. I've emailed support again to see if this can be finally resolved.

[wingsohot]

Good input, which other providers have this issue too? Any large ones? Never saw it with TimeWarner over 2 years of service.

I've just started having the same issue with Timewarner. Noticed in my call logs that the times were showing up as am, however it was pm when I was calling out.

[rmwlaw]

I am having the same problem with a wide variety of telephone numbers I am trying to call. Sometimes, it will drop the call after 15-20 seconds into the call.
I truly hope that VOIPO is on top of this, and is in the process of fixing this. I cannot afford to not be able to return calls from clients, or be in the midst of a conversation with a client, and voila.... No one on the other end of the phone.

ISP is Comcast.

[jimski]

I have similar issues. Finally got everything working about 2 weeks ago & then after my home phone number was successfully ported 2 days ago, these same outgoing call issues re-emerged; calls ring once & drop or go to called no. voicemail. Also can't get simultaneous ring to work on incoming calls. Both lines(one is cellphone) sometimes ring only once & then quickly go to voicemail before either line can be answered? ? ?

[DaveH]

I've seen posts regarding Callcentric, VOIP.ms.

I posted a question on the Broadband VOIP tech board:

A few weeks ago I had issues with outbound calls to 2 specific numbers. One would consistently go to the recipient's voicemail, the other would drop after one ring. I contacted my VOIP provider (VOIPo) and the fixed the issue by modifying the routes.

Is this common among VOIP providers?

What can they actually modify and how much control do they have over the route a call takes?

... and got this answer:

As with all providers they do choose the routes that your calls take.
The routes are generally chosen by what is called least cost routing. That means that in practicality, the provider tries to choose the route that cost the least and hopefully works.
When that route doesn't work for some, they simply put them over another carrier that maybe costs more or maybe has better access to the terminating point.

Mostly has to do with cost to the provider but as in any business in the world, cost is a major factor..

With respect to VOIPo, I have been around since the beta testing days and they have evolved into a first class VOIP provider and at one of the lowest cost...service, in my opinion, is second to none, as in many cases the owner of the company gets personally involved in any issue that routine support cannot solve..

No, I don't work for them..

[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.