Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] voicecall: fix release and answer existing call validation
Date: Thu, 19 Apr 2012 08:42:25 -0500	[thread overview]
Message-ID: <4F901641.2020104@gmail.com> (raw)
In-Reply-To: <1334873443-21124-1-git-send-email-puffy.taco@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]

Hi Michael,

On 04/19/2012 05:10 PM, Mike Brudevold wrote:
> From: Michael Brudevold <michael.brudevold@logicpd.com>
> 
> Release and answer should be allowed when there are held calls as well as the
> existing check for waiting calls.  Most implementations use AT+CHLD=1 which
> will resume the other call, be it waiting or held.  This follows the HFP,
> GSM 07.07 and 3GPP 27.007 specs.
> ---
>  src/voicecall.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 

This isn't really a bug, but an explicit choice we made with the API.
See the previous discussion here:
http://lists.ofono.org/pipermail/ofono/2011-January/008029.html.

For HFP this is further made funny by the fact that CHLD=1X is supposed
to retrieve the held call automatically for you by the AG according to
section 4.32.1, making CHLD=1 behavior in question somewhat redundant.

However, I do see that this could be useful, so I suggest we add a new
ReleaseAndSwap method.  I prefer this approach especially since the
current D-Bus API is frozen and I don't want to modify the behavior of
existing methods.

Regards,
-Denis

  reply	other threads:[~2012-04-19 13:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 22:10 [PATCH] voicecall: fix release and answer existing call validation Mike Brudevold
2012-04-19 13:42 ` Denis Kenzior [this message]
2012-04-21  1:34   ` Mike

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=4F901641.2020104@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