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