User Manual
Table Of Contents
- Access Server
- Table of Contents
- List of Tables
- Chapter 1. Introduction to Access Server
- Chapter 2. Getting Started with Access Server
- Chapter 3. Using the System
- 3.1. Network Interfaces
- 3.2. Bluetooth
- 3.3. Compact Flash Cards
- 3.4. USB Memory Dongles and Compact Flash Memory Cards
- 3.5. Servers
- 3.5.1. Finder
- 3.5.2. ObexSender
- 3.5.3. SMS Gateway Server
- 3.5.4. User Level Watchdog
- 3.5.5. Remote Management
- 3.5.5.1. Overview
- 3.5.5.2. Management Packet Format
- 3.5.5.3. Management Packet Information File Format
- 3.5.5.4. Management Operation Example: Hello World
- 3.5.5.5. Management Operation Example: Software Update
- 3.5.5.6. Management Operation Example: IPQUERY
- 3.5.5.7. Management with USB Memory Dongle or Compact Flash Memory Card
- 3.5.6. FTP
- 3.5.7. Web Server
- 3.5.8. SNMP
- 3.5.9. OpenVPN
- 3.5.10. SSH
- 3.5.11. Telnet
- 3.5.12. NTP
- 3.6. Utilities
- 3.7. Real Time Clock
- 3.8. Time Zone
- 3.9. System ReInstall and Upgrade
- Chapter 4. SPPoverIP
- Chapter 5. Obexsender
- Chapter 6. Software Development Kit
- 6.1. Introduction to SDK
- 6.2. Installing SDK
- 6.3. Creating Applications
- Chapter 7. iWRAP Bluetooth Interface
- 7.1. Terms
- 7.2. Starting the iWRAP Servers
- 7.3. Writing iWRAP Applications
- 7.4. Commands Controlling iWRAP
- INFO
- QUIT
- SET
- SAVE
- LOAD
- PING
- PONG
- ECHO
- LOCK
- UNLOCK
- SHUTDOWN
- SLEEP
- 7.5. Finding Bluetooth Devices
- INQUIRY
- NAME
- 7.6. Making a Bluetooth Connection
- CALL
- CONNECT
- NO CARRIER
- RING
- RINGING
- CLOSE
- LIST
- STATUS
- 7.7. Service Discovery
- SDPSEARCH
- SDPATTR
- SDPQUERY
- SDP bdaddr
- SDP ADD
- SDP DEL
- SDP LIST
- 7.8. Example Sessions
- 7.9. Error Codes
- Chapter 8. I/O API
- Chapter 9. Advanced Use Cases for Access Server
- Chapter 10. Certification Information and WEEE Compliance
- Appendix A. Directory Structure
- Appendix B. Setup Options
- Appendix C. Open Source Software Licenses
- Appendix D. Supported Hardware
CONNECT
CONNECT — Connected to other device
Synopsis
This is not a command.
Description
CONNECT is not a command, but rather a reply broadcast to you when CALL successfully estab-
lishes the connection. Remember to check that the link_id matches your CALL.
On RFCOMM/L2CAP connections, there is an additional parameter called port. Port refers to
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 iWRAP server. The connection is
"raw", which means that no processing of incoming or outgoing data is made.
Note: In the case of L2CAP connections, the data is handled as packets. Therefore, both the incoming
and outgoing data must follow the "HDR+L2CAPDATA" format, where HDR is two bytes; first the
low byte, and then the high byte of the L2CAPDATA packet length. L2CAPDATA contains the actual
L2CAP packet.
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
READY.
CALL 00:07:80:80:bf:01 SDP
CALL 0
RINGING 0
CONNECT 0 SDP
CALL 00:07:80:80:bf:01 LAN PPP
CALL 1
RINGING 1
CONNECT 1 PPP
CALL 00:07:80:80:bf:01 1 RFCOMM
CALL 2
RINGING 2
CONNECT 2 RFCOMM 1042
<Client can open socket connection to port 1042>
96