Hi Johan, Thanks for the reply. I understand how a server can use RegisterProfile to advertise its UUID & RFCOMM channel with SDP (as demonstrated in test-profile). It's still not clear to me how a client can use D-Bus to establish an RFCOMM socket connection given a device address & UUID. Can you point me in the right direction? Regards, Mark On Mon, Sep 28, 2015 at 11:49 PM, Johan Hedberg <johan.hedberg@xxxxxxxxx> wrote: > Hi Mark, > > On Mon, Sep 28, 2015, Mark Spruiell wrote: >> We currently use sdp_connect and sdp_service_search_attr_req to >> determine the RFCOMM channel associated with a service on a remote >> device. >> >> Does the D-Bus API provide an equivalent way to discover this information? > > Not directly, but there's a more convenient & higher level API available > if you look at doc/profile-api.txt and test/test-profile. This will not > only look up the RFCOMM channel for you, but also go ahead and connect > to the service and then give you back the connected RFCOMM socket over > D-Bus. > > Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
