From: Manuel Naranjo <naranjo.manuel@gmail.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] How to become a bluetooth obex server
Date: Thu, 09 Aug 2007 10:58:38 -0300 [thread overview]
Message-ID: <46BB1D8E.6050506@gmail.com> (raw)
In-Reply-To: <EJENLMBEOLKAMCJFBFMDMEEECAAA.leiyu@kcoe.cn>
[-- Attachment #1: Type: text/plain, Size: 2177 bytes --]
Leiyu,
The package obexftp has an app called obexftpd that's an obexftp server
daemon. You just do obexftpd -b and then you need to register OPUSH with
sdptool, first check that obexftpd has registered a new service with
sdptool records local, get the channel for FTP and then do sdptool add
OPUSH --channel=<NUMBER> usually obexftpd uses channel 10 unleash you
tell it to use another one
Cheers,
Manuel
> Dear All,
>
>
> I am doing a project , it is a bluetooth obex server and other bluetooth device can send file to it
> I install openobex-1.3 . after below procedure , I can send file to SE K900c
>
> #obex_test -b 00:19:63:A7:59:3B 6
> Using Bluetooth RFCOMM transport
> OBEX Interactive test client/server.
>
>> c
>>
> .....
>
> but after below procedure ,SE K900c can not send file to me
> #obex_test -b 00:19:63:A7:59:3B 6
> Using Bluetooth RFCOMM transport
> OBEX Interactive test client/server.
>
>> s
>>
> .....
>
> Above failture is not important, as running obex_test command need know the bluetooth address and RFCOMM channel of OPUSH, It is very not convenient.
> I want to reach this target , I do not need to know other device's information , RFCOMM channel and so on.
> just like this , run a command "obex_server ", then other bluetooth device that has opp profile can send file to me
> it is not need GUI too, because it run in embedded device finally.
> Could you help to suggest me that which package I need?
> Thanks in advance!
>
> Best regards,
> Leiyu
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
[-- Attachment #2: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-08-09 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 13:29 [Bluez-users] How to become a bluetooth obex server leiyu
2007-08-09 13:58 ` Manuel Naranjo [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-13 4:41 leiyu
2007-08-13 13:19 ` Manuel Naranjo
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=46BB1D8E.6050506@gmail.com \
--to=naranjo.manuel@gmail.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