Echolink not allowed

w9gil

HA2NON is there an export function which saves all the settings I have? I have done extensive customazation of my M1KE.

HA2NON

DO1ABL The M1KE does not accept incoming EchoLink connections. It can only connect to other EchoLink servers.

w9gil You can export your configuration by clicking on the Export button on the Settings page https://manuals.sharkrf.com/m1ke/web/settings/cfgprofile.html

DO1ABL

I must have expressed myself wrong, we would like to talk about a server together (DB0RUG) and that works now strangely with one yes but with me and my friend not and we have the settings all 3 the same!

HA2NON

Do you mean that you are all connected to an EchoLink server and you can't hear each other?

DO1ABL

Hallo HA2NEIN Also nach dem Status der Konsole sollte ich mit DB0RUG verbunden sein, mit einer Echolink-App auf dem Server DB0RUG konnte ich dort auch die M1KE sehen, nur nichts kommt an der M1KE an. Im Display flash EchoLink oben links und die LED am Gerät blinkt ebenfalls rot/orange/blau und nicht grün für Verbunden!

HA2NON

Please use English on this forum.

w9amt

Same issue for me. I can connect to the Echolink node (local repeater to me, so I can hear the repeater connecting to me), but no audio to the repeater and no audio from the repeater going to the M1KE

Vk4my

Similar issue here. I can connect to the Echolink test server. M1KE tells me I am connected.
Transmitting a test call seems to go out. No reply from the test transmission.
Other Echolink servers are connecting however, no audio back from the server on most occasions.
Monitoring that same server via Echolink App on Android and there is traffic.
Occasionally audio can be heard via the M1KE.
Very intermittent on my experience.
73 Mike

ON9CJX

We can link via the Echolink app to an Echolink server that works fine via 4G/5G provider . But link on the same network with the M1KE is a no go.
Same result with the Echolink app on Wifi but with the M1KE no connection.
What do we do wrong?

dk9jy

We need a network connection via proxy server because of the problem with the ports.

HA2NON

The EchoLink network requires that each client has a unique internet IP address. If your internet service provider uses Carrier Grade NAT (you don’t have a unique public IP address) you will not be able to connect to EchoLink servers.

Docksea

HA2NON it works over the same internet connection with the EchoLink APP using Relay.

HA2NON

Yes, as the proxy provides an external IP address. The M1KE currently does not support connecting through EchoLink proxies.

Docksea

HA2NON then you should have a note on your advertising that it only works with a dedicated IP and not mobile networks, Starlink, many home ISPs...

Someone buying it thinking Echolink is fully functional might be disappointed.

ON9CJX

Have a static ip address.....but no luck. Wondering why the Android Echolink app is working without static ip address and the M1ke not. But still a happy user. HA2NON keep up the good work.

Vk4my

I have a static IP. I connected to a public AS node that also has a Echolink connection with my own Allstar Node (606160). I can key the Allstar Node with M1KE Echolink mode however, there is no audio passed either way. Allstar and all other modes on the M1KE work great. I can use the Android and Repeaterphone Apps for Echolink so not a big issue.
Maybe more programming work required to make Echolink useful on the M1KE now we know that “Static” IP’s are required. Keep up the good work Norbert and team……
73 Mike

HA2NON

Static IP addresses (on your local network) have nothing to do with CGNAT and public internet addresses. The EchoLink network requires that each client has a unique internet IP address. If your internet service provider uses Carrier Grade NAT (you don’t have a unique public IP address) you will not be able to connect to EchoLink servers.

Vk4my

HA2NON
My internet supplier is a fixed fibre service and I have a fixed IP. Has been the same IP for many years. I have port forwarding to my AS and DVS nodes allowing others to always connect.
The test noted in previous msg above I would have thought would have worked. No CGNAT involved at either end.
73 Mike

HA2NON

Vk4my Please make sure UDP ports 5198 and 5199 are not forwarded in your router, or forwarded to your M1KE's local IP address.

DO1ABL

@VK4MY
With me it is exactly the same, it connects according to the console but nothing comes through to the M1KE, a friend also bought the M1KE and with him it works strangely, the settings are the same as with me only that he bought a new M1KE. I was happy that it finally starts with FM also in Germany, but I was probably deceived there!

Vk4my

DO1ABL
Has there been a hardware change to the most recent shipments?

w9amt

HA2NON How does that work if we are using the hotspot on our phone?

Vk4my

HA2NON
Neither 5198 or 5199 are port forwarded in my router. Only have port forwarding for those port Nrs required for my AS Nodes/s.
73 Mike