[Asterisk-Users] Cannot compile chan_bluetooth on Asterisk 1.2.1

[Nilesh Londhe]

Hi Joseph:

>>I still couldn't compile the newest cvs version of chan_bluetooth, so
>>I again tried my trick of using the Makefile from an older version
>>(which used .tmp to compile) and it worked!

Can you please point to the cvs you used, the location and content of
pin files you created and paste a copy of the make file that worked
for you?

Appreciate you sharing this information. Thanks.

On 1/20/06, Joseph Tanner <joseph at thetechguide.com> wrote:
> Ok, I did get this going (somewhat), and in case someone else has the
> same issues I'll detail what I had to do.
>
> First, I was using the instructions at
> http://mundy.org/blog/index.php?p=79.  They stated that Asterisk at Home
> 2.2 already had all the rpms necessary for bluetooth and that I could
> skip the yum install step.  I did, however, run the command anyways
> after a few failed attempts.  There's an error in the rpm name, they
> tell you to install bluez-libs, the correct name is bluez-libs-devel
> (at least, that's what I needed to install).
>
> I still couldn't compile the newest cvs version of chan_bluetooth, so
> I again tried my trick of using the Makefile from an older version
> (which used .tmp to compile) and it worked!  Once compiled, I
> installed and started up asterisk.  I then received a message on my
> phone asking if I wanted to allow asterisk to connect, and then asked
> for a pin.  This took a bit of figuring out, but I got passed that.
> In /etc/bluetooth/hcid.conf, there's a line that says "pin_helper
> /usr/bin/bluepin;" (it may have a different path, the important thing
> is the pin_helper part).  Now backup the script in question, i.e. in
> my case mv /usr/bin/bluepin /usr/bin/bluepin.bak.  Use your editor of
> choice to create a new file with the same name, and in it enter:
>
>
> #!/bin/sh -e
> echo "PIN:1234"
>
> Replace the 1234 with whatever you want your pin to be.  I don't know
> if this is necessary, but I also edited /etc/bluetooth/pin to read:
>
> 1234
>
> Again, 1234 should be whatever you want your pin to be.  I then
> stopped asterisk, stopped the bluetooth service, started the bluetooth
> service back up, started asterisk, then when my phone asked for a pin
> I put in 1234, and it worked!
>
> You may also need to make another edit to hcid.conf, under Local
> Device Class change it to read class "0x200404;" or possibly "class
> 0x700408;".  This makes your bluetooth dongle look like a headset, and
> not a data device (I experienced some flakiness until I changed this).
>
> Now, I edited /etc/asterisk/bluetooth.conf appropriately (changed the
> channel for the phone to 7, it's a Motorola V551), started it all up,
> made some test calls and...no audio!  The cellphone works  great
> otherwise.  It'll connect, stay connected as long as I want it to, and
> when I hang up the asterisk extension the cellphone will disconnect
> too.  Too bad I didn't realize 611 was a free call until after I made
> a lot of test calls (it's a prepaid phone).  I did call our home
> number directly to see if maybe I just had a one-way audio problem,
> but nobody could hear a thing on either end.  I will continue to
> troubleshoot this before I ask another question about it, but it's not
> looking good.  BTW, the usb dongle I'm using is a Linksys USBBT100.
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> Asterisk-Users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>