You are visiting:Home arrow Articles for Geeks arrow Asterisk arrow HOWTO build and configure chan_mobile on Trixbox Thursday, 28 August 2008
Google
Support Geek-Pages.com in making a small donation:
Main Menu
Home
Articles for Geeks
FAQs for Non-Geeks
Links
Kevan's Blog
Contact Us
Forum
Search
Login Form





Lost Password?
No account yet? Register
Submit article to:
HOWTO build and configure chan_mobile on Trixbox PDF Print E-mail
Written by Kevan   

22. The CLI command 'mobile show devices' can be used at any time to show the status of configured
devices, and whether or not the device is capable of sending / receiving SMS via bluetooth:

trixbox1*CLI> mobile show devices
ID Address Connected State SMS
my_phone 00:12:56:90:6E:00 Yes Free Yes
my_headset 00:0B:9E:11:74:A5 Yes Free No

trixbox1*CLI>

23. All being well Asterisk will now try and establish a connection to each configured device.
If it can’t it will retry after 'interval' seconds, infinitely. This means that as your cell
phone comes into range and goes out of range, Asterisk will automatically connect and disconnect
from it. You don’t need to worry about it.
24. As each phone is connected you will see a message on the Asterisk console:

trixbox1*CLI>
Loaded chan_mobile.so => (Bluetooth Mobile Device Channel Driver)
-- Bluetooth Device my_phone has connected.
-- Bluetooth Device my_headset has connected.

25. If someone calls your cell phone now, Asterisk will handle the call and it will be sent to the
context you specified, or the default context. Hopefully this means some SIP phone somewhere will ring,
pick it up and take the call.
26. Important: Watch what your cell phone is doing the first few times. Asterisk won’t make random
calls but if chan_mobile fails to hang up for some reason and you get a huge bill from your telco,
don’t blame me.

Comments
Written by Vladje on 2007-12-16 17:55:44
This is a very good tutorial, but my mobile phone disconnects directly after receiving a call. 
 
Could you also give an example of a trunk, and this to make call?
Yeah, but....
Written by This email address is being protected from spam bots, you need Javascript enabled to view it on 2008-07-15 16:27:28
I am stuck with the bit where it says make it discoverable.  
 
The spacing of the command string is not obvious.  
 
oot@pbx:~ $ dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/blue/hci0 org.bluez.Adapter.SetMode string:discoverable 
Error org.freedesktop.DBus.Error.UnknownMethod: Method "SetMode" with signature "s" on interface "org.bluez.Adapter" doesn't exist 
 
root@pbx:~ $ dbus-send --system --type=method_call --print-reply --dest=org.bluez/org/blue/hci0 org.bluez.Adapter.SetMode string:discoverable 
Must use org.mydomain.Interface.Method notation, no dot in "string:discoverable" 
root@pbx:~ $  
 
Either way doesn't seem to work...

Only registered users can write comments.
Please login or register.

Powered by AkoComment!