From: Rafael Seste <rseste@gmail.com>
To: Hugo Mildenberger <Hugo.Mildenberger@namir.de>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: bluez 4.x, SCO socket - connection reset by peer
Date: Thu, 21 May 2009 10:22:25 -0300 [thread overview]
Message-ID: <5d223510905210622h4d3b4ec5h9b4772a3393f2fb1@mail.gmail.com> (raw)
In-Reply-To: <200905211346.28693.Hugo.Mildenberger@namir.de>
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
prev parent reply other threads:[~2009-05-21 13:22 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
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 [this message]
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=5d223510905210622h4d3b4ec5h9b4772a3393f2fb1@mail.gmail.com \
--to=rseste@gmail.com \
--cc=Hugo.Mildenberger@namir.de \
--cc=linux-bluetooth@vger.kernel.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