No devices registered in Vpanel

[VOIPoTim]

No need for a ticket right now, but can those of you that have lost it recently (or ever) please open a ticket if you do from here on out.

I don't want to get into details just yet, but I just made a rather big discovery.

I was just looking in system logs myself and noticed something pretty big standing out (at least to me). I may not know what it means fully, but I know keywords and when certain keywords and ERROR shouldn't be together. I had 2 of our admins look into it and sure enough they said it's an issue that should be fixed, but was overlooked all this time.

I think sometimes admins see errors and think "oh that's ok to ignore" since they know what it is and "know" that there are a lot of things that "shouldn't be an issue" but when I don't know what it is to the extent that I don't brush it off until someone explains to me why it says error "even if it doesn't matter" just so I know. With that being said, I noticed something that several other full-time sys admins did not and we think it could be the culprit.

We're looking into this more, but this little error could have been causing this entire mess.

In relation to this, check out http://forums.voipo.com/showthread.php?t=1187

[VOIPoTim]

44K errors this afternoon today when I found this to none since. Looking good so far.

[quattrohead]

Thats why I always ask questions even when out of my depth on something, I like to have people really think about the question from a simple point of view.

[Brian]

When I checked a few minutes ago, I was not registered

[burris]

Just for the record..

My PAP2T that I use for my main line hasn't missed yet...registration is set for 1 hour.

My 502 that I have connected in tandem for my 2nd number and is pointed to the sip server, has been on all night and has not missed. Last reboot was almost 10 hours ago. Registration is still set for 1 minute. Firmware is still 1.0.1.21...no change

Both residing behind my router with no DMZ-no port forwarding-no nothing.

burris

[bubbanc]

So what exactly was the DNS issue that was resolved? Just curious since my BYOD hasn't had any registration issues nor have I had issues with the panel or placing/receiving calls.

[dswartz]

So what exactly was the DNS issue that was resolved? Just curious since my BYOD hasn't had any registration issues nor have I had issues with the panel or placing/receiving calls.

Same here

[Brian]

So am I the only one that lost registration again? Just a fluke hopefully?

[kevm]

did you reboot after they announced the fix? If they had a DNS issue, maybe you need to register again. I am not sure what the issue is or was.. Could have been something with the naming such as the incorrect FQDN for the primary DNS I suppose, but of course thats just a guess.
I believe Tim asked us all to reboot after the possible fix. I have not yet and I am still registered, but it might be worth a try.

Just a thought. Good luck.

Kevm

[NY Tel Guy]

I am still registered as of this morning.