-
Notifications
You must be signed in to change notification settings - Fork 349
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 A isn't working. #552
Comments
You say "Firmware: 2.1.27". What do you mean? This is the original stock firmware, not my firmware, in that case I have nothing to do with this. @AsciiWolf you mentioned this issue. Initially I confused it with something else. What problem do you have here? |
Oops! I did not notice what firmware version the author of this ticket mentioned. I personally did not test this, but if it does not happen with the Egzumer firmware, there is nothing to fix and this ticket can be closed and/or ignored. :-) |
My bad on the firmware as I had a 2nd radio here at the time. I have firmware EGZUMER 502300b. |
I did all the tests before to make sure that it is all hunky dory with DTMF tones so I don't see what may be the issue. Read through #85. There is a description of all steps to diagnose what is the issue. Use other radio that works and compare what is the difference. You can also record the audio and share here so I can compare. |
I was setting up HamVOIP and reached the DTMF testing stage of Asterisk. All DTMF codes work as expected except the letter A.
I saw issue 85 (closed) where something went wrong with 6.
#85
It was suggested to try the DTMF decoding app:
https://play.google.com/store/apps/details?id=com.arcoirislabs.dtmfencdec.app&pcampaignid=web_share
The app successfully decoded all DTMF codes except A.
Radio: Quansheng UV-K5
Firmware: 2.1.27
Behavior was repeated on a 2nd Quansheng UV-K5
Update: after mucking around with position of uv-k5 speaker near phone, app has picked up the letter A a few times.
Asterisk still refuses to detect it but detects all others fine.
The text was updated successfully, but these errors were encountered: