开云体育

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: ASL3 DTMF not recognized

 

Here is a connect command to node 534630 that fails. Note the second "3" has a problem and the error is repeatable.? ?They sound fine on the radio (ID-50A) and DTMF speed is set to 300 ms in the radio.? The earlier post was just my running through all the keys.? ? Interestingly if I do the same on my AnyTone 878 UVII where I use the keypad the commands work fine

[2024-07-10 13:47:26.959] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '*' received on SimpleUSB/59753
[2024-07-10 13:47:26.959] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '*' on SimpleUSB/59753
[2024-07-10 13:47:27.257] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '*' received on SimpleUSB/59753, duration 298 ms
[2024-07-10 13:47:27.257] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '*' on SimpleUSB/59753
[2024-07-10 13:47:27.257] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '*' on SimpleUSB/59753
[2024-07-10 13:47:27.620] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 13:47:27.620] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '3' on SimpleUSB/59753
[2024-07-10 13:47:27.855] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 235 ms
[2024-07-10 13:47:27.855] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '3' on SimpleUSB/59753
[2024-07-10 13:47:27.855] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '3' on SimpleUSB/59753
[2024-07-10 13:47:28.175] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '5' received on SimpleUSB/59753
[2024-07-10 13:47:28.175] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '5' on SimpleUSB/59753
[2024-07-10 13:47:28.473] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '5' received on SimpleUSB/59753, duration 298 ms
[2024-07-10 13:47:28.473] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '5' on SimpleUSB/59753
[2024-07-10 13:47:28.473] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '5' on SimpleUSB/59753
[2024-07-10 13:47:28.858] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 13:47:28.858] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '3' on SimpleUSB/59753
[2024-07-10 13:47:28.985] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 127 ms
[2024-07-10 13:47:28.985] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '3' on SimpleUSB/59753
[2024-07-10 13:47:28.985] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '3' on SimpleUSB/59753
[2024-07-10 13:47:29.369] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '4' received on SimpleUSB/59753
[2024-07-10 13:47:29.370] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '4' on SimpleUSB/59753
[2024-07-10 13:47:29.669] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '4' received on SimpleUSB/59753, duration 299 ms
[2024-07-10 13:47:29.669] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '4' on SimpleUSB/59753
[2024-07-10 13:47:29.669] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '4' on SimpleUSB/59753
[2024-07-10 13:47:29.968] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '6' received on SimpleUSB/59753
[2024-07-10 13:47:29.968] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '6' on SimpleUSB/59753
[2024-07-10 13:47:30.266] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '6' received on SimpleUSB/59753, duration 298 ms
[2024-07-10 13:47:30.266] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '6' on SimpleUSB/59753
[2024-07-10 13:47:30.266] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '6' on SimpleUSB/59753
[2024-07-10 13:47:30.833] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 13:47:30.833] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '3' on SimpleUSB/59753
[2024-07-10 13:47:30.834] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 1 ms
[2024-07-10 13:47:30.834] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '3' on SimpleUSB/59753
[2024-07-10 13:47:30.834] DTMF[3892]: channel.c:3960 __ast_read: DTMF end '3' detected to have actual duration 1 on the wire, emulation will be triggered on SimpleUSB/59753
[2024-07-10 13:47:30.834] DTMF[3892]: channel.c:3967 __ast_read: DTMF end '3' has duration 1 but want minimum 80, emulating on SimpleUSB/59753
[2024-07-10 13:47:30.835] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 13:47:30.835] DTMF[3892]: channel.c:4012 __ast_read: DTMF begin ignored '3' on SimpleUSB/59753
[2024-07-10 13:47:30.854] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 19 ms
[2024-07-10 13:47:30.912] DTMF[3892]: channel.c:4042 __ast_read: DTMF end emulation of '3' queued on SimpleUSB/59753
[2024-07-10 13:47:31.132] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 19 ms
[2024-07-10 13:47:31.132] DTMF[3892]: channel.c:3921 __ast_read: DTMF begin emulation of '3' with duration 80 queued on SimpleUSB/59753
[2024-07-10 13:47:31.153] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '0' received on SimpleUSB/59753
[2024-07-10 13:47:31.153] DTMF[3892]: channel.c:4012 __ast_read: DTMF begin ignored '0' on SimpleUSB/59753
[2024-07-10 13:47:31.213] DTMF[3892]: channel.c:4100 __ast_read: DTMF end emulation of '3' queued on SimpleUSB/59753
[2024-07-10 13:47:31.461] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '0' received on SimpleUSB/59753, duration 308 ms
[2024-07-10 13:47:31.461] DTMF[3892]: channel.c:3921 __ast_read: DTMF begin emulation of '0' with duration 308 queued on SimpleUSB/59753
[2024-07-10 13:47:31.781] DTMF[3892]: channel.c:4100 __ast_read: DTMF end emulation of '0' queued on SimpleUSB/59753

