From: Denis Kenzior <denkenz@gmail.com>
To: Adam Pigg <piggz1@gmail.com>, ofono@lists.linux.dev
Subject: Re: [PATCH 4/4] qmimodem: voicecall: Implement DTMF tones
Date: Tue, 23 Apr 2024 10:01:10 -0500 [thread overview]
Message-ID: <81f70af9-4659-495b-9928-14d4286ea80e@gmail.com> (raw)
In-Reply-To: <1934099.7Z3S40VBb9@adam-laptop-hp>
Hi Adam,
On 4/23/24 05:10, Adam Pigg wrote:
> Hi Dennis
>
> Thanks for the thorough review and merging the others....
>
And thanks for doing all the hard work :)
<snip>
>>> +
>>> + CALLBACK_WITH_SUCCESS(vd->send_dtmf_cb, vd->send_dtmf_data);
>>
>> This calls back into oFono core unconditionally. Doesn't this imply that
>> you're handling only a single DTMF character?
>>
> Currently, ive only been able to test using single character invocations,
> using the num-pad on the phone app. Do you have any suggestions on how to
> trigger multiple characters?
Take a look at doc/voicecallmanager-api.txt. The SendTones() method takes a
string of tones, so there can be multiple tones per request. If your phone
dialer UI does not support sending multiple tones, then the easiest way is to
use a command line utility like 'dbus-send' (from dbus-1) or 'busctl' (from
systemd), or a graphical one like d-feet or qdbus.
Something like:
dbus-send --print-reply --system --dest=org.ofono /phonesim
org.ofono.VoicecallManager.SendTones string:"1234"
Replace /phonesim with the path of your modem device.
<snip>
>>
>> This function doesn't seem to be invoked?
> This function is passed into send_one_dtmf but yes, potentially goes unused,
> unless it gets invoked in the macro call? Ill double-check the original
> implementation to see if i messed anything up, but open to suggestions :)
I think your v4 implementation handled multiple characters correctly, just
FYI. Just the memory free paths were not completely correct.
Regards,
-Denis
next prev parent reply other threads:[~2024-04-23 15:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 19:49 [PATCH 1/4] qmimodem: voicecall: Implement call dialing Adam Pigg
2024-04-21 19:49 ` [PATCH 2/4] qmimodem: voicecall: Implement call answer Adam Pigg
2024-04-21 19:49 ` [PATCH 3/4] qmimodem: voicecall: Implement active call hangup Adam Pigg
2024-04-21 19:49 ` [PATCH 4/4] qmimodem: voicecall: Implement DTMF tones Adam Pigg
2024-04-21 20:06 ` Adam Pigg
2024-04-22 21:00 ` Denis Kenzior
2024-04-23 10:10 ` Adam Pigg
2024-04-23 15:01 ` Denis Kenzior [this message]
2024-04-23 21:54 ` Adam Pigg
2024-04-25 19:07 ` adam
2024-04-25 20:30 ` Denis Kenzior
2024-04-21 20:06 ` [PATCH 1/4] qmimodem: voicecall: Implement call dialing Adam Pigg
2024-04-22 21:05 ` Denis Kenzior
2024-04-22 21:10 ` patchwork-bot+ofono
-- strict thread matches above, loose matches on Subject: below --
2024-03-25 22:16 [PATCH 1/4] [qmimodem][voicecall] " Adam Pigg
2024-03-25 22:17 ` [PATCH 4/4] [qmimodem][voicecall] Implement DTMF tones Adam Pigg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81f70af9-4659-495b-9928-14d4286ea80e@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@lists.linux.dev \
--cc=piggz1@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox