- Member Success Stories (
-   -   Skype Bluetooth Headset (

TB0ne 08-09-2009 04:55 PM

Skype Bluetooth Headset
After getting Skype working well under OpenSuSE 11.1 with my hard-wired devices, I thought I'd branch out.....

I use the Vaio CS110E laptop, with built-in bluetooth. Mice, keyboards, etc., all worked well, but haven't done headset/headphones.

To get your Bluetooth headset working, create an .asoundrc file in your home directory, with the following contents:

pcm.Dragon {
              type bluetooth
              device "00:11:22:33:44:55"
              profile "voice"

I use a Callpod Dragon headset, so feel free to change the "Dragon" above, to something a bit more user-friendly for yourself. Replace the Bluetooth "MAC" address with the one for your headset. You can get this by putting your headset into discoverable mode, then running:


hcitool scan
and you should see the address. Run Skype, then choose it as your input/output device.

NOTE ABOUT PAIRING! The Callpod Dragon V2 can pair with two devices. Most (from what I know), can only pair with one. The first time I ran Skype with the headset selected, it popped up a pairing connection window. After that, no problems. If your headset is already paired with your phone, pairing it with your PC may break that connection. Not a huge deal...headset pairing is simple to do, but it can be a pain.

TB0ne 11-23-2009 10:30 PM


The steps I mentioned in my previous post about getting Skype to work at all (adding to the Pulse groups, etc.), are still valid in 11.2, as is the $HOME/.asoundrc file.

BUT! I accidently omitted a step:

The following commands need to be run:

rfcomm connect 11:22:33:44:55:66
rfcomm bind 11:22:33:44:55:66

This will pop up the pairing dialog, and allow the headset to be talked to, via the .asoundrc. Also, edit the /etc/bluetooth/rfcomm.conf file. Add the following:

rfcomm0 {
      # Automatically bind the device at startup
      bind no;

      # Bluetooth address of the device
      device 11:22:33:44:55:66;

      # RFCOMM channel for the connection
      channel 1;

      # Description of the connection
      comment "Your device name";

Obvioulsy, replace the 11:22, etc, with your real Bluetooth 'mac' address, and modify the rfcomm0 to be a different #, if you've already got auto-paired devices in your rfcomm.conf.

All times are GMT -5. The time now is 12:08 PM.