Dropped cals - any issues today?

[Mike_TV]

I've had three dropped calls today where the call just dropped mid-conversation. All calls were outbound calls. Both lines blinked and few seconds later I was able to get a dial tone and redial the number in each case.

Any problems happening today? When this happens two or three times in one day is it better to check here on the forums or just go and open a ticket?

[sr98user]

I made couple of short calls today without any problems. You should probably open a ticket.

[Mike_TV]

Will open a ticket but in past experiences with my previous VOIP provider, if you can't replicate the problem on a consistent basis opening a ticket was kind of pointless.

[Russell]

Will open a ticket but in past experiences with my previous VOIP provider, if you can't replicate the problem on a consistent basis opening a ticket was kind of pointless.

I tend to agree with you. And, yes, I've had more than one experience like yours in the past week and I believe one this morning. In one case (previous day) the RT31P2 went appeared to go through a reboot sequence.

[MisterEd]

Was in the middle of a call yesterday and suddenly got a fast busy. It's happened before.

[VOIPoTim]

There are no issues on our network. Any issues (including network issues) that would affect large number of users are posted on our Twitter at www.twitter.com/voipo

Typically issues like dropped calls are caused by intermittent network issues or a lack of QOS.

Basically if there is any delay or drop int he packets, the call will drop. There's just no way to prevent this. So if there is a tiny delay even along the way or there is a tiny delay caused by something downloading there is potential to drop the call.

If you've ever been browsing and it takes a few seconds longer for a page to load than normal, this is an example. If you've ever been watching a video clip online and it skips for a second or has to re-buffer, this is an example. In regular web browsing it's not as disruptive since it just delays things a second or so and you may not notice.

Unfortunately since this stuff happens commonly on the internet and are not as noticeable during browsing, but are in a VoIP call since it's less forgiving.

Having an occasional dropped call is just part of the nature of VoIP since it uses the internet. If you're having constant, chronic drops over a long period of time then that's the point you'd want to contact support.

[MisterEd]

There has to be some difference between VOIPo and that other "V" provider. Never had any of these issues there for close to 2 years. Never dropped calls, never loss of audio, never 1 way calls and I call pretty much the same 4 or 5 numbers 90% of the time. I'm not writing this to be "spiteful" or crap on VOIPo but there must be something else at play relating to the VOIPo network vs. the other guy. Sure, I had an echo here and there on the other "V" but never the quantity of issues as I have experienced here in 6 months. I used the "same internet" on both services.

Yes VOIPo is less expensive but that shouldn't have anything to do with the quality of the phone service itself. If there was a disclaimer stating "VOIPo costs you less so expect more issues" when you sign up that would be another story. I didn't switch for the cost alone but that was a definite plus, I switched mainly for the features and more specifically for the call "routing" feature. I'd have no problem paying VOIPo more if that would resolve the sporadic network problems but I don't think the cost of service is the issue.

[usa2k]

If calls end abrupt versus properly close, is that something that can be internally monitored at VOIPo? Just wondering?



I suppose some debug mode on a specific ATA could maybe get to the root issue if it happens often enough.


A network of a couple years ago is unlikely to be comparable to a network of today. Things are always changing ... bandwidth ... modems from DOCSYS 1 -> 2 -> 3 ... modem profiles ... routing across the Internet ... levels of customer traffic ... VoIP topologies ... servers ... DNS ... the best fair comparison is running both side-by-side, and that could have issues with NAT routing between the two devices to the Internet for some router/modem pairs also - as well as port forwarding would not be feasible, so the hardware must be a good fit.

My luck with different VoIP providers and Cable providers, modems, and my router choices have always been remarkably good. I am looking at moving in the Fall and I hope my luck will continue, but I will only know when I put it to the test.

[VOIPoTim]

There has to be some difference between VOIPo and that other "V" provider. Never had any of these issues there for close to 2 years. Never dropped calls, never loss of audio, never 1 way calls and I call pretty much the same 4 or 5 numbers 90% of the time. I'm not writing this to be "spiteful" or crap on VOIPo but there must be something else at play relating to the VOIPo network vs. the other guy. Sure, I had an echo here and there on the other "V" but never the quantity of issues as I have experienced here in 6 months. I used the "same internet" on both services.

Yes VOIPo is less expensive but that shouldn't have anything to do with the quality of the phone service itself. If there was a disclaimer stating "VOIPo costs you less so expect more issues" when you sign up that would be another story. I didn't switch for the cost alone but that was a definite plus, I switched mainly for the features and more specifically for the call "routing" feature. I'd have no problem paying VOIPo more if that would resolve the sporadic network problems but I don't think the cost of service is the issue.

