Incoming calls drop after 30 seconds - Pending ACK

[pshiffe1]

Outgoing calls work fine. Incoming calls only stay up 30 seconds while the status displays "Pending ACK" with a timer that counts up to 30 seconds and drops the call. The conversation can continue successfully up until the 30 second drop. Any ideas?

[az2008]

Outgoing calls work fine. Incoming calls only stay up 30 seconds while the status displays "Pending ACK" with a timer that counts up to 30 seconds and drops the call. The conversation can continue successfully up until the 30 second drop. Any ideas?

This seems to be a problem specific to Linksys routers. Eliminate the router if you can just to test. (Be aware this can expose you to hacks from the extranet if you don't run a software firewall).

The solution may be to open UDP ports 5060-5070 and UDP ports 10000-20000.

You shouldn't have to open any ports. And, 10,000 ports is a lot of ports to open. But, that may cause the Linksys firmware not to be confused.

Some have fixed it by flashing their routers with the latest Linksys firmware (even if it's the same version.). Others have flashed to the free, open source Tomato or DD-WRT firmwares. After that they didn't have to expose all those ports to the extranet.

Mark

[pshiffe1]

You were correct. I took the router out of the path and it works fine. Those ports are VOIP ports. Didn't realize that the router has those blocked. Thanks for the hot tip

[az2008]

You were correct. I took the router out of the path and it works fine. Those ports are VOIP ports. Didn't realize that the router has those blocked. Thanks for the hot tip

MJ doesn't require those ports to be open. The softphone initiates all connections to the MJ servers. It's something about Linksys's firmware that causes it to get confused.

You might try upgrading the firmware to whatever the latest is on the Linksys web site. Even if it's the same version (maybe you have a bad flash). Otherwise, flash it with the freeware Tomato or DD-WRT firmwares.

Or, if you're ok having all those ports open, do nothing.

Mark

[pshiffe1]

Updated firmware, opened ports, talked to MJ and LinkSys tech support. No luck this time. Some kind of ACK is not getting back to the phone. Works fine if I take the router out of the path. If I have time I will do a packet trace and see what IP packet is being blocked. Any suggestions are welcome.

[az2008]

If I have time I will do a packet trace and see what IP packet is being blocked.

I'm not sure you'll get much from that exercise. Personally, I'd be interested in it because most people take the understandably easy way out by flashing their router to Tomato or DD-WRT. It would be interesting to see what's actually going on. If you run Wireshark and trust me with what may reveal personal info, I'd like to see it.

But, it sounds like it's a problem with Linksys firmware. The easy way out is to flash it with Tomato or DD-WRT. Which model do you have?

Mark

[az2008]

Updated firmware, opened ports,

BTW: The recommendation to open ports may be dumb. The MJ softphone opens ports to MJ servers at the ports I mentioned. The MJ servers don't open ports on your computer. So, forwarding those ports on your router doesn't make much sense.

Something about Linksys's firmware gets confused. One person reported that upgrading to the latest Linksys firmware fixed the problem. A few people reported that flashing to Tomato or DD-WRT fixed it. The problem is that recent Linksys routers (except the WRT54GL) makes it difficult to flash to alternative firmwares. Recent 54G(GS) models require DD-WRT which is a bit more difficult.

Mark

[pshiffe1]

Unfortunately I have a WRT610N and there is no DD-WRT for it yet (if ever). Tomato I haven't heard of. I'll mess with it some more tomorrow.

[az2008]

Unfortunately I have a WRT610N and there is no DD-WRT for it yet (if ever). Tomato I haven't heard of. I'll mess with it some more tomorrow.

My recommendation is a WRT54GL. Flash it to Tomato if you want QoS. But, it should work without it. (It worked fine for me without flashing.). I believe eventually the 610N will be supported by DD-WRT. I'm not a big fan of DD-WRT. But, it supports more routers.

Mark

[side4]

Unfortunately I have a WRT610N and there is no DD-WRT for it yet (if ever). Tomato I haven't heard of. I'll mess with it some more tomorrow.

or you can try and downgrade your routers firmware as I had issues where my linksys router would crash on streaming video downgraded the firmware problem solved!

[az2008]

Unfortunately I have a WRT610N and there is no DD-WRT for it yet (if ever). Tomato I haven't heard of. I'll mess with it some more tomorrow.

or you can try and downgrade your routers firmware as I had issues where my linksys router would crash on streaming video downgraded the firmware problem solved!

Someone else said they fixed this 30-second problem (or the problem with indefinite ringing when an inbound call is answered by voice mail, which seems to be due to the same Linksys firmware problem) by upgrading to the latest firmware on Linksys. I suggested pshiffe1 do it (even if it's the same version just to eliminate the possibility of a bad burn from the factory). He indicated he did when he said that upgrading the firmware didn't fix it.

If that's the case, then that solution is dependent upon the model of the Linksys router. I think the other person had a wrt54GS.

Mark

[tDogEast]

Hello,

After you restart the MJ application, run an application like TCPView or do a netstat an. TCPView (sysinternals) makes this easier to see. The Acknowledge that MJ is waiting for is on a port that is reassigned every time the MJ applicaiton is restarted, so this method has to be followed after every restart of the machine or MJ.

Run TCPView and look at the open ports that are associated with the MJ applicaiton. There will be one UDP port that is duplicated for both the IP address of the machine MJ is running on and for the loopback adapter (127.0.0.1). This port is typically in the 4X,XXX to 6X,XXX range.

Once you find this port, go to the "Applications and Gaming"/Single Port forwarding screen of your router. As and example my current UDP port for MJ is 52,597.

Make a new entry:

External Port: 52,597
Internal Port: 52,597
Protocol: UDP
To IP Address: The IP address of the PC that MJ is running on
Enabled: Checked

Remember, this port will have to be reset every time the machine or the MJ application is restarted. MJ and the MJ servers negotiate a new port every time the application is started.

This will work!

[az2008]

External Port: 52,597
Internal Port: 52,597

I've never seen what you describe. Are you saying this is specific to Linksys routers with the firmware problem?

For routers without the Linksys firmware problem, MJ opens one connection:

- At startup the MJ proxy server's port 5070. Your computer's port can be in the range of 20000 to 50000.
- When a call is placed or received, the MJ's vms server's port in the range of 10000 to 20000. Your computer's port range can be in the range of 20000 to 50000.

I've never seen what you describe where it opens a destination port in the range of 50000, or that the source (local) port is the exact same port.

Is this what's broken with Linksys's firmware?

Mark

[tDogEast]

Mark,

I can't say for certain whether this is caused by the router or by Vista. Running TCPView on my machine yields the following. All listening ports are UDP, there are no active TCP ports listening.

Process

magicJack.exe:3872 UDP 10.1.1.50:62427
magicJack.exe:3872 UDP 127.0.0.1:62427
magicJack.exe:3872 UDP 127.0.0.1:63947
magicJack.exe:3872 UDP 127.0.0.1:63948
magicJack.exe:3872 UDP 0.0.0.0:64005
magicJack.exe:3872 UDP 127.0.0.1:64034

This is when MJ is in an idle state. When MJ first starts up it opens a TCP connection to the MJ server on TCP port 5060 (or 5070 I don't recall) and passes traffic back and forth. At the end of the negotiation, the TCP port is closed and the result is that it negotiates UDP port 62427. This changes every time MJ is restarted (as I mentioned in my previous post). The application continues to listen on this port.

By running Wireshark and also turning on logging on my router (Linksys WRT 610N), I see that when a call is received, the SIP session is initiated normally. The remote server sends a connection acknowledgement to my system on port 62427. This message is resent 3 times in 33 seconds and is blocked every time by the router, while SIP sessions (in and out) continue normally. When my machine does not acknowledge the remote server ACK request (because my router blocks it) the remote server terminates the session after 33 seconds.

In this case, if I manually port forward UDP port 62427 to my MJ pc (10.1.1.150) then everything works fine.

Toby

[az2008]

This is when MJ is in an idle state. When MJ first starts up it opens a TCP connection to the MJ server on TCP port 5060 (or 5070 I don't recall) and passes traffic back and forth. At the end of the negotiation, the TCP port is closed and the result is that it negotiates UDP port 62427. This changes every time MJ is restarted (as I mentioned in my previous post). The application continues to listen on this port.

TCPviewer may be useful, but I don't believe it's the ideal way to look at this. It doesn't really show the destination port. Just the destination as the magicjack.exe process sees it, which is actually a source port on your firewall.

For example, you say you don't see the UDP (SIP) port 5070 connection. I don't see it either. I see connections to port 50623. However, if I look at it using Wireshark or Tomato's QoS->Charts, 50623 is a source port on my firewall, connected to port 5070 on the destination MagicJack "proxy1" server.

Likewise, I see a UDP connection in TCPviewer to destination port 49154. But, in WireShark (or Tomato's QoS->Charts), 49154 is a source port connecting to MagicJack's "vms1" (RTP) server on port 26244.

So, my point is, using TCPviewer doesn't really show you the destination ports. It's just showing you the software port that the process is using, and the port it connects to on your router.

Maybe for the Linksys firmware problem that's important. But, it should be clearly stated that the ports being referenced aren't MJ's destination ports (which is how most people think of port forwarding, and opening ports to allow external processes to open them.).

Mark

[tDogEast]

Mark,

I am sure you are correct in your assertions, but with the software load on the linksys router, I don't know how to view the port mappings from the router's point of view.

All I know is that mapping the port as I described from the router to the MJ PC cures the problem. Another thing that I do know is that the MJ server is sending an acknowledge request to my router IP address on the WAN port using destination port UDP 62427 in this case. Manually forwarding this port (and this port only - I have to forward no other ports) fixes the ACK problem.

Toby

[az2008]

I am sure you are correct in your assertions, but with the software load on the linksys router, I don't know how to view the port mappings from the router's point of view.

Toby, Sorry. I didn't want to take away from your discovery. Now that I understand it better it sounds ingenious. It was only hard for me to understand because:

1. I don't have the Linksys firmware problem. I can't test it, or may not be seeing the same network activity you do (especially if some Linksys firmware gets confused, translating traffic incorrectly, routing it differently, or whatever).

2. In the context of how people usually speak of opening ports, and port forwarding, it was confusing to me (and I was concerned it might confuse others about what's normally *not* required for opening ports). But, it sounds like what you're really doing is forwarding internal router ports to internal software ports. Like, some Linksys firmware gets confused and needs internal ports to be treated like external ports.

I encourage you to work with the next person who posts with symptoms of a Linksys router and confirm that it works. If you don't read the forum religiously, I'll PM you when I see someone. I'd like to post your solution to the wiki as a solution. I'd just like to confirm that it works, and better depict what the solution is (that it's not really dealing with external traffic).

My concern was that people don't get confused about how the network activity works between the softphone and MJ servers (described in the background section here: http://en.wikibooks.org/wiki/MagicJack/ ... Proxy_Find).

MJ's network activity (LAN to WAN) works as described there. What you were describing was the local computer port to the router's LAN port, and that treating it as a LAN-to-WAN connection seems to fix whatever the problem is with some Linksys firmware.

So, it sounds like an ingenious solution. I'd like to see someone else affected by the Linksys firmware problem confirm it. And, I just wanted to avoid confusion (I was confused) about the network activity you described.

BTW: You can see the LAN to WAN port usage with Wireshark. For example, when starting MJ it makes a SIP connection to an MJ "proxy1" server on its port 5070. That connection will be identified as SIP (protocol) in the Wireshark capture. Click one of those lines, and you'll see some expandable sections in the middle pane. One says "Internet Protocol." Another says "User Datagram Protocol." The first one shows the WAN and LAN IP addresses. The second one shows the WAN and LAN ports.

Mark

[tDogEast]

Mark,

I assure you that my only goal is through my limited understanding was to get my MJ to work reliably. I am sure that my incompete explanation (which stems from my incomplete understanding) is the cause of your confusion.

Here is an example of the packet that is dropped by my router that causes the failure of the incoming connection to be acknowledged.

In this case the destination IP is my routers WAN port (98.200.60.166). Notice that the source port is UDP 5070 and the destination is UDP 51210. As you can see, my router is dropping this transmission.

Again, I can't say that I know what this means, but TCPView show that the MJ applicaiton is open and listening to UDP Port 51210 on both IP address 10.1.1.50 as well as on the loopback 127.0.0.1.

I simply made the connection between the session that was being dropped and the ports that MJ was listening to on my local PC. Given that, I made an entry into my routers IP Forwarding table to allow all communication on UDP port 51210 to be forwarded to my MJ PC at 10.1.1.50.

What happens in between is beyond my understanding at this point, and if you have the time and patience I would like to understand. If I could then maybe I could communicate to Cisco/Linksys what is going wrong in their latest router code!

It sounds like pshiffe1 has the exact same router and problem that I do. I would be interested in his/her input as to whether this works!

Thanks for you time and interest in this!

Toby



klogd: DROP IN=vlan2 OUT= MAC=00:21:29:c7:a5:39:00:13:5f:05:bf:05:08:00 SRC=67.88.84.6 DST=98.200.60.166 LEN=486 TOS=0x00 PREC=0x20 TTL=48 ID=0 DF PROTO=UDP SPT=5070 DPT=51210 LEN=466

[swierzycki]

Thanks Toby.
I've got the WRT610 and was having the same problem. I saw that the DD-WRT firmware for this router is still in the early stages of testing so I didn't want to mess with it.
I tryed you're suggestion of forwarding the port (55222 for me this time) and it worked.

Scott

[Lresidence]

You should contact livechat and tell them about your issue. You must be getting the message "Pending ACK" on your softphone when it drops. That is a routing issue on their end. Otherwise you need to try using different router

[GreyGhost]

tDogEast.

I have had the exact same problem. I have WRT610N on XP so the problem clearly seems to be the Linksys router. I did as you stated and the problem has disappeared. But clearly this identifies the problem and hopefully a longterm solution can be found. Waiting to see DD-WRT solution maybe.


GreyGhost

[tDogEast]

I am glad the fix worked for you. I too will probably try the DD-WRT code when it is through testing. For now, I have gotten my MJ to run on my Windows Home Server, which I leave on all of the time. Since it is rarely rebooted, I don't have to reconfigure the router very often.

Cheers!

Toby

[GreyGhost]

Had the same problem with the Pending ACK. I went ahead and flashed the WT610N with dd-wrt.v24-11762_mega-wrt610n.bin. Everything is working great. I even think the performance of the router is better but need to get tools that prove this. I did use the newest build of the dd-wrt because I found that this build had work for several people. When I feel brave I'll try the latest build.

[QuickShot]

I was having the same problem with the Pending ACK dropping incoming calls at 32 seconds. Just like everyone else, it turned out to be my Linksys router. Model WRT54GS, Version 1.1 (an old one). Upgrading to the latest Linksys firmware did not help the problem.

So I went to the dd-wrt.com website, downloaded their firmware file:

dd-wrt.v24_voip_generic.bin

It installed on the first try with no problem. Now there's no more disconnected calls and everything else on the router works, maybe even a little better than before. Many thanks to the people at dd-wrt.com!!

[tDogEast]

Linksys has finally posted new firmware for the WRT610N. This fixes the MagicJack Pending ACK problem for this router.

The new firmware lets you turn OFF (Disable) SIP ALG. The SIP application layer gateway was included in the original code, but since MJ implemented it's own methodology for dealing with SIP behind a NAT router, the ALG in the router did nothing but interfere.

Simply go to the Administration tab in the router's web interface under advance features and DISABLE SIP ALG.

After I did this, no more problems. I also no longer have to port forward 5060 and 5070. Everything is working as it should for now (only took Cisco 6 months to fix!).

[darthyahya]

ALL I DID AFTER HOURS OF DEALING WITH LIVE HELP AND FORUMS SEARCHES IS THIS:
WENT TO APPLICATIONS AND GAMING TAB OF MY LINKSYS WRT54GS AND INPUT
MAGICJACK [NAME OF APPLICATION]: START 62427 to END 62427 Both [TCP UDP] 192.168.1.11 [ADDRESS OF PC] AND CHECKED THE ENABLE BOX. SCROLLED DOWN AND CLICKED SAVED AND NO MORE DROPPED CALLS.

I COULD ALWAYS MAKE OUTGOING CALLS WITH MJ NOI PROBLEM BUT EVERY INCMING CALL FROM EVERY DIFFERENT PHONE I TRIED DROPPED THE CALL AFTER 30 SECONDS. I PLUGGED UP 5 DIFFERENT CORDED AND CORDLESS PHONES AND LOST EVEN MORE HAIR ON MY ALREADY BALDING HEAD. BELIEVE ME I TRIED EVERYTHING. BUT THIS WORKS FOR ME. AMEN

[edenkers]

Linksys has finally posted new firmware for the WRT610N. This fixes the MagicJack Pending ACK problem for this router.

The new firmware lets you turn OFF (Disable) SIP ALG. The SIP application layer gateway was included in the original code, but since MJ implemented it's own methodology for dealing with SIP behind a NAT router, the ALG in the router did nothing but interfere.

Simply go to the Administration tab in the router's web interface under advance features and DISABLE SIP ALG.

After I did this, no more problems. I also no longer have to port forward 5060 and 5070. Everything is working as it should for now (only took Cisco 6 months to fix!).

This solved the problem for me!

And I too did not have to do any port forwarding on 5060 or 5070.

Thanks tDogEast for this discovery and more importantly, posting the find on the forum

[Count_to_30]

...thanks guys, especially tDogEast and az2008...!

I have a Linksys WRT54GL and upgraded the firmware from ver. 4.30.12 to ver.4.30.13 with no change in being dropped after 30 seconds.

I then followed the directions in tDogEast's post and WHAM...! it worked like a charm.... port 51320 (I know it will change when I reboot or restart MagicJack)

I have 4 MagicJacks in the house running on 4 separate computers, so my work is cut-out for me. Maybe later I will flash my Linksys router with Tomato or WRT to make my life easier... but for now all of the universe is in balance...!

BTW... I tried twice to get help form MagicJack Chat without success. Actually after my fiasco today with Irish (you all know that they use fake names...doh!) I almost threw all 4 into the trash... only Comcast online help is worse and I have to pay to get abused by them....!

I am rambling, sorry.... thanks again guys, please know that your time on this board is much appreciated by us MJ Newbies...![/b]

[mabraham33]

I have the same problem with the WRT54GL router. I get dropped calls everytime. what can I do? I dont understand what to do for tdogs post? please explain it to me.

[Count_to_30]

: Count_to_30
To: mabraham33
Posted: Thu Dec 31, 2009 9:10 am
Subject: Re: magicjack
I will attempt to walk-you thru this... please do not be offended if I seem to over-simplify:

------------
PART ONE
------------
1.) In windows click the lower-left START button
2.) ...then click on the ...RUN item ( a pop-up box will pop-up)
3.) at the Open: space type "cmd" (without the quotes)
4.) hit OK (this brings up a DOS command-line terminal...)

---------------
PART TWO
---------------
1.) at the command prompt > type "netstat -an" (without the quotes)
2.) hit the return button
3.) a chart called "Active Connections" will appear

----------------------
PART THREE
----------------------
1.) the first column (reading left-to-right) is PROTO
2.) two types of protocols appear: TCP and UDP
3.) the second column (Local Address) reads: "ip_address:port_number"
4.) look for a line having these 3 values:
1... UDP (that's easy)
2... 127.0.0.1 (that's a little more difficult)
3... a port number between 40,000 and 65,000 (that's tough)
5.) EXAMPLE
UDP 127.0.0.1:58228 *.*

--------------------------
PART FOUR
--------------------------
1.) look for a matching line with the same "UDP, the same port_numeber,
but a different ip_address
UDP 192.168.1.7:58228 *.*
2.) the different ip_number is the ip address of your MagicJack unit

