linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jerry Geis <geisj@pagestation.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] not getting audio
Date: Wed, 04 Jan 2006 21:17:10 -0500	[thread overview]
Message-ID: <43BC81A6.3040800@pagestation.com> (raw)

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

all,

I am using a kensington bluetooth adapter 2.0, with a plantronics 510 
headset.
I am using centos 4.2, asterisk 1.2.1 and chan_bluetooth. All that is 
installed
and I can place a call to my bluetooth headset. I hear the ring in my 
ear I see
the ring on the asterisk console. When I answer I hear NO audio.

The console gives errors "chan_bluetooth/chan_bluetooth.c:685 sco_thread 
wrote <48 to sco".

I dont seem to have the hciconfig to run hciconfig -a.

I am wondering what else I can give you so I might be able to get audio or
is there something I just plane missed?

I can ping with l2ping my headset.

Thanks,

Jerry





[-- Attachment #2: Type: text/html, Size: 985 bytes --]

                 reply	other threads:[~2006-01-05  2:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=43BC81A6.3040800@pagestation.com \
    --to=geisj@pagestation.com \
    --cc=bluez-users@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;
as well as URLs for NNTP newsgroup(s).