From: Rafael Seste <rseste@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: bluez 4.x, SCO socket - connection reset by peer
Date: Thu, 21 May 2009 11:10:26 -0300 [thread overview]
Message-ID: <5d223510905210710s21f5a433r50ae5ca610ccff4@mail.gmail.com> (raw)
In-Reply-To: <1242853150.3147.32.camel@localhost.localdomain>
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
next prev parent reply other threads:[~2009-05-21 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 20:49 bluez 4.x, SCO socket - connection reset by peer Rafael Seste
2009-05-20 20:59 ` Marcel Holtmann
2009-05-21 14:10 ` Rafael Seste [this message]
2009-05-22 17:14 ` Hugo Mildenberger
2009-05-22 18:39 ` Rafael Seste
2009-05-26 19:03 ` Rafael Seste
2009-05-27 16:57 ` Rafael Seste
2009-05-21 11:46 ` Hugo Mildenberger
2009-05-21 13:22 ` Rafael Seste
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d223510905210710s21f5a433r50ae5ca610ccff4@mail.gmail.com \
--to=rseste@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox