Phone Trouble

**energyx** · 05-05-2010 10:36 AM

Originally Posted by stevech

My problem, #5 in this list, was quickly responded to by support's ticket system. The instruction to me was "reboot the ATA". I did. Problem gone.
Did the ATA forget the settings they put in place on the prior ticket for the same problem?
Why do *I* have to reboot the ATA? Can't they? I want the service to be transparent to people in this house. Me the geek is often not here, and reboot-the-ATA by on line support desk login is not viable for others in the family.

But thanks, VoIPo, for the rapid attention from support.

I'm in the same boat. I've tried the ATA in front of my router, behind my router, the problems resurface after a day or two. Support resorted to blaming a few 140ms pings during peak times as the problem. I am in networking/servers for a living and a 140ms ping time should not result in a call being dropped when answered, or not even ring at times.

My last resort is trying DD-WRT, as many have had luck with here. I just tried to call home and it never rang on my end, then went busy. My wife called back saying she answered, but got fast busy. I just disabled the SPI firewall as my last resort. The ATA is DMZ'd. As much as I'd hate to lose our phone number of 10+ years, I may have to resort to Time Warner for phone service.

edit: I forgot to add that this all started when I got a replacement ATA (HT-502) back in March. The Linksys RT3P2 just hummed along with little issue.

**voipinit** · 05-05-2010 02:28 PM

Are you forwarding the proper ports on your router? If your router has an UPnP option, enable it, although DD-WRT may help your situation.

**energyx** · 05-05-2010 02:32 PM

Originally Posted by voipinit

Are you forwarding the proper ports on your router? If your router has an UPnP option, enable it, although DD-WRT may help your situation.

The ATA is in the DMZ, so all ports are forwarded to it that aren't already assigned. My main point was that going from Linksys to Grandstream should not require all this changing and troubleshooting.

**Xponder1** · 05-05-2010 02:53 PM

For the record my ATA was just sitting here with the phone lights out. Reboot seems to have resolved.

**VOIPoTim** · 05-05-2010 03:03 PM

Originally Posted by Xponder1

For the record my ATA was just sitting here with the phone lights out. Reboot seems to have resolved.

http://forums.voipo.com/showthread.php?t=2397

**Xponder1** · 05-05-2010 03:36 PM

Thanks Tim

**Xponder1** · 05-05-2010 03:40 PM

I no more than hit Enter on the previous message and noticed the lights are out again

**eagle 1** · 05-05-2010 04:38 PM

My service is also down, both accounts with both ATA's and BYOD device. Have opened ticket at about 12

m est today (ticket #HUR-511483). Support has responded by having me reboot the ata's, then changed my provisioning (changed by ata to point to east01 instead of central01, they also used the IP address instead of the name.. All internet and other providers are working ok. Can ping and tracert to both servers. see registration request, then contact to hermes.voipwelcome, then the request seems to time-out...wife is pissed at me as usual for phone calls she has missed...The fail over is working and going to my cell though.

**VOIPoTim** · 05-05-2010 06:00 PM

Originally Posted by eagle 1

My service is also down, both accounts with both ATA's and BYOD device. Have opened ticket at about 12

m est today (ticket #HUR-511483). Support has responded by having me reboot the ata's, then changed my provisioning (changed by ata to point to east01 instead of central01, they also used the IP address instead of the name.. All internet and other providers are working ok. Can ping and tracert to both servers. see registration request, then contact to hermes.voipwelcome, then the request seems to time-out...wife is pissed at me as usual for phone calls she has missed...The fail over is working and going to my cell though.

I had someone check your ticket a few minutes ago and they said our logs are showing that the traffic isn't getting back into your network and they think it's network related.

I will have someone contact you about it, but they said the logs are definitely showing that it's not making it through so if you want to check any network/firewall settings, you may be able to resolve it on your own.

**tritch** · 05-24-2010 05:13 PM

Originally Posted by caseydoug

For what it's worth, I've been having problems since late last week. First it was one-way audio, then calls dropping as soon as I answer (all the problems are with inbound calls). All requisite ports are forwarded, and I haven't changed anything lately.

Ticket #HRN-434952

Originally Posted by Russell

Glad I'm not the only one who experienced that! It was just one call - unfortunately, it was the wife. Ask the caller on those dropped calls if you can - see if they say it went to voicemail. I'm curious.

Caseydoug or Russell,

Have either of you had these types of problems lately? If not, what was the fix?

I randomly started having this issue about 4 weeks ago on inbound calls only. It seems to be happening only on inbound Voipo to Voipo calls for me. The caller goes straight to voicemail, but my phones ring anyway (dead air when answered). I've had no issues for over a year until lately. All required ports are forwarded. Thanks