-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DTMF via IAX VOIP connection fails #435
Comments
When you say "Before latest update, it WAS operational.", what update are you referring to? Are you saying that you have been regularly updating your node and a recent ASL3 update/upgrade changed the behavior without your having made any configuration changes? Can you attach the ... and, if not obvious in ... and, yes, you should remove any passwords? Note: you may need to add a ".txt" extension to the filenames to keep GitHub happy. |
Right now Jessie is researching, so let me wait till he’s done and report back if he found a reason from his side…
See answers below
From: Allan Nathanson ***@***.***>
Sent: Wednesday, December 18, 2024 8:20 PM
To: AllStarLink/ASL3 ***@***.***>
Cc: Wayne Spivak ***@***.***>; Author ***@***.***>
Subject: Re: [AllStarLink/ASL3] DTMF via IAX VOIP connection fails (Issue AllStarLink/app_rpt#435)
When you say "Before latest update, it WAS operational.", what update are you referring to? Are you saying that you have been regularly updating your node and a recent ASL3 update/upgrade changed the behavior without your having made any configuration changes?
I update the Pi daily, and ASL did a update a week or two ago???, well I updated. I changed nothing with the HOIP node (1500) or IAX/Extensions from the time I installed. Since that time, I’ve updated the Extensions commands per Jason (Jessie agreed) and I, today as I said changed jitterbuffer. Other than that, no changes.
Can you attach the rpt.conf and extensions.conf files from your node?
... and, if not obvious in rpt.conf, add some notes to this issue noting the node(s) in play (e.g. what nodes are connected, what node you are entering *99, etc)
... and, yes, you should remove any passwords?
Note: you may need to add a ".txt" extension to the filenames to keep GitHub happy.
—
Reply to this email directly, view it on GitHub <#435> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB4D5CTNBCSW3CXK4Z3JHVL2GINLRAVCNFSM6AAAAABT33VAS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJSGU3TOMBSGM> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AB4D5CSQ6O7UOWLMDZCBRMD2GINLRA5CNFSM6AAAAABT33VAS2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUYEU576.gif> Message ID: ***@***.*** ***@***.***> >
|
I guess he wasn't successful, so the files are here that were requested. |
HOIP says this is a recurring, occasional error on my node:
|
Using HOIP on an Asterisk 20.10.0+asl3-3.1.0-1.deb12, DTMF fails after connection to the private node.
The HOIP softphone connects in monitor mode, but I am unable to get node to decode *99. Gescio Alpuro, WH6AV of HOIP tried to get it to work on my node without success. Before latest update, it WAS operational.
Currently: DTMF works via CLI and/or RF connected to node.
Tried setting jitterbuffer to "NO" (via Jason N8EI) and it refuses to maintain a connection to HOIP.
The text was updated successfully, but these errors were encountered: