User Manual

Table Of Contents

USER'S AND DEVELOPER'S GUIDE WRAP MULTIRADIO ACCESS SERVER

C: CALL 00:11:22:33:44:55 1 RFCOMM

S: CALL 2

S: CONNECT 2 RFCOMM 1042

S: STATUS 2 MSC 8d

C: CLOSE 2

S: NO CARRIER 2 ERROR 000

Incoming RFCOMM Call:

S: READY.

C: RING 2 00:11:22:33:44:55 1 RFCOMM 1042

S: STATUS 2 MSC 8d

S NO CARRIER 2 ERROR 000

9.7 E

RROR CODES

Some commands may reply with an error code. The human-readable name of the error is

displayed as well, if the "SET BLUETOOTH READABLE" setting has a value of 1 (see the

description of the SET command). Error code 8 indicates that the Bluetooth server is busy

executing any 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

Bluetooth socket server interface errors, described in in Table 10.

Code Textual form Reason

900 SERVICE_NOT_FOUND Tried to CALL a device whose SDP records doesn't

include 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

couldn't be found with inquiry.

904 BUSY Tried to CALL but there is another CALL still waiting for

CONNECT or NO CARRIER.

905 BUSY Tried to issue SDPATTR but another SDP request was

in progress.

906 BUSY Tried to issue SDPQUERY but another SDP request was

in progress.

907 NOT_CONNECTED Tried to CLOSE a connection handle that is not active.

908 BUSY Tried to issue SDPSEARCH but another SDP request

was in progress.

909 INVALID_ADDRESS Tried to NAME a device with a friendly name that can't

be found with inquiry.

90a BUSY Tried to issue NAME but another NAME was in

progress.

Table 10. Bluetooth Socket Server Interface Errors.