bluez 4.x, SCO socket - connection reset by peer

bluez 4.x, SCO socket - connection reset by peer

[Rafael Seste]

Hi,

I trying to use asterisk (with chan_mobile) to connect with my mobile phone.
When there is a incoming/outgoing call, this module creates a
sco_socket to send/receive audio packets.

socket(PF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_SCO)

when this socket is ready...it can write data once, after that when it
tries to read an error is returned:

sco_read() error 104

104 means - connection reset by peer

after this i got error 107 - not connect.

Some one knows why is the reason of this error 104???

kernel 2.6.22.18
bluez 4.32

tks
-- 
Rafael S. Seste

Re: bluez 4.x, SCO socket - connection reset by peer

[Marcel Holtmann]

Hi Rafael,

> I trying to use asterisk (with chan_mobile) to connect with my mobile phone.
> When there is a incoming/outgoing call, this module creates a
> sco_socket to send/receive audio packets.
> 
> socket(PF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_SCO)
> 
> when this socket is ready...it can write data once, after that when it
> tries to read an error is returned:
> 
> sco_read() error 104
> 
> 104 means - connection reset by peer
> 
> after this i got error 107 - not connect.
> 
> Some one knows why is the reason of this error 104???
> 
> kernel 2.6.22.18
> bluez 4.32

I don't know, but your kernel is ancient. Please re-test with 2.6.30-rc6
and bluez-4.40 to see if this error still persists.

Regards

Marcel

Re: bluez 4.x, SCO socket - connection reset by peer

[Hugo Mildenberger]

Am Mittwoch, 20. Mai 2009 schrieb Rafael Seste:
> Hi,
> 
> I trying to use asterisk (with chan_mobile) to connect with my mobile phone.
> When there is a incoming/outgoing call, this module creates a
> sco_socket to send/receive audio packets.
> 
> socket(PF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_SCO)
> 
> when this socket is ready...it can write data once, after that when it
> tries to read an error is returned:
> 
> sco_read() error 104
> 
> 104 means - connection reset by peer
> 
> after this i got error 107 - not connect.
> 
> Some one knows why is the reason of this error 104???
> 
> kernel 2.6.22.18
> bluez 4.32
> 
> tks


Are you also using a Nokia cell phone? This error
is likely a consequence of the patch introduced by
  
https://issues.asterisk.org/view.php?id=15037 

Maybe you would like to report your setup also here:
 
https://issues.asterisk.org/view.php?id=15075


Best Regards

Re: bluez 4.x, SCO socket - connection reset by peer

[Rafael Seste]

Hugo,

On Thu, May 21, 2009 at 8:46 AM, Hugo Mildenberger
<Hugo.Mildenberger@namir.de> wrote:
> Am Mittwoch, 20. Mai 2009 schrieb Rafael Seste:
>> Hi,
>>
>> I trying to use asterisk (with chan_mobile) to connect with my mobile phone.
>> When there is a incoming/outgoing call, this module creates a
>> sco_socket to send/receive audio packets.
>>
>> socket(PF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_SCO)
>>
>> when this socket is ready...it can write data once, after that when it
>> tries to read an error is returned:
>>
>> sco_read() error 104
>>
>> 104 means - connection reset by peer
>>
>> after this i got error 107 - not connect.
>>
>> Some one knows why is the reason of this error 104???
>>
>> kernel 2.6.22.18
>> bluez 4.32
>>
>> tks
>
>
> Are you also using a Nokia cell phone? This error
> is likely a consequence of the patch introduced by
>
> https://issues.asterisk.org/view.php?id=15037
>
> Maybe you would like to report your setup also here:
>
> https://issues.asterisk.org/view.php?id=15075
>
>
> Best Regards
>
>

I'm testing with a Nokia 5310 and a LG KF-240
This error occurs with both mobile phones.

I will try the new versions of kernel and bluez

-- 
Rafael S. Seste
Eng Computação - Unicamp

Re: bluez 4.x, SCO socket - connection reset by peer

[Rafael Seste]

Marcel

