From: Georg Chini <georg@chini.tk>
To: ofono@ofono.org
Subject: Re: HFP HF - Reject SCO Issue
Date: Wed, 25 May 2016 18:30:53 +0200 [thread overview]
Message-ID: <5745D33D.40703@chini.tk> (raw)
In-Reply-To: <5745BD55.3030108@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2265 bytes --]
On 25.05.2016 16:57, 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.
>
Did you load module-bluetooth-discover with headset=ofono as argument?
Normally this should be sufficient to make it work. When the connection
is established,
pulseaudio automatically loads loopback modules for the phone. You might
have
to check if the modules have the correct source / sink.
Additionally to observing the log files, you can debug what is going on
by using
dbus-monitor to see the messages on the dbus.
> 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?
>
Unfortunately there is no HowTo as far as I know. Most stuff you find on
the net is outdated.
> Regards,
> -Denis
>
> _______________________________________________
> ofono mailing list
> ofono(a)ofono.org
> https://lists.ofono.org/mailman/listinfo/ofono
next prev parent reply other threads:[~2016-05-25 16:30 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 ` [pulseaudio-discuss] " Tanu Kaskinen
2016-05-25 16:30 ` Denis Kenzior
2016-07-13 14:47 ` PulseAudio bluetooth wiki page (was: HFP HF - Reject SCO Issue) Tanu Kaskinen
2016-05-25 16:30 ` Georg Chini [this message]
2016-05-26 18:22 ` [pulseaudio-discuss] HFP HF - Reject SCO Issue 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=5745D33D.40703@chini.tk \
--to=georg@chini.tk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.