locked Re: Single/double click within callsigns window not working


HamApps Support (VK3AMA)
 

On 8/07/2021 9:53 am, BOB K5HX via groups.io wrote:
Also,  I attempted to configure the firewall to allow inbound and outbound UDP traffic on port 2237 but wasn't sure if that was correct. 

That is not correct.

While JTAlert will be listening to port 2237 for UDP traffic from WSJT-X, the UDP messages it sends back to WSJT-X will not be to port 2237, they will be to a port that is automatically assigned by Windows when the WSJT-X network interface code is run. Similarly, the port that JTAlert sends from is also automatically assigned by Windows, it is not hard coded. Windows simply assigns a port from its pool of unused ports. These are called Ephemeral Ports and for Windows (post XP) are in the range 49152-65535.

You will need to create an application-rule in the firewall rather than a port-rule if Zone Alarm is blocking JTAlert <-> WSJT-X comms.

de Laurie VK3AMA





Join Support@HamApps.groups.io to automatically receive all group messages.