Here is trying to connect to *355553 again a problem with the "3"

[2024-07-10 14:03:33.953] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '*' received on SimpleUSB/59753
[2024-07-10 14:03:33.953] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '*' on SimpleUSB/59753
[2024-07-10 14:03:34.251] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '*' received on SimpleUSB/59753, duration 298 ms
[2024-07-10 14:03:34.251] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '*' on SimpleUSB/59753
[2024-07-10 14:03:34.251] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '*' on SimpleUSB/59753
[2024-07-10 14:03:34.571] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 14:03:34.571] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '3' on SimpleUSB/59753
[2024-07-10 14:03:34.614] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 42 ms
[2024-07-10 14:03:34.614] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '3' on SimpleUSB/59753
[2024-07-10 14:03:34.614] DTMF[3892]: channel.c:3960 __ast_read: DTMF end '3' detected to have actual duration 42 on the wire, emulation will be triggered on SimpleUSB/59753
[2024-07-10 14:03:34.614] DTMF[3892]: channel.c:3967 __ast_read: DTMF end '3' has duration 42 but want minimum 80, emulating on SimpleUSB/59753
[2024-07-10 14:03:34.614] DTMF[3892]: channel.c:4100 __ast_read: DTMF end emulation of '3' queued on SimpleUSB/59753
[2024-07-10 14:03:34.675] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 14:03:34.675] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '3' on SimpleUSB/59753
[2024-07-10 14:03:34.775] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 99 ms
[2024-07-10 14:03:34.775] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '3' on SimpleUSB/59753
[2024-07-10 14:03:34.775] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '3' on SimpleUSB/59753
[2024-07-10 14:03:35.169] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '5' received on SimpleUSB/59753
[2024-07-10 14:03:35.169] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '5' on SimpleUSB/59753
[2024-07-10 14:03:35.467] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '5' received on SimpleUSB/59753, duration 298 ms
[2024-07-10 14:03:35.467] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '5' on SimpleUSB/59753
[2024-07-10 14:03:35.467] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '5' on SimpleUSB/59753
[2024-07-10 14:03:35.766] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '5' received on SimpleUSB/59753
[2024-07-10 14:03:35.766] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '5' on SimpleUSB/59753
[2024-07-10 14:03:36.065] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '5' received on SimpleUSB/59753, duration 299 ms
[2024-07-10 14:03:36.065] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '5' on SimpleUSB/59753
[2024-07-10 14:03:36.065] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '5' on SimpleUSB/59753
[2024-07-10 14:03:36.363] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '5' received on SimpleUSB/59753
[2024-07-10 14:03:36.363] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '5' on SimpleUSB/59753
[2024-07-10 14:03:36.663] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '5' received on SimpleUSB/59753, duration 299 ms
[2024-07-10 14:03:36.663] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '5' on SimpleUSB/59753
[2024-07-10 14:03:36.663] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '5' on SimpleUSB/59753
[2024-07-10 14:03:36.982] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '5' received on SimpleUSB/59753
[2024-07-10 14:03:36.982] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '5' on SimpleUSB/59753
[2024-07-10 14:03:37.282] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '5' received on SimpleUSB/59753, duration 299 ms
[2024-07-10 14:03:37.282] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '5' on SimpleUSB/59753
[2024-07-10 14:03:37.282] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '5' on SimpleUSB/59753
[2024-07-10 14:03:37.580] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 14:03:37.580] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '3' on SimpleUSB/59753
[2024-07-10 14:03:37.687] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 107 ms
[2024-07-10 14:03:37.687] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '3' on SimpleUSB/59753
[2024-07-10 14:03:37.687] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '3' on SimpleUSB/59753
[2024-07-10 14:03:37.747] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 14:03:37.747] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '3' on SimpleUSB/59753
[2024-07-10 14:03:37.827] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 80 ms
[2024-07-10 14:03:37.827] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '3' on SimpleUSB/59753
[2024-07-10 14:03:37.827] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '3' on SimpleUSB/59753
[2024-07-10 14:03:37.827] WARNING[3892]: channel.c:6332 request_channel: No channel type registered for 'echolink'
[2024-07-10 14:03:37.827] WARNING[3892]: app_rpt/rpt_link.c:728 connect_link: Unable to place call to echolink/el0/555533
? ? -- Hungup 'DAHDI/pseudo-462280106'
[2024-07-10 14:03:48.001] WARNING[3889]: res_rpt_http_registrations.c:148 curl_post: Failed to connect to register.allstarlink.org port 443 after 1000 ms: Timeout was reached
[2024-07-10 14:03:48.001] WARNING[3889]: res_rpt_http_registrations.c:150 curl_post: Failed to curl URL 'https://register.allstarlink.org/'



