Open Source Telephony
 help / color / mirror / Atom feed
From: Tanu Kaskinen <tanuk@iki.fi>
To: ofono@ofono.org
Subject: Re: [pulseaudio-discuss] HFP HF - Reject SCO Issue
Date: Wed, 25 May 2016 19:22:48 +0300	[thread overview]
Message-ID: <1464193368.13843.65.camel@iki.fi> (raw)
In-Reply-To: <5745BD55.3030108@gmail.com>

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

On Wed, 2016-05-25 at 09:57 -0500, Denis Kenzior wrote:
> Hi John,
> 
> On 05/25/2016 06:01 AM, Jomon John wrote:
> > Hi,
> > 
> > I am trying to configure HFP with Bluez(5.34), Ofono(1.17) and
> > pulseaudio(6) on a Freescale i.MX6 board using Linux 4.1.15 kernel,
> > the idea is to use the target board in HFP/Handsfree Unit role. The
> > bluetooth controller is a Pluggable USB Bluetooth Dongle (0a5c:21e8
> > - BCM20702A0) with updated firmware.
> > 
> > The procedure followed is,
> > 
> > * Pair & connect with the android mobile phone with the bluetoothctl
> > * Enable modem and dial number using ofono test scripts
> > 
> > After this the call is being made but the audio routing fails with
> > "Reject SCO : Agent not registered" message from oFono. While
> > checking with btmon its found that the SCO Connect Request has been
> > rejected with the reason of limited resources(0x0d).
> > 
> > Can anyone help me to identify the root cause, I spent a lot of
> > time trying different version combinations, loading firmware and
> > checking logs but still nothing.
> 
> This looks like a problem with PulseAudio configuration. oFono does not 
> handle SCO data, PulseAudio does that. In order to do that, PulseAudio 
> needs to register an agent with oFono. Then the SCO socket will be 
> established and the fd handed off to PulseAudio to process the audio data.
> 
> I have no idea how this is accomplished in PulseAudio.  This question is 
> being asked fairly often recently.  Does PulseAudio have an 
> FAQ/documentation for this yet?

In /etc/pulse/default.pa, add parameter headset=ofono to module-
bluetooth-discover. That should be all that's needed at PulseAudio
side.

Denis, would you be willing to help me with the oFono parts, if I write
a document explaining how to make bluetooth audio work with
BlueZ5+PA+oFono?

-- 
Tanu

  reply	other threads:[~2016-05-25 16:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-25 11:01 HFP HF - Reject SCO Issue Jomon John
2016-05-25 14:57 ` Denis Kenzior
2016-05-25 16:22   ` Tanu Kaskinen [this message]
2016-05-25 16:30     ` [pulseaudio-discuss] " Denis Kenzior
2016-07-13 14:47       ` PulseAudio bluetooth wiki page (was: HFP HF - Reject SCO Issue) Tanu Kaskinen
2016-05-25 16:30   ` HFP HF - Reject SCO Issue Georg Chini
2016-05-26 18:22     ` [pulseaudio-discuss] " Jomon John
2016-05-27 19:18       ` Jomon John
2016-05-28 12:11         ` Georg Chini
2016-06-07  7:53           ` Jomon John
2016-06-07  8:31             ` Georg Chini
2016-06-07 10:11               ` Jomon John
2016-06-07 10:55                 ` Georg Chini
2016-06-07 12:47                   ` Jomon John
2016-06-07 13:22                     ` Georg Chini
2016-06-07 15:23                       ` Jomon John
2016-06-07 19:10                         ` Georg Chini
2016-06-09 16:59                           ` Jomon John
2016-06-09 19:37                             ` Georg Chini

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=1464193368.13843.65.camel@iki.fi \
    --to=tanuk@iki.fi \
    --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