Hello,
I'm Using Asterisk 1.8.11.0 on Debian Squeeze. I was experiencing problems
with ${SMSSRC} being blank, so I applied this patch:
https://issues.asterisk.org/jira/secure/attachment/42026/sms-sender-fix.diff
but otherwise everything is standard.
As the subject says, if I am making a call through the phone when an SMS is
received, the bluetooth connection drops and the call ends. The SMS is
delivered successfully.
This happens on two different 6021 handsets, one is connected to a DBT-120
(csr) dongle and the other is connected to a no-name btusb dongle. Nothing
unexpected shows up in the Asterisk console:
-- Executing [*00@house-phones:4] Dial("SIP/200-00000037",
"MOBILE/JS6021/4444,60,rTK") in new stack
-- Called MOBILE/JS6021/4444
[2012-04-30 19:13:15] WARNING[25326]: channel.c:4913 ast_write: Codec mismatch
on channel Mobile/JS6021-6e5b setting write format to alaw from slin native
formats 0x40 (slin)
-- Mobile/JS6021-6e5b is making progress passing it to SIP/200-00000037
-- Mobile/JS6021-6e5b answered SIP/200-00000037
-- Executing [sms@from-stocksy-orange:1] Verbose("Mobile/JS6021-b05c",
"Incoming SMS from <numberremoved> <message>
") in new stack
Incoming SMS from <numberremoved> <message>
-- Executing [sms@from-stocksy-orange:2] System("Mobile/JS6021-b05c", "echo
"To: mymail" > /tmp/smsmail-stocksy") in new stack
-- Executing [sms@from-stocksy-orange:3] System("Mobile/JS6021-b05c", "echo
"Subject: SMS from <numberremoved>" >> /tmp/smsmail-stocksy") in new stack
-- Executing [sms@from-stocksy-orange:4] System("Mobile/JS6021-b05c", "echo
"<message>
" >> /tmp/smsmail-stocksy") in new stack
-- Executing [sms@from-stocksy-orange:5] System("Mobile/JS6021-b05c",
"sendmail -t -f <numberremoved>@sms.stocksy.co.uk < /tmp/smsmail-stocksy") in
new stack
-- Executing [sms@from-stocksy-orange:6] Hangup("Mobile/JS6021-b05c", "")
in new stack
== Spawn extension (from-stocksy-orange, sms, 6) exited non-zero on
'Mobile/JS6021-b05c'
-- Bluetooth Device JS6021 has disconnected.
I do get some messages in syslog at this time, I don't know if they are
significant:
Apr 30 19:13:19 pabx kernel: [696331.658348] btusb_isoc_complete: hci1
corrupted SCO packet
Apr 30 19:13:19 pabx kernel: [696331.658394] hci_scodata_packet: hci1 SCO
packet for unknown connection handle 0
I have (I think!) loaded btusb with force_scofix by creating this file:
# more /etc/modprobe.d/btusb.conf
options btusb force_scofix=1
and reloading the btusb module.
Is this a known problem?
Regards,
James.
smime.p7s
Description: S/MIME cryptographic signature
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
