No devices registered (502)

**usa2k** · 01-24-2009 07:24 AM

You do not currently have any devices registered to our servers!

That is odd?

**burris** · 01-24-2009 07:27 AM

Originally Posted by usa2k

You do not currently have any devices registered to our servers!

That is odd?

Mine shows ok..both devices(clone).

**VOIPoBrandon** · 01-24-2009 08:15 AM

Have you tried re-registering? Anything go in in the mid-night with the network?

**usa2k** · 01-24-2009 09:44 AM

Originally Posted by VOIPoBrandon

Have you tried re-registering? Anything go in in the mid-night with the network?

Interesting,

I thought it was just vPanel. I looked up the device and it said FXS 1 was not registered and FXS 2 was registered. A soft reboot and both were not registered, but minutes later they are registered.

vPanel now shows both. Maybe a side-effect of the upgrade?
I had not rebooted until now, and outbound has been fine.

BOTTOM LINE: All is well.

**hines86fan** · 01-24-2009 08:54 AM

I've not been able to get my ATA registered since I upgraded late last evening. They are working on my ticket.

**voxabox** · 01-24-2009 01:53 PM

uhm, my bro just told me that he tried to reach us at home (via phone) and got forwarded to my wife's cell. CP showed "No devices registered"
Anyways, I rebooted the HT-502, and it's registered now

**1bird2** · 01-24-2009 02:53 PM

I am seeing the same issue too. Devices will not register (as seen in vpanel). I have a ticket open and am in a dialog with Voipo support.

Question for anyone that has had this -- are you behind or in front of a router (I am, and have always been, behind a router - Linksys WRT54g, running Tomato 1.23).

Thanks,

-bird

**voxabox** · 01-24-2009 03:21 PM

Originally Posted by 1bird2

I am seeing the same issue too. Devices will not register (as seen in vpanel). I have a ticket open and am in a dialog with Voipo support.

Question for anyone that has had this -- are you behind or in front of a router (I am, and have always been, behind a router - Linksys WRT54g, running Tomato 1.23).

Thanks,

-bird

my ATA is and has been behind a router (WRT54GS v1.1 w. tomato v1.23)

**1bird2** · 01-24-2009 03:43 PM

Thanks for the info voxabox, I have the exact same config as you do (v 1.1 of the WRT54g as well). Really like the QoS capabilities of this software and I saw a major throughput performance gain when I moved to this configuration a few months back (moved from a Netgear ProSafe fvs33

.

Anyway, back on topic..... Really weird for me I guess. I have zero configuration rules to block anything on the router, and support told me the update should be coming via some address on port 80. I suppose I will temporarily have to move the ATA in front of my router and see if that resolves this problem -- ugh.

-bird

**myvoip07** · 01-24-2009 03:43 PM

Originally Posted by voxabox

my ATA is and has been behind a router (WRT54GS v1.1 w. tomato v1.23)

My ATA is and has been behind a router(WRT54GL with dd-wrt) as well and haven't had any problems. I don't use STUN but does port forwarding on the router for the ATA and other services. Before and after reboot my ATA is still connected.