Re: ASL3 DTMF not recognized

 

Are you starting each command with an asterisk "*"?? (i.e. *70 for status or *355553 for the level check parrot node)


Re: ASL3 DTMF not recognized

 

Well looks like asterisk detecting your dtmf. What is the output on asterisk cli when you send connect dtmf from your radio?


Re: ASL3 echolink

 

On Wed, Jul 10, 2024 at 07:58 AM, Sander [VK6PI] wrote:
I've tried to get echolink working on ASL3 and have been following this thread. I was wondering how I can check that my configuration is set up for echolink, e.g., that the correct module is actually loaded. Or modules (plural)? Trying to connect to the parrot node 9999 failed, for example. DTMF is correctly received, though, I can see that in the asterisk*CLI.
There's a ASL3 bug that prevents you from connecting to 4/5 digit EchoLink nodes. ?The fix should be out real soon. ?If you want to test your setup without the fix then try connecting to 6-digit node (with no leading zeros) like?ARRLNEWS, #826983.


Re: ASL3 echolink

 

I've tried to get echolink working on ASL3 and have been following this thread. I was wondering how I can check that my configuration is set up for echolink, e.g., that the correct module is actually loaded. Or modules (plural)? Trying to connect to the parrot node 9999 failed, for example. DTMF is correctly received, though, I can see that in the asterisk*CLI.

Any thoughts on how to tackle this problem?

73
Sander


On Tue, 9 Jul 2024 at 12:18, Patrick Perdue via <borrisinabox=[email protected]> wrote:
The firewall problem has been resolved in the latest asl3-appliance package update a couple of days ago. Just install the package maintainers version of ?firewall.xml, and the zone should exist from that point.
Sent from my zippo


On Jul 8, 2024, at 21:44, Omar Asfour via <ve3kdc=[email protected]> wrote:

?Also saw that same error. Somewhere along the way, things started to work; though I'm not quite sure what single thing did it. For what it's worth: A couple of notes of what I tried (in addition to the documented steps out there):

Get a clean configuration file; and make sure it's owned by the same user that runs the asterisk application ("asterisk"user and group).

bash $ sudo rm /etc/asterisk/echolink.conf
bash $ sudo cp /usr/share/doc/asl3-asterisk-config/examples/configs/asl3/echolink.conf /etc/asteriskbash $ chown asterisk: /etc/asterisk/echolink.conf

Carefully edit the config file. My not doing so contributed to my issues.


After enabling the module (/etc/asterisk/module.conf), I opted to restart the server entirely (probably overkill; but why not).

You can also try to manually load it in Asterisk CLI.
CLI> module load chan_echolink

In my case, doing so help reveal to me that I had an invalid password.

Occasionally, the after reboot, the simpleusb module would fail. Still working through that; but it seems that restarting the asterisk service does the trick.
bash $ sudo systemctl restart asterisk.service

Somewhat related: I noticed that a firewall was enabled out of the box; but without "echolink" service added; the symptom being my echolink node was registered; but could not receive incoming calls. The following command added the echolink service to the firewall.

bash $ sudo firewall-cmd --zone-allstarlink --add-service=echolink

I hope some or all of this helps. Good luck and 73


Re: ASL3 echolink

 

Hm, minutes after sending my previous question, I ran into some rather important information, and my problem now comes down to this known problem:

but more specifically this:

73
Sander


On Wed, 10 Jul 2024 at 17:34, djtomny <djtomny.ingress@...> wrote:
I've tried to get echolink working on ASL3 and have been following this thread. I was wondering how I can check that my configuration is set up for echolink, e.g., that the correct module is actually loaded. Or modules (plural)? Trying to connect to the parrot node 9999 failed, for example. DTMF is correctly received, though, I can see that in the asterisk*CLI.

