Am Donnerstag 22 März 2007 21:26 schrieb martin f krafft: > also sprach Debian Bug Tracking System <[EMAIL PROTECTED]> [2007.03.22.2118 +0100]: > > Note that the printed output refers to what is _detected_ (via > > SDP) and not necessarily to what is used. You can use hcidump to > > check that. I just checked and using -B 6 (detected value) get > > a folder listing but -B 5 doesn't. > > Huh? This makes no sense to me. If I specify -B6 and it connects to > channel 7, you're telling me that's by design?
No, I meant: what is printed is not necessarily what gets used. Are you sure that it _connects_ to channel 7 or is that based on what obexftp prints out? What does it: 1. In the parameter -b, it does an SDP lookup for the given address. _There_, it prints the message that you see. 2. In the parameter -B, it overwrites the detected channel with what you give define. In the source, this is variable btchannel in apps/obexftp.c. Detection is done in apps/bt_discovery.c and there in line 139, it prints the channel information. So if you see: Channel: 7 it could also be printed as: Channel for OBEX-FBS according to SDP: 7 and then for the -B option (where NOTHING is currently printed): Overriding channel, now using channel: 6 That also why the -B option must not be before the -b option. This scheme works with my phone (Siemens SL75 just fine). I hope this makes is clearer for you. When you run hcidump during the connection, you can grep for "dlci" to see a different assignment. The dlci maps to (channel*2) and (channel*2 + 1). For channel 5, those are dlci 10 and 11, for channel 6, those are dlci 12 and 13. You will only see one of those values for each channel. Also note that the exact same service can be available on multiple channels. Some implementation do not correctly differ between the instances for Obex-Push and Obex-FBS. You can also add some debugging messages to libopenobex and to obexftp. However, this requires a recompilation. HS
