Magic Jack Plus and AT&T Uverse Motorola NVG510

[nevadaneal]

Has anyone been able to find a solution for reliable connection for this router? Have setup port forwarding, pass through, set packet filter on. There is no DMZ setting. Getting error 23 intermittently, will work ok sometimes for a week and sometimes will get error twice in one day. Thanks.

[troyamiller]

Has anyone been able to find a solution for reliable connection for this router? Have setup port forwarding, pass through, set packet filter on. There is no DMZ setting. Getting error 23 intermittently, will work ok sometimes for a week and sometimes will get error twice in one day. Thanks.

EXACTLY the same issue here. Hadn't really dug into it until this morning - and likewise, hadn't considered putting the MJ+ MAC in the DMZ - found a thread on that earlier this morning. However, as you mention, there is no specifically labeled DMZ on this unit - and I'm not sure WHAT to try...

...would sure love to hear if someone has found an answer. (I cannot stand this modem - PPTP VPN connections don't work thru it... DNS probs... and here, no formal DMZ to deal with this. AT&T FAIL.)

[nevadaneal]

Am still having same issues, if you ever do find a solution, please post. Running out of options............
Thanks

[admin]

See if this helps
http://broadband.custhelp.com/app/answe ... a_id/21989

[nevadaneal]

See if this helps
http://broadband.custhelp.com/app/answe ... a_id/21989

Thanks for the link, but thats the options I have tried to no avail. Setting up in fixed ip pass through gives me error 3 instead of 23.

[laserjobs]

Try this:

1) Get the physical MAC address of your MagicJack Plus or computer ethernet adapter if you are using the magicjack through your computer.

2) Type http://192.168.1.254 in your internet browser.
- Click on "Firewall" at the top, then click on "IP Passthrough"
- Enter the Access Code for your NVG510. It is printed on a yellow sticker on the side of your NVG510
- Select "Passthrough"
- Leave Default Server Internal Access blank
- Select "DHCPS-fixed"
- Enter your MAC address from step 1
- Hit "Save"
- Hit "restart" and your modem will reboot

Reboot the magicjack Plus or your computer

[nevadaneal]

Try this:

1) Get the physical MAC address of your MagicJack Plus or computer ethernet adapter if you are using the magicjack through your computer.

2) Type http://192.168.1.254 in your internet browser.
- Click on "Firewall" at the top, then click on "IP Passthrough"
- Enter the Access Code for your NVG510. It is printed on a yellow sticker on the side of your NVG510
- Select "Passthrough"
- Leave Default Server Internal Access blank
- Select "DHCPS-fixed"
- Enter your MAC address from step 1
- Hit "Save"
- Hit "restart" and your modem will reboot

Reboot the magicjack Plus or your computer

That is what gives me an error 3, it only works without error 23 ( for a while-1 to 7 days) when in manual.

[troyamiller]

Try this:

1) Get the physical MAC address of your MagicJack Plus or computer ethernet adapter if you are using the magicjack through your computer.

2) Type http://192.168.1.254 in your internet browser.
- Click on "Firewall" at the top, then click on "IP Passthrough"
- Enter the Access Code for your NVG510. It is printed on a yellow sticker on the side of your NVG510
- Select "Passthrough"
- Leave Default Server Internal Access blank
- Select "DHCPS-fixed"
- Enter your MAC address from step 1
- Hit "Save"
- Hit "restart" and your modem will reboot

Reboot the magicjack Plus or your computer

That is what gives me an error 3, it only works without error 23 ( for a while-1 to 7 days) when in manual.

Same for me (error 3 - and no blinking 'line' light on the MJ+), but laserjobs may be on the right track! Here's what I just did...

1) Plugged my MJ+ into the computer.
2) Went to my.magicjack.com and logged into my account.
3) Went to the 'subscriptions' tab and clicked on the "magicjack plus static network configuration" button.
4) There, I UNchecked "use dhcp" and gave my MJ+ a static IP on my home network - specifically, an address that was outside the dhcp range that my router was using. I then entered the subnet mask and gateway ip (the ip of your router), left the 'broadcast ip' blank, then entered Google dns for the dns servers (8.8.8.8 and 8.8.4.4) (because this crummy nvg510 has dns issues). Then I saved that info.
5) Logged into my router, went to Firewall, the IP Passthrough. I set the 'allocation mode' to 'default server', then entered the static ip that I had assigned the MJ+ in the 'default server internal address' field. I then saved that, and restarted the router.
6) Once the router was back up, plugged the MJ+ back into AC power and the router - it came up... lights on the MJ+ are now RIGHT... successfully calling in and out. Working.