On Wed, May 20, 2009 at 5:59 PM, Marcel Holtmann <marcel@holtmann.org> wrot=
e:
> Hi Rafael,
>
>> I trying to use asterisk (with chan_mobile) to connect with my mobile ph=
one.
>> When there is a incoming/outgoing call, this module creates a
>> sco_socket to send/receive audio packets.
>>
>> socket(PF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_SCO)
>>
>> when this socket is ready...it can write data once, after that when it
>> tries to read an error is returned:
>>
>> sco_read() error 104
>>
>> 104 means - connection reset by peer
>>
>> after this i got error 107 - not connect.
>>
>> Some one knows why is the reason of this error 104???
>>
>> kernel 2.6.22.18
>> bluez 4.32
>
> I don't know, but your kernel is ancient. Please re-test with 2.6.30-rc6
> and bluez-4.40 to see if this error still persists.
>
> Regards
>
> Marcel
>
>
>

I have a setup:
kernel 2.6.9-78.ELsmp #1 SMP Fri Jul 25 00:04:28 EDT 2008 i686 i686
i386 GNU/Linux
and bluez 2.10-3

and it works fine.

The difference is the arch that now I changed to an ARM and i can't
install this old kernel.

--=20
Rafael S. Seste
Eng Computa=E7=E3o - Unicamp

Re: bluez 4.x, SCO socket - connection reset by peer

[Hugo Mildenberger]

Am Donnerstag, 21. Mai 2009 schrieb Rafael Seste:
> Marcel
> 
> On Wed, May 20, 2009 at 5:59 PM, Marcel Holtmann <marcel@holtmann.org> wrote:
> > Hi Rafael,
> >
> >> I trying to use asterisk (with chan_mobile) to connect with my mobile phone.
> >> When there is a incoming/outgoing call, this module creates a
> >> sco_socket to send/receive audio packets.
> >>
> >> socket(PF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_SCO)
> >>
> >> when this socket is ready...it can write data once, after that when it
> >> tries to read an error is returned:
> >>
> >> sco_read() error 104
> >>
> >> 104 means - connection reset by peer
> >>
> >> after this i got error 107 - not connect.
> >>
> >> Some one knows why is the reason of this error 104???
> >>
> >> kernel 2.6.22.18
> >> bluez 4.32
> >
> > I don't know, but your kernel is ancient. Please re-test with 2.6.30-rc6
> > and bluez-4.40 to see if this error still persists.
> >
> > Regards
> >
> > Marcel
> >
> >
> >
> 
> I have a setup:
> kernel 2.6.9-78.ELsmp #1 SMP Fri Jul 25 00:04:28 EDT 2008 i686 i686
> i386 GNU/Linux
> and bluez 2.10-3
> 
> and it works fine.
> 
> The difference is the arch that now I changed to an ARM and i can't
> install this old kernel.
> 

I can confirm this behaviour on x86 with a CSR Adapter (0a12:0001), 
a Nokia 6280 V6.43, linux-2.6.30-rc6-00159-ga15ae93 and bluez-4.40. 

Until today, I thought it might be related to the interaction between 
the Nokia firmware and Asterisk, but if Rafael says 2.6.9-78/bluez-2.10.3 
would be working?

https://issues.asterisk.org/view.php?id=15075 now has a patch which at 
least cures the symptoms.
  
I do also see some kernel errors via dmesg:

btusb_isoc_complete: hci0 corrupted SCO packet
hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
btusb_isoc_complete: hci0 corrupted SCO packet
hci_scodata_packet: hci0 SCO packet for unknown connection handle 46
hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
[...]

Re: bluez 4.x, SCO socket - connection reset by peer

[Rafael Seste]

On Fri, May 22, 2009 at 2:14 PM, Hugo Mildenberger
<Hugo.Mildenberger@namir.de> wrote:
> Am Donnerstag, 21. Mai 2009 schrieb Rafael Seste:
>> Marcel
>>
>> On Wed, May 20, 2009 at 5:59 PM, Marcel Holtmann <marcel@holtmann.org> w=
rote:
>> > Hi Rafael,
>> >
>> >> I trying to use asterisk (with chan_mobile) to connect with my mobile=
 phone.
