User Manual

Table Of Contents
Chapter 7. iWRAP - Bluetooth Interface
7.8. Example Sessions
Outgoing RFCOMM Call:
READY.
CALL 00:07:80:80:bf:01 1 RFCOMM
CALL 2
RINGING 2
CONNECT 2 RFCOMM 1042
STATUS 2 MSC 8d
<Client opens socket connection to port 1042 and transfers data>
CLOSE 2
NO CARRIER 2 ERROR 000
Incoming RFCOMM Call:
READY.
RING 2 00:07:80:80:bf:01 1 RFCOMM 1042
STATUS 2 MSC 8d
<Client opens socket connection to port 1042 and transfers data>
NO CARRIER 2 ERROR 000
7.9. Error Codes
Some commands may reply with an error code. The human-readable name of the error is dis-
played, if the
SET BLUETOOTH READABLE setting has value 1. Error code 8 indicates that the
iWRAP server is busy executing a number of commands; there can be several client applications
using the stack. Just wait a few seconds and try again. Other error codes indicate unexpected,
but often only temporary, communication problems.
You can analyze the error from the numeric code. Values bigger than or equal to 900 are iWRAP
errors, described in Table 7-5.
Code Textual Form Reason
900 SERVICE_NOT_FOUND Tried to CALL a device whose SDP
records do not include the requested
service.
901 ALREADY_CONNECTED Tried to CALL a device and a service
channel that is already connected.
902 OUT_OF_HANDLES Tried to CALL, but there are too many
open connections.
903 INVALID_ADDRESS_<addr> Tried to CALL a device with a friendly
name that could not be found with the
inquiry.
904 REJECTED An incoming call was rejected by the
iWRAP server.
905 BUSY Tried to issue SDPATTR, but another
SDP request was in progress.
114