No devices registered in Vpanel

Quote:

---

Originally Posted by dbmaven

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.

---

It's only Line 2 though? Very odd.

Line 1 remains active and available at all times.

Very odd may be an understatement.

Absolutely reproducible.

And Line 2, right now, remains active.

So this is about PAP2T not HT502, right DBMaven?

Yes - this is a PAP2T

For what it's worth, I have 2 accounts with a PAP2T on one and a 502 on the other, both in tandem.

Although the PAP2 has never missed, I see this morning that the 502 has been up and running and registered for the last 19 hours.
Sure looks good.

PAP2T line 1=5060 line2=5061

502 line1=5079 line2=5062

So, just an interesting note, not a complaint: My internet died for about 30 minutes last night. My GS was not registered this morning - my PAP2T (2nd line, BYOD) was. I'm not necessarily saying there's anything wrong - I don't know that a device should re-register after a network failure, but it was just interesting that the PAP2T didn't have any issues.

Line 2 remained active/available overnight.

Quote:

---

Originally Posted by Brian

So, just an interesting note, not a complaint: My internet died for about 30 minutes last night. My GS was not registered this morning - my PAP2T (2nd line, BYOD) was. I'm not necessarily saying there's anything wrong - I don't know that a device should re-register after a network failure, but it was just interesting that the PAP2T didn't have any issues.

---

An interesting problem.

I wonder just what it is that tells the ATA to register/re-register?
Evidently the 1 minute setting is not effective for everyone. Maybe the DNS gets confused after the network failure.

Quote:

---

Originally Posted by Brian

So, just an interesting note, not a complaint: My internet died for about 30 minutes last night. My GS was not registered this morning - my PAP2T (2nd line, BYOD) was. I'm not necessarily saying there's anything wrong - I don't know that a device should re-register after a network failure, but it was just interesting that the PAP2T didn't have any issues.

---

Brian,

Just curious, do you have DNS servers hardcoded into the 502 or is it just the default DHCP?

What about the PAP2T?

Quote:

---

Originally Posted by VOIPoTim

Brian,

Just curious, do you have DNS servers hardcoded into the 502 or is it just the default DHCP?

What about the PAP2T?

---

DHCP on both - which is my router's address, pointing back to Comcast. I have no problem changing it - just let me know what you'd like me to try, if anything.