headset not connecting, pin issue?

Hello all. I have searched around and seen people with similar issues but have not found a solution yet.

I am trying to connect a headset to a linux box with a usb Bluetooth dongle. I would like to listen to music through the headset.

When I run mplayer -ao alsa:device=Bluetooth song.mp3, I get:

alsa-lib: pcm_bluetooth.c:1145:(bluetooth_init) Connection fail
alsa-init: playback open error: Connection refused Could not open/initialize audio device -> no sound.

Which tells me that it sees the .asoundrc file and is trying to play via Bluetooth. However, I do not think that the headset is connected. So, when I hit the button on the headset, I get the following from the hcidump. Keep in mind that I have hcid.conf configured so that it points to a pin file with the echo PIN="0000"
pin_helper /home/root/bluepin; (in hcid.conf)
#!/bin/sh (in bluepin with chmod 777)
echo "PIN:0000"

root@sarge-at91:/etc/bluetooth$ > HCI Event: Connect Request (0x04) plen 10
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7

< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22

< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2

< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4

< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4

    L2CAP(s): Connect req: psm 1 scid 0x004e
< ACL data: handle 11 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x004e result 0 status 0
      Connection successful

    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 48
< ACL data: handle 11 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x004e flags 0x00 result 0 clen 4
      Success
      MTU 48
< ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x004e flags 0x00 clen 0

< HCI Command: Remote Name Request (0x01|0x0019) plen 10

    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success

    L2CAP(d): cid 0x0040 len 15 [psm 1]
        SDP SS Req: tid 0x1 len 0xa
          pat uuid-32 0x111f (Handsfree AG)
          max 40
          cont 00
< ACL data: handle 11 flags 0x02 dlen 14
    L2CAP(d): cid 0x004e len 10 [psm 1]
        SDP SS Rsp: tid 0x1 len 0x5
          count 0
          cont 00

    L2CAP(d): cid 0x0040 len 15 [psm 1]
        SDP SS Req: tid 0x2 len 0xa
          pat uuid-32 0x1112 (Headset AG)
          max 40
          cont 00
< ACL data: handle 11 flags 0x02 dlen 14
    L2CAP(d): cid 0x004e len 10 [psm 1]
        SDP SS Rsp: tid 0x2 len 0x5
          count 0
          cont 00

    L2CAP(s): Disconn req: dcid 0x0040 scid 0x004e
< ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x004e

I see from this that it sees the headset but is not connecting. I don't know if it is because of the pin not connecting, or if the hcid.conf is not correct. Can anyone offer a suggestion on this?

I can post more info if anyone needs something that I have not put in here.

Thanks
Christopher

Internal Virus Database is out-of-date.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.15.34/1134 - Release Date: 11/16/2007 9:52 AM

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Sorry for the previous post as I am further along than I thought. This may be the wrong list but I'll continue what I found in the hopes that someone can tell me where I have gone wrong and what I need to do.

I think the issue is that the audio service has not started. I did a hciconfig -a and I don't see that in the services. I do see audio.service in the /etc/bluetooth directory.

I don't have python installed as this is an embedded system, but I would like to have the audio service running (which may be what needs to connect alsa to bluetooth).

Currently, I am able to connect to the headset via rfcomm and it does the pin and connection correctly.

Any help in this regard would be appreciated.

Christopher

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users