Any thoughts on how to tackle this problem?

73
Sander


On Tue, 9 Jul 2024 at 12:18, Patrick Perdue via <borrisinabox=[email protected]> wrote:
The firewall problem has been resolved in the latest asl3-appliance package update a couple of days ago. Just install the package maintainers version of ?firewall.xml, and the zone should exist from that point.
Sent from my zippo


On Jul 8, 2024, at 21:44, Omar Asfour via <ve3kdc=[email protected]> wrote:

?Also saw that same error. Somewhere along the way, things started to work; though I'm not quite sure what single thing did it. For what it's worth: A couple of notes of what I tried (in addition to the documented steps out there):

Get a clean configuration file; and make sure it's owned by the same user that runs the asterisk application ("asterisk"user and group).

bash $ sudo rm /etc/asterisk/echolink.conf
bash $ sudo cp /usr/share/doc/asl3-asterisk-config/examples/configs/asl3/echolink.conf /etc/asteriskbash $ chown asterisk: /etc/asterisk/echolink.conf

Carefully edit the config file. My not doing so contributed to my issues.


After enabling the module (/etc/asterisk/module.conf), I opted to restart the server entirely (probably overkill; but why not).

You can also try to manually load it in Asterisk CLI.
CLI> module load chan_echolink

In my case, doing so help reveal to me that I had an invalid password.

Occasionally, the after reboot, the simpleusb module would fail. Still working through that; but it seems that restarting the asterisk service does the trick.
bash $ sudo systemctl restart asterisk.service

Somewhat related: I noticed that a firewall was enabled out of the box; but without "echolink" service added; the symptom being my echolink node was registered; but could not receive incoming calls. The following command added the echolink service to the firewall.

bash $ sudo firewall-cmd --zone-allstarlink --add-service=echolink

I hope some or all of this helps. Good luck and 73


Re: ASL3 DTMF not recognized

 

Yes,? I have run the rx volume test.? Here is me testing the codes.? I can hear the codes with no problem on a second radio but I cannot link, get the time, etc. by entering the codes in the radio.? All works fine from the Node Links menu and Supermon.? I have the same problem using a different HT as well.??

Joe AF1E