Don't know if this is the answer or not... mine (like yours) was sporadic - sometimes (previous) mine would be fine for a week; other times it wouldn't last an hour. I guess we'll see...!...

(and on a parallel note, I REEEAAALLY hate this router. I am actually/oddly pretty pleased with AT&T Uverse internet service - but this NVG510 is horrible.)

[troyamiller]

...but NO. Connection stayed up for about 2-3 hours, then went back to "error 23". So, here's what I've tried since (condensed version).

1) Set the MJ+ back to using dhcp (plugged into the computer, via my.magicjack.com).
2) Logged into my NVG510, and went to Firewall, IP Passthru and set the allocation mode to 'off'.
3) Went to Firewall, NAT/Gaming, and clicked the Custom Services button.
4) I created two services... named them "MJ 5060" and "MJ 5070" respectively. On the first, I set the global port range to 5060-5060 and the base host port to 5060, and the protocol to 'both'. Did the same thing with the second one, using port 5070.
5) I then restarted the router, and once up, plugged the MJ+ back in.
6) Logged back into the router, and went to Device, Device List. I had previously (some time ago) used this little utility: http://zaxa.ca/Downloads/DistMagicJackGetMAC.exe
to get the MAC address of my MJ+ and had noted that down. I looked on the 'device list' here in the router for that MAC address - so I could find the IP address that the router had assigned the MJ+. I made note of that.
7) I went to Firewall, NAT/Gaming. From there, I selected from the dropdown list the new service that I'd added... MJ 5060... and for 'needed by device', I selected the IP address of my MJ+ - and clicked 'add'. I then did the same thing for the new MJ 5070 service.
I then restarted everything (just for good measure), and so far, it's still up... (over an hour now)...

[bitstopjoe]

And yet it is so easy a child can do it I mean they say so in the Infomercial, so it HAS to be true, right?
Sure the child of EINSTEIN!!!
That is a LOT of hoops you had to jump through to get it to work.. Glad I never got the Plus and just have my soon to be 4 + yr old Orig. MJ.( which has been in my closet since March of 2011 and replaced with an OBi100. Which is connected to my router and worked right away and I was making calls in 3 min.)
I guess the Plus is just as picky with routers as the Orig was with PC's and USB ports..

[troyamiller]

I really don't think the MJ+ is the problem here... I really think that the issue is this crummy NVG510. It has issues... DNS doesn't work correctly in it (so you have to assign Google DNS to your individual TCP connections to get consistent connectvity), PPTP VPN doesn't work... heaven knows what else. AT&T and/or Motorola have promised firmware updates for this thing for months - and nothin'. I do think the prob is the router tho...

[nevadaneal]

...but NO. Connection stayed up for about 2-3 hours, then went back to "error 23". So, here's what I've tried since (condensed version).

1) Set the MJ+ back to using dhcp (plugged into the computer, via my.magicjack.com).
2) Logged into my NVG510, and went to Firewall, IP Passthru and set the allocation mode to 'off'.
3) Went to Firewall, NAT/Gaming, and clicked the Custom Services button.
4) I created two services... named them "MJ 5060" and "MJ 5070" respectively. On the first, I set the global port range to 5060-5060 and the base host port to 5060, and the protocol to 'both'. Did the same thing with the second one, using port 5070.
5) I then restarted the router, and once up, plugged the MJ+ back in.
6) Logged back into the router, and went to Device, Device List. I had previously (some time ago) used this little utility: http://zaxa.ca/Downloads/DistMagicJackGetMAC.exe
to get the MAC address of my MJ+ and had noted that down. I looked on the 'device list' here in the router for that MAC address - so I could find the IP address that the router had assigned the MJ+. I made note of that.
7) I went to Firewall, NAT/Gaming. From there, I selected from the dropdown list the new service that I'd added... MJ 5060... and for 'needed by device', I selected the IP address of my MJ+ - and clicked 'add'. I then did the same thing for the new MJ 5070 service.
I then restarted everything (just for good measure), and so far, it's still up... (over an hour now)...

Thanks, please post results and I will try it if it works out for you.

[bitstopjoe]

Good point but LOTS of people have different routers so there are bound to be MANY problems. Thankfully this forum is here to help those who are not so lucky to have it Plug and Play....
Thankfully you, as well as a few of us on here, know how to get into things when they dont work as advertised... PLUS I look at it as a great learing experience when you have to troubleshoot that way...

[cell14]

LOTS of people have different routers so there are bound to be MANY problems

