No devices registered in Vpanel

[carlquist]

I had lost registration sometime overnight or early this morning as well. I waited approx 3 mins before rebooting the 502. The devices page never indicated a registration within that time so I went ahead and rebooted. That corrected the problem.

[burris]

Just for the record, I have both my PAP2T as well as my 502(2nd number) online.
I did just take a look at the VPanel for my 2nd line, and although the 502 shows as registered in the ATA, I had to do a manual reboot for it to really register.
Outbound of course, did work before I rebooted. Now it does shows in the panel.
The 502 is set for 1 minute registration and is pointed to the sip server..

The PAP2T sits there and purrs..not a problem.

[dlangley]

After about 2 weeks of no probems, yesterday I started having registration problems again.
Once yesterday afternoon, once last night and once this morning.
Yesterday afternoon: 1 port showed as registered, calls went to failover.
last night: port 2 unregistered but still got calls on port 1.
this morning: same as last night.

in all 3 cases a reboot fixed the registrations.

[orum]

Lost registration again last night/this morning...

Dan

[Montano]

My BYOD PAP2T has had no registration issues for a couple weeks now. I'm feeling better and better as each trouble free day passes.

[Brian]

Lost registration on one of my lines this AM (and I waited quite a while before I power cycled).

[kevm]

I'm unregistered again too. just checked

[ralfaro]

This is really getting to be a bit much. My ATA was registered and working yesterday morning when we left for the day and returned home this afternoon. I got a call from my Son on my wife's cell phone tellimg me his calls were going to my failover number again. When I checked VPanel, sure enough, the ATA was not registered. I'm opening a ticket to see what if anything can be done about this as it has been worse in the last few days. I really don't want to have to babysit my GrandStream all the time. Hoping we can get to the bottom of this.

RA

[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.

[kevm]

Great. Thanks Tim. Your communication through this entire thing has been top notch.