Recent Posts

Pages: 1 [2] 3 4 ... 10
EchoHam / Re: EchoHam 2.13 Connection Issues
« Last post by philhowes on July 13, 2020, 04:47:21 AM »
Hello, thanks for getting back to me. Unfortunately the same thing happens when I reboot. Also if I disable Upnp in Echoham it doesn't connect either. I can't find what's blocking port 1900. If I use netstat in the terminal and search for 1900 I get nothing?


EchoHam / Re: EchoHam 2.13 Connection Issues
« Last post by support on July 10, 2020, 10:10:03 PM »
Hi Phil,
the console messages indicate that you have another application running which is hogging port 1900.
Do you have anything uPnP related installed?
Do you get the same console messages if run EchoHam straight after a reboot?
Any possibility that you have other software which could block EchoHam from port 1900?

EchoHam / Re: EchoHam 2.13 Connection Issues
« Last post by philhowes on July 10, 2020, 05:18:58 PM »

My callsign is M7PHX

Thanks very much for your help


EchoHam / Re: EchoHam 2.13 Connection Issues
« Last post by support on July 10, 2020, 08:55:32 AM »
Hi Phil,
could you please advise your call sign so I can do some diagnostics from this end.

EchoHam / EchoHam 2.13 Connection Issues
« Last post by philhowes on July 10, 2020, 03:31:09 AM »
Hello, I'm currently trying to use EchoHam 2.13  with MacOs 10.11.6 El Capitan.
I've registered with EchoLink and received confirmation. I can use the Android version on my tablet happily.

I start EchoHam and it downloads the callsign list, but I cannot connect to any repeater, link or callsign.

I've opened up ports 5198-99 on my router and forwarded them to my Mac (which has a static i.p)
I've created a Port Triggering with 5200 to open 5198-99.
I added EchoHam to the mac Firewall to allow incoming connections, and even tried with the firewall turned off.

I still cannot get EchoHam to connect to any repeater, link or callsign.

In the /applications/utilities/console app doing a search for EchoHam i get:

09/07/2020 18:16:42.974 EchoHam[4423]: EchoHam.EHPortmapping.startUPNPadd() - Unable to bind to upnp port 1900: Error Domain=NSPOSIXErrorDomain Code=48 "Address already in use" UserInfo={NSLocalizedDescription=Address already in use, NSLocalizedFailureReason=Error in bind() function}

09/07/2020 18:16:53.135 EchoHam[4423]: -[EHControlConnection _connectRemoteHost:] - timer started

any help would be greatly appreciated.

cheers Phil
EchoHam / EchoHam V2.13 released
« Last post by support on June 29, 2020, 11:00:52 AM »
A few more improvements to make network debugging easier.
The port checking facility now tests for two different scenarios:
1) EchoHam connecting to another station (Outgoing Connection)
2) Another station connecting to EchoHam (Incoming connection)
Most modern routers will support outgoing connections without any special requirements.
Incoming connection pose more of a challenge and need port forwarding to be functioning correctly.

As of V2.13 the Port Check user alert will report separately on Incoming and Outgoing connections to enable better network diagnostics. 
EchoHam / Re: Connection Issues
« Last post by support on June 26, 2020, 09:16:21 PM »
includes a number of connectivity improvements and tries to automatically configure your router for port forwarding.
The proxy server option is now implemented but at this stage you have to manually enter proxy server details.
In the near future I will include and automatic selection for public proxy servers.
EchoHam / EchoHam V2.12 released
« Last post by support on June 25, 2020, 09:22:14 AM »
V2.12 is now in the AppStore
the main improvement is the addition of NAT-PMP protocol to establish port forwarding.
NAT-PMP is very popular in Apple devices.
EchoHam / EchoHam V2.10 / V2.11 released
« Last post by support on June 21, 2020, 10:18:46 PM »
V2.10 improvements:
- uPnP based automatic port forwarding
- tested on macOS 10.15 Catalina
- station connection progress indicator
- reliability improvements and bug fixes

Unfortunately a bug crashed EchoHam when the user connects to another station.
V2.11 was released within 24hrs to fix this bug.
EchoHam / EchoHam port forwarding update
« Last post by support on June 21, 2020, 10:15:35 PM »
As of V2.10 EchoHam uses uPnP (Universal Plug N Play) to automatically establish port forwarding on routers.
I hope this improvement makes it easier for everyone to get the right ports forwarded to correct IP address.
It also allows for multiple computers on the same network to have EchoHam installed as long as only one is running EchoHam at any time.
As of V2.12 EchoHam also utilises NAT-PMP for port forwarding. This feature is very popular on Apple devices.
Pages: 1 [2] 3 4 ... 10