Brandon has a PAP2T was on the way for me (for a different, ongoing ticket).
FWIW, I've had several changes applied to my account over the last 2 weeks to try to fix this, and it's still happening. Hopefully the Linksys will help with both issues.
Brandon has a PAP2T was on the way for me (for a different, ongoing ticket).
FWIW, I've had several changes applied to my account over the last 2 weeks to try to fix this, and it's still happening. Hopefully the Linksys will help with both issues.
Yeah it could. Grandstream finally told us that the HT502 is not thoroughly tested (or really designed) to be used behind any kind of complex NAT since they have other products without a built in router that are designed for that. We suspect over time that as more bugs are discover, they'll continue to enhance support for more and more complex scenarios. This would explain the devices giving a "500 Internal Error" in the logs when we see this.
When connected directly to the modem and with most simple NATs, the HT502 continues to work very very well.
We are maintaining a list of network setups/routes that the PAP2T works better on. I suspect it'll resolve your issue.
Before, there was a bigger issue going on for sure given the huge fluctuations we saw. So anyone still experiencing registration issues, contact us.
I had a problem with echos yesterday. Never had that issue before. Only affected the person on the other line. Did not have any audio problems on my end. It happened in the early AM on one call and then again when I called my wife from work last night. Hung up and called back and it was fine. Logged in webmail and submitted a ticket.
Support sent me a message telling me to move my ATA in front of the router. This is after someone else in support told me due to my pppoe connection and AT&T it was better to leave it behind my router.
When I replied and told them I would leave it behind my router because I had not had any echo problems before they never even bothered to reply back. I actually included the email with the ticket where I was told to leave it this way. I reset the ATA and the issue is gone. I do not think it had anything to do with my router.
Then I noticed today that I had a voice mail. Voice mail indicators not flashing and no tone to indicate I had a message. When I had the echo problem yesterday morning the call dropped a few minutes later. I guess she called me back and got voice mail but if I had not logged in vpanel I would have never known it was there. It also did not email it to me as it usually would.
Something fishy going on and its not my router. Anyway the echo issue seems to be gone now and I deleted the voicemail I never got.
If you think thats what is best I will gladly ship you this ATA back (and another that is broke has a major audio problem) and you can ship the Linksys but from the following posts I do not think I am the only one who has had a problem in say the last 24 - 36 hours.
Your call. I will also gladly watch it and see if I continue to have a problem and then we can make a decision. I do not want over react.
Lots of possible reasons for the problems. I am positive this ATA will not function in a normal fashion in front of my router. When I had it doing PPPoE connections my connection speed dropped by over half. It is just not a very good router.
Thanks Tim.
Yeah definitely not the only one. We're up to 12 reports now, so I agree it is odd for them to all happen around the same time. It's just hard to diagnose a bigger issue since 12 out of thousands really isn't that much.
We're continuing to monitor it in case anything more does come up.
Count me in as well. I got calls going to my failover and I looked in vPanel and it did not show anything registered. Can I get a Linksys as well??![]()
I have seen similar symptoms. For me, it's very hit-or-miss as to whether the message waiting indicator and/or stutter tone will work. I've tried it all in terms of how the adapter is set-up: in front of the router, behind the router, in DMZ. No difference. If the mail-gods are smiling on me, I'll have the PAP2T today and report back. It might help you, too...
For what it's worth; I tried calling my house today from my cell phone (Which happens to also be the failover and simultaneous ring number). Normally, if all is working fine, I can get the home phone to ring 3-4 times and then go to voicemail. If the adapter isn't working, I will go straight to my CELL Phone voicemail (Being I'm on it and it's the failover). The voipo line was fine for the last few days. Today; I logged into my adapter (Remotely). Both ports showed "REGISTERED". The vpanel showed 1 device registered. However; when I called it, I went straight to my cell phone voicemail. I.e. The adapter, while saying registered, wouldn't receive a call. I remoted in and rebooted. Waiting a couple of minutes; remoted in; verified register; called it with my cell phone and it would ring like it was suppose to and after 4 rings went to voipo voicemail.
So, maybe voipo made some changes and the adapter doesn't catch up until a reboot. Maybe the registration problem is in effect again. My problem is I have simultaneous ring on the cell phone. So, when I answe a call, I don't know if it's because I answered the cell phone for that or because of failover. I'll try calling the house every night when I get home from work to see if the phones ring in the house. Calling out has worked, because I usually do that at least once a night. So, I'll do some more experimenting. later... mike....
Mike
"Born Wild - Raised Proud"
Do you like your life? - Thank a Vet!!!
Bookmarks