Return-Path: MIME-Version: 1.0 In-Reply-To: References: <1335342544-17320-1-git-send-email-manojkr.sharma@stericsson.com> <1335342544-17320-2-git-send-email-manojkr.sharma@stericsson.com> Date: Sun, 13 Jan 2013 17:42:51 +0200 Message-ID: Subject: Re: Obexd OPP filesend fails with Windows7 stack From: Luiz Augusto von Dentz To: Syam Sidhardhan Cc: "linux-bluetooth@vger.kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Syam, On Fri, Jan 11, 2013 at 10:32 AM, Syam Sidhardhan wrote: > Hi, > > We are using the obexd 0.48 version and testing the obexd. > During testing OPP file send, we found one interoperability > issue with the Windows7 PC stack and some commercialized devices > available in the market. > > The issue is: OBEXD file transfer is getting failed > once after the complete file content got transfferd. This is > because of, we do a direct RFCOMM disconection rather than > doing a proper OBEX disconection before. > > Does someone can help me a with a fix for this? We probably need to send a disconnect command before disconnecting RFCOMM, iirc there was someone else looking into a similar problem with a Nokia phone, the strange part is that the remote stack has acknowledged the transfer complete and in theory we could go ahead and start another one using the same session. -- Luiz Augusto von Dentz