>> >> When there is a incoming/outgoing call, this module creates a
>> >> sco_socket to send/receive audio packets.
>> >>
>> >> socket(PF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_SCO)
>> >>
>> >> when this socket is ready...it can write data once, after that when i=
t
>> >> tries to read an error is returned:
>> >>
>> >> sco_read() error 104
>> >>
>> >> 104 means - connection reset by peer
>> >>
>> >> after this i got error 107 - not connect.
>> >>
>> >> Some one knows why is the reason of this error 104???
>> >>
>> >> kernel 2.6.22.18
>> >> bluez 4.32
>> >
>> > I don't know, but your kernel is ancient. Please re-test with 2.6.30-r=
c6
>> > and bluez-4.40 to see if this error still persists.
>> >
>> > Regards
>> >
>> > Marcel
>> >
>> >
>> >
>>
>> I have a setup:
>> kernel 2.6.9-78.ELsmp #1 SMP Fri Jul 25 00:04:28 EDT 2008 i686 i686
>> i386 GNU/Linux
>> and bluez 2.10-3
>>
>> and it works fine.
>>
>> The difference is the arch that now I changed to an ARM and i can't
>> install this old kernel.
>>
>
> I can confirm this behaviour on x86 with a CSR Adapter (0a12:0001),
> a Nokia 6280 V6.43, linux-2.6.30-rc6-00159-ga15ae93 and bluez-4.40.
>
> Until today, I thought it might be related to the interaction between
> the Nokia firmware and Asterisk, but if Rafael says 2.6.9-78/bluez-2.10.3
> would be working?
>
> https://issues.asterisk.org/view.php?id=3D15075 now has a patch which at
> least cures the symptoms.
>
> I do also see some kernel errors via dmesg:
>
> btusb_isoc_complete: hci0 corrupted SCO packet
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
> btusb_isoc_complete: hci0 corrupted SCO packet
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 46
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
> [...]
>
>
>
>

I forgot to tell one important detail. I'm trying to install this
stuffs in a SoC. It is a ARM
root@debian:~# uname -a
Linux debian 2.6.22.18 #1 Thu Mar 19 14:46:22 IST 2009 armv5tejl GNU/Linux
The kernel that I'm using has a lot of patchs to work in this architecture.

Today I reproduce the same setup in a PC (i386):
root@ubuntu:/var/log# uname -a
Linux ubuntu 2.6.22.18 #4 SMP Fri May 22 09:29:09 BRT 2009 i686 GNU/Linux
bluez 4.32 from apt-get and asterisk 1.6.1.0

and it works....
Maybe this is an architecture incompatibility..

Investigating the logs from the ARM, I found that the error
"connection reset by peer" occurs after I hang up.
So, asterisk writes once in the socket ( I can see the SCO package
going out in hcidump), then it tries to read from the sco socket but
there is no data available. It sleeps until some data arrives. The
only information that arrives is when I hang up so it returns the
error.

On hcidump output I can see only one sco package from asterisk to
mobile phone, and no SCO package from mobile to the asterisk.

Could it be some connection configuration problem??
What kernel drivers/modules are necessary??? I enable the bluetooth
ones in networking-->bluetooth subsystem support!!






--=20
Rafael S. Seste
Eng Computa=E7=E3o - Unicamp

Re: bluez 4.x, SCO socket - connection reset by peer

[Rafael Seste]

Hi Marcel,

