From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH v2] hfpmodem: Handle repeated held call indicator
Date: Tue, 12 Jan 2016 10:31:59 -0600 [thread overview]
Message-ID: <56952A7F.7050001@gmail.com> (raw)
In-Reply-To: <1452611009-15781-1-git-send-email-kubax.t.pawlak@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
Hi Kuba,
On 01/12/2016 09:03 AM, Kuba Pawlak wrote:
> An issue with iPhone 5C iOS 9.2 triggers desynchronization in call
> states. When an active call is put on hold and another call arrives,
> it is in WAITING state. It should be possible to answer it by issuing
> AT+CHLD=2 but the phone changes its state to INCOMING so ATA should be
> used. This change is advertised by sending callheld:2 event, but it is
> not handled. This event can be used to trigger CLCC poll to synchronize
> call states.
>
> +CIEV: 3,1 <- first call arrives
> AT+CLCC
> +CLCC: 1,1,4,0,0,"01234567890",129
> OK
> RING
> +CLIP: "01234567890",129
> ATA
> OK
> +CIEV: 2,1
> +CIEV: 3,0.
> AT+CHLD=2.$ <- first call is put on hold
> OK
> +CIEV: 7,2 <- notification confirming that call #1 is on hold
> +CCWA: "09876543210",129,1 <- second call arrives
> +CIEV: 7,2
> +CIEV: 3,1
> AT+CLCC
> +CLCC: 1,1,1,0,0,"01234567890",129
> +CLCC: 2,1,5,0,0,"09876543210",129 <- new call is still in WAITING state
> OK
> +CIEV: 7,2 <- phone iternally promotes WAITING call to INCOMING
> AT+CHLD=2 <- there is no WAITING call anymore, ATA should be used
> +CME ERROR:3
> ---
> drivers/hfpmodem/voicecall.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
Applied, thanks.
Regards,
-Denis
prev parent reply other threads:[~2016-01-12 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 15:03 [PATCH v2] hfpmodem: Handle repeated held call indicator Kuba Pawlak
2016-01-12 16:31 ` 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=56952A7F.7050001@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