No devices registered in Vpanel

**VOIPoTim** · 02-11-2009 11:12 AM

Originally Posted by scott2020

I can't receive inbound calls or make outbound calls. Opened a ticket.

Inbound calls ring, but can't be answered. When it goes to voicemail, it drops the call.

Outbound calls just fast busy.

Scott

That sounds more like an audio issue. If it's ringing, you're registered, etc.

If you have a few mins, can you call in since that's likely easier to diagnose via phone?

**scott2020** · 02-11-2009 11:17 AM

Will do.

I have to conference in my wife probably when she gets back.

When she calls out, gets only fast busy. When I call her from work, the phone rings but when she picks up the phone, she gets silence, a click, then a fast busy. I eventually go to voicemail, but me being the caller I never hear her pick up, it just rings until it goes to voicemail.

**CrownSeven** · 02-12-2009 12:31 AM

I had a similar issue as scott2020 yesterday. A reboot solved the issue, but it was the second time it happened. I'll also give customer support a call.

**KayakinMike** · 02-12-2009 07:24 AM

Originally Posted by scott2020

Will do.

I have to conference in my wife probably when she gets back.

When she calls out, gets only fast busy. When I call her from work, the phone rings but when she picks up the phone, she gets silence, a click, then a fast busy. I eventually go to voicemail, but me being the caller I never hear her pick up, it just rings until it goes to voicemail.

I had this same issue. Support switched my STUN to NO and all is fine again.
Mike

**scott2020** · 02-12-2009 09:18 AM

I did have STUN turned on, and my device was still going to central02. Brandon got me re-provisioned to central01 and disabled all STUN and that fixed me up. My STUN was set to some "goes.com" address. I have tried both ways and have had trouble with both, so hopefully this will clear things up.

**bretski** · 02-13-2009 10:26 AM

This morning, I discovered that all inbound calls since about 5:00pm MST (yesterday) were going to failover (voicemail). Had to reboot.

**VOIPoTim** · 02-13-2009 10:34 AM

If you are seeing this, there are changes we can apply to your account that will likely resolve it in your specific situation.

We're just not seeing a large drop like before when it was obviously a larger issue. Registration levels look normal.

Now we're only seeing a few cases not hundreds like we did when we were seeing a system issue. A few registrations out of thousands just isn't really that much.

The few cases of this are likely just specific NAT setups that need something specific set and support will try to determine that on a case-by-case basis and apply changes to your account that could help.

For some specific ISPs and network setups, we've determined that the PAP2T is a better option and in some cases may process a replacement if we've seen cases where it's worked better for specific ISPs/setups.

**bretski** · 02-13-2009 10:50 AM

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.

**VOIPoTim** · 02-13-2009 11:00 AM

Originally Posted by bretski

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.

**Xponder1** · 02-13-2009 11:02 AM

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.