I've seen it mentioned time and time again that using bluez-audio, the
bluetooth headset will not be enumerated as a sound device as other
devices are, like sound cards.  The answer seems to be always, "just
type in bluetooth where it wants a device selection".  Well, I guess
that's fine for an application that provides that.

But how does one deal with this problem with devices that enumerate
sound devices and provide a point-and-click-menu type interface for
them.  One example of such is Ekiga.

Despite my previous posting about my troubles with getting a BT headset
working on Ubuntu Hardy (my desktop workstation), I did manage to get it
working on Ubuntu Gutsy on my laptop.  i.e. I can successfully do:

$ arecord -D bluetooth -f S16_LE | aplay -D bluetooth -f S16_LE

and hear myself.  I'd like to use this headset with Ekiga though.  Any
ideas?

BTW: what's with the long pause opening the headset for playback?

20228 23:14:06 socket(PF_FILE, SOCK_STREAM, 0) = 3
20228 23:14:06 connect(3, {sa_family=AF_FILE, path=@/org/bluez/audio}, 110) = 0
20228 23:14:06 pipe([4, 5])             = 0
20228 23:14:06 fcntl64(4, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
20228 23:14:06 fcntl64(5, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
20228 23:14:06 send(3, "00:1A:45:1B:19:89\0\0\0\0\f\1\0\0\0\0\0\0\0\0\0"..., 34, 0) = 34
20228 23:14:06 recv(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\10\0010\0\2"..., 30, 0) = 30
20228 23:14:10 recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"m", 1}], msg_controllen=16, {cmsg_len=16, cmsg_level=SOL_SOCKET, cmsg_type=SCM_RIGHTS, {6}}, msg_flags=0}, 0) = 1
20228 23:14:10 recv(6, 0x8062324, 48, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily unavailable)

Notice the 4 seconds between sending and receiving a message on
the /org/bluez/audio socket.

b.