ATT Uv verse hardware seems to be a real *bitch with many VOIP providers.
I ( and a number of other people ) went through a lot of hassle with Localphone ( you can check the Obi forum) , Anveo and others.

[troyamiller]

...and I'm back to getting 'error 23'. FRUSTRATED! Okay, until now, I've drug my feet at bridging this awful NVG510 (because I shouldn't HAVE to) - but at this point, just because of the other issues - er, FEATURES - it has, I'm really thinking that the it is the culprit. Inasmuch, I'm going to tackle that tonight when I get home (I'm at work right now).

I'll be bridging the NVG510 to an old wireless g Belkin router that I've had sitting around that I used to use pre-AT&T. It was cheap and it worked absolutely fine for me then... we'll see what happens, and I'll post what I find...

[troyamiller]

Okay, so tonight, I did a factory reset on my NVG510 (under Diagnostics, Resets, Reset Device). I also did a factory reset on my old wireless g Belkin that I've had for quite a few years.

After that, set the NVG510 to bridge (manually) by following the instructions on Ron Berman's blog, item #6, here: http://www.ron-berman.com/2011/11/24/mo ... rse-users/ . I did this with a network cable connected directly to the NVG510.

I subsequently unplugged from there, and plugged into the old Belkin. I continued his instructions for that.

After that, I cabled from a LAN port on the NVG510 into the WAN port on the Belkin. I restarted everything, in order, and...

...it's working. I pluged my MJ+ into the Belkin box about 3 hours ago... still up, coming and going. I'll continue to report on this, but at least at this point, it's quite promising... (and would confirm that the issue is not with the MJ+, but with this crummy NVG510...)... we'll see.

[nevadaneal]

Okay, so tonight, I did a factory reset on my NVG510 (under Diagnostics, Resets, Reset Device). I also did a factory reset on my old wireless g Belkin that I've had for quite a few years.

After that, set the NVG510 to bridge (manually) by following the instructions on Ron Berman's blog, item #6, here: http://www.ron-berman.com/2011/11/24/mo ... rse-users/ . I did this with a network cable connected directly to the NVG510.

I subsequently unplugged from there, and plugged into the old Belkin. I continued his instructions for that.

After that, I cabled from a LAN port on the NVG510 into the WAN port on the Belkin. I restarted everything, in order, and...

...it's working. I pluged my MJ+ into the Belkin box about 3 hours ago... still up, coming and going. I'll continue to report on this, but at least at this point, it's quite promising... (and would confirm that the issue is not with the MJ+, but with this crummy NVG510...)... we'll see.

Thanks for update!
Please do keep us updated,as the only other router I have is the old 2-wire from att. Not sure if this would work or not. If your last "fix" works, then I may have to buy another router to "bridge".

[troyamiller]

About 14 hours still up and running right now...! This is looking encouraging...!...

Nevadaneal, if it's the 2wire gateway that AT&T supplied (with the modem built in), I don't think that'll work - there's no WAN port on that, so there wouldn't be a good way to separate the 'outside' from the 'inside'. However, you could get an inexpensive one from somewhere like TigerDirect.com for $30 or so.

[nevadaneal]

troyamiller, That's good so far, altho mine has worked without error for as much as a week. If yours is still up and running for a week or so I will go for it. Agree on the 2wire not an option. Tiger or New Egg has good deals, any particular brand to recommend?
Hopefully you have found the solution, looking forward to an update.
Thanks

[troyamiller]

So far, so good... 9p tonight will be 48 hours UP... looking good! Nevadaneal, I don't think mine ever made it a week - I was usually good for a day or two at best - so if I make it to tomorrow, I think I'll consider it 'solved' for me...!

As far as a router to recommend... I've used a ton of 'em. I own a small computer shop. I'm a programmer by trade, and while I don't do much hands on installation work myself anymore, I still play with stuff pretty regularly. For business installs, we typically only use Cisco. But for residential installs, we use whatever looks the best price-wise (within reason, of course). Of all of those that I've used, I'd have to say that the Belkin's have been extremely consistent for me. They're inexpensive, and I don't think we've ever even had one go bad. The user interface is laid out well... not cryptic... and they just seem to work. As I'd mentioned previously, I'm using an older Belkin (because I already had it), and it's working just fine.

[troyamiller]

...still UP! Tonight will be 3 straight days - and I think that this is THE longest mine has ever run without having to be reset...!

[troyamiller]

...and in less than an hour here, my MJ+ has been up without reset for 8 days. I've never had it run this long. I'm pretty certain at this point that bridging the NVG510 to another router (in my case, an old Belkin) has solved this issue for me.