From: Johan Hedberg <johan.hedberg@gmail.com>
To: Vikram Kandukuri <Vikram.Kandukuri@Atheros.com>
Cc: Jothikumar Mothilal <Jothikumar.Mothilal@Atheros.com>,
"marcel@holtmann.org" <marcel@holtmann.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: HSP Ring command
Date: Wed, 17 Jun 2009 19:34:29 +0300 [thread overview]
Message-ID: <20090617163429.GA14295@jh-x301> (raw)
In-Reply-To: <44EE5C37ADC36343B0625A05DD408C485068E39C75@CHEXMB-01.global.atheros.com>
Hi,
Please don't use top posting on this list. The flow of quoted emails gets
messed up when inline and top posting are mixed.
On Wed, Jun 17, 2009, Vikram Kandukuri wrote:
> Do we have any VOIP application like SKYPE which has implemented D-Bus
> methods for incoming/outgoing/call hold indications?
AFAIK no.
> If we do not use *RING* indication for inband ring from HSP 1.2 I wonder
> why BQB tests for HSP still have a test case where we have to send
> AT+RING command when we place a call.
I'm not sure what you're referring to here. I've never heard of an AT+RING
AT command. Also the HSP spec has no mention of such a thing and actually
the AG is never sending AT commands to the headset but only responses to
AT commands or unsolicited result codes like the RING indication.
If you were talking about the RING indication and not an AT command, then
it should depend on what kind of PICS values you have selected. It is
possible to disable the RING requirement for the AG role completely with
HSP 1.2.
Johan
next prev parent reply other threads:[~2009-06-17 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 12:49 HSP Ring command Jothikumar Mothilal
2009-06-17 15:45 ` Johan Hedberg
2009-06-17 16:05 ` Vikram Kandukuri
2009-06-17 16:34 ` Johan Hedberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-17 12:37 Jothikumar Mothilal
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=20090617163429.GA14295@jh-x301 \
--to=johan.hedberg@gmail.com \
--cc=Jothikumar.Mothilal@Atheros.com \
--cc=Vikram.Kandukuri@Atheros.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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