Just downloaded the latest version of ASL3 3.0.13? and still seeing a issue that was never fixed
regarding the autopatch. This is having to do with DANDI and App_rpt/rpt_bridging. (app_rpt/rpt_bridging.c: Failed to request SimpleUSB/42285.) posted from asterisk error log.
I’m also running the hamvoip version of Allstar with no issues. Would appreciate seeing this issue fixed as this is a deal breaker switching over from hamvoip Allstar.
N7JYS
Please provide some sort of logging or explanation of your problem.
Connected to Asterisk 20.9.3+asl3-3.0.6-1.deb12 currently running on Node42285 (pid = 18447)
Node42285*CLI> rpt fun 42285 *61
[2024-10-14 10:39:22.480] WARNING[24298]: app_rpt/rpt_bridging.c:567 rpt_play_tone: Cannot start tone on DAHDI/pseudo-901721958
– Hungup ‘DAHDI/pseudo-1284268905’
– Hungup ‘DAHDI/pseudo-901721958’
This is what I get in response to simply accessing the autopatch.
This is what is what I have put in my node [FUNCTIONS]
;;;;; Autopatch Commands ;;;;;
; Note, This may be a good place for other 2 digit frequently used commands
61 = autopatchup, context=voip-outbound, noct=1, farenddisconnect=1, dialtime=20000 quiet=0 ; Autopatch up
0 = autopatchdn ; Autopatch down
With quite = 0 ; There should be a dial tone when I access the autopatch.
I have followed instructions on github by N5LSN with no results of it working.
I have a several Hamvoip Allstar nodes running with an autopatch function and works just fine.
This is only an issue with ALS3 ver. 13, the latest download as of 10/13/24
N7JYS
If you followed the instructions, then why are you trying to set quiet=0 when the instructions clearly say to set quiet=1?
Because I what to hear a dial tone indicating to me the patch is ready for a phone number to be entered. This setting does not nor should it stop the phone patch from working and sending an error. As I have previously mentioned I have 5 hamvoip allstar node running with phone patch properly working with quite=0.!! This is an ASL3 issue!! I have been running hamvoip Allstar for over 10 years with no issues and they all send out a dial tone!
In ASL3 version 13 it does not matter if quite is set to 1 or 0 as I get the same error.
[2024-10-14 16:15:41.569] WARNING[34567]: app_rpt/rpt_bridging.c:567 rpt_play_tone: Cannot start tone on DAHDI/pseudo-194450514
– Hungup ‘DAHDI/pseudo-556167383’
– Hungup ‘DAHDI/pseudo-194450514’
Doug (WA3DSP) and David (K4FXC) with Hamvoip.org have been wonderful about fixing the version of Allstar minus the criticism! Besides their version of software worked right from the get go without the additional need for programing instruction and additional creation of files and or modules.
N7JYS
Do you have the following in modules.conf.
load => bridge_simple.so
Yes I have added this module to the file modules.conf
Cool, I was just pointing out that the error you’re experiencing has nothing to do with my GitHub instructions. The “cannot start tone” error in ASL3 is already known and is being tracked in their GitHub repo.
ASL3 is beta software. If you’re not prepared to deal with a couple of bugs that come with 15+ years of improvements, then don’t use it yet. You can stick with the other flavor that is still running code from 2 decades ago.
Or, use the beta software and politely assist with proper bug reports via GitHub rather than bashing the devs with nasty forum posts full of finger pointing and exclamation points.
If you followed the instructions, then why are you trying to set quiet=0 when the instructions clearly say to set quiet=1?
Nasty? Really?
Quite = 1 was a work-around to at least make it work without dial tone
and other audio prompts.
This has been flawed for the last 2 versions and I can confirm it is still present in the asl3
without any work around for it so far, quite=1 or not.
Unless someone has a new work-around or a change for proper setting not documented ?
ASL v1.01 & 2.0b6 quite=1 will at least allow it to work.
The proper setting is to not use quite at all or quite = 0
unless you don’t want the voice and dial tone.
Without authority, I have guessed the issue was in dahdi.
If my memory serves me well, it originally worked in asl 1.01 then a update to dahdi somewhere along the line broke it.
Was unnoticed by me as I use quite anyway.
But don’t pull out to many hairs on it.
Well Im glad it worked for you. I even tried both quiet = 0 and 1 and even eliminated it all together in the stanza but got the same results.
What version of DAHDI are you running? Are you running the ASL3-provided DKMS package and is it upgraded to v3.4.0-4+asl? There was some changes to address an autopatch bug.
Also, “threatening” to keep using HamVOIP isn’t helpful. We’re more than happy to help try to debug and fix the issue, but we need information and it’s likely going to take more than a day to fix. Not the least reason for which one of the main developers is doing hurricane recovery work in the Carolinas. Simply saying “it’s been broken for years and HamVOIP fixed it” isn’t actionable debugging information. HamVOIP’s software is not developed in the open so no one working on modern ASL but them knows what the issue was that fixed it nor are we able to incorporate the code into ASL3.
Thank you for adding your information to bug app_apt/#383 - that will be very helpful.
Upgraded one of my ASL3 boxes yesterday and still getting nowhere besides the dreaded “cannot start dialtone” error.
Looks like my issue is still open but not assigned etc
Thanks. 73
Kyle
K0KN
It’s just an error message that can easily be worked around. Just use quiet=1 and it works fine.
Thanks for the reply.
Unfortunately quiet=1 doesn’t work as it has in past releases. From what i have read here and Github, it’s a known bug
N7JYS’s initial post didn’t seem nasty at all. It looks like you just took offense to it or took it out of context automatically. He was posting his issue here which is what these discussions are for.