----------------------------
PART FIVE
----------------------------
I am assumng that you know how to forward ports in your Linksys Router:
1.) open the admin page of your Linksys router and allow the port_number
(per the example 58228, yours will be different) to be forwarded to the ip_address of the MagicJack unit (per the example 192.168.1.7, yours will be different).

EXAMPLE:

GIVE-IT-A-NAME 58228 58228 192.168.1.7 (Check-box)

---------------------------
PART SIX
---------------------------
Close down all the windows and enjoy...!

-------------------------
PART SEVEN
-------------------------
Remember EACH TIME YOU REBOOT YOUR COMPUTER. YOU NEED TO REPEAT THIS PROCESS.....! the computer re-assigns a different port_number to the MagicJack unit.


Please let me know how it works for you... I had some sound quality issues afterwards and suspect that its just noise on my ISP line coming into my house.... thanks!

[Count_to_30]

Okay.... follow-up....!

After success using tDogEast's discovery, I got brave and flashed my Linksys WRT54GL router with Tomato.... successfully. No dropped calls, no MJ problems... just bad audio quality that I don't believe to be an MJ issue.

However, I did not find the Tomato software as easy or flexible as the original Linksys so I switched back and continued to forward ports. My theory on routers is that they should be set and forgotten... Tomato is more fo the guy who wants to tinker with eerything... but that's just my opinion.