Connected to Asterisk 20.8.1+asl3-3.0.0-1.deb12 currently running on node59753 (pid = 2182)
[2024-07-10 07:10:41.076] DTMF[2230]: channel.c:4008 __ast_read: DTMF begin '0' received on SimpleUSB/59753
[2024-07-10 07:10:41.076] DTMF[2230]: channel.c:4019 __ast_read: DTMF begin passthrough '0' on SimpleUSB/59753
[2024-07-10 07:10:41.354] DTMF[2230]: channel.c:3894 __ast_read: DTMF end '0' received on SimpleUSB/59753, duration 278 ms
[2024-07-10 07:10:41.354] DTMF[2230]: channel.c:3945 __ast_read: DTMF end accepted with begin '0' on SimpleUSB/59753
[2024-07-10 07:10:41.354] DTMF[2230]: channel.c:3983 __ast_read: DTMF end passthrough '0' on SimpleUSB/59753
[2024-07-10 07:10:41.652] DTMF[2230]: channel.c:4008 __ast_read: DTMF begin '1' received on SimpleUSB/59753
[2024-07-10 07:10:41.652] DTMF[2230]: channel.c:4019 __ast_read: DTMF begin passthrough '1' on SimpleUSB/59753
[2024-07-10 07:10:41.951] DTMF[2230]: channel.c:3894 __ast_read: DTMF end '1' received on SimpleUSB/59753, duration 299 ms
[2024-07-10 07:10:41.951] DTMF[2230]: channel.c:3945 __ast_read: DTMF end accepted with begin '1' on SimpleUSB/59753
[2024-07-10 07:10:41.951] DTMF[2230]: channel.c:3983 __ast_read: DTMF end passthrough '1' on SimpleUSB/59753
[2024-07-10 07:10:42.250] DTMF[2230]: channel.c:4008 __ast_read: DTMF begin '2' received on SimpleUSB/59753
[2024-07-10 07:10:42.250] DTMF[2230]: channel.c:4019 __ast_read: DTMF begin passthrough '2' on SimpleUSB/59753
[2024-07-10 07:10:42.548] DTMF[2230]: channel.c:3894 __ast_read: DTMF end '2' received on SimpleUSB/59753, duration 298 ms
[2024-07-10 07:10:42.548] DTMF[2230]: channel.c:3945 __ast_read: DTMF end accepted with begin '2' on SimpleUSB/59753
[2024-07-10 07:10:42.548] DTMF[2230]: channel.c:3983 __ast_read: DTMF end passthrough '2' on SimpleUSB/59753
[2024-07-10 07:10:42.868] DTMF[2230]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 07:10:42.868] DTMF[2230]: channel.c:4019 __ast_read: DTMF begin passthrough '3' on SimpleUSB/59753
[2024-07-10 07:10:42.954] DTMF[2230]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 86 ms
[2024-07-10 07:10:42.954] DTMF[2230]: channel.c:3945 __ast_read: DTMF end accepted with begin '3' on SimpleUSB/59753
[2024-07-10 07:10:42.954] DTMF[2230]: channel.c:3983 __ast_read: DTMF end passthrough '3' on SimpleUSB/59753
[2024-07-10 07:10:43.034] DTMF[2230]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 07:10:43.034] DTMF[2230]: channel.c:4019 __ast_read: DTMF begin passthrough '3' on SimpleUSB/59753
[2024-07-10 07:10:43.134] DTMF[2230]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 99 ms
[2024-07-10 07:10:43.134] DTMF[2230]: channel.c:3945 __ast_read: DTMF end accepted with begin '3' on SimpleUSB/59753
[2024-07-10 07:10:43.134] DTMF[2230]: channel.c:3983 __ast_read: DTMF end passthrough '3' on SimpleUSB/59753
[2024-07-10 07:10:43.466] DTMF[2230]: channel.c:4008 __ast_read: DTMF begin '4' received on SimpleUSB/59753
[2024-07-10 07:10:43.466] DTMF[2230]: channel.c:4019 __ast_read: DTMF begin passthrough '4' on SimpleUSB/59753
[2024-07-10 07:10:43.764] DTMF[2230]: channel.c:3894 __ast_read: DTMF end '4' received on SimpleUSB/59753, duration 298 ms
[2024-07-10 07:10:43.764] DTMF[2230]: channel.c:3945 __ast_read: DTMF end accepted with begin '4' on SimpleUSB/59753
[2024-07-10 07:10:43.764] DTMF[2230]: channel.c:3983 __ast_read: DTMF end passthrough '4' on SimpleUSB/59753
[2024-07-10 07:10:44.084] DTMF[2230]: channel.c:4008 __ast_read: DTMF begin '5' received on SimpleUSB/59753
[2024-07-10 07:10:44.084] DTMF[2230]: channel.c:4019 __ast_read: DTMF begin passthrough '5' on SimpleUSB/59753
[2024-07-10 07:10:44.362] DTMF[2230]: channel.c:3894 __ast_read: DTMF end '5' received on SimpleUSB/59753, duration 278 ms
[2024-07-10 07:10:44.362] DTMF[2230]: channel.c:3945 __ast_read: DTMF end accepted with begin '5' on SimpleUSB/59753
[2024-07-10 07:10:44.362] DTMF[2230]: channel.c:3983 __ast_read: DTMF end passthrough '5' on SimpleUSB/59753
[2024-07-10 07:10:44.682] DTMF[2230]: channel.c:4008 __ast_read: DTMF begin '6' received on SimpleUSB/59753
[2024-07-10 07:10:44.682] DTMF[2230]: channel.c:4019 __ast_read: DTMF begin passthrough '6' on SimpleUSB/59753
[2024-07-10 07:10:44.959] DTMF[2230]: channel.c:3894 __ast_read: DTMF end '6' received on SimpleUSB/59753, duration 277 ms
[2024-07-10 07:10:44.959] DTMF[2230]: channel.c:3945 __ast_read: DTMF end accepted with begin '6' on SimpleUSB/59753
[2024-07-10 07:10:44.959] DTMF[2230]: channel.c:3983 __ast_read: DTMF end passthrough '6' on SimpleUSB/59753
[2024-07-10 07:10:45.279] DTMF[2230]: channel.c:4008 __ast_read: DTMF begin '7' received on SimpleUSB/59753
[2024-07-10 07:10:45.279] DTMF[2230]: channel.c:4019 __ast_read: DTMF begin passthrough '7' on SimpleUSB/59753
[2024-07-10 07:10:45.578] DTMF[2230]: channel.c:3894 __ast_read: DTMF end '7' received on SimpleUSB/59753, duration 299 ms
[2024-07-10 07:10:45.578] DTMF[2230]: channel.c:3945 __ast_read: DTMF end accepted with begin '7' on SimpleUSB/59753
[2024-07-10 07:10:45.578] DTMF[2230]: channel.c:3983 __ast_read: DTMF end passthrough '7' on SimpleUSB/59753
[2024-07-10 07:10:45.855] DTMF[2230]: channel.c:4008 __ast_read: DTMF begin '8' received on SimpleUSB/59753
[2024-07-10 07:10:45.855] DTMF[2230]: channel.c:4019 __ast_read: DTMF begin passthrough '8' on SimpleUSB/59753
[2024-07-10 07:10:46.154] DTMF[2230]: channel.c:3894 __ast_read: DTMF end '8' received on SimpleUSB/59753, duration 299 ms
[2024-07-10 07:10:46.154] DTMF[2230]: channel.c:3945 __ast_read: DTMF end accepted with begin '8' on SimpleUSB/59753
[2024-07-10 07:10:46.154] DTMF[2230]: channel.c:3983 __ast_read: DTMF end passthrough '8' on SimpleUSB/59753
[2024-07-10 07:10:46.452] DTMF[2230]: channel.c:4008 __ast_read: DTMF begin '9' received on SimpleUSB/59753
[2024-07-10 07:10:46.452] DTMF[2230]: channel.c:4019 __ast_read: DTMF begin passthrough '9' on SimpleUSB/59753
[2024-07-10 07:10:46.772] DTMF[2230]: channel.c:3894 __ast_read: DTMF end '9' received on SimpleUSB/59753, duration 320 ms
[2024-07-10 07:10:46.772] DTMF[2230]: channel.c:3945 __ast_read: DTMF end accepted with begin '9' on SimpleUSB/59753
[2024-07-10 07:10:46.772] DTMF[2230]: channel.c:3983 __ast_read: DTMF end passthrough '9' on SimpleUSB/59753
[2024-07-10 07:10:47.669] DTMF[2230]: channel.c:4008 __ast_read: DTMF begin 'B' received on SimpleUSB/59753
[2024-07-10 07:10:47.669] DTMF[2230]: channel.c:4019 __ast_read: DTMF begin passthrough 'B' on SimpleUSB/59753
[2024-07-10 07:10:47.947] DTMF[2230]: channel.c:3894 __ast_read: DTMF end 'B' received on SimpleUSB/59753, duration 278 ms
[2024-07-10 07:10:47.947] DTMF[2230]: channel.c:3945 __ast_read: DTMF end accepted with begin 'B' on SimpleUSB/59753
[2024-07-10 07:10:47.947] DTMF[2230]: channel.c:3983 __ast_read: DTMF end passthrough 'B' on SimpleUSB/59753
[2024-07-10 07:10:48.245] DTMF[2230]: channel.c:4008 __ast_read: DTMF begin 'C' received on SimpleUSB/59753
[2024-07-10 07:10:48.245] DTMF[2230]: channel.c:4019 __ast_read: DTMF begin passthrough 'C' on SimpleUSB/59753
[2024-07-10 07:10:48.565] DTMF[2230]: channel.c:3894 __ast_read: DTMF end 'C' received on SimpleUSB/59753, duration 320 ms
[2024-07-10 07:10:48.565] DTMF[2230]: channel.c:3945 __ast_read: DTMF end accepted with begin 'C' on SimpleUSB/59753
[2024-07-10 07:10:48.565] DTMF[2230]: channel.c:3983 __ast_read: DTMF end passthrough 'C' on SimpleUSB/59753
[2024-07-10 07:10:48.864] DTMF[2230]: channel.c:4008 __ast_read: DTMF begin 'D' received on SimpleUSB/59753
[2024-07-10 07:10:48.864] DTMF[2230]: channel.c:4019 __ast_read: DTMF begin passthrough 'D' on SimpleUSB/59753
[2024-07-10 07:10:49.184] DTMF[2230]: channel.c:3894 __ast_read: DTMF end 'D' received on SimpleUSB/59753, duration 320 ms
[2024-07-10 07:10:49.184] DTMF[2230]: channel.c:3945 __ast_read: DTMF end accepted with begin 'D' on SimpleUSB/59753
[2024-07-10 07:10:49.184] DTMF[2230]: channel.c:3983 __ast_read: DTMF end passthrough 'D' on SimpleUSB/59753
[2024-07-10 07:10:49.461] DTMF[2230]: channel.c:4008 __ast_read: DTMF begin '*' received on SimpleUSB/59753
[2024-07-10 07:10:49.461] DTMF[2230]: channel.c:4019 __ast_read: DTMF begin passthrough '*' on SimpleUSB/59753
[2024-07-10 07:10:49.781] DTMF[2230]: channel.c:3894 __ast_read: DTMF end '*' received on SimpleUSB/59753, duration 320 ms
[2024-07-10 07:10:49.781] DTMF[2230]: channel.c:3945 __ast_read: DTMF end accepted with begin '*' on SimpleUSB/59753
[2024-07-10 07:10:49.781] DTMF[2230]: channel.c:3983 __ast_read: DTMF end passthrough '*' on SimpleUSB/59753
[2024-07-10 07:10:50.059] DTMF[2230]: channel.c:4008 __ast_read: DTMF begin '#' received on SimpleUSB/59753
[2024-07-10 07:10:50.059] DTMF[2230]: channel.c:4019 __ast_read: DTMF begin passthrough '#' on SimpleUSB/59753
[2024-07-10 07:10:50.379] DTMF[2230]: channel.c:3894 __ast_read: DTMF end '#' received on SimpleUSB/59753, duration 320 ms
[2024-07-10 07:10:50.379] DTMF[2230]: channel.c:3945 __ast_read: DTMF end accepted with begin '#' on SimpleUSB/59753
[2024-07-10 07:10:50.379] DTMF[2230]: channel.c:3983 __ast_read: DTMF end passthrough '#' on SimpleUSB/59753


