From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: oFono DUN server issue
Date: Thu, 14 Jun 2012 17:46:34 -0500 [thread overview]
Message-ID: <4FDA69CA.5080100@gmail.com> (raw)
In-Reply-To: <20120615025829.GB3538@joana>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
Hi Gustavo,
>>> We actually don't have an client uuid for DUN, and we need to put the server
>>> uuid here in order to find the remote DUN Gateways.
>>> Other than that he reported an issue in oFono, so how can dundee interfere on
>>> it?
>>
>> I'm just speculating, but the problem here is that both dundee and
>> the modem emulator are registering the DUN service. Unfortunately
>> dundee is implementing the client role and modem emulator is
>> implementing the server role.
>
> They aren't, DUN server register a server, through
> bluetooth_register_server(), there is no UUID on this. Only DUN Service
> register itself as DUN on BlueZ.
>
>>
>> Perhaps dundee does not need to register an SDP record at all. I'm
>> too lazy to dig out the DUN spec.
>
> It doesn't need because it doesn't have one. We use DUN_GW_UUID here because
> we want plugins/bluetooth.c to notify us when a DUN_GW device appears so then
> we can use or DUN Client (dundee) to connect to it.
>
> HFP does the same, in the Handsfree side we register for the UUID of the
> Gateway side because you want to know about new HFP gateways on the system.
>
Fair enough. Then I have no idea what is causing this regression.
Regards,
-Denis
next prev parent reply other threads:[~2012-06-14 22:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 14:21 oFono DUN server issue Guillaume Zajac
2012-06-14 12:43 ` Denis Kenzior
2012-06-15 2:27 ` Gustavo Padovan
2012-06-14 22:29 ` Denis Kenzior
2012-06-15 2:58 ` Gustavo Padovan
2012-06-14 22:46 ` Denis Kenzior [this message]
2012-06-15 3:11 ` Gustavo Padovan
2012-06-14 23:09 ` Denis Kenzior
2012-06-18 10:04 ` Guillaume Zajac
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=4FDA69CA.5080100@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.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