Audio from echolink was fine before the last batch of updates 3.4.4 and 3.4.5 , seems as though its clipping I've been changing settings to see if I could resolve it to the extent of a fresh install on a different Pi , allstar audio is fine.
RX audio is fine i.e me transmitting on a HT to my node that is connected to any echolink node, what is heard from me is fine no issues, I can monitor on several external echolink nodes and I concur the audio is fine.
TX audio from any connected echolink node is very poor, like its clipping or missing a packet.
Allstart audio is excellent both ways.
I've changed the Pi3 for a Pi4 and back again, several fresh installs , changed the cm108 but all that has not sorted the issue.
Other than the echolink gain settings what else can I play with to resolve this.
Hi Mike.
Currently Rpi3 + CM108 (G6OJB style mod) running 3.4.5 Half duplex, the tx/rx is a Baofeng UV-5R Mk5.
I've rotated all of the hardware individually but still the same.
Kev G0TPZ
Its only on the TX'd echolink audio all ok on the Allstar Tx'd audio . Only on echolink audio from the internet being transmitted by my node Baofeng radio.
Ok, I've now changed to a thin client but its still the same so yes I'm now sure its a bug in the system.
I'm running
Asterisk 22.4.1+asl3-3.5.4-1.deb12,CN108 usb sound fob to Baofeng UV5 Mrk5.
Just to confirm
Audio from echolink was fine before the last batch of updates 3.4.4 and 3.4.5 , seems as though its clipping I've been changing settings to see if I could resolve it to the extent of a fresh install on a different Pi , allstar audio is fine.
RX audio is fine i.e me transmitting on a HT to my node that is connected to any echolink node, what is heard from me is fine no issues, I can monitor on several external echolink nodes and I concur the audio is fine.
TX audio from any connected echolink node is very poor, like its clipping or missing a packet.
Allstart audio is excellent both ways.
I've changed the Pi3 for a Pi4 and back again, several fresh installs , changed the cm108 but all that has not sorted the issue.
Other than the echolink gain settings what else can I play with to resolve this.
For the most part, yes, but it's a couple more steps than that. You can fetch the whole asl3 install back to asl3-3.0.0 from the Debian distributions. Package name is asl3-asterisk. Instructions for this are here: Downgrading a Package via apt-get in Ubuntu and Debian
Thanks Chuck but I've failed at the first hurdle,I just don't know what I'm doing with linux.
Can someone point me to where I can get asl3-3.0.0 and then how to download/clone it.
Thanks
Nope need help. This is what I'm getting when trying to roll back to 3.3.0
oot@Allstarlink:/home/g0tpz# sudo apt install asl3-asterisk=2:22.2.0+asl3-3.3.0-6.deb12
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
asl3-asterisk : Depends: asl3-asterisk-config (= 2:22.2.0+asl3-3.3.0-6.deb12) but 2:22.4.1+asl3-3.5.4-1.deb12 is to be installed or
asterisk-config-custom but it is not installable
Depends: asl3-asterisk-modules (= 2:22.2.0+asl3-3.3.0-6.deb12) but 2:22.4.1+asl3-3.5.4-1.deb12 is to be installed
E: Unable to correct problems, you have held broken packages.
WOW, I've got it back to 2:22.2.0+asl3-3.3.0-6.deb12. Echolink audio is good both ways now.
What I needed to do was roll back asl3-asterisk-modules,asl3-asterisk-config and asl3-asterisk
All sorted now
Thanks for your help
Sorry about that - asl3-asterisk package apparently does not carry its own dependencies. It looks like only the asl3 metapackage has the dependencies. However, in that case you'd have to correlate version numbers since asl3 is versioned differently.
Good morning, wondering what the expected resolution date is for this bug? Trying to decide if I just live with the issue for the time being, or try some of the workaround ideas listed in previous posts.
Just had another idea. I have a node using only Dahdi/pseudo, to access ASL3 using Android devices. It has no issue with Echolink send/receive. Once I set up my simpleusb node again, I will try connecting from the node using SimpleUSB to the node using Dahdi/pseudo, and see how that works. I ordered a new Raspi 5 to use for the new node, and expect to receive it this week. Once set up, I will report back.
This is already known to work, but it requires a second RPi. See the discussion on issue #700 above.
A manager where I once worked asked a programmer how long it would take to find a bug he was tracing. The programmer asked the manager "How long will it take to catch a fish?".
Fair enough! I guess I was looking for relative priority and how far down it is in the queue of bugs. I don't think a second RPi would be needed, since the first node is hosted in the cloud. Thanks for your response!