On Fri, May 22, 2009 at 3:39 PM, Rafael Seste <rseste@gmail.com> wrote:
> On Fri, May 22, 2009 at 2:14 PM, Hugo Mildenberger
> <Hugo.Mildenberger@namir.de> wrote:
>> Am Donnerstag, 21. Mai 2009 schrieb Rafael Seste:
>>> Marcel
>>>
>>> On Wed, May 20, 2009 at 5:59 PM, Marcel Holtmann <marcel@holtmann.org> =
wrote:
>>> > Hi Rafael,
>>> >
>>> >> I trying to use asterisk (with chan_mobile) to connect with my mobil=
e phone.
>>> >> When there is a incoming/outgoing call, this module creates a
>>> >> sco_socket to send/receive audio packets.
>>> >>
>>> >> socket(PF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_SCO)
>>> >>
>>> >> when this socket is ready...it can write data once, after that when =
it
>>> >> tries to read an error is returned:
>>> >>
>>> >> sco_read() error 104
>>> >>
>>> >> 104 means - connection reset by peer
>>> >>
>>> >> after this i got error 107 - not connect.
>>> >>
>>> >> Some one knows why is the reason of this error 104???
>>> >>
>>> >> kernel 2.6.22.18
>>> >> bluez 4.32
>>> >
>>> > I don't know, but your kernel is ancient. Please re-test with 2.6.30-=
rc6
>>> > and bluez-4.40 to see if this error still persists.
>>> >
>>> > Regards
>>> >
>>> > Marcel
>>> >
>>> >
>>> >
>>>
>>> I have a setup:
>>> kernel 2.6.9-78.ELsmp #1 SMP Fri Jul 25 00:04:28 EDT 2008 i686 i686
>>> i386 GNU/Linux
>>> and bluez 2.10-3
>>>
>>> and it works fine.
>>>
>>> The difference is the arch that now I changed to an ARM and i can't
>>> install this old kernel.
>>>
>>
>> I can confirm this behaviour on x86 with a CSR Adapter (0a12:0001),
>> a Nokia 6280 V6.43, linux-2.6.30-rc6-00159-ga15ae93 and bluez-4.40.
>>
>> Until today, I thought it might be related to the interaction between
>> the Nokia firmware and Asterisk, but if Rafael says 2.6.9-78/bluez-2.10.=
3
>> would be working?
>>
>> https://issues.asterisk.org/view.php?id=3D15075 now has a patch which at
>> least cures the symptoms.
>>
>> I do also see some kernel errors via dmesg:
>>
>> btusb_isoc_complete: hci0 corrupted SCO packet
>> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
>> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
>> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
>> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
>> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
>> btusb_isoc_complete: hci0 corrupted SCO packet
>> hci_scodata_packet: hci0 SCO packet for unknown connection handle 46
>> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
>> [...]
>>
>>
>>
>>
>
> I forgot to tell one important detail. I'm trying to install this
> stuffs in a SoC. It is a ARM
> root@debian:~# uname -a
> Linux debian 2.6.22.18 #1 Thu Mar 19 14:46:22 IST 2009 armv5tejl GNU/Linu=
x
> The kernel that I'm using has a lot of patchs to work in this architectur=
e.
>
> Today I reproduce the same setup in a PC (i386):
> root@ubuntu:/var/log# uname -a
> Linux ubuntu 2.6.22.18 #4 SMP Fri May 22 09:29:09 BRT 2009 i686 GNU/Linux
> bluez 4.32 from apt-get and asterisk 1.6.1.0
>
> and it works....
> Maybe this is an architecture incompatibility..
>
> Investigating the logs from the ARM, I found that the error
> "connection reset by peer" occurs after I hang up.
> So, asterisk writes once in the socket ( I can see the SCO package
> going out in hcidump), then it tries to read from the sco socket but
> there is no data available. It sleeps until some data arrives. The
> only information that arrives is when I hang up so it returns the
> error.
>
> On hcidump output I can see only one sco package from asterisk to
> mobile phone, and no SCO package from mobile to the asterisk.
>
> Could it be some connection configuration problem??
> What kernel drivers/modules are necessary??? I enable the bluetooth
> ones in networking-->bluetooth subsystem support!!
>
>
>
>
>
>
> --
> Rafael S. Seste
> Eng Computa=E7=E3o - Unicamp
>

I installed the new kernel 2.6.30-rc6 and bluez 4.40
Now I can hear =93audio noise=94 only, it is not intelligible.
The syslog is flooded by this message:

hci_scodata_packet: hci0 SCO packet for unknown connection handle 63231
hci_scodata_packet: hci0 SCO packet for unknown connection handle 235
hci_scodata_packet: hci0 SCO packet for unknown connection handle 52224
hci_scodata_packet: hci0 SCO packet for unknown connection handle 210
hci_scodata_packet: hci0 SCO packet for unknown connection handle 79
hci_scodata_packet: hci0 SCO packet for unknown connection handle 27646
hci_scodata_packet: hci0 SCO packet for unknown connection handle 204
btusb_isoc_complete: hci0 corrupted SCO packet
hci_scodata_packet: hci0 SCO packet for unknown connection handle 153
hci_scodata_packet: hci0 SCO packet for unknown connection handle 9727
hci_scodata_packet: hci0 SCO packet for unknown connection handle 47616
hci_scodata_packet: hci0 SCO packet for unknown connection handle 159
hci_scodata_packet: hci0 SCO packet for unknown connection handle 35584
hci_scodata_packet: hci0 SCO packet for unknown connection handle 190
hci_scodata_packet: hci0 SCO packet for unknown connection handle 65520
hci_scodata_packet: hci0 SCO packet for unknown connection handle 90
hci_scodata_packet: hci0 SCO packet for unknown connection handle 39679
hci_scodata_packet: hci0 SCO packet for unknown connection handle 65492
hci_scodata_packet: hci0 SCO packet for unknown connection handle 63487
hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
btusb_isoc_complete: hci0 corrupted SCO packet

