No devices registered in Vpanel

[Brian]

A Grandstream?

Yup.

BTW, I have no desire to ditch the GS and switch to a PAP - I'd much rather stick with the issue and help get it fixed.

[carlquist]

Just wanted to chime in that mine dropped as well. I read the thread in the announcement forum. Somehow I always seem to be in the 5% or whatever small number of users that is affected by these issues.

As usual, a reboot of my 502 corrected the problem.

My question is, why didn't it re-register by itself? And also why does the adapter always think it's registered when it obviously (as evidenced from the Devices vPanel page) is not?

[VOIPoTim]

My question is, why didn't it re-register by itself? And also why does the adapter always think it's registered when it obviously (as evidenced from the Devices vPanel page) is not?

They should be.

That's what we keep asking Grandstream and they don't have an answer for.

The PAP2Ts and Grandstream 286 (older models) re-register almost instantly.

When 502's don't re-register (not all the time), they have either an "Internal Server Error" or "Segmentation Fault" error.

[carlquist]

They should be.

That's what we keep asking Grandstream and they don't have an answer for.

The PAP2Ts and Grandstream 286 (older models) re-register almost instantly.

When 502's don't re-register (not all the time), they have either an "Internal Server Error" or "Segmentation Fault" error.

Fair enough. I understand you can't write Grandstream's firmware for them.

I'm not to this point yet. But are you guys willing to swap out my 502 for a PAP2T? If they aren't able to nail down the cause and correct it in the near future, I will probably get to the point where constantly "policing" my 502's registration status becomes too cumbersome.