WhiteAxe -
There is almost NO ONE using these forums, so in general, you'll probably find
(like I have) that posting questions in these forums will yield only
sporatic answers.
As to your question, the answer is that you can NOT explicitly specify
the channel #. According to BOTH the JSR-82 bluetooth-textbooks I bought,
they both say that the stack itself is the arbitrator/assigner of the channel#
that they specify which channel will be used. (If you print out the 'connection-URL' that gets
generated, you should be able to SEE which channel got assigned (which you
no doubt have already, since you say that it was channel-10).
So, my best guess is that your 'bluetooth stack' must have some sort of fault
or bug in it. Either that, or else you are not 'cleaning up' from some earlier
experiment running some earlier server/client!? (Just reboot between experiments
if in doubt.)
If you reply back, state which vendor's adapter, stack, and OS that you
are using, as bluetooth works on all OSes (WinXP,Win-Vista, Mac, and Linux), you know.
[Having said that, I too am having trouble understanding exactly whose
'stack' that I am using, as the term 'stack' gets confused by all the various
vendors whose hands are in the 'bluetooth soup', as I call it. For example,
I own 3 separate USB-bluetooth adapters (an 'Encore', a 'Cirago', and a
'TRENDnet', and they all came with various INCOMPATIBLE Windows stacks/drivers/services.
e.g. the 'Cirago' was the worst...it came with a 'Toshiba' software stack, which
claimed that it had expired about two weeks after I started using it. The 'Encore'
works pretty well WITHOUT me needing to install the CDROM-stuff that came with
it (as it uses the existing Microsoft-stack that comes with Vista), but the
TRENDnet would not respond AT ALL, until I installed its 'driver' (which
it claims is a 'Widcomm stack').] [I've also tried my adapters on Linux and all
work uniformly there, althought one Java device-detection-API behaves a bit
differently there than it does on Windows.]
For my JSR-82/Java support, on top of the 'drivers and native stack', one must
additionally install/use a 'Java stack', and my chosen one has been 'Bluecove 2.1.0' in
all my experiments and code-development so far. (I'm trying to mostly stay PC-based and
use JavaSE, before I even consider trying to write 'Midlets' for a cellphone/PDA,
partly just because I don't own a Java-capable cell/PDA.)
Needless to say, I am NOT HAPPY with this state of affairs in the 'bluetooth-adapter'
market. [Can we imagine what chaos there'd be if 'flash-drives' all came with
separate conflicting drivers?] So, why doesn't Microsoft (or some designated member
of the bluetooth-SIG) step up and STANDARDIZE this Bluetooth driver/stack/firmware
mess on the Windows-platform? [Really glad to have had Linux to test against, as it
showed the confusions are mostly confined to the Windows-world.]
[Thanks to all for listening to my rant. Not that I expect any action, but it makes me
feel good to rant.

]