Finally, after hearing about the golden benefits of PF packet filtering software, I took an old Pentium 4 box and installed FreeBSD 7.0 with PF and set it in-line as a router... works great and is REALLY simple to maintain. Basically it blocks everything coming in (firewall) and allows anything out from my LAN with return privileges... if it didn't orginate from within my network it gets dropped...! MJ works great...!

My only issues now are Windowz related and I am smacking them down one-by-one with the help of the posts on this forum.

Also, for what it's worth, of my 4 MagicJacks, I am successfully using one on Linux with a VMware/WindowsXP guest operating system.

Thanks...!

[mabraham33]

Count_to_30
that worked perfect. have no more dropped calls. I just wont reboot my computer and will not have the change the info. again thanks for your help.

[mabraham33]

now just need to get the caller ID working. got a powered hub but when I call it disconnects me. what is the best one to buy or easiest way to get it? I hoop the magicjack into my cable box so it will goto all my phones. any ideas?

[mabraham33]

I have done the thing to do the port forwarding but I notice I do not reboot my laptop and the number changes all the time. anyone help with this?

[barrychap]

This was a relatively easy fix for me, thanks to this forum and tDogEast post of 9/8/2009. I downloaded the latest firmware (1.00.03.15) which lets you disable SIP ALG. I logged into the router, upgraded the firmware, disabled SIP ALG, hit the save button, and it works fine. I did not have to reset the router or re-enter my configuration.