Re: ASL3 DTMF not recognized

 

Did you set it up and test rx volume through simpleusb?


ASL3 DTMF not recognized

 

My node is a setup up with the new ASL3 and Supermonwith my Shari.? All is working well except I cannot input DTMF codes on the radio to establish links or get status.? All of this works fine in Allmon3 and SuperMon just not directly from my radios.? The DTMF codes are recognized in the Asterisk CLI with no problem.? What am I missing?

Thanks? Joe AF1E


Re: ASL3 echolink

 

开云体育

The firewall problem has been resolved in the latest asl3-appliance package update a couple of days ago. Just install the package maintainers version of ?firewall.xml, and the zone should exist from that point.
Sent from my zippo


On Jul 8, 2024, at 21:44, Omar Asfour via groups.io <ve3kdc@...> wrote:

?Also saw that same error. Somewhere along the way, things started to work; though I'm not quite sure what single thing did it. For what it's worth: A couple of notes of what I tried (in addition to the documented steps out there):

Get a clean configuration file; and make sure it's owned by the same user that runs the asterisk application ("asterisk"user and group).

bash $ sudo rm /etc/asterisk/echolink.conf
bash $ sudo cp /usr/share/doc/asl3-asterisk-config/examples/configs/asl3/echolink.conf /etc/asteriskbash $ chown asterisk: /etc/asterisk/echolink.conf

