No devices registered in Vpanel

Quote:

---

Originally Posted by 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

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

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.

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

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

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.

Quote:

---

Originally Posted by 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.

---

Same here :)

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

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

I am still registered as of this morning.

Quote:

---

Originally Posted by Brian

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

---

That's known as the administrator penalty.;)

My line dropped this morning in the middle of a call at 9:40 AM EST. No devices registered in VPanel. Rebooted Grandstream device and I'm back up.

I submitted new case to Voipo support.

I lost registration again this morning and didnt realize it until a call went to my failover number about 10 minutes ago.

My grandstream also lost registration. I noticed after trying to make a call, it took longer than usual to ring out, but it did eventually. Checked to see if it was registered after that and saw that it was not - reboot time. I was surprised that I could still dial out even though the device was not registered.

Quote:

---

Originally Posted by CrownSeven

My grandstream also lost registration. I noticed after trying to make a call, it took longer than usual to ring out, but it did eventually. Checked to see if it was registered after that and saw that it was not - reboot time. I was surprised that I could still dial out even though the device was not registered.

---

Just checked again, mine are still registered.

Still registerd as well. last reboot for the unregistered issue was 17 hours ago.

The people who are saying they had a problem today need to indicate if they rebooted last night so they know if its related to the old problem or if its something else.

I rebooted yesterday and everything is still fine.System Up Time: 10:13:19 up 14:11

Yes, I followed Tim's instructions and rebooted right after he told us to ;)

After all the good things that were happening, I'm sorry to say that after 13 1/2 hours of up time on my 502, it just dropped registration..however a reboot quickly restored it.

Meanwhile, the PAP2T has not missed once.

Are you guys sure it wasn't just in the process of re-registering or was it down for a while?

Quote:

---

Originally Posted by VOIPoTim

Are you guys sure it wasn't just in the process of re-registering or was it down for a while?

---

I don't know what time it went down, but when I checked, I gave it a good couple mins before posting.

Tim,

Remember, I was actually dropped from a call I was on. That's how I knew it happened. If it was in the process of re-registering, why would it have dropped me from the call?

It probably took me ~ 4/5 minutes from the dropped call, until I manually rebooted the ATA.

Quote:

---

Originally Posted by VOIPoTim

Are you guys sure it wasn't just in the process of re-registering or was it down for a while?

---

I can't tell you.

I know it was up and running for over 13 hours. I clicked on my tab and it was down. I looked at the VPanel and it said device was down.
If it was reregistering, why would it go down?

Tim, this is my second line and it's on the 502. I only use it for testing, so any tests you need to run on it...go ahead.
I won't be around to help for the rest of the afternoon, but you can do whatever you need to do.

I have only have had the registration issue a few times, the last time was yesterday around noon EST. I rebooted and it has been stable since, and rebooted again after I read the posts suggesting so. I think the problem is with the GS devices as a whole. It appears to attempt to re-register about 20-30 seconds before the expiration and if it fails for whatever reason, it's done and does not try again (or if it does it sends gibberish). Talking to the GS folks on a similar problem that I noticed when I first lost registration several weeks back (line 1 with a different provider failed when line 2 [Voipo] failed to re-register). They have been in contact and I think the next firmware release will address this, but who knows when that will be, they didn't say. Like Tim said sometime back, I don't think the maturity of the GS HT-502 is there yet. That said, with the same GS HT-502 (line 1), I have NEVER lost registration with the other provider.

Quote:

---

Originally Posted by Hawkmeister

Tim,

Remember, I was actually dropped from a call I was on. That's how I knew it happened. If it was in the process of re-registering, why would it have dropped me from the call?

It probably took me ~ 4/5 minutes from the dropped call, until I manually rebooted the ATA.

---

Were you on the older .8 firmware by chance?

Hi Tim,

I don't believe so. I've tried to keep things updated. Here's the ATA detail..

Product Model: HT-502 V1.1B
Software Version: Program-- 1.0.1.21 Bootloader-- 1.0.0.9 Core-- 1.0.0.25 Base-- 1.0.0.76

I don't know if the Motorola Cable modem logs would be of any help. I have noticed records being logged that were not present prior to adding the ATA. The following is an example of the events:

2009-02-17 09:02:23 6-Notice M571.1 Ethernet link up - ready to pass packets
2009-02-17 09:02:21 6-Notice M571.4 Ethernet link dormant - not currently active
2009-02-17 09:02:19 6-Notice M571.1 Ethernet link up - ready to pass packets
2009-02-17 09:02:11 6-Notice M571.4 Ethernet link dormant - not currently active
2009-02-17 09:02:09 6-Notice M571.1 Ethernet link up - ready to pass packets
2009-02-17 09:02:07 6-Notice M571.4 Ethernet link dormant - not currently active


