Jump to content

You're browsing the 2004-2023 VATSIM Forums archive. All content is preserved in a read-only fashion.
For the latest forum posts, please visit https://forum.vatsim.net.

Need to find something? Use the Google search below.

Euroscope sometimes does not output pilots on frequency.


Kai Black 1409513
 Share

Recommended Posts

Kai Black 1409513
Posted
Posted

I was controlling yesterday and I had number of pilots ask me if I received their transmissions. I had not, I reconnected and that solved the issue for the next half an hour but it happened again. This has never happened in the past. I have not updated my Euroscope, I double checked my hardware settings and also made sure the icons on frequency setup were green instead of red.

I truly have no idea what is wrong.

Link to comment
Share on other sites

Nestor Perez
Posted
Posted

Hi Kai!

 

Search for "voice timeout" or "port forwarding" around the XSquawkBox threads.

 

Same reason, same problem, same solution.

 

Cheers,

Me.

Link to comment
Share on other sites

Kai Black 1409513
Posted
Posted

Thanks for the quick response!

Do you know what port I need to increase the NAT timeout value for?

Link to comment
Share on other sites

Kai Black 1409513
Posted
Posted

Don't worry I have forwarded the correct port

Link to comment
Share on other sites

Martijn Rammeloo
Posted
Posted

And for future visitors to this thread: which port would that be? Or a link to the specific thread/post?

 

Martijn

Link to comment
Share on other sites

Nestor Perez
Posted
Posted

I'm sure other people could look for that in the forums, but anyway, here you go:

 

Normally, it is UDP Port 3290 that is required to be forwarded. Why do I say 'normally'? Well, because that's the theory; but in practice it wouldn't be the first time I'd see somebody on a different port for voice comms (generally 3291 or 3292).

 

In my case for example, the 'external' port I had to open for voice communications was UDP Port 12742. Weird, right? Well, from what I can understand, this happens because my ISP has a weird tunneling service from IPv4 to IPv6 (or the other way round; can't really remember). So this is the result: to the outside everything happens through port 12742, but from the inside, everything happens through port 3292.

 

In order to find out which port you need to forward 'for the outside', enter this webpage and change the domain for the one corresponding to whichever server you're connected to. Search for your callsign and after the (hidden) IP address, you'll see the port number which you use to communicate outside your LAN. This port is the one you should forward/map to port 3290 (3291, 3292) inside your LAN.

 

It looks more complicated than it really is.

 

If I am too bad explaining myself or you're too 'uninteligent' to understand it (it will probably be the first option, though), let me know down here and we'll see what we can do.

 

Cheerio,

Me.

Link to comment
Share on other sites

 Share