[kharma25]

Thank you SOOOOO much Count_To_30!!!!!! I was about ready to pull my hair out with this MagicJack. Every incoming call was dropped soon after receiving it, and I was about to totally give up on MagicJack. After about 2 hours of research, I found this post and tried it. Now it works PERFECTLY!!! Thank you, thank you, thank you!!!

[kuhntech]

It seems strange to me that some people have issues with ports needing to be opened. I have the firewall on my dsl modem/router fully intact and I have yet to have a single issue with my mj and it's been 6 months. I have the windows software firewall disabled. Maybe that's part of it?? Who knows...phone for $20 a year is bound to have it's little quirks but I'm in it till the end!

[crackerjack]

It seems strange to me that some people have issues with ports needing to be opened. I have the firewall on my dsl modem/router fully intact and I have yet to have a single issue with my mj and it's been 6 months. I have the windows software firewall disabled. Maybe that's part of it?? Who knows...phone for $20 a year is bound to have it's little quirks but I'm in it till the end!

The need for opening ports is not related specifically to MJ, but to VOIP technology in general.
Opening ports or not is entirely dependent on the nature of the router and/or internal firewall deployed. Once you experience one-way or non-existent audio, port forwarding and/or use of a stun server is the only solution.

Try to see the world beyond your limited horizon and you will realize there are millions of potential pitfalls that may impact on the MJ device which is so dependent on the black art of USB I/O interaction as to be laughable.
I think it is a true credit to the tigerjet folks who originally made this pile of kludges work at all.