Carefully edit the config file. My not doing so contributed to my issues.


After enabling the module (/etc/asterisk/module.conf), I opted to restart the server entirely (probably overkill; but why not).

You can also try to manually load it in Asterisk CLI.
CLI> module load chan_echolink

In my case, doing so help reveal to me that I had an invalid password.

Occasionally, the after reboot, the simpleusb module would fail. Still working through that; but it seems that restarting the asterisk service does the trick.
bash $ sudo systemctl restart asterisk.service

Somewhat related: I noticed that a firewall was enabled out of the box; but without "echolink" service added; the symptom being my echolink node was registered; but could not receive incoming calls. The following command added the echolink service to the firewall.

bash $ sudo firewall-cmd --zone-allstarlink --add-service=echolink

I hope some or all of this helps. Good luck and 73


Re: ASL3 echolink

 

Also saw that same error. Somewhere along the way, things started to work; though I'm not quite sure what single thing did it. For what it's worth: A couple of notes of what I tried (in addition to the documented steps out there):

Get a clean configuration file; and make sure it's owned by the same user that runs the asterisk application ("asterisk"user and group).

bash $ sudo rm /etc/asterisk/echolink.conf
bash $ sudo cp /usr/share/doc/asl3-asterisk-config/examples/configs/asl3/echolink.conf /etc/asteriskbash $ chown asterisk: /etc/asterisk/echolink.conf

