public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] How to know the packet loss ratio of SCO socket
Date: Mon, 18 Aug 2008 07:10:41 +0200	[thread overview]
Message-ID: <1219036241.7591.15.camel@violet.holtmann.net> (raw)
In-Reply-To: <loom.20080815T184330-967@post.gmane.org>

Hi,

> > SCO are voice connections and they are CVSD encoded. It is not a  
> > reliable data transport. Use L2CAP or RFCOMM for that.
>
> I think you are right.
> My original purpose is to test the voice quality when 12 SCO server-client pairs
> are running in the same room (which means 12 small piconets contending the
> channel, although each pair has its own frequency hopping pattern).
> 
> Is there any good way to gather the voice quality information? (actually I don't
> know how to tell a voice qualify is "acceptable" to human ears. is there any
> good references?)

I have no idea. However you will see interference if the devices are
close. SCO consumes a fixed amount bandwidth.

Regards

Marcel



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2008-08-18  5:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-15 13:42 [Bluez-devel] How to know the packet loss ratio of SCO socket Jui-Hao Chiang
2008-08-15 13:50 ` Jui-Hao Chiang
2008-08-15 17:26 ` Marcel Holtmann
2008-08-15 18:50   ` Jui-Hao Chiang
2008-08-18  5:10     ` Marcel Holtmann [this message]

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=1219036241.7591.15.camel@violet.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /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