I understand that you're saying you've had a lot of problems with VOIPo, but it's definitely not the case that VOIPo users have constant issues.

Less than 2% of users have ever contacted support and our support levels are extremely low over the last few months. The majority of users have virtually no issues outside of occasional hiccups due to the nature of VoIP. In the rare cases were a user does have a lot issues, they are constant and ongoing and will never be fully resolved.

While it's normal to see occasional dropped calls, etc with any VoIP service as I explained above, your post makes it sound like you're having constant issues. If you have constant issues with our service, then it's not for you.

There are virtually no standards in designing VoIP networks so all providers have networks that are very very different. Different services also work better for different people depending on their internet connection and the path it takes to the provider, the path to the media gateways used (typically not operated by the provider), the home networking gear, etc.

If you're having that many problems, it may be best to find another provider that works better for you. There may be some kind of underlying issue (like the connection to us) that makes VOIPo not work well for you. If you decide to go this route, we can arrange for a prorated refund of any unused time (just contact me about this).

We hate to lose a customer, but if you really are having that many issues, it may be best to find another provider because it's just not normal for VOIPo.

While Vonage worked well for you, there are many people that report the same issues you're reporting experiencing on VOIPo at Vonage. All networks work differently for different people and there's not likely going to ever be a way to design one where it works for everyone given all the variables involved. It's just one of the downsides of VoIP. What works well for one person may not for another if they have different variables (different router, ISP, etc) in the mix.

[MisterEd]

I'm not having "that many" issues just a lot of issues that I never had before and am trying to understand the reasons. They aren't constant but they are intermittent enough to be annoying. It's also possible that some people are more tolerant than others when it comes to these issues.

While it may (or may not) be true, I just can't accept the fact that it's "the nature of VOIP." Occasional "audio problems" (echos, garbled calls etc) I can understand being "the nature of VOIP" but not what gets described as network issues where the problem is caused by "the downstream provider" or a database problem etc. Those issues aren't internet related or the "nature of VOIP."

As VOIPo grows and becomes more of a mainstream company where people just want telephone service like they're used to you will find they will become even less tolerant than those of us with some understanding and technical knowledge. I have no idea how many subs VOIPo has but I experienced a company that grew from 250,000 to almost 2,000,000 in less than 2 years from the inside and I can assure you (and as I'm sure you know) that the tolerance level drops as the number of "joe six-packs" sign up. They don't care about the nature of the internet or voip or forwarding ports. They just want phone service. :)

I appreciate your interest but unless your firing me I'm going to stick it out. :)

Please don't take it personally when I post a message stating I have had an issue or confirm an issue someone else has had as being similar to mine. For the most part people don't log on to these types of forums just to say "everything is hunky dory." "That's the nature of a support board." :D

[usa2k]

That's VOIPoTrump's job :)

[voipinit]

... For the most part people don't log on to these types of forums just to say "everything is hunky dory." "That's the nature of a support board." :D


Everything is hunky dory.

[MisterEd]

Everything is hunky dory. I knew I was walking into that. :)

[stevech]

It's not the Nature Of VoIP.
It's the Nature Of VoIP across the Internet (rather than a private network).

My employer uses VoIP on a very large scale (Hundreds of offices including Asia and the UK/EU). Its QoS is like POTS, because traffic does NOT flow on the wild-west of the Internet routing.

VoIPo, In My Experience, is near average in quality/reliability, a bit overpriced, slowly improving. In the running. Not yet way above average.

But really, the combination of the Internet and use of Asterisk (which I assume) mean that no cottage-industry VoIP provider can excel. But with the slow demise of the US class 5 switch POTS, this is the future.

I don't rely on VoIP - just testing the waters.

[ctaranto]

For the most part, everything is also hunky dory for me. I lost my Comcast connection for a few hours last week. No phone service, very little mobile coverage (T-Mobile at my house is weak and we rely on UMA over WiFi/Internet for connectivity). If we had an emergency, we'd be screwed, but we didn't and everything came back automatically.

As for VOIPo specific issues, I had a ton at first, but once I started using a solid adapter (the 2nd of 2 PAP2Ts tried), it's been relatively solid. We did have an issue with incoming calls last week, but that was an announced issue on VOIPo Twitter account.

Earlier this week, I was getting echoes and got an echo for a few minutes today (I was talking to my wife who was at home).

It's not perfect, nor do I expect it to be, but for $8 and change per month (2 year pre-paid), I have no complaints.

