EchoLink Connection

StanLaMuth

I’ve updated to V38 and have entered my call and password for EL . I’ve selected my desired server and the M1KE connects and confirms the connection . When I select the repeater on my handheld Radio and transmit the M1KE shows nothing . I hear nothing . When I activate PTT on the M1KE and talk the repeater sends no audio or RF signal. What am I doing wrong ?

HA2NON

The server does not forward calls, or the repeater is not linked to the EchoLink server. Try contacting the server and/or repeater admin.

Docksea

I also have been able to connect but no audio passes to the m1ke, but I have another node on the same system that echolink is connected to and audio dose not pass to the m1ke but dose to the other non m1ke.
And if the m1ke keys up it dissconnects ALL nodes on the system.
So there are big bugs in the code for echolink

StanLaMuth

HA2NON
So in this case the server is connected to a transceiver which transmits and receives signals to the actual remote repeater. So this means I’m connected to the server but it will not pass traffic from the physical repeater?

I use the EchoLink App on my iPhone all the time and it performs flawlessly.

Thanks in advance for your help

HA2NON

Docksea Please describe how we can reproduce the issue.

StanLaMuth Verify that both your iPhone and M1KE are connected to the exact same server and try transmitting with both the iPhone and M1KE. If the server passes traffic correctly then you'll hear both devices.

Docksea

connect via echolink to N7EAL-R
it's a Allstar/echolink ASL 2.x
http://593251.nodes.allstarlink.org/supermon/link.php?nodes=593251
when the m1ke keys up, sometimes the audio passes, sometimes not, but it locks up the supermon page and my other node via allstar will drop and reconnect (I have auto reconnect on), notice the 'Connect time' resets. Nodes that don't have auto reconnect have to manualy reconnect.
Happing on nodes other than my own, some have disabled Echolink incoming until this gets fixed.

Docksea

looking at the server logs I see a GSM codec error that might point you in the right direction.

Sep 18 11:39:26 593251 asterisk[25134]: [Sep 18 11:39:26] WARNING[25161]: codec_gsm.c:144 gsmtolin_framein: Invalid GSM data (1)
Sep 18 11:39:26 593251 asterisk[25134]: [Sep 18 11:39:26] WARNING[25161]: translate.c:211 framein: gsmtolin did not update samples 0
Sep 18 11:39:26 593251 kernel: [3095558.929411] asterisk[25161]: segfault at 50 ip 0000559f23d34f9b sp 00007f8970c36050 error 4 in asterisk[559f23cf3000+ac000]

HA2NON

EchoLink puts 4 GSM frames into one RTP packet. If the user releases PTT and there are fewer than 4 frames available, the M1KE fills remaining GSM data with zeroes. Probably that triggers this software error in Asterisk. We modified the code to fill remaining RTP data with valid silent GSM frames. Update is now available in beta firmware v39, please report if this fixes the issue.

StanLaMuth

HA2NON

In the v38 firmware I was able to reliably connect to EchoLink servers I selected . With the v.39 firmware I can no longer connect to any EchoLink server at all.

Docksea

I believe you have successfully addressed the issue. I am no longer able to reproduce the problem, and I am not seeing any GSM errors in the log.

Docksea

StanLaMuth

are you by chance using something other than #1 wifi ? mine works if I'm on the wifi network #1, but if I'm on my phone wifi hotspot in slot 2 on the M1ke Echolink will not connect.

StanLaMuth

Docksea

As of tonight I have EchoLink working great under v.39 when connected to wifi networks other than the T Mobile Home Internet service that I have at my summer home . There are a couple of ports that the T Mobile device does not forward to the M1KE that are required.

I was on 2 nets tonight and got excellent signal reports on . The connection stayed up and solid for 4+ hours .

Docksea

StanLaMuth

good to know, looks like a T-mobile issue that is what I failed on also

StanLaMuth

Docksea

Thanks for the confirmation .

Bob_N5DEA

StanLaMuth yes I have T- Mobile home internet and also my phone is on the T-Mobile system. I have yet to get Echolink to work on either one. I sure hope there is a fix for this.
But I can use the Echolink app on my phone and it works fine. The same with RepeaterPhone.

HA2NON

Docksea Thank you for the feedback. Please report the GSM codec issue also to AllStarLink and/or Asterisk as it is a vulnerability and they should fix it as soon as possible.

Bob_N5DEA

So if you have T-mobile for your home internet and for your cell phone you’re pretty much s&@t out of luck for using the Echolink feature. Unless you understand how to change something in the firewall which I have no idea how to do.
Thanks a lot

EA7KGO

I have seen in an advertisement that it can be inserted or will it be a new update of Mike with Echolink, my question is, will it be possible in those who already have Mike also EA7KGO

Bob_N5DEA

Others are reporting on the FB groups that they are having issues connecting to Echolink while using either t-Mobile, Verizon and AT&T cell service.

HA2NON

EA7KGO EchoLink support is available in (currently beta) firmware v39. You can enable beta firmware upgrades on the Settings page, Firmware upgrade section. Make sure Advanced mode is enabled at the bottom right of the web interface.

EA7KGO EchoLink uses RTP and RTCP UDP packets for communication, which is a commonly used protocol for VoIP. Cell phone providers may filter these RTP/RTCP packets to force you not using VoIP and instead use (and pay) for regular phone calls. Try contacting your provider and explain them your issue.