Bad News: There is no driver for the internal adapter that we can find.
Now it's time to make our annual attempt at getting chan_mobile to work. Here's a great tutorial for Ubuntu.
At least one exists and it appears to be working on my Cubox-i 4. I see both wlan0 and hci0 just fine. Nope no dongles to be seen anywhere. Unfortunately this box is running Arch Linux.
I've tried to replicate the Arch Linux firmware install on the 3.10.53 kernel and it just won't take. I think I'm going to go ahead and finally make that arch linux 3.10.30 kernel work with Ubuntu Trusty like I've threatened to do too many times already.
Hi Ward,
Any feedback on Chan_Mobile - it works on BBB, would like to know if it works on the box before I get my hands on it....
amportal kill
cd /usr/src/asterisk*
./configure --with-bluetooth
make menuconfig # activate chan_mobile THEN save & exit
make && make install
cd ..
cd Asterisk*
make clean
make
make install
amportal start
# HCId options
options {
autoinit yes;
security auto;
pairing multi;
passkey "0000";
}
device {
name "cubox-0";
class 0x3e0100;
iscan enable; pscan enable;
discovto 0;
lm accept;
lp rswitch,hold,sniff,park;
}
options {
autoinit yes;
security auto;
pairing multi;
#pin_helper /etc/bluetooth/pin;
}
[adapter]
id=blue
address=00:27:67:8E:11:2F ; the MAC address of your USB Bluetooth dongle in step #4
[GalaxyS4]
address=10:D5:42:16:15:CF ; the address of the phone
port=3 ; the rfcomm port number (from mobile search in step #8)
context=from-trunk ; dialplan context for incoming calls
adapter=blue ; adapter to use
group=1 ; this phone is in channel group 1
sms=yes ; support SMS, defaults to yes but had to force it for S4
nocallsetup=yes ; set this only if your phone reports that it supports call progress notification, but does not do it. Motorola L6 for example.
exten => 767,1,MobileSendSMS(GalaxyS4,8431234567,Hello World)
The problem with older kernels is IPtables and Fail2Ban stop working.
I don't believe *fail2ban* is an issue with the latest build I've done.
I don't believe that's an issue with the latest build I've done.
You're using the newer kernel.
cd /root
mkdir cubox-bt
cd cubox-bt
wget http://us.mirror.archlinuxarm.org/armv7h/alarm/firmware-brcm43xx-1.1-2-armv7h.pkg.tar.xz
tar xvf firmware-brcm43xx-1.1-2-armv7h.pkg.tar.xz
mkdir /etc/conf.d
cp etc/conf.d/bcm43xx /etc/conf.d
sed '1 s/sh/bash/;s/ --enable_lpm//' < usr/lib/systemd/scripts/brcm43xx-firmware-update > /usr/local/bin/brcm43xx-firmware-update
chmod +x /usr/local/bin/brcm43xx-firmware-update
cp usr/bin/brcm_patchram_plus /usr/bin
cp usr/lib/firmware/brcm/*.hcd /usr/lib/firmware/brcm/
cp usr/lib/firmware/brcm/*.hcd /lib/firmware/brcm/
# don't use the command below with shipping images of Incredible PBX. see below for fix.
sed '
/nothing./ a\
\
/usr/local/bin/brcm43xx-firmware-update\
wait\
/usr/sbin/hciattach -n /dev/brcm43xx any 3000000 &
' < /etc/rc.local > /etc/rc.local
Well.. Never say never! The SR forum comes through... No need to use another kernel.. This works on 3.10.53..
check if everything is copacetic (wait? sleep?) and reboot. hcitool dev should work and hcitool scan should find stuff.
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
/usr/local/sbin/iptables-restart
service ntp restart
/usr/local/bin/brcm43xx-firmware-update
/bin/sleep 5
/usr/sbin/hciattach -n /dev/brcm43xx any 3000000 &
/usr/local/sbin/amportal restart
exit 0
Might be completely wrong here, but have tried running the alsa mixer to see if any of the channels are on mute/low volume ?While that get's everything installed and working, there's still a major problem. Audio doesn't work in either direction on any BT calls using the internal adapter.
Fixed a couple of little things in your commands and the /etc/rc.local sed piece won't work with our setup.
Link up your team and customers Phone System Live Chat Video Conferencing
Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.
Check your inbox!
We’ve sent you an email. Click on the button in the email body to verify your email address – (if you can not find it, check your spam folder).
Upon verification you will be directed to the 3CX setup wizard.