In hcidump output there are a lot of packets with different lengths
and connection handler (ARM).
The output from the pc that works (x86), all packets have the same
handler and the same length.

Anybody knows why this is happening?

--=20
Rafael S. Seste

Re: bluez 4.x, SCO socket - connection reset by peer

[Rafael Seste]

Hi,

On Tue, May 26, 2009 at 4:03 PM, Rafael Seste <rseste@gmail.com> wrote:
> Hi Marcel,
>
> On Fri, May 22, 2009 at 3:39 PM, Rafael Seste <rseste@gmail.com> wrote:
>> On Fri, May 22, 2009 at 2:14 PM, Hugo Mildenberger
>> <Hugo.Mildenberger@namir.de> wrote:
>>> Am Donnerstag, 21. Mai 2009 schrieb Rafael Seste:
>>>> Marcel
>>>>
>>>> On Wed, May 20, 2009 at 5:59 PM, Marcel Holtmann <marcel@holtmann.org>=
 wrote:
>>>> > Hi Rafael,
>>>> >
>>>> >> I trying to use asterisk (with chan_mobile) to connect with my mobi=
le phone.
>>>> >> When there is a incoming/outgoing call, this module creates a
>>>> >> sco_socket to send/receive audio packets.
>>>> >>
>>>> >> socket(PF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_SCO)
>>>> >>
>>>> >> when this socket is ready...it can write data once, after that when=
 it
>>>> >> tries to read an error is returned:
>>>> >>
>>>> >> sco_read() error 104
>>>> >>
>>>> >> 104 means - connection reset by peer
>>>> >>
>>>> >> after this i got error 107 - not connect.
>>>> >>
>>>> >> Some one knows why is the reason of this error 104???
>>>> >>
>>>> >> kernel 2.6.22.18
>>>> >> bluez 4.32
>>>> >
>>>> > I don't know, but your kernel is ancient. Please re-test with 2.6.30=
-rc6
>>>> > and bluez-4.40 to see if this error still persists.
>>>> >
>>>> > Regards
>>>> >
>>>> > Marcel
>>>> >
>>>> >
>>>> >
>>>>
>>>> I have a setup:
>>>> kernel 2.6.9-78.ELsmp #1 SMP Fri Jul 25 00:04:28 EDT 2008 i686 i686
>>>> i386 GNU/Linux
>>>> and bluez 2.10-3
>>>>
>>>> and it works fine.
>>>>
>>>> The difference is the arch that now I changed to an ARM and i can't
>>>> install this old kernel.
>>>>
>>>
>>> I can confirm this behaviour on x86 with a CSR Adapter (0a12:0001),
>>> a Nokia 6280 V6.43, linux-2.6.30-rc6-00159-ga15ae93 and bluez-4.40.
>>>
>>> Until today, I thought it might be related to the interaction between
>>> the Nokia firmware and Asterisk, but if Rafael says 2.6.9-78/bluez-2.10=
.3
>>> would be working?
>>>
>>> https://issues.asterisk.org/view.php?id=3D15075 now has a patch which a=
t
>>> least cures the symptoms.
>>>
>>> I do also see some kernel errors via dmesg:
>>>
>>> btusb_isoc_complete: hci0 corrupted SCO packet
>>> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
>>> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
>>> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
>>> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
>>> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
>>> btusb_isoc_complete: hci0 corrupted SCO packet
>>> hci_scodata_packet: hci0 SCO packet for unknown connection handle 46
>>> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
>>> [...]
>>>
>>>
>>>
>>>
>>
>> I forgot to tell one important detail. I'm trying to install this
>> stuffs in a SoC. It is a ARM
>> root@debian:~# uname -a
>> Linux debian 2.6.22.18 #1 Thu Mar 19 14:46:22 IST 2009 armv5tejl GNU/Lin=
ux
>> The kernel that I'm using has a lot of patchs to work in this architectu=
re.
>>
>> Today I reproduce the same setup in a PC (i386):
>> root@ubuntu:/var/log# uname -a
>> Linux ubuntu 2.6.22.18 #4 SMP Fri May 22 09:29:09 BRT 2009 i686 GNU/Linu=
x
>> bluez 4.32 from apt-get and asterisk 1.6.1.0
>>
>> and it works....
>> Maybe this is an architecture incompatibility..
>>
>> Investigating the logs from the ARM, I found that the error
>> "connection reset by peer" occurs after I hang up.
>> So, asterisk writes once in the socket ( I can see the SCO package
>> going out in hcidump), then it tries to read from the sco socket but
>> there is no data available. It sleeps until some data arrives. The
>> only information that arrives is when I hang up so it returns the
>> error.
>>
>> On hcidump output I can see only one sco package from asterisk to
>> mobile phone, and no SCO package from mobile to the asterisk.
>>
>> Could it be some connection configuration problem??
>> What kernel drivers/modules are necessary??? I enable the bluetooth
>> ones in networking-->bluetooth subsystem support!!
>>
>>
>>
>>
>>
>>
>> --
>> Rafael S. Seste
>> Eng Computa=E7=E3o - Unicamp
>>
>
> I installed the new kernel 2.6.30-rc6 and bluez 4.40
> Now I can hear =93audio noise=94 only, it is not intelligible.
> The syslog is flooded by this message:
>
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 63231
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 235
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 52224
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 210
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 79
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 27646
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 204
> btusb_isoc_complete: hci0 corrupted SCO packet
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 153
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 9727
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 47616
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 159
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 35584
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 190
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 65520
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 90
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 39679
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 65492
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 63487
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
> btusb_isoc_complete: hci0 corrupted SCO packet
>
> In hcidump output there are a lot of packets with different lengths
> and connection handler (ARM).
> The output from the pc that works (x86), all packets have the same
> handler and the same length.
>
> Anybody knows why this is happening?
>
> --
> Rafael S. Seste
>

