User Manual
Table Of Contents
- INTRODUCTION
- CONTROLLING THE ACCESS SERVER
- CONFIGURATION
- USING THE SYSTEM
- BLUETOOTH TECHNOLOGY OVERVIEW
- INTRODUCTION TO SDK
- INSTALLING THE WRAP SOFTWARE DEVELOPMENT ENVIRONMENT
- CREATING WRAP APPLICATIONS
- BLUETOOTH SERVER SOCKET INTERFACE
- I/O API
- ABOUT BLUEGIGA
- APPENDIX A – WRAP DIRECTORY STRUCTURE
USER'S AND DEVELOPER'S GUIDE WRAP MULTIRADIO ACCESS SERVER
9.4.2 C
ONNECT
CONNECT is not a command, but rather a reply broadcast to you when CALL successfully
makes the connection. Remember to check that the link_id matches your CALL!
On RFCOMM/L2CAP connections, there is an additional parameter called port. It is the TCP
socket port number, which is used to send and receive data to and from the remote device.
Connect to the port just like you connected to the Bluetooth server. The connection is "raw",
which means that no processing of incoming or outgoing data is made.
Note: In case of L2CAP connections, the data is handled as packets. Therefore both the
incoming and outgoing data must follow the format "HDR+L2CAPDATA", where HDR is two
bytes; first the low byte and then the high byte of the length of the L2CAPDATA packet and
L2CAPDATA contains the actual L2CAP-packet.
Command: This is not a command.
Reply:
CONNECT link_id SDP
CONNECT link_id RFCOMM port
CONNECT link_id L2CAP port
CONNECT link_id PPP
CONNECT link_id FORK
CONNECT link_id PAN-PANU
CONNECT link_id PAN-GN
CONNECT link_id PAN-NAP
Example:
S: READY.
C: CALL 00:11:22:33:44:55 SDP
S: CALL 0
S: CONNECT 0 SDP
C: CALL 00:11:22:33:44:55 4 PPP
S: CALL 1
S: CONNECT 1 PPP
C: CALL 00:11:22:33:44:55 1 RFCOMM
S: CALL 2
S: CONNECT 2 RFCOMM 1042
<Client can open socket connection to port 1042>
C: CALL 00:11:22:33:44:55 2 FORK /bin/login
S: CALL 3
S: CONNECT 3 FORK
C: CALL 00:11:22:33:44:66 PAN-NAP
S: CALL 5
S: CONNECT 5 PAN-NAP
C: CALL 00:11:22:33:44:77 PAN-NAP PAN-NAP
S: CALL 6
S: CONNECT 6 PAN-NAP
Bluegiga Proprietary, Copyright © Bluegiga Technologies 2001-2004 69 (94)