From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-bluetooth@vger.kernel.org
Subject: Error: Connection Rejected due to Limited Resources
Date: Wed, 30 Dec 2009 16:45:26 -0500 [thread overview]
Message-ID: <1262209526.9675.475.camel@pc.interlinx.bc.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 3706 bytes --]
Hi.
I am trying to play some audio to a headset with bluez 4.51 and getting
the following from hcidump -t -X -V:
HCI sniffer - Bluetooth packet analyzer ver 1.42
device: hci0 snap_len: 1028 filter: 0xffffffff
2009-12-30 08:54:19.708880 < HCI Command: Setup Synchronous Connection (0x01|0x0028) plen 17
handle 12 voice setting 0x0060
2009-12-30 08:54:19.711125 > HCI Event: Command Status (0x0f) plen 4
Setup Synchronous Connection (0x01|0x0028) status 0x00 ncmd 1
2009-12-30 08:54:20.478112 > HCI Event: Synchronous Connect Complete (0x2c) plen 17
status 0x0d handle 0 bdaddr 00:1A:45:1B:19:89 type SCO
Error: Connection Rejected due to Limited Resources
The command I am trying to play with is:
$ aplay /mnt/mp3/bad_mouth.wav -Dplug:bluetoothraw
Playing WAVE '/mnt/mp3/bad_mouth.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
aplay: pcm_write:1528: write error: Transport endpoint is not connected
Where bluetoothraw is defined as:
pcm.bluetoothraw {
type bluetooth
device 00:1A:45:1B:19:89
}
bluetoothd had to say at the time:
Dec 30 08:54:19 pc bluetoothd[7373]: Accepted new client connection on unix socket (fd=22)
Dec 30 08:54:19 pc bluetoothd[7373]: Audio API: BT_REQUEST <- BT_GET_CAPABILITIES
Dec 30 08:54:19 pc bluetoothd[7373]: Audio API: BT_RESPONSE -> BT_GET_CAPABILITIES
Dec 30 08:54:19 pc bluetoothd[7373]: Audio API: BT_REQUEST <- BT_OPEN
Dec 30 08:54:19 pc bluetoothd[7373]: open sco - object=ANY source=ANY destination=00:1A:45:1B:19:89 lock=write
Dec 30 08:54:19 pc bluetoothd[7373]: Audio API: BT_RESPONSE -> BT_OPEN
Dec 30 08:54:19 pc bluetoothd[7373]: Audio API: BT_REQUEST <- BT_SET_CONFIGURATION
Dec 30 08:54:19 pc bluetoothd[7373]: Audio API: BT_RESPONSE -> BT_SET_CONFIGURATION
Dec 30 08:54:19 pc bluetoothd[7373]: Audio API: BT_REQUEST <- BT_START_STREAM
Dec 30 08:54:19 pc bluetoothd[7373]: State changed /org/bluez/7365/hci0/dev_00_1A_45_1B_19_89: HEADSET_STATE_CONNECTED -> HEADSET_STATE_PLAY_IN_PROGRESS
Dec 30 08:54:20 pc bluetoothd[7373]: Audio API: BT_RESPONSE -> BT_START_STREAM
Dec 30 08:54:20 pc bluetoothd[7373]: Audio API: BT_INDICATION -> BT_NEW_STREAM
Dec 30 08:54:20 pc bluetoothd[7373]: State changed /org/bluez/7365/hci0/dev_00_1A_45_1B_19_89: HEADSET_STATE_PLAY_IN_PROGRESS -> HEADSET_STATE_CONNECTED
Dec 30 08:54:20 pc bluetoothd[7373]: Unix client disconnected (fd=22)
Dec 30 08:54:20 pc bluetoothd[7373]: client_free(0x14c5960)
Some info:
$ hciconfig -a
hci0: Type: USB
BD Address: 00:0D:18:01:3B:9B ACL MTU: 1017:8 SCO MTU: 64:0
UP RUNNING PSCAN ISCAN
RX bytes:3470820 acl:370 sco:67685 events:543 errors:0
TX bytes:9185 acl:338 sco:0 commands:201 errors:0
Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'pc-0'
Class: 0x0a0104
Service Classes: Networking, Capturing
Device Class: Computer, Desktop workstation
HCI Ver: 2.0 (0x3) HCI Rev: 0x4000 LMP Ver: 2.0 (0x3) LMP Subver: 0x430e
Manufacturer: Broadcom Corporation (15)
$ hcitool info 00:1A:45:1B:19:89
Requesting information ...
BD Address: 00:1A:45:1B:19:89
Device Name: Jabra BT125
LMP Version: 2.0 (0x3) LMP Subversion: 0x978
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xfc 0xfe 0x0b 0x00 0x08 0x08 0x00 0x00
<encryption> <slot offset> <timing accuracy> <role switch>
<hold mode> <sniff mode> <RSSI> <channel quality> <SCO link>
<HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD>
<paging scheme> <transparent SCO> <AFH cap. slave>
<AFH cap. master>
Any ideas what's going on/wrong?
Thanx,
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-12-30 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 21:45 Brian J. Murrell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-31 3:57 Error: Connection Rejected due to Limited Resources Brian J. Murrell
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=1262209526.9675.475.camel@pc.interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--cc=linux-bluetooth@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).