Carefully edit the config file. My not doing so contributed to my issues.


After enabling the module (/etc/asterisk/module.conf), I opted to restart the server entirely (probably overkill; but why not).

You can also try to manually load it in Asterisk CLI.
CLI> module load chan_echolink

In my case, doing so help reveal to me that I had an invalid password.

Occasionally, the after reboot, the simpleusb module would fail. Still working through that; but it seems that restarting the asterisk service does the trick.
bash $ sudo systemctl restart asterisk.service

Somewhat related: I noticed that a firewall was enabled out of the box; but without "echolink" service added; the symptom being my echolink node was registered; but could not receive incoming calls. The following command added the echolink service to the firewall.

bash $ sudo firewall-cmd --zone-allstarlink --add-service=echolink

I hope some or all of this helps. Good luck and 73


Re: increasing audio bandwidth on ASL3

 

开云体育

Interestingly, that was already enabled on my node. Maybe I did that and forgot to mention it? Not sure.


On 7/8/2024 8:13 AM, Danny Lloyd via groups.io wrote:

In order for me to use slin16, I had to update modules.conf with the following entry.

load => codec_resample.so
I saw this error message on startup "unable to find a codec translation path: (slin16) -> (slin)"

Danny/KB4MDD


Re: increasing audio bandwidth on ASL3

 

开云体育

I'd love to hear/use an active system consisting of all SLIN16-connected nodes. Please post when this is a thing.


On 7/7/2024 4:21 PM, Carl Swanson via groups.io wrote:

This is the #1 reason we are overhauling two of our hubs from v2 and installing v3.

Carl/K6CRS


Re: increasing audio bandwidth on ASL3

 

In order for me to use slin16, I had to update modules.conf with the following entry.

load => codec_resample.so
I saw this error message on startup "unable to find a codec translation path: (slin16) -> (slin)"

Danny/KB4MDD


Re: increasing audio bandwidth on ASL3

 

This is the #1 reason we are overhauling two of our hubs from v2 and installing v3.

Carl/K6CRS


Re: ASL3 echolink

 

开云体育

I am aware. That is why I disabled the echolimk module on the other node, and forwarded the port range to the new one when testing.

Sent from my zippo


On Jul 6, 2024, at 10:03, Brad N8PC via groups.io <bradn8pc@...> wrote:

?

You can not run 2 echolinks on the same network


On Sat, Jul 6, 2024, 9:10 AM Allan, WA3WCO via <ajn=[email protected]> wrote:
In short, we found an issue with connecting to nodes that, as 6-digits, have leading zeros.? A fix is on the way.

For details, you can look at :?


Re: ASL3 echolink

 

You can not run 2 echolinks on the same network


On Sat, Jul 6, 2024, 9:10 AM Allan, WA3WCO via <ajn=[email protected]> wrote:
In short, we found an issue with connecting to nodes that, as 6-digits, have leading zeros.? A fix is on the way.

For details, you can look at :?


Re: ASL3 echolink

 

In short, we found an issue with connecting to nodes that, as 6-digits, have leading zeros. ?A fix is on the way.

For details, you can look at :?


Re: ASL3 on a SHARI

 

开云体育

volume 6, HPF, LPF and emphasis enabled.


On 7/6/2024 8:46 AM, N8AR via groups.io wrote:

What SA818 settings do you use for these simpleusb.conf and usbradio.conf files?

On Sat, Jul 6, 2024 at 08:43 AM, Patrick Perdue wrote:

Should anyone want them for reference, I have attached both my simpleusb.conf and usbradio.conf files to this post. Both are working, and (I think) reasonably tuned. Use these as examples if you like.

They reference my node number (508422) so replace with yours if you are going to do a wholesale drop-in for testing.

?


Re: ASL3 on a SHARI

 

What SA818 settings do you use for these simpleusb.conf and usbradio.conf files?


On Sat, Jul 6, 2024 at 08:43 AM, Patrick Perdue wrote:

Should anyone want them for reference, I have attached both my simpleusb.conf and usbradio.conf files to this post. Both are working, and (I think) reasonably tuned. Use these as examples if you like.

They reference my node number (508422) so replace with yours if you are going to do a wholesale drop-in for testing.

?