Hardware Update

**dswartz** · 10-17-2008 03:09 PM

By 'not fixable', I assume it only does the *23 3-way calling. Bummer...

**NY Tel Guy** · 10-17-2008 03:36 PM

Originally Posted by dswartz

By 'not fixable', I assume it only does the *23 3-way calling. Bummer...

I sent you a PM.

**usa2k** · 10-19-2008 03:29 PM

So you must be getting enough sign-ups that you don't need to actually beta the 502 devices? Note the comment about Viatalk having NAT issues per this DSLR comment:

http://www.dslreports.com/forum/r21292925-

And then there was the issue I noted below also from DSLR, but a different provider ...

**VOIPoTim** · 10-19-2008 03:56 PM

Originally Posted by usa2k

So you must be getting enough sign-ups that you don't need to actually beta the 502 devices? Note the comment about Viatalk having NAT issues per this DSLR comment:

http://www.dslreports.com/forum/r21292925-

And then there was the issue I noted below also from DSLR, but a different provider ...

Yeah we're not seeing issues with it so far. VT had the NAT issues with the PAP2 (which we didn't with 286) so it's likely just their system.

Right now the ratio of new customer signs to BETA is at least 5-1. We're already ahead of the numbers from when we launched VT.

**digger16309** · 10-20-2008 06:18 PM

Originally Posted by scott2020

If I plan on putting the 502 behind an existing router/firewall, can I just connect the WAN side of the 502 to the existing firewall? That would put the 502 WAN port on my existing LAN and obtain an IP address on the WAN side from my LAN DHCP server. Then, just leave the 502's LAN side disconnected? I don't plan to use the 502 as my primary gateway/router. If you then turn on the WAN HTTP access (which in this case would actually be my LAN) then you can get to it to administer or whatever. I would think the 502's WAN side would get the IP, gateway, DNS, etc information and know how to get out to the Internet and things would be OK.
Scott

That is exactly how I hooked mine up. I had to do reboots of my components in a certain order, but it all came alive and seems to be working well.

**GTOJim** · 10-20-2008 07:41 PM

Received a GS-502 this afternoon, so far working great behind my router.

**zevin** · 10-20-2008 10:11 PM

If asking the users to place the GS-205 between the modem and router would be asking them to possibly make changes for PPPoE. IMO that would be a support nightmare.

**burris** · 10-21-2008 04:29 AM

Originally Posted by zevin

If asking the users to place the GS-205 between the modem and router would be asking them to possibly make changes for PPPoE. IMO that would be a support nightmare.

At some point in the setup, if you use PPPoE, you still have to engage it. Why is this more difficult?

At the moment, I have my DSL modem bridged and my router does the PPPoE.

I will shortly try to set up the 502 as a router in addition to the VOIP functions (I bought 2 lines) and my present router only as an access point for my lan.
Since my present setup is working flawlessly, I am hesitant to mess it up.

**voxabox** · 10-21-2008 05:04 AM

guys,
what's your HT-502 firmware version?
my HT502 shows: Program-- 1.0.1.8 Bootloader-- 1.0.0.9 Core-- 1.0.0.23 Base-- 1.0.0.66
according to GS site, the latest is 1.0.1.15 - release notes

**burris** · 10-21-2008 05:26 AM

Originally Posted by voxabox

guys,
what's your HT-502 firmware version?
my HT502 shows: Program-- 1.0.1.8 Bootloader-- 1.0.0.9 Core-- 1.0.0.23 Base-- 1.0.0.66
according to GS site, the latest is 1.0.1.15 - release notes

When I first got the 286, I also noticed the firmware was out of date. At that time, Norm and I tried upgrading it and found a bunch of problems happening.
I would maybe wait for VOIPo to push any acceptable upgrades via the MAC from their servers. If you are provisioned, I believe they can take care of it.