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
Chapter 7. iWRAP - Bluetooth Interface
The Bluetooth service in Access Server is controlled through the TCP socket interface called
iWRAP. The first iWRAP server is listening on port 10101. In the case of Access Server 2293, the
second iWRAP server is listening on port 10102, and the third one is listening on port 10103. All
commands to an iWRAP server and replies from the server are plain ASCII strings ending in
CR+LF ("\r\n"). Commands and replies are not case sensitive.
When connecting to a server, you must first wait for the READY. prompt. Do not send any com-
mands prior to this. Some replies are broadcast to all clients of the server. If you see something
that you have not requested or that is not intended for your client (identified by the link identi-
fier), simply ignore the reply.
Normally, the iWRAP is protected with the buffy password. The password can be disabled
or changed. For more information, see the SET command. If the password is enabled, it must
be sent first, immediately following the READY. prompt, to the iWRAP server. Otherwise, all
commands will fail.
For an example of using the iWRAP, please see the asdk/examples/btsend file in the SDK
directory.
In the following examples, bold lines are commands sent by the client to the iWRAP server
and normal lines are replies received from the iWRAP server by the client.
7.1. Terms
Bluetooth address (bdaddr) consists of six hex digits separated by a colon. For example,
"00:07:80:80:bf:01". With commands requiring a Bluetooth address, you can also use the
Bluetooth friendly name instead.
Bluetooth channels are numbered from 1 to 30. In Access Server, the Serial Port Profile is as-
signed to channel number two, the Object Push Profile and File Transfer Profile to channel num-
ber three, and the LAN Access Profile is on channel number four. The other channels are free for
user applications.
Link Identifier (link_id) is a number from 0 to 99. It is used to identify established Bluetooth
connections.
7.2. Starting the iWRAP Servers
Normally, the iWRAP servers are started automatically upon power-up. You can restart the
servers manually (for example, to apply the changes made to the iWRAP settings with the setup
application without rebooting the system). To restart the servers manually, execute the startup
script with option restart:
[root@wrap /] /etc/init.d/bluetooth restart
When the iWRAP servers start up, they use the settings configured with the setup application.
You can put additional iWRAP commands to the /etc/bluetooth.conf file. The commands in
that file are processed as the last task every time the iWRAP server is started.
68