[Senator]

Hi, I just wanted to contribute my findings on getting the mj to work. Mine were working fine for months then all of a suden the sound would cut out when the mj was in active mode. I wasted many hours with their so called on line chat support agents. They have no idea how the mj really works and just go over the same scripts again and again expecting a different outcome. I am positive it was one of their "updates" that caused this to happen - "Lucky Us" right !! I finally turned to this forum for insite and answers and found the issue is with the ports the mj uses. Using Active Ports, I found the mj uses many different ramdom ports when starting up and different ports when in active mode. When it loads up, it randomly uses 4 ports in the 1000 range and 1 port anywhere between 49,000 to 65,000. Then when a call is placed or received, it switches 2 of the low number ports to a random high number port. Each time the mj is restarted, the low number ports are changed. Each time a call is placed or received, it opens random high number ports. It never uses the same ports !! Such an application is a nightmare for Network Admins because you have to turn off your firewall to get the mj to work consistantly and turning off the firewall for the network is not the answer. So I took one of my computers, wiped it and reinstalled XP and gave it a static IP and public DNS settings. Then I went into the router and put it in a DMZ zone and bypassed the firewall for that computer only. This seems to be the only way to get the mj to work consistantly. This is a terible design flaw if you ask me, but worth the trouble for all the money it saves in the long run. This may fix a lot of issues people are having with their mj....

