David M 1103581 Posted April 5, 2009 at 08:26 AM Posted April 5, 2009 at 08:26 AM Hey Guys, I'm having major issues with receiving voice. I can transmit fine and can then receive voice for a few seconds until it drops out. I need to press PTT to receive voice again. I'm running: FSX + SP1 SetupFSCopilot17B2_4.exe SetupFSInn13B2_3.exe Router is a 5200G R4 Its connected using a ethernet cable so no wireless. I have forwarded UDP port 3290 to my computer. Still hasn't resolved the issue. I don't know what else I can try. I've searched extensively for a solution but haven't found anything. I've read that UDP port times out on some routers. Does anyone know how to disable this? Are there any other alternatives I can use besides FSFDT? Link to comment Share on other sites More sharing options...
Norman Blackburn Posted April 5, 2009 at 09:10 AM Posted April 5, 2009 at 09:10 AM Take a look at UDP timeouts on the squawkbox / VRC forums. Basically think of your voice transmissions as going through an open door. Once your voice transmission stops the door will start to close preventing incoming voice. Change the UDP timeout value and you "slow down the door" from closing. Norman Link to comment Share on other sites More sharing options...
Larry James 901346 Posted April 5, 2009 at 12:16 PM Posted April 5, 2009 at 12:16 PM Hey Guys, I'm having major issues with receiving voice. I can transmit fine and can then receive voice for a few seconds until it drops out. I need to press PTT to receive voice again. I'm running: FSX + SP1 SetupFSCopilot17B2_4.exe SetupFSInn13B2_3.exe Router is a 5200G R4 Its connected using a ethernet cable so no wireless. I have forwarded UDP port 3290 to my computer. Still hasn't resolved the issue. I don't know what else I can try. I've searched extensively for a solution but haven't found anything. I've read that UDP port times out on some routers. Does anyone know how to disable this? Are there any other alternatives I can use besides FSFDT? Which key have you selected for your PTT? Take in the FSInn Help forum at the resolutions for connection issues, namely the fs9tool.exe. -- L. James -- L. D. James [email protected] www.apollo3.com/~ljames sticky: Not a regular post, but a special thread/message stuck to the top with special meaning… containing important forum information. For FSInn/VATSIM issues, please test the FSInn Installation sticky and linked FAQ. It really works! Link to comment Share on other sites More sharing options...
Norman Blackburn Posted April 5, 2009 at 12:42 PM Posted April 5, 2009 at 12:42 PM Hi Larry, The OP stated his transmissions were fine so its fair to believe his PTT is setup correctly. Norman Link to comment Share on other sites More sharing options...
Larry James 901346 Posted April 5, 2009 at 12:53 PM Posted April 5, 2009 at 12:53 PM Hi Larry, The OP stated his transmissions were fine so its fair to believe his PTT is setup correctly. I've seen erratic behavior in voice operation based on some PTT configurations. Because there is erratic voice behavior in this instance, for my information, I find it useful (for me) to have this information, just for the record. I also see this as a connection issue. It appears that he looses connection to the voice servers and has to reconnect. I understand my method of investigation isn't the exact same as yours, but I believe by the time I have all the information and can test was I have, the results will probably become the same... the intended successful and consistent voice connection. I have other checks that might appear even more redundant to you, but again, for me, the information is important to have a full understanding of what is different from his environment than any I'm immediately familiar with, that will cause this (what I consider) un-normal circomestances with FSInn and VATSIM. -- L. James -- L. D. James [email protected] www.apollo3.com/~ljames sticky: Not a regular post, but a special thread/message stuck to the top with special meaning… containing important forum information. For FSInn/VATSIM issues, please test the FSInn Installation sticky and linked FAQ. It really works! Link to comment Share on other sites More sharing options...
Norman Blackburn Posted April 5, 2009 at 01:02 PM Posted April 5, 2009 at 01:02 PM Hi Larry, its fair to say we share the same wish for resolution however in the case above the user has clearly defined that voice is his only issue, alluding to what he already discovered; udp timeout is the issue. Both MSFS pilot clients will exhibit the same issue since the symptoms exactly match the causem The ideal solution is to read the router manual. If you don't have one then check your favourite search engine usung the terms router name + manual. Best regards, Norman Link to comment Share on other sites More sharing options...
Larry James 901346 Posted April 5, 2009 at 04:08 PM Posted April 5, 2009 at 04:08 PM Hi Larry, its fair to say we share the same wish for resolution however in the case above the user has clearly defined that voice is his only issue, alluding to what he already discovered; udp timeout is the issue. Both MSFS pilot clients will exhibit the same issue since the symptoms exactly match the causem The ideal solution is to read the router manual. If you don't have one then check your favourite search engine usung the terms router name + manual. Best regards, Hi, Norman. I have actually purchased a number of routers in an effort to run various test on differ routers to see how FSInn functions with them. I appreciate your suggestion that I do more reading. I do a lot of reading, but must admit that I don't read everything. I didn't ask the user what type of router he has so that I could go out and do research on his router. I might never have come to that direction. I probably would have asked him to byp[Mod - Happy Thoughts] the router after going a few steps in a direction that I understand that you wouldn't have done. My reading of the FSInn manual says that it has been tested to automatic function with most Routers without any problems or special configurations. This is how it has functioned with the four different routers that I have used. Again, I understand that a person can perform special configurations of their routers for other things before they start to use FSInn, so because it's not functioning by its default, the special configuration might be the problem. I have also seen people have problems, reset their router to factory default, then no longer have problems. Again, I appreciate that the route that you have chosen to do is to concentrate on the technology of the router... for the user to learn all the things that you know about the router. That might be the issue and the only issue. If I (knew) or thought that was the issue, and the only issue, I would probably have verified it to the user by asking him to byp[Mod - Happy Thoughts] the router and see if he still have problems (which over the years I might have done twice). If the router turned out to have been the culprit, my usual next step would be to learn how many computers would be affected by making a change (and who setup the router). I wouldn't want to risk telling what might be a 13 year old to change settings that might break the integrity of a home business network. I'm also not suggesting that the steps of my investigation be exclusive. I'll follow the thread and be glad for what I learn. I'll add everything I learn to my reservoir of knowledge and the FSInn FAQ's. But I have to admit that it's not easy for me to suspect the router as the culprit when it has been such a rare occurrence over the years... and restarting the router back to the way it came from the factory cured it in those rare occasions. -- L. James -- L. D. James [email protected] http://www.apollo3.com/~ljames sticky: Not a regular post, but a special thread/message stuck to the top with special meaning… containing important forum information. For FSInn/VATSIM issues, please test the FSInn Installation sticky and linked FAQ. It really works! Link to comment Share on other sites More sharing options...
Norman Blackburn Posted April 5, 2009 at 04:22 PM Posted April 5, 2009 at 04:22 PM Sorry Larry, I should have been more clear. This requires the user, rather than you or me, obtaining the router manual. Sometimes we need to teach a person how to fish. The OP actually stated their router type in the original post - a model where the router and modem are a single unit so removing this item most probably isn't an option. Tony, have you tried port triggering? http://portforward.com/help/porttriggering.htm has more information. Norman Link to comment Share on other sites More sharing options...
Lennart Vedin Posted April 5, 2009 at 09:34 PM Posted April 5, 2009 at 09:34 PM To receive VATSIM voice continues, it is requireed to open UDP port 3290. If you have router you typical need manual config the router. There are two general way to do this: 1. To open and forward port UDP 3290 to the IP-address of the computer with SB (or FSInn). Static IP address in computer is recommended. 2. To open port UDP 3290 trigged by TCP 6809 ( 'cause SB does continues send messages at TCP 6809, IP-address of the computer with SB are not required to know). Dynamic IP address in computer may be used. If you proper open port UDP 3290 by method 1 or 2, there should not be any timeout in router. While if you have not proper open port UDP 3290, then yes the router timeout close the port after you have sent by push PTT. A software firewall in your computer could possible block the port as well. If you send voice, the port should automatically be hold open by the router to receive voice for a while. That mean if you push the PTT button, you should be able to receive VATSIM voice for a while after the push (router open port timeout). For a PC software antivirus/firewall it should display that that receiving messages appear at UDP port 3290, and prompt if you allow traffic. But the antivirus/firewall may need to be configured to message and prompt to open ports. Run FS in Window-mode (not full screen), so that you see the firewall-message. / Lennart Vedin / Link to comment Share on other sites More sharing options...
Larry James 901346 Posted April 5, 2009 at 11:00 PM Posted April 5, 2009 at 11:00 PM Hi, Lennart. Your message makes a lot of sense and is very consistent with my expectation. After a verification of proper installation of FSInn, I'd suspect a firewall issue as in the past. A special configuration of the router has never been a necessity with FSInn (in all my experience). -- L. James -- L. D. James [email protected] www.apollo3.com/~ljames sticky: Not a regular post, but a special thread/message stuck to the top with special meaning… containing important forum information. For FSInn/VATSIM issues, please test the FSInn Installation sticky and linked FAQ. It really works! Link to comment Share on other sites More sharing options...
David M 1103581 Posted April 6, 2009 at 06:28 AM Author Posted April 6, 2009 at 06:28 AM Which key have you selected for your PTT? Right CTRL Link to comment Share on other sites More sharing options...
David M 1103581 Posted April 6, 2009 at 06:33 AM Author Posted April 6, 2009 at 06:33 AM Tony, have you tried port triggering? http://portforward.com/help/porttriggering.htm has more information. No I haven't. I need to do some research on the parameters on my router to enable the trigger. Link to comment Share on other sites More sharing options...
David M 1103581 Posted April 6, 2009 at 06:38 AM Author Posted April 6, 2009 at 06:38 AM To receive VATSIM voice continues, it is requireed to open UDP port 3290.1. To open and forward port UDP 3290 to the IP-address of the computer with SB (or FSInn). Static IP address in computer is recommended. ... Run FS in Window-mode (not full screen), so that you see the firewall-message. I have forwarded UDP 3290 successfully. I have tested with port scanners and it is indeed open. I have also disabled XP firewall to test. Made no difference. Link to comment Share on other sites More sharing options...
Norman Blackburn Posted April 6, 2009 at 07:53 AM Posted April 6, 2009 at 07:53 AM Port triggering? Norman Link to comment Share on other sites More sharing options...
Larry James 901346 Posted April 6, 2009 at 11:07 AM Posted April 6, 2009 at 11:07 AM To receive VATSIM voice continues, it is requireed to open UDP port 3290.1. To open and forward port UDP 3290 to the IP-address of the computer with SB (or FSInn). Static IP address in computer is recommended. ... Run FS in Window-mode (not full screen), so that you see the firewall-message. I have forwarded UDP 3290 successfully. I have tested with port scanners and it is indeed open. I have also disabled XP firewall to test. Made no difference. Hi, Tony. Windows firewall has never been a problem with FSInn. Are you running any third party firewall/antivirus programs? Did you run the fs9tool.exe utility? -- L. James -- L. D. James [email protected] www.apollo3.com/~ljames sticky: Not a regular post, but a special thread/message stuck to the top with special meaning… containing important forum information. For FSInn/VATSIM issues, please test the FSInn Installation sticky and linked FAQ. It really works! Link to comment Share on other sites More sharing options...
Norman Blackburn Posted April 6, 2009 at 11:12 AM Posted April 6, 2009 at 11:12 AM Hi Larry, Tony is not running FS9. Norman Link to comment Share on other sites More sharing options...
Recommended Posts