From: Moises Silva <moises.silva@gmail.com>
To: ofono@ofono.org
Subject: Re: Using ofono HFP
Date: Fri, 08 Oct 2010 13:59:21 -0400 [thread overview]
Message-ID: <AANLkTi=uppgrW4-Q_ZjZU=2QqwGj7jm0kLLyqQ4SDVbq@mail.gmail.com> (raw)
In-Reply-To: <33AB447FBD802F4E932063B962385B352DA74327@shsmsx501.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1631 bytes --]
On Thu, Oct 7, 2010 at 11:25 PM, Zhang, Zhenhua <zhenhua.zhang@intel.com> wrote:
>>
>> Where does this 48 comes from? I come from the TDM open source world,
>> where typical configuration for TDM devices is 160 (160 bytes of
>> alaw/ulaw, 160 samples, each 20ms).
>>
>> Is there any way to change that socket MTU to 160 or 320 (depending if
>> it's either SLN16 or alaw/mulaw?
>
> You might want to raise your question on bluez's IRC or mailing list. oFono takes care of call control logic while BlueZ/PulseAudio takes care of SCO audio packets.
I will do that. I just thought somebody around here could know.
>> How can I know the format for the audio?
>
> I think it should be PCM raw data from SCO packets but it could wrong maybe.
Just for the record. I found out the format is SLN16, but the MTU is
fixed and hard-coded in bluez to 48 bytes (that is 24 samples). I
don't know if the format is cell-phone specific or is always SLN16 for
MTU.
Just throwing another question in the air, what should be the best way
to go to use Ofono DBUS API from a C program?
I am trying to write the C version of ./list-modems Python script. I
see in the D-BUS page that they don't recommend using the bare bones
D-BUS C API but rather bindings, like glib bindings. What do you
think? I was trying to use glib for the list-modems C port, but got
stuck on which data type to use for the return value of the GetModems
API.
Thanks,
Moises Silva
Senior Software Engineer
Sangoma Technologies Inc. | 100 Renfrew Drive, Suite 100, Markham ON
L3R 9R6 Canada
t. 1 905 474 1990 x128 | e. moy(a)sangoma.com
next prev parent reply other threads:[~2010-10-08 17:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 15:51 Using ofono HFP Moises Silva
2010-09-27 0:26 ` Denis Kenzior
2010-09-27 0:37 ` Moises Silva
2010-09-28 1:26 ` Zhang, Zhenhua
2010-09-28 2:45 ` Moises Silva
2010-09-28 3:23 ` Zhang, Zhenhua
2010-09-28 3:57 ` Moises Silva
2010-09-29 2:33 ` Moises Silva
2010-09-29 2:44 ` Zhang, Zhenhua
2010-09-29 2:50 ` Moises Silva
2010-09-29 2:50 ` Denis Kenzior
2010-10-02 22:27 ` Moises Silva
2010-10-08 3:25 ` Zhang, Zhenhua
2010-10-08 17:59 ` Moises Silva [this message]
2010-10-14 12:00 ` Pekka Pessi
2010-10-22 14:05 ` Moises Silva
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='AANLkTi=uppgrW4-Q_ZjZU=2QqwGj7jm0kLLyqQ4SDVbq@mail.gmail.com' \
--to=moises.silva@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 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.