I'm about 30 miles west of Boston using Comcast and a DOCSIS3 modem (Motorola SB6120), connected to the Central servers.

[sr98user]

I just had a outgoing call drop after about 20 minutes. I checked my router and there were no dropped packets and the NAT entry was still there for the call.

I noticed that it was using the media gateway at 66.62.140.38. When I ping that machine, I get a very high latency.. Most of the times its around 110ms. But sometimes its very high.. If I do a traceroute most of the hops are fine except for the last one.

ping -t 66.62.140.38
Pinging 66.62.140.38 with 32 bytes of data:
Reply from 66.62.140.38: bytes=32 time=437ms TTL=48
Reply from 66.62.140.38: bytes=32 time=438ms TTL=48
Reply from 66.62.140.38: bytes=32 time=430ms TTL=48
Reply from 66.62.140.38: bytes=32 time=440ms TTL=48
Reply from 66.62.140.38: bytes=32 time=437ms TTL=48

Ping statistics for 66.62.140.38:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 430ms, Maximum = 440ms, Average = 436ms

[stevech]

FYI
66.62.140.38
from here in So. CA.

average 80-100. But often increases to 200-400mSec then timeouts, for tens of seconds for minutes. I just watched it go from 90 to 500, then timeouts, then back to 80mSec in two episodes.

Not my connection: pings to yahoo.com are without anomalies (steady 50-60mSec)

That address may be a client on
OrgName: 360Networks (USA) Inc.
OrgID: 360NE-1
Address: 2401 4th Avenue
Address: 11th Floor
City: Seattle
StateProv: WA
PostalCode: 98121
Country: US

NetRange: 66.62.0.0 - 66.62.255.255
CIDR: 66.62.0.0/16
NetName: 360NETWORKS-BLK-1
NetHandle: NET-66-62-0-0-1
Parent: NET-66-0-0-0-0
NetType: Direct Allocation
NameServer: TAISP1.IN-TCH.COM
NameServer: TAISP2.IN-TCH.COM
Comment: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
RegDate: 2001-01-03
Updated: 2004-08-05

OrgTechHandle: 360NE1-ARIN
OrgTechName: 360Networks Technical
OrgTechPhone: +1-877-993-4237
OrgTechEmail: network.operations@360.net

[rjbasye]

From KY

ping -t 66.62.140.38

Pinging 66.62.140.38 with 32 bytes of data:
Reply from 66.62.140.38: bytes=32 time=110ms TTL=53
Reply from 66.62.140.38: bytes=32 time=99ms TTL=53
Reply from 66.62.140.38: bytes=32 time=102ms TTL=53
Reply from 66.62.140.38: bytes=32 time=100ms TTL=53
Reply from 66.62.140.38: bytes=32 time=97ms TTL=53
Reply from 66.62.140.38: bytes=32 time=95ms TTL=53
Reply from 66.62.140.38: bytes=32 time=105ms TTL=53
Reply from 66.62.140.38: bytes=32 time=93ms TTL=53
Reply from 66.62.140.38: bytes=32 time=93ms TTL=53
Reply from 66.62.140.38: bytes=32 time=97ms TTL=53
Reply from 66.62.140.38: bytes=32 time=111ms TTL=53
Reply from 66.62.140.38: bytes=32 time=91ms TTL=53
Reply from 66.62.140.38: bytes=32 time=106ms TTL=53
Reply from 66.62.140.38: bytes=32 time=100ms TTL=53
Reply from 66.62.140.38: bytes=32 time=92ms TTL=53
Reply from 66.62.140.38: bytes=32 time=91ms TTL=53
Reply from 66.62.140.38: bytes=32 time=92ms TTL=53
Reply from 66.62.140.38: bytes=32 time=93ms TTL=53
Reply from 66.62.140.38: bytes=32 time=91ms TTL=53
Reply from 66.62.140.38: bytes=32 time=91ms TTL=53
Reply from 66.62.140.38: bytes=32 time=103ms TTL=53

Ping statistics for 66.62.140.38:
Packets: Sent = 52, Received = 52, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 133ms, Average = 98ms

[stevech]

66.62.140.38
watch pings for 10 minutes, in the busy hour. Much worse.

( we should not be using this thread's title for this gripe re a non-VoIPo server)

[scott2020]

66.62.140.38
watch pings for 10 minutes, in the busy hour. Much worse.

( we should not be using this thread's title for this gripe re a non-VoIPo server)

Maybe, but if one of VOIPo's upstream providers has a crummy gateway causing problems, Tim can put some pressure on them to fix it. It doesn't hurt to call out the upstream in my opinion.

I average 130ms from Missouri btw.