From: Pedro Monjo Florit <pedro.monjo@futurlink.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] OBEX Push without pairing
Date: Tue, 01 Mar 2005 12:04:45 +0100 [thread overview]
Message-ID: <42244C4D.3030109@futurlink.com> (raw)
In-Reply-To: <200503011150.57455.bluez-user@schaettgen.de>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
Hi Fred:
Fred Schaettgen wrote:
>On Tuesday 01 March 2005 11:14, Pedro Monjo Florit wrote:
>
>>but still no success. With the same computer and configuration and as a
>>normal user, if I send a file from KDE using kbtobexclient, it works as
>>expected (no PIN requested, just the confirmation for receiving the
>>message), so I believe that there is some other things to do. I guess
>>that it should be a library call or somthing similar. Any suggestions?
>>
>
>Are you sure that you are connecting to the rfcomm channel of the obex push
>service? All others require authentication usually. Maybe you should have a
>look at hcidump's output to see the difference and at which point the phone
>is requesting authentication.
>
>Fred
>
>
Thank you very much for your suggestion. It was indeed what you said. I
was sending the data to the service "OBEX File Transfer" instead of
"OBEX Object Push". Now it works exactly as expected.
Cheers,
Pedro
[-- Attachment #2: Type: text/html, Size: 1405 bytes --]
prev parent reply other threads:[~2005-03-01 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 8:45 [Bluez-users] OBEX Push without pairing Pedro Monjo Florit
2005-03-01 9:01 ` Marcel Holtmann
2005-03-01 10:14 ` Pedro Monjo Florit
2005-03-01 10:47 ` Marcel Holtmann
2005-03-01 10:50 ` Fred Schaettgen
2005-03-01 11:04 ` Pedro Monjo Florit [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=42244C4D.3030109@futurlink.com \
--to=pedro.monjo@futurlink.com \
--cc=bluez-users@lists.sourceforge.net \
/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