**** BEGIN LOGGING AT Mon Jul 12 02:59:57 2010 Jul 13 00:56:06 denkenz: anything else to do for "PPP server support"? if no, i think it's done. Jul 13 01:13:59 padovan: i read DUN spec again. DialupNetworkingServiceClass_UUID is GW side uuid. and there's no uuid for data terminal side. Jul 13 01:14:32 padovan: so i think i can reuse uuid_hash in your code now. :-) Jul 13 01:15:17 see dun spec page 243, 5.3 SDP INTEROPERABILITY REQUIREMENTS for details. Jul 13 01:21:12 zhenhua: I'm seeing a consistency problem with the uuid, for HFP handsfree side we use the GW uuid. If we implement the HFP gateway we will use the handsfree side uuid. But for DUN we are doing it in the other way around. Jul 13 01:25:50 yes. Jul 13 01:26:12 padovan: for HFP, you parse device properties which is peer's properties Jul 13 01:26:45 padovan: but for DUN, i assume we parse adapter properties (which is our own capatibility) i think Jul 13 01:28:12 zhenhua: Actually I'm fine with that, but we have to remember that we have this little incosistance Jul 13 01:28:15 padovan: i don't find DUN client uuid yet. all i have is only GW UUID in SDP database Jul 13 01:28:58 padovan: agree. we should add comments in somewhere. Jul 13 01:31:27 zhenhua: maybe we really don't have it, because the GW side can't initiate the connection Jul 13 01:32:44 padovan: but how could ofono register itself to bluez agent? Jul 13 01:33:34 want to share more ideas? ;-) Jul 13 01:34:19 zhenhua: the server side? Jul 13 01:37:42 yes Jul 13 01:38:19 zhenhua: do you have a proposed API? Jul 13 01:39:12 for bluez, it's simple. similiar to gateway.c, we use agent to listen ofono registeration. Jul 13 01:39:25 i can draft a doc quickly Jul 13 01:40:49 Hold on for a second. Jul 13 01:41:24 Who need to listen to ofono registration? Jul 13 01:42:08 holtmann: similar to gateway.c, i want to create serial/dun.c in bluez to expose dbus API. Jul 13 01:42:39 RegisterAgent/UnregisterAgent/ Jul 13 01:43:23 it listens incoming DUN connection request and pass RFCOMM fd to ofono Jul 13 01:43:49 Nope. Jul 13 01:43:59 Dialup will be done completely inside oFono. Jul 13 01:44:19 Or are we talking about the client here. Jul 13 01:44:35 we are talking DUN server here Jul 13 01:49:07 I am talking about DUN server. Jul 13 01:49:07 So why should we bother with getting bluetoothd involved (besides SDP record and authorization). Jul 13 01:51:28 any better idea? we need bluetoothd providing us RFCOMM fd, right? Jul 13 01:52:07 you need bluez to register the DUN gw role Jul 13 01:52:08 Unless you want to keep the serial proxy & its associated overhead Jul 13 01:52:52 yes. i have made a bluez plugin to register DUN gw already Jul 13 01:53:01 locally Jul 13 01:53:16 it coexists with existing serial proxy Jul 13 01:55:59 holtmann: what do u think? Jul 13 02:00:13 No. The serial proxy needs to die. Jul 13 02:00:13 That will just go away. Jul 13 02:01:09 so DUN plugin will replace it **** BEGIN LOGGING AT Tue Jul 13 15:10:14 2010 **** ENDING LOGGING AT Wed Jul 14 02:59:56 2010