Let me know if there's anything else i can provide in my environment that will help troubleshoot.

Tim you think it would help to find the cause if the logging on the devices was set to debug? Last time you gave out the pass I noticed a log level setting. Maybe its something simple that is not getting logged because its set to error only or something like that.

Just tossing out ideas. I understand that would create a lot of traffic so maybe try it with a test group (folks who have more problems then others perhaps).

Mine is still up.
Product Model: HT-502 V1.1B
Software Version: Program-- 1.0.1.21 Bootloader-- 1.0.0.9 Core-- 1.0.0.25 Base-- 1.0.0.76
System Up Time: 13:03:02 up 17:00

So far, support is almost dead today and things are very quiet (just catching up on tickets) and the graphs have never been higher, so while it's still to early to tell, this is all a good sign.

Quote:

---

Originally Posted by VOIPoTim

So far, support is almost dead today and things are very quiet (just catching up on tickets) and the graphs have never been higher, so while it's still to early to tell, this is all a good sign.

---

Good to hear! Long overdue break for support ;)

I can tell you right now that I have only today had registration issues and when calling out the number originated from a 310 number. on chat right now with support. Been solid on the GS until today.

Quote:

---

Originally Posted by mboudoin

I can tell you right now that I have only today had registration issues and when calling out the number originated from a 310 number. on chat right now with support. Been solid on the GS until today.

---

Yeah I know someone was just talking about your account with 310. It looks like someone accidentally typed in your MAC address to assign to another account.

So when you rebooted it provisioned the wrong account info so you were registering, but not to your account.

They should have that fixed shortly.

Fixed already. Something weird with the way the account was provisioned. ATA seems to have updated after the error was found. I have to hand it to you guys. As long as you can keep up with the support side of the issues then I am here for a while.

I just re-opened ticket IWH-339207

I don't know if you pushed something out or not - but the Line 2 not registering problem is back. It was fine all day *(as far as I know). I even had to reboot my modem/router, and when I rebooted the PAP2T it was fine - then on the first or maybe second re-registration Line 2 went out.....

Quote:

---

Originally Posted by dbmaven

I just re-opened ticket IWH-339207

I don't know if you pushed something out or not - but the Line 2 not registering problem is back. It was fine all day *(as far as I know). I even had to reboot my modem/router, and when I rebooted the PAP2T it was fine - then on the first or maybe second re-registration Line 2 went out.....

---

Do you have anything else connecting on that port by chance? 5061

That's interesting.

Let me check something out and get back.

Quote:

---

Originally Posted by dbmaven

That's interesting.

Let me check something out and get back.

---

PAP2 is using 5060 and 5061 for the main signaling ports so just make sure nothing else running on those. If you need to change them due to something else being not changeable, we can.

I have a MagicJack - which might well use 5061.
It has been active all the time and has not previously caused problems.....

But I pulled it - and rebooted the PAP2T - still won't register on Line 2.

Quote:

---

Originally Posted by dbmaven

I have a MagicJack - which might well use 5061.
It has been active all the time and has not previously caused problems.....

But I pulled it - and rebooted the PAP2T - still won't register on Line 2.

---

Let's try changing your port. I'll set it to 5079. Especially since it's just 1 line having issues, it sounds like a port issue. Reboot now and try that.

That did it. Line 2 is active - has dial tone and was able to dial out.

Very strange...

Thanks !

Spoke too soon.

I've now duplicated the sequence of events that caused it to go out.

I call my VOIPO line from my MagicJack.
I don't answer, and let it go to voicemail.
Line 2 is active (light is 'on' on the PAP2T).
I go to vPanel, and play the voicemail online.
Line 2 is still active.
As soon as I delete the voicemail, Line 2 light goes out, and the PAP2T status page shows:
Display Name: User ID: ##########B
Hook State: On Registration State: Can't connect to login server
Last Registration At: 2/23/2009 21:40:54 Next Registration In: 9 s
Message Waiting: No Call Back Active: No

The same sequence caused it both times - so it wouldn't appear to be the specific port.

Edit to add:
MagicJack not installed.
I pulled power from the ATA.
I rebooted my router to clear any 'active' ports.
After applying power to the ATA, both lines went active.

I then called my VOIPO number from my cell phone, and repeated the steps above.
Before deleting the message (while it was still playing, actually) Line 2 went dead and shows the same result in the PAP2T status page.
Doesn't appear to be related to the MagicJack or even a specific port....
Reset the ATA and router, both ports active. I'll monitor to see if Line 2 stays up.