You do not currently have any devices registered to our servers!
That is odd?
Printable View
You do not currently have any devices registered to our servers!
That is odd?
Mine shows ok..both devices(clone).Quote:
Originally Posted by usa2k
Have you tried re-registering? Anything go in in the mid-night with the network?
I've not been able to get my ATA registered since I upgraded late last evening. They are working on my ticket.
Interesting,Quote:
Originally Posted by VOIPoBrandon
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.
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
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)Quote:
Originally Posted by 1bird2
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 fvs338).
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
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.Quote:
Originally Posted by voxabox
Okay -- I have reluctantly moved the ATA outside of the router.
Current configuration:
Cable Modem <--> ATA <--> Router <--> Lan Devices
Still not working, as expected as I think there is something else going on with either the verision of old code that is on my ATA or a configuration issue on there end. Everthing was working until this weekend and I have not made any changes -- until I now moved the ATA to in front of the router.
I have a ticket open and hope to get this resolved soon. Good news is that the failover feature is working as my cell phone rings when someone calls my Voipo number.
-bird
I am also running into this with one of my 502's also. I had a heck of a time getting it to upgrade, now it's upgraded it will not register.
Looks like provisioning is not working or at least yesterday I was able to view the dat files for the 502 and the 286 in FireFox.
This is only for testing if provisioning is the problem. If you have admin access then disable provisioning and manually enter the SIP and your account details and see if it works.Quote:
Originally Posted by zevin
I'm still suffering from the inability to register after the upgrade. I moved the ATA in front of the router. Then tech support called, and we went through and verified the settings for firmware path and config path, and various other settings. But, alas, no joy was had.
Based on most, if not all, of the posts -- I see that most are able to get the upgrade. My ATA will not even upgrade. In fact, the support guy I talked with today was suprised at the version of firmware I had, 1.0.0.76. I guess I have some really old version/device, which is weird as I really have not had any issues since getting the 502 ATA, until today of course.
I hope I am contacted soon to get this resolved.
-bird
This is how it show after upgrade to 1.0.1.21. What does your shows?Quote:
Originally Posted by 1bird2
Software Version: Program-- 1.0.1.21 Bootloader-- 1.0.0.9 Core-- 1.0.0.25 Base-- 1.0.0.76
Also i doubt there was 1.0.0.76 firmware version before as i couldn't find it. But i may be wrong.
I guess they have them locked to MAC address because it will register for only one of the 4 lines I have. I was wanting to switch my GS286 on my main line with this particular GS502. None of my ATA's have anything filled in in the firmware/configuration server path. I have been here awhile. :rolleyes: ;)Quote:
Originally Posted by myvoip07
So as for the firmware upgrade bit mine is done, and working.
For those of you having problems with this, make sure you have a ticket open so we can work through them with you.
My unit would not find the updated firmware until I changed the settings to use TFTP and Grandstreams IP.
We should probably have the correct info from VoIPO for future upgrades, unless they are going to use the factory standard firmware from now on.
Sounds like they should do as they seem to have a good working relationship with them and have pushed the firmware along in the right direction.
Same versions here.Quote:
Originally Posted by myvoip07
Software Version: Program-- 1.0.0.76 Bootloader-- 1.0.0.9 Core-- 1.0.0.25 Base-- 1.0.0.76
Directly from the 502 interface.
This is how mine looks...and it works well...Quote:
Originally Posted by 1bird2
HT-502 V1.1B
Program-- 1.0.1.21
Bootloader-- 1.0.0.9
Core-- 1.0.0.25
Base-- 1.0.0.76
1bird2 I would update your support ticket with a screen shot of the GS GUI.
Looks like the Program Version hasn't been updated on your HT502 to 1.0.1.21, rest of them firmware is part of version 1.0.1.21. Would recommend to open a support ticket to work with them to get it upgraded to 1.0.1.21.Quote:
Originally Posted by 1bird2
I am now good. After moving ATA to outside the router, making it available in the public IP space. Voipo tech support logged in and resolved the issue. Looks like I had a very old firmware version.
ATA is at the right version now and is registered as of earlier today. I am satisfied with the service as I am sure this was definitely a one-off problem they saw. I have since moved my configuration back to the way it was, i.e. ATA behind my router and all is good.
I look forward to trying out the new features as the rest of you have been reporting on. Even though my line was inactive for much of the weekend, the support team worked through this issue and got me back up and running. I did not miss any calls as the failover feature worked as advertised.
I am most impressed with the diligence and follow up the Voipo team provided, as I am sure they were scratching their heads on this one -- I hope this problem helped their overall product, in that, they can think about this type of issue in the future and help others avoid it.
Very impressed in Las Vegas -- good work Voipo support team!!
-bird
My problem persists. I believe the firmware update went south. I have put the ATA directly behind the cable modem. I can browse and ping the firmware, config, and registration servers from my computer (going through the ATA) but for some unknown reason the ATA wont communicate with them to conduct its business. It's a quizzer. As a result, I've asked that a replacement be sent out. I was hoping for a quicker solution. Good thing there is the failsafe feature.
Just an update. Got it all straightened out with a replacement ATA. Thanks Guys!