[asterisk-bugs] [Asterisk 0010443]: One way totaly distorted audio, the other way is OK.

noreply at bugs.digium.com noreply at bugs.digium.com
Thu Aug 16 03:50:52 CDT 2007


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10443 
====================================================================== 
Reported By:                phokz
Assigned To:                dbowerman
====================================================================== 
Project:                    Asterisk
Issue ID:                   10443
Category:                   Addons/chan_mobile
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.10  
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 424 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-13-2007 17:02 CDT
Last Modified:              08-16-2007 03:50 CDT
====================================================================== 
Summary:                    One way totaly distorted audio, the other way is OK.
Description: 
My test setup is
Nokia6234---BT Dongle MSI BToes---openSUSE 10.2 w/Asterisk
1.4.10---Twinkle sip phone on same machine.

When I place call from SIP to mobile, it dials and with 70% probability
everything goes just fine.

However, some calls are bad. The audio from phone do not get through to
pbx. SIP phone plays back random memory content - loud noise. In syslog
appears message

Aug 13 23:57:56 gromit kernel: hci_scodata_packet: hci0 SCO packet for
unknown connection handle 73

just before call is bridged. It looks as if receiving thread died or
somehow blocked. There must be a kind of race condition.

But sometimes the same messages appear in log and call is good.

First call after plugging in BT dongle is almost certainly good. Once
there is a bad call, probability of next call being bad too is high. After
unplugging/replugging BT dongle the next call is almost certainly good.


====================================================================== 

---------------------------------------------------------------------- 
 phokz - 08-16-07 03:50  
---------------------------------------------------------------------- 
I have tested my setup again with different BT dongle.
New BT dongle has this ID:
1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

Old BT dongle has this ID:
0db0:6970 Micro Star International

Now it seems to work correctly! I'll perform some more test, and post the
results.

dbowerman: if you are interested in this issue, I can send you the "bad"
BT dongle for your own testing.

I'd suggest making a blacklist of misbehaving dongles, at least in docs,
but better in program itself. It could issue a big fat warning during
initialization if BT dongle ID is in list of know bad dongles.

I also think this issue can be marked closed. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-16-07 03:50  phokz          Note Added: 0068910                          
======================================================================




More information about the asterisk-bugs mailing list