[ydkjman]

I have recently upgraded to the newest firmwar on my WRT54GS router
v7.50.8 build 001

And if any one has this router and has gotten your Magic Jack to work with out loosing your internet will you please let me know how you did it. I have read that people are able to go in and Disable the SIP ALG but when I go in looking for those options in my router set up I just don't see those options.

[tomquinnta]

I have no issues with incoming calls. But for some of our outgoing calls we get the ACK pending message flashing on the MJ dashboard after the call is answered. After 5 seconds or so the call drops. Up to whenthe call drops both us (caller) and the receiver can not decipher audio.

Is this something that can be addressed on my end? The router / modem setup is adminstered by Cable MAS - Cozumel, Mexico. Our MJ number is registered as a US based number. The modem model is UBEE U10C022.

When the MJ works we have a seamless call. But we are hitting too many problem numbers.

Appreciate any help available on this issue. Otherwise we are left having to pay for international calling.

Thanks

Tom

[intor1]

tDogEast solution worked for Pending ACK [error 3] issue that disconnected outgoing MJ calls to cell phones on AT&T (iPhones actually).

New firmware FW_WRT610N_1.00.03.15_20090514 allowed the SIP ALG to be disabled, and, as promised, now talking long and strong to cells.

Thanks much tDogEast. An elegant solution compared to port forwarding with every reboot.

Linksys has finally posted new firmware for the WRT610N. This fixes the MagicJack Pending ACK problem for this router.

The new firmware lets you turn OFF (Disable) SIP ALG. The SIP application layer gateway was included in the original code, but since MJ implemented it's own methodology for dealing with SIP behind a NAT router, the ALG in the router did nothing but interfere.

Simply go to the Administration tab in the router's web interface under advance features and DISABLE SIP ALG.

After I did this, no more problems. I also no longer have to port forward 5060 and 5070. Everything is working as it should for now (only took Cisco 6 months to fix!).

[User919]

When I call my MJ phone using my cell phone I get the same message ("You have reached YMAX Communications test number. This call was successful."). And everyone who tries to call me, gets this same recorded message. My MJ phone doesn't even ring. I have no problem with outgoing calls; it's just incoming calls that don't come through.

Anyway, I have a Time Warner router/modem combo. The brand is "ubee". Any suggestions? KIS please.