By 'not fixable', I assume it only does the *23 3-way calling. Bummer...
Printable View
By 'not fixable', I assume it only does the *23 3-way calling. Bummer...
I sent you a PM.Quote:
Originally Posted by dswartz
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 ...
Quote:
Originally Posted by usa2k
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.
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.Quote:
Originally Posted by scott2020
Received a GS-502 this afternoon, so far working great behind my router.
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?Quote:
Originally Posted by zevin
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.
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.Quote:
Originally Posted by voxabox
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.
Burris, the point is that with DHCP, the ATA requires no special configuration by the VSP, whereas for PPPoE, it may very well need it, which means to have the ATA/router sitting in front of the customer's network will require VOIPO (or whoever) to have to know your PPPoE credentials. Aside from the support hassle, there is also the security aspect - VOIPO is my VSP, not my ISP...
Already submitted a request - ticket EHX-260881Quote:
Originally Posted by burris
FYI, from VoIPo Support Team:Quote:
Originally Posted by voxabox
Suggestion to VoIPo Support Team:Quote:
While we agree that upgrading to the latest firmware always sounds like a good idea, we've had some problems in times past with one problem being fixed while more problems arise. That said, this firmware is not going to be supported until we have the chance to thoroughly test it in our lab. We are working diligently to provide you the best service possible, so we will be testing this new firmware as time permits. When we have tested this firmware and feel comfortable with rolling it out to all of our customers, it will be automatically upgraded.
Regards,
VoIPo Support Team
support@voipo.com
http://support.voipo.com
To avoid unnecessary support tickets, perhaps there should be a list of VOIPo approved firmware versions; furthermore, the ATAs should be configured to perform periodic/automatic upgrade; otherwise, customers (I, for instance have the modem, router, ATAs on UPS) will need to be notified of new firmware availability to reboot their ATAs (to get the upgrade)
I'm well aware of SIP NOTIFY reboot/restart method
I got the 502 yesterday but I didn't get a chance to connect it yet.
From what I understand, on the 502 LAN side the end user should have access to make changes to PPPOE credentials and such. Is that correct? In that sense it is more like a store bought router that would need to be configured for PPPOE anyway. I don't think VOIPo wants to manage or even know about it's customers PPPOE credentials. There would be a lot of risk in that.
scott
the WAN/LAN is user configurableQuote:
Originally Posted by scott2020
login with password: 123
That's not so bad then, I guess. I still think ATAs have no business being routers, but that's just me I guess :)
I just see hassles from having to connect it to a pc configure PPPoE, reconnect to modem. Perhaps I am making to much out of this but I would recommend putting the 502 after a router more plug and play that way.
You are going to ask the users to rip apart their network to install the ATA. Feels like trouble to me.
I'm trying to understand what you wrote.Quote:
Originally Posted by dswartz
At the moment, with DSL, I have the DSL modem in a bridged mode..feeding my wireless router that performs the PPPoE that is set up in the router, not with the ISP.
When I hook up the 502, I will set up the router to do PPPoE. The 502 router DHCP can be NAT router(so it can go behind a firewall) or switched mode..I'm not keen on using IVR to set it up, and I think direct access will do the job..
I then hope to go into my existing router that will function as an access point.
What is it that you see differently with the 502?
With PPPoE, the client (your router) has to communicate with (and authenticate with) the ISP's server. Once that works, you have an IP address and can do stuff. If you put an ATA in front of router, then the ATA needs to do the PPPoE authentication with the ISP, since your original router is sitting behind it and can't do PPPoE. Not to mention having to deal with possible double-NAT issues from apps on my internal LAN.
You see what I am talking about... I can see "DSL Joe" under his desk unplugging things, using the wrong AC adapter, and trying to remember PPPoE login details like password. Who remembers the DSL password, I don't.Quote:
Originally Posted by dswartz
For the average "Joe" something that just plugs in and goes is best. Now if you say the 502 can do that, well I see problems with "Joe" knowing which port on the 502 he should use to plug into the router: wan or lan. Perhaps VOIPo should include an instruction sheet with the adapter or cover the other port with a sticker.
Yes you and I know how to go in and set up PPPoE on the 502. However "Joe" is going to get lost real fast. I was not talking about it being difficult for us. You have to consider on occasions the cable or DSL provider installs the modem, connection and even sets up the computers for the user. Granted custom installs is not as common, but still exists. That user has no idea what was done.Quote:
Originally Posted by burris
Now the user who's modem doesn't require another device to do authentication should have no problem placing the 502 between the modem and router.
Food for thought.
I agree, the ATA should be a guest device after the router. Too much to go wrong otherwise.
When I switched to DSL from cable a while back, I first set up the DSL modem to handle the PPPoE and fed it into the router. I did not have very good results..quirky everything..drop outs, etc.Quote:
Originally Posted by quattrohead
I then made mt DSL modem bridged and fed it to my wireless router that took care of the PPPoE. I simply connected from a router port to my ATA and haven't had a connectivity problem since.
I was waiting for Tim to ask me to do some experimenting with the 502, but all is working so well I am leery.
By the way, the 286 did not give me good results...even after trying every kind of hookup...having a firmware upgrade done on line by VOIPo..doing all kinds of tweaking, etc.
I will of course run the 502 through the paces in order to see what happens and maybe discover some tweaks or information that might be of help to Tim and others..
I connected the WAN side of the 502 to my internal network, so it is behind the firewall/router. I left the LAN side disconnected. The WAN side got an internal LAN ip with the firewall/router as the default gateway and all of the other IP settings. I plugged it in and it seems to work fine. I know several others have done this but I wanted to report it seems to be fine. I don't want to use the 502 as a router/firewall either, but some may. I think it will work great either way, but for the average Joe it might be a little more complex. Lots of variables to consider.
It is nice to be able to toggle between callers with call waiting though! I haven't tried 3-way calling yet though.
scott
The only complication (I think) is that managing the 502 through the web interface would require configuring it so that WAN-side access is allowed. Dunno if that's the default or not.
WAN access to it is disabled by default, but it can be enabled if needed with a ticket.Quote:
Originally Posted by dswartz
On mine it was already enabled, but I'm not sure if that was done before they shipped it to me. Basically I went with my web browser to the IP address the WAN side picked up from my internal DHCP server and it let me right in.
scott
Do you all mean WAN or LAN. The wan has to be enabled or it wouldn't accept an IP address from your DSL, Cable, or Router depending on if it's connected before or after the home router. The LAN side; which is it's router functions can be disabled if you are connecting after a home router and not using it to feed/route PC's or other devices.
On a similar side bar: Is the WAN side accessible to the web interface so that we can give the 502 a static IP address from our home network, or do we HAVE TO let it grab an IP address via DHCP? I run only static IP addresses on my home network and need to be able to see the 502 to a 192.168.x.x static IP address on the WAN side. Thx... Mike....
If you don't yet have it, here is the manual for it.Quote:
Originally Posted by christcorp
See if you can figure it out.;)
http://tinyurl.com/6n9nmq
Sorry if I was unclear. By 'enabled on the WAN', I meant the management interface.
On mine the way I received it from VOIPo, the WAN side had the HTTP management interface enabled. It is configurable to enable or disable from entering in touch tones per the quick setup guide. I guess that is why I could get to the management HTTP via the WAN interface, even though the WAN is connected to my LAN. Confusing huh!
Also, it looks like you can static IP the WAN port IP address. It has DHCP, PPPOE, or Static. You would just need to put in a static IP from your LAN on the WAN configuration of the 502 and it should work. I didn't need to make any other changes.
scott
Link doesn't work dude. But that's OK. It's probably similar to all other voip ata with built in routers. I plug it in, it grabs and IP address. I look at my regular router. It tells me the IP address it GAVE the voip adapter. I go to that IP address. It allows me into the configuration. I set up a static IP address on it. We probably don't have access to certain advanced features. Sound pretty typical to 99% of voip adapters in the world.Quote:
Originally Posted by burris
The only reason I asked was because the way some of the questions were being asked, it sounded like EVERYTHING was set up with DHCP and obtaining IP addresses automatically; that it was 100% plug and Pray and couldn't be changed. Sounds like a normal typical setup. later... mike....
You're actually able to login to the ATA to manage all the network settings yourself (static IPs, PPoE, etc). We don't provision that stuff.Quote:
Originally Posted by christcorp
By default it's all set to DHCP and a default 192.168.2.1 for it's lan port when used as a router.
Also can do port forwarding, dmz, etc...basic stuff, but it's there.
When you login though you can change that stuff.
What's the default password for this model?
Should be 123.Quote:
Originally Posted by Brian
Hi, Tim....Quote:
Originally Posted by VOIPoTim
123 does get me into the 502 static and basic screens, but when going to any other tabs, it keeps asking for a new password and nothing I have works.
Thanks....
burris
"123" is the "user" password to the HT-502Quote:
Originally Posted by burris
"user" login allows LAN administrations, "administrator" login, other ATA/SIP administrations (which is under controlled/provisioned by the ITSP - i.e., VOIPo)
Strangely enough, the first time a few days ago that I tried it, I did have access. Then it only did as I described above.Quote:
Originally Posted by voxabox
My need is to set up both my lines in the ATA..
I believe Tim said the 502's will be able to support 2 VOIPo lines, but not be provisioned for any other services. VOIPo can provision your 2nd line from their service, if you have one.Quote:
Originally Posted by burris
The password is: 123 for the first 2 tabs on the leftQuote:
Originally Posted by Brian
The 3 tabs to the right use password admin1
hope this helps.
Been there...done that, but I will try again before my next glass of wine..Quote:
Originally Posted by NY Tel Guy
Thanks....