Hi Gustavo,

Likely the culprit is this line inside __dundee_bluetooth_init

         err = bluetooth_register_uuid(DUN_GW_UUID,&dun_profile);

It should probably use the UUID of the DUN client, not the gateway.

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.

Perhaps dundee does not need to register an SDP record at all. I'm too lazy to dig out the DUN spec.

Regards,
-Denis
_______________________________________________
ofono mailing list
[email protected]
http://lists.ofono.org/listinfo/ofono

Reply via email to