False busy signals on calls to the midwest

Posts: 19 · Vonage Forum Associate Joined: Feb 24, 2005 Posts: 19

I am in Indiana.

I've been trying to call my brother in South Dakota all evening on my Vonage phone and his phone has been busy.

After a couple of hours I started to panic and immediately after hearing the busy signal I called him on my Verizon cell phone and it rang right in.

He said he was worried that I wouldn't call him and he had been sitting by the phone waiting for my call. He hadn't used the phone all evening.

I've never had a problem like that before. I get a busy signal when I call him on my Vonage phone, it rings in with no problem when I call him on my Verizon cell phone.

All the other phone numbers I've called today from my Vonage phone worked just fine..

Anyone else have any problems like this?

Posts: 153 · Vonage Forum Master Joined: Jan 11, 2007 Posts: 153

Just called a number in Iowa (515) and another number in Pierre, South Dakota (605) no problem.

Posts: 19 · Vonage Forum Associate Joined: Feb 24, 2005 Posts: 19

I'm getting through to SD today just fine..

Posts: 148 · Vonage Forum Senior Joined: Feb 28, 2005 Posts: 148

I'm getting false busy signals today, calling to Urbana, IL..... Have to make several attempts to get through.

Posts: 208 · Posted: Fri Mar 30, 2007 12:06 pm Post subject:

I wonder if it's your ISP that's causing the trouble. Is this something new? Are you a new customer? Did you port your number in? Was your brother a Vonage customer, then left?

Sounds like if your calls are going to a fast busy, then maybe something's going on with your ISP or your device.

Posts: 18

I'm not a new customer and my setup has worked well for over 2 years. Lately I can call my mother's numbers in 856 with no problem, but when my wife tries to call her family in 225 (home, work, cell x 2 people) we have trouble getting through. On our end we get nothing but silence for about 30 seconds and then we get the fast busy error tones. On the receiving end the phone rings but when they answer they can't hear us.

Sometimes the phone will finally ring 30-45 seconds after dialing. Sometimes it works fine right away, but mostly it doesn't to 225 numbers.

If I were experiencing this problem with all numbers I'd suspect my end, but since it's only with certain numbers I suspect the problem lies outside my setup. Any ideas?

Posts: 66 · Full Forum Member Joined: Jul 20, 2006 Posts: 66

DoomedTX wrote:

I'm not a new customer and my setup has worked well for over 2 years. Lately I can call my mother's numbers in 856 with no problem, but when my wife tries to call her family in 225 (home, work, cell x 2 people) we have trouble getting through. On our end we get nothing but silence for about 30 seconds and then we get the fast busy error tones. On the receiving end the phone rings but when they answer they can't hear us.

Sometimes the phone will finally ring 30-45 seconds after dialing. Sometimes it works fine right away, but mostly it doesn't to 225 numbers.

If I were experiencing this problem with all numbers I'd suspect my end, but since it's only with certain numbers I suspect the problem lies outside my setup. Any ideas?

I was getting a fast busy after a long delay after auto-dialing when I called my cardiologist (of all people).

Come to find out, somehow an extra digit got put into the autodial setup.

Posts: 414 · Posted: Fri Mar 30, 2007 8:45 pm Post subject:

Doomedtx, Who is your internet service provider? There was an issue for today(past few days maybe) with calls traffic looping over an AT&T router on certain traffic being passed to the western US. My bet is on you having someone like Cox or Suddenlink and being effected by this on calls to a Vonage server on the west coast which is probably handling the 225 LA area.

Posts: 18 · Posted: Sat Mar 31, 2007 1:04 am Post subject:

My ISP is Mayanet in Turkey. I figured it out yesterday. I forgot that we switched ADSL modems...the new USR unit has a firewall setting to protect against DDoS attacks. For some reason when I dialed the 225 numbers it was detecting an attack while the 856 numbers did not. When I disabled this setting everything returned to normal.