I'm using a Linksys PAP2T-NA. I followed the screenshot configuration for the PAP2 posted in one of the threads to match exactly what they have. I'm using Buffalo WHR-G54S routers with Tomato v1.23 firmware around the house using WDS. The PAP2 is in one of my WDS routers. I'm able to make calls fine, but I'm unable to receive incoming calls unless I turn on port forwarding for UDP 5060, 5070, and 5071. According to my searches here, port forwarding is required for Linksys routers if they have Linksys firmware, it looks like this is true for my Buffalo router w/ Tomato, too...or am I just missing something? My "Register Expires" is already set to 180. I currently have 1 MJ account and am planning to get another one for a second line, but if port forwarding is required, then my 2nd line won't be able to receive incoming calls since I can only port forward these 3 ports onto 1 IP address.
Anyone know what else I need to check? Thanks!
Unable to receive calls if port forwarding is turned off
Moderators: Bill Smith, Pilot
Is your router being supplied with a public IP address or a private IP address? The only reason I ever acquiesce to forwarding ports inbound through a NAT router is if that NAT router is behind yet another NAT router, like in a hotel or office or apartment building or low cost ISP.
Compare your WHR's reported WAN address with the address that comes back from whatismyip.com. If they don't match, this is likely your problem. If they do match, we will have to ponder this some more.
Compare your WHR's reported WAN address with the address that comes back from whatismyip.com. If they don't match, this is likely your problem. If they do match, we will have to ponder this some more.
Re: Unable to receive calls if port forwarding is turned off
Incorrect. Some people with newer Linksys routers have had to disable their firewalls or forward external to internal ports to work around a bug in the firmware of those newer routers.AlpineMan wrote:According to my searches here, port forwarding is required for Linksys routers if they have Linksys firmware,
Mark
See the MagicJack Wiki (FAQ, How-To, history and more).
I don't know if it makes any difference, but I have an ABN Adapter (from nextalarm.com) which is a PAP2T-NA...no port forwarding there. I also have a SunRocket Gizmo ATA (Innomedia MTA6328-2Re) box used for net2phone...no forwarding there either, and both work 100% incoming/outgoing...these 2 attached via WDS as well (different room).
This is almost the same setup as mine: Tomato on main router then second router setup as WDS bridge(OpenWRT+Asterisk, actually) with PAP2(flash to SPA1001) hooked.
I have no problem receiving calls here, other than STUN, I also turn on "NAT Mapping Enable:" and "NAT Keep Alive Enable:"----suppose that's the way to keep the router ports open for PAP2 without port forwarding.
I have no problem receiving calls here, other than STUN, I also turn on "NAT Mapping Enable:" and "NAT Keep Alive Enable:"----suppose that's the way to keep the router ports open for PAP2 without port forwarding.
I have not applied the STUN and NAT stuff, but it looks like I'm able to receive incoming calls ever since I rebooted the PAP2T after applying the config screens from the PAP2T config thread, and port forwarding turned off in my main Buffalo Wifi router. I thought changes take effect and a reboot already occurs when you make changes...I dunno. If I get no rings again later, I'll apply the STUN and NAT suggestions...or should I do those now anyway?
BTW, I don't see a "NAT Mapping Enable:" and "NAT Keep Alive Enable:" entries in my PAP2T. I have Firmware Version: 5.1.6(LS)...nevermind...saw it in Line settings.
BTW, I don't see a "NAT Mapping Enable:" and "NAT Keep Alive Enable:" entries in my PAP2T. I have Firmware Version: 5.1.6(LS)...nevermind...saw it in Line settings.
In my case, without STUN, both incoming and outgoing calls still work fine, but the ATA would fail to register if the WAN IP changes, and I have to power cycle the unit----even reboot wouldn't help. Needless to say, STUN solves the issue.
It's safe to turn on "NAT Keep Alive", as thats exactly what official MJ dongle does, the "correct" period is 20 seconds instead of default 15, though.
It's safe to turn on "NAT Keep Alive", as thats exactly what official MJ dongle does, the "correct" period is 20 seconds instead of default 15, though.
20 seconds is less wear and tear on your internet connection, but it doesn't matter to MJ's servers. STUN is just between your client and the STUN server (they all interchangeable). The results of the STUN transaction are reported to the SIP server in the Register packet, but the SIP server is blind to how your client got that information.pagemen wrote:It's safe to turn on "NAT Keep Alive", as thats exactly what official MJ dongle does, the "correct" period is 20 seconds instead of default 15, though.
both 15 and 20 seconds would work, I just want to keep sync. with the MJ usb dongle, which sends keep alive msg. every 20 seconds.mberlant wrote:20 seconds is less wear and tear on your internet connection, but it doesn't matter to MJ's servers. STUN is just between your client and the STUN server (they all interchangeable). The results of the STUN transaction are reported to the SIP server in the Register packet, but the SIP server is blind to how your client got that information.pagemen wrote:It's safe to turn on "NAT Keep Alive", as thats exactly what official MJ dongle does, the "correct" period is 20 seconds instead of default 15, though.