public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Jothikumar Mothilal <Jothikumar.Mothilal@Atheros.com>
Cc: "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 18:45:29 +0300	[thread overview]
Message-ID: <20090617154529.GA12943@jh-x301> (raw)
In-Reply-To: <44EE5C37ADC36343B0625A05DD408C485068E39C2B@CHEXMB-01.global.atheros.com>

Hi Jothi,

On Wed, Jun 17, 2009, Jothikumar Mothilal wrote:
> I am running HSP profile test cases with PTS tool.
> I am using Ubuntu 9.04 with Bluez 4.32.
> 
> For all HSP test cases, PTS is expecting RING command from IUT.
> From our analysis, headset_send(hs, "\r\nRING\r\n"); " in
> audio/headset.c is not getting initiated.
> I am thinking, RING command is suppose to send by dbus as we register
> the call backs. But dbus is not triggering the RING command.
> Is this expected behavior in BlueZ?

There is the IndicateCall D-Bus method in the org.bluez.Headset interface
which you can use (see doc/audio-api.txt for more info). However for
proper telephony integration you'll need to use a telephony driver (see
audio/telephony-*.c) so that the call indication occurs because of a real
call event of your telephony subsystem.

By default bluez compiles in the dummy telephony driver which provides a
simple D-Bus interface to drive it. There's also a python test script for
it in test/test-telephony which you can use to simulate telephony events.
E.g. "test-telephony incoming 1234" would simulate an incoming call from
the number "1234" and should cause the RING to be sent for HSP
connections.

Also note that starting with version 4.33 bluez uses HSP version 1.2 which
does *not* use the RING indication when the AG has been configured to use
inband-ringtone (for out-of-band ringing it's still used). However 4.32
(which you have) still has HSP 1.1 where the RING indication will always
be sent.

Johan

  reply	other threads:[~2009-06-17 15:45 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 [this message]
2009-06-17 16:05   ` Vikram Kandukuri
2009-06-17 16:34     ` Johan Hedberg
  -- 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=20090617154529.GA12943@jh-x301 \
    --to=johan.hedberg@gmail.com \
    --cc=Jothikumar.Mothilal@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