Echolink channel

App_rpt-users
1

Hello everyone problem the Echolink channel activated I have this result
The version derived from this installation.
apt update
apt install curl gpg

cd /tmp
wget http://apt.allstarlink.org/repos/asl_builds/install-allstarlink-repository
chmod +x install-allstarlink-repository
./install-allstarlink-repository

Install ASL

Next as root (or with sudo) run the following commands to install ASL.

apt -y install linux-headers-$(uname -r)
apt -y install asl-asterisk
apt -y install allstar-helpers
apt -y install asl-dahdi-linux
apt -y install asl-update-node-list

Then I had problems with the Dahdi driver with the block of asterisk and I solved
Now I find myself working everything but I have a problem for echolink and I have this error

– Executing [515930@radio-secure:1] Rpt(“echolink/el0-1”, “515930”) in new stack
== Spawn extension (radio-secure, 515930, 1) exited KEEPALIVE on ‘echolink/el0-1’
– Remote UNIX connection
– Hungup ‘DAHDI/pseudo-422437406’
– Remote UNIX connection
– <DAHDI/pseudo-510727014> Playing ‘rpt/node’ (language ‘en’)
– Remote UNIX connection disconnected
– Remote UNIX connection
– Remote UNIX connection disconnected
– Remote UNIX connection
– Remote UNIX connection disconnected
– Remote UNIX connection disconnected
– <DAHDI/pseudo-510727014> Playing ‘digits/3’ (language ‘en’)
– <DAHDI/pseudo-510727014> Playing ‘digits/9’ (language ‘en’)
– Executing [515930@radio-secure:1] Rpt(“echolink/el0-2”, “515930”) in new stack
== Spawn extension (radio-secure, 515930, 1) exited KEEPALIVE on ‘echolink/el0-2’
– Remote UNIX connection
– Hungup ‘DAHDI/pseudo-1197159042’
– Remote UNIX connection
– <DAHDI/pseudo-510727014> Playing ‘digits/9’ (language ‘en’)
– Remote UNIX connection disconnected
– Remote UNIX connection
– Remote UNIX connection disconnected

Recharged the echolink.conf file but I do not find a solution an idea for help
Thank you

2

Is this an invound or outbound connection?

Danny/KB4MDD

3

I doubt the issue is related your config, but it is possible.

Many little things to know about this.
If this is a inbound connect, and I have to guess it is from the playback, there are several reasons why it might not process.

If you are using a relay that has an issue.
OR
You are attempting to connect via the same network the node is on (WAN) for echolink will only allow one connect per ip address and if you are connecting via wifi it will do something similar.
In this case, I would suggest you turn wifi off on your phone for the test.
And if it is some other device, know it can’t be done on the same network.
Have a friend connect preferable who has a cable/broadband connection that does not have to relay.
Some of the relay servers are not config’d well.

But don’t adjust you config till you check / test for above.

But those are the top 2 issues.

4

Hello to you and thanks for the answers then I made the connection to one of our colleague try and the result is that it has connected to my -r the thing is that the server that hosts Allstar has just been passed in Ampnet and therefore the Echolink clientk of the smartphone is to be used with the proxy

5

Sorry, I am not reading your post well. But I don’t want to leave you hanging if you still need help.
So,
Understanding your colleague was able to connect to -r asl attached node.
If you still have an issue, just state what that is, we will start from there.

6

I have found the echolink conf needs to have the same case as your echolink account.
for the user ID

7

Thanks Mike but exchanged on Echolink Client of my phone I managed to connect through the proxy connections having put asl-ndt.ampr.org/ activation
http://asl-ndt.ampr.org//supermon/link.php?nodes=515930
And now to connect in Echolink it works if a proxy is used