[Asterisk-Users] Cannot compile chan_bluetooth on Asterisk 1.2.1
Nilesh Londhe
lvnilesh at gmail.com
Thu Jan 26 21:57:41 MST 2006
Since T616 is not answering (and incoming calls are going to Cingular
voicemail after 30 sec,) I suspect the problem focus area is...
> -- Executing Answer("BLT/T616", "") in new stack
Is http://www.thetechguide.com/howto/asterisk/bluetoothfiles.tar.gz
tar xzf bluetoothfiles.tar.gz the latest source (r40?)
On 1/26/06, Nilesh Londhe <lvnilesh at gmail.com> wrote:
> Here are my findings with my experiment using Sony Erisson T616 with
> Cingular Service and connected to asterisk at home 2.2 on a freshly
> installed system and following the instructions
> http://www.thetechguide.com/howto/asterisk/chanbluetooth.html
>
> Outbound calls (Asterisk to T616 via bluetooth):
>
> Works OK via Dial(BLT/T616/8005551212)
>
> Inbound calling (T616 to asterisk via bluetooth):
>
> My configuration for inbound calls:
>
> [bluetooth]
> exten => s,1,Wait(1)
> exten => s,2,Answer
> exten => s,3,Dial(SIP/1007,15,rtT)
> exten => s,4,VoiceMail(1000 at default)
> exten => s,5,Hangup
>
> My observation:
>
> When I call my cell T616 from my landline, SIP/1007 rings for 2
> seconds and the call is answered by Cingular voicemail not by asterisk
> voicemail. My cingular voicemail is set to answer in 30 seconds after
> first ring.
>
> Output on the asterisk CLI:
>
> [root at asterisk1 ~]# asterisk -r
> Asterisk 1.2.1, Copyright (C) 1999 - 2005 Digium.
> Written by Mark Spencer <markster at digium.com>
> =========================================================================
> Connected to Asterisk 1.2.1 currently running on asterisk1 (pid = 3025)
> Verbosity is at least 3
> [AG] T616 > +CIEV: 2,4
> [AG] T616 > +CIEV: 2,3
> [AG] T616 > RING
> [AG] T616 > +CLIP: "4255551212",161,,,"Landline"
> -- Executing Wait("BLT/T616", "1") in new stack
> -- Executing Answer("BLT/T616", "") in new stack
> [AG] T616 < +CIEV: 2,1
> [AG] T616 < +CIEV: 3,0
> -- Executing Dial("BLT/T616", "SIP/1007|15|rtT") in new stack
> -- Called 1007
> -- SIP/1007-d97e is ringing
> == Spawn extension (bluetooth, s, 3) exited non-zero on 'BLT/T616'
> [AG] T616 < ATH
> [AG] T616 < AT+CHUP
> [AG] T616 > ERROR
> [AG] T616 > OK
> [AG] T616 < AT+BRSF=23
> [AG] T616 > ERROR
> [AG] T616 < AT+CIND=?
> [AG] T616 > +CIND:
> ("battchg",(0-5)),("signal",(0-5)),("batterywarning",(0-1)),("chargerconnected",(0-1)),("service",(0-1)),("sounder",(0-1)),("message",(0-1)),("call",(0-1)),("roam",(0-1)),("smsfull",(0-1))
> [AG] T616 > OK
> [AG] T616 < AT+CIND?
> [AG] T616 > +CIND: 5,3,0,1,1,0,0,0,0,0
> [AG] T616 > OK
> [AG] T616 < AT+CMER=3,0,0,1
> [AG] T616 > OK
> [AG] T616 < AT+CLIP=1
> [AG] T616 > OK
> [AG] T616 < AT+CGMI
> [AG] T616 > SONY ERICSSON
> [AG] T616 > OK
> [AG] T616 < AT+CGMI
> [AG] T616 > SONY ERICSSON
> [AG] T616 > OK
> [AG] T616 > +CIEV: 2,4
> [AG] T616 > +CIEV: 2,3
> asterisk1*CLI>
>
> On 1/26/06, Nilesh Londhe <lvnilesh at gmail.com> wrote:
> > BTW, I did get clear bidirectional audio when I succeded in dialing
> > out...(with the channel = 3 in /etc/asterisk/bluetooth.conf) I have
> > Sony Ericsson T616 connected to a cheap commodity bluetooth USB dongle
> > that I bought ages ago from meritline.
> >
> > On 1/26/06, Nilesh Londhe <lvnilesh at gmail.com> wrote:
> > > Thanks a billion.
> > >
> > > Outbound bluetooth dialling on the lines of
> > > Dial(BLT/DevName/8005551212) worked for me.
> > >
> > > Still trying out the inbound route. Before I created the [bluetooth]
> > > context, it tried to reach the [default] context but then I began by
> > > creating a new context [bluetooth] in extensions.conf and got my
> > > internal SIP phone to ring when I received a call on my SE T616 cell
> > > phone. However, I could not get the inbound line answered and I will
> > > continue to work on this over the weekend and report back my progress.
> > >
> > > On 1/25/06, Joseph Tanner <joseph at thetechguide.com> wrote:
> > > > 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
> > > > >
> > > > _______________________________________________
> > > > --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