I applied the patch that Hugo sent
https://issues.asterisk.org/view.php?id=3D15075
Now, the outgoing audio is ok, but the incoming is still truncated, I
can't understand almost anything.

from HCIDump i got this received SCO packet:

0000 03 ff ee ff ee ff ee ff ee ff ee ff 5c 00 30 ee ........ ....\.0.
0010 ff ee ff ee ff ee ff ee ff ee ff ee ff ee ff ee ........ ........
0020 ff ee ff ee ff ee ff ee ff ee ff ee ff ee ff ee ........ ........
0030 ff ee ff ee ff ee ff ee ff ee ff ee ff ee ff 5c ........ .......\
0040 00 30 ee ff ee ff ee ff ee ff ee ff ee ff ee ff .0...... ........
0050 ee ff ee ff ee ff ee ff ee ff ee ff ee ff ee ff ........ ........
0060 ee ff ee ff ee ff ee ff ee ff ee ff ee ff ee ff ........ ........
0070 ee ff 5c 00 30 ee ff ee ff ee ff ee ff ee ff ee ..\.0... ........
0080 ff ee ff ee ff ee ff ee ff ee ff ee ff ee ff ee ........ ........
0090 ff ee ff ee ff ee ff ee ff ee ff ee ff ee ff ee ........ ........
00a0 ff ee ff ee ff 5c 00 30 ee ff ee ff ee ff ee ff .....\.0 ........
00b0 ee ff ee ff ee ff ee ff ee ff ee ff ee ff ee ff ........ ........
00c0 ee ff ee ff ee ff ee ff ee ff ee ff ee ff ee ff ........ ........
00d0 ee ff ee ff ee ff ee ff 5c 00 30 ee ff ee ff ee ........ \.0.....
00e0 ff ee ff ee ff ee ff ee ff ee ff ee ff ee ff ee ........ ........
00f0 ff ee ff ee ff ee ff ee ff ee ff ee ff ee ff ee ........ ........
0100 ff ee ff ...

the connection handler( 2=BA and 3=BA bytes) and data length (4=BA bytes) a=
re wrong.

a correct received packet should look likes this:

0000  03 5c 00 30 c7 ff 97 ff  77 ff e1 fe c3 fe cf fe   .\.0.... w.......
0010  df fe 64 ff bb ff 36 00  bc 00 5e 01 11 02 6c 02   ..d...6. ..^...l.
0020  87 02 68 02 54 02 ba 01  b7 00 8b ff 69 fe a9 fd   ..h.T... ....i...
0030  b6 fc 43 fc                                        ..C.

with 48 bytes of payload.

For some reason the packet data is not correctly evaluated.
May because of a structure padding or littleendia/bigendian settings,
differences between x86 and ARM.

Is there any known issue related to this compilation problems?
Or could this be related to other things?
What part of the kernel/bluez code should I take a look to try to
solve this issue?

tks

--=20
Rafael S. Seste