No devices registered in Vpanel

[Montano]

Interesting Tim. I got the generic response to my ticket that everyone else got and assumed a fix had been found for all. Now it makes me feel as if I was lumped in with everyone else, and no one really looked at my issues. I was quite clear in my ticket that I use a PAP2T.

Here is the initial ticket entry:
"It seems like every 2 or 3 days my PAP2T looses registration over night. It's down this morning and a reboot did not seem to help. I'm on central02."

[VOIPoTim]

Interesting Tim. I got the generic response to my ticket that everyone else got and assumed a fix had been found for all. Now it makes me feel as if I was lumped in with everyone else, and no one really looked at my issues. I was quite clear in my ticket that I use a PAP2T.

Here is the initial ticket entry:
"It seems like every 2 or 3 days my PAP2T looses registration over night. It's down this morning and a reboot did not seem to help. I'm on central02."

Sorry about that. It was likely because it was BYOD. They should have responded directly, but we've been stressing that we do not provide BYOD support internally to our team a lot lately since it was making up the bulk of our time spent on support calls slowing all the other response times down, so that's likely why. They should have still replied mentioning BYOD though vs a reply with no real useful info for your situation.

The T values and 1 minute registration interval should help you get to a point of being problem-free again.

[Montano]

Thanks for the info Tim. Hopefully BYODers are entitled to support when they are experiencing the same loss-of-registration issues as non-BYODers. I can totally understand not supporting configuration, etc... but when a service works perfectly for 2 1/2 years with no changes to a device, then all of a sudden it won't register on repeated occasions and others are experiencing the same issues, I would hope support would be given.

Edit: Not saying I haven't been given great support, just wondering where you are going to draw that fine line.

[myvoip07]

Well i haven't gone this full thread specially the last 1 week. I started seeing the problem devices not registered on my HT502 since sometime after 8:00pm on 2/13 and till now. Outgoing seems to be working fine. Incoming goes to failover i.e voicemail right now.
I just logged in to HT502 and it show the below.
System Up Time: 23:50:37 up 3 days

[VOIPoTim]

Well i haven't gone this full thread specially the last 1 week. I started seeing the problem devices not registered on my HT502 since sometime after 8:00pm on 2/13 and till now. Outgoing seems to be working fine. Incoming goes to failover i.e voicemail right now.
I just logged in to HT502 and it show the below.
System Up Time: 23:50:37 up 3 days

I just applied the mentioned change to your account. Reboot and it should pick it up. Should be smooth sailing after that.

[myvoip07]

Tim, Thanks. Rebooted the HT502 as requested and now it shows 1 line registered in devices option in Vpanel.

[VOIPoTim]

Tim, Thanks. Rebooted the HT502 as requested and now it shows 1 line registered in devices option in Vpanel.

Yeah. Both lines are registered though. Your 2nd line is now a real clone though and not just two registrations, so you'll only see 1 in vPanel. Both will work though.

[Brian]

It seems that I don't have any devices currently registered. I'll reboot in a few, but wanted to post this first.

[Montano]

Both my lines are registered. Been that way for 3 days straight now

[usa2k]

Both my lines are registered. Been that way for 3 days straight now

Not to gloat, but mine have been flawless for a while now! (I love the GS HT502!)