Take a look at Xbtrc<br><br><a href="http://wwwhome.cs.utwente.nl/~dijkhw/index.php?p=Katlijk/Xbtrc">http://wwwhome.cs.utwente.nl/~dijkhw/index.php?p=Katlijk/Xbtrc</a><br><br><div><span class="gmail_quote"><br></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="direction: ltr;">problems encountered: multiple remotes can't connect to the same server.<br> <br> i see that the accept method (unlike tcp implementation) returns the server port upon accepting an incoming connection. for
 instance, if the server is listening on port 16, when any remote connects to the server, the server port 16 is used to establish end-to-end connection with the client. now, another device cannot connect to the same server until the first remote disconnects. this problem stops us from using multiple remotes with a single linux server.
</div></blockquote><div><br>There is no such restriction in hardware or bluetooth software stack.&nbsp; Multiple clients can be simultaneously connected to the same RFCOMM channel on a server.&nbsp; Use hcidump -X -V to find out where the connection fails.&nbsp; Make sure that the server is always the master and that the clients are always the slaves.&nbsp; This probably requires a role switch after each connect.
<br>&nbsp;</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style="direction: ltr;">&gt;rfcomm connect 00:0D:88:C0:61:55 16<br> Can't connect RFCOMM
 socket: Host is down</div></blockquote><div><br>This syntax is incorrect.&nbsp; See the rfcomm documentation.<br>&nbsp;</div>-albert</div>