[Asterisk-Users] Cannot compile chan_bluetooth on Asterisk 1.2.1

Joseph Tanner joseph at thetechguide.com
Wed Jan 25 23:28:43 MST 2006


Again, my documentation is still sparse.  I should have noted that the
phone will recognize asterisk and connect even if the channel in
bluetooth.conf is configured wrong.  You'll just get no audio, or
disconnects, or what-not until it's set correctly.  So realize that
later on when you're testing.  Also the usb dongle must have a CSR
chipset, else it won't work (well, at least probably won't work, I'll
provide instructions on how to tell if it should work or not later).

Here's the relevant instructions on
http://www.crazygreek.co.uk/content/chan_bluetooth for how to dial
out:  Send a call out by using Dial(BLT/DevName/0123456).

As far as dialing in, there's a special context (I think [bluetooth]
maybe?  I'll have to get back to you on that).  I know that it should
work fine, because I tried dialing the phone, asterisk picked it up
then immediately disconnected because there was no context for it to
go to (I think it tried to fall back on [default], which I didn't have
configured to accept an incoming call).

Good luck!

Joseph Tanner

On 1/26/06, Nilesh Londhe <lvnilesh at gmail.com> wrote:
> Thanks a lot. I succeeded in pairing my Sony Ericson T616 using your
> instructions at
> http://www.thetechguide.com/howto/asterisk/chanbluetooth.html without
> any problems. I rebooted and the phone prompted me to connect to
> asterisk. I provided the pin 1234 and voila it connected...
>
> Couple of observations:
>
> I started off with clean slate and booted off from A at H 2.2 CD.
> skipped the initial yum -u update part to save some time.
>
> When I ran the "sdptool search --bdaddr MACADDRESS 0x111F" command,
> below is what I got:
>
> Class 0x111F
> Searching on MACADDRESS
> Service Name: HF Voice Gateway
> Service RecHandle: 0x10007
> Service Class ID List:
> "" (0x111f)
> "Generic Audio" (0x1203)
> Protocol Descriptor List:
> "L2CAP" (0x0100)
> "RFCOMM" (0x0003)
> Channel: 6
> Profile Descriptor List
> "" 0x111e
> Version 0x0100
>
> Note that in /etc/asterisk/bluetooth.conf, I kept Channel = 3 (did not
> change it to 6) and it paired my tooth in the first attempt after I
> rebooted asterisk box.
>
> Now, I want to get rid of my Doc-N-Talk that I currently connect my
> T616 to and the other end of Doc-N-Talk goes to x100p.
>
> Although I have worked with linux a bit, I am basically an ASTERISK
> NEWBIE so please pardon my ignorane but I don't know what to do
> next...that is.. how to define this bluetooth channel to make and
> receive calls using this setup...
>
> Appreciate your help.
>
>
> On 1/25/06, Joseph Tanner <joseph at thetechguide.com> wrote:
> > Please note this is a work in progress:
> >
> > http://www.thetechguide.com/howto/asterisk/chanbluetooth.html
> >
> > Basically the bluetoothfiles.tar.gz has the cvs code with the Makefile
> > that worked for me, plus the edited Makefile in
> > /usr/src/asterisk/channels, and the bluez edits I needed (hcid.conf
> > with the correct profile, the files needed for the pin which is set to
> > 1234, etc.).  The guide is supposed to walk a person through the
> > entire process of getting an Asterisk box setup and bluetooth working,
> > but it's grossly incomplete.  Maybe it'll help you out.
> >
> > Joseph Tanner
> >
> > On 1/25/06, Nilesh Londhe <lvnilesh at gmail.com> wrote:
> > > 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
> > > >
> > > _______________________________________________
> > > --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
> > >
> > _______________________________________________
> > --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
> >
> _______________________________________________
> --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
>



More information about the asterisk-users mailing list