Result: Paired successfully (after quite a few tries), was visible with # hcitool scan and showed up under CLI> mobile search. After configuring in chan_nf, the phone would connect with Asterisk, initialising, then failing and disconnecting repeatedly with Asterisk. Result: Paired successfully, was visible with # hcitool scan and showed up under CLI> mobile search. In my attempts to get this setup and working on my system I tried pairing and using the following handsets without much success (and I have to say quite a bit of aggravation):
Getting a solid and stable Bluetooth phone to Asterisk connection has proven to be anything but easy and predictable. The lessons learnt here are that overall success with chan_mobile is critically dependent on the dongle and phone used. I have this working successfully using an iPhone 4S (with v5.1 firmware) and using the MSI BToes 2.0 EDR Micro Dongle.
In the first stanza where “id=blue” replace the mac address with the one you copied down.
If you’re alerted that some other application isn’t running, we don’t care. You should see messages that look like this:
I’ve also read on asterisk support forums that a minor patch (to chan_mobile.c) may be required for this to work, although I think this relates to Debian-based installs, rather than CentOS.įor info I would be recompiling Asterisk to install the channel driver. Latest supported version of bluez bluetooth utilities and libraries I’ve been googling away and there a few articles like the one on which highlight key implementation decisions (in terms of compatibility and functionality), such as: Has anyone had any experience running the chan_mobile channel driver? I’m thinking of dipping my toes in the water as I could see it could be quite a useful solution to route my mobile calls via Asterisk (and also maximise the value of my monthly mobile call allowance). I just saw AndrewZ’s comment in response to the question posed by zlotowinfo.