From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCHv3 1/3] hfpmodem: Retry AT+CLCC request after outgoing callsetup
Date: Wed, 27 Mar 2013 00:05:53 -0500 [thread overview]
Message-ID: <51527E31.4090604@gmail.com> (raw)
In-Reply-To: <da43e0125ebcdf570d287d3d84fbf139cc2bfa9e.1360663430.git.timo.mueller@bmw-carit.de>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
Hi Timo,
On 02/13/2013 02:36 AM, Timo Mueller wrote:
> From: Timo Mueller<timo.mueller@bmw-carit.de>
>
> Currently the list of current calls is requested right after an
> outgoing callsetup has been reported by the AG device. If the AG
> device updates the list after reporting the callsetup the +CLCC
> response may not contain the new call and it is not registered
> with oFono.
>
> In this case AT+CLCC should be requested again once after a small
> delay.
>
> AT sequence that exhibited the failure (AG device was a Nokia N9
> placing an outgoing call)
>
> < \r\n+CIEV: 5,2\r\n
>> AT+CLCC\r
> < \r\nOK\r\n
> < \r\n+VGS=7\r\n
> < \r\n+VGM=7\r\n
> < \r\n+CIEV: 5,3\r\n
> < \r\n+CIEV: 4,1\r\n
> < \r\n+CIEV: 5,0\r\n
> ---
> v3: Splitted clcc_poll_cb to avoid parsing of the clcc result twice
> when a dialing call was found in the response.
I'm fine with this version, however I still would prefer that we hid the
poll-for-dialing logic behind the N9 vendor quirk.
Regards,
-Denis
prev parent reply other threads:[~2013-03-27 5:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 8:36 [PATCHv3 1/3] hfpmodem: Retry AT+CLCC request after outgoing callsetup Timo Mueller
2013-02-13 8:36 ` [PATCHv3 2/3] hfp_hf: Add generic hfp modem vendor Timo Mueller
2013-02-13 8:36 ` [PATCHv3 3/3] hfpmodem: Add N9 quirk to run CLCC after callheld=<2 or 3> Timo Mueller
2013-03-26 9:25 ` Timo =?unknown-8bit?q?M=C3=BCller?=
2013-03-27 5:13 ` Denis Kenzior
2013-03-27 5:09 ` [PATCHv3 2/3] hfp_hf: Add generic hfp modem vendor Denis Kenzior
2013-03-27 5:05 ` Denis Kenzior [this message]
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=51527E31.4090604@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.org \
/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