|
|
DLCI Allocation in Client/Server Applications 2
Original Post: This is regarding RFCOMM DLCI & server channel business
(eGroups Msg. ) Date: 2000-08-16
Note: server application on the non-initiating
device are allocated DLCIs 2,4,6,…,60 (even numbers); and server applications
on the initiating device are allocated DLCIs 3,5,7,…,61 (odd numbers). This
DLCI value is determined by combining the Server channel number and the
direction bit of the proposed new link.
Assuming A and B have an RFCOMM session
established.
A initiates a DLC connection with B on Server Channel number
1, the DLCI for A will be 000011 and the DLCI for B will be 000010 (where the
rightmost bit is the D bit). A needs to put 000010 as DLCI in the Address field
to get the Server Channel number 1 connected on B, and B needs to put 000011 as
DLCI in the Address field to get the Server Channel number 1 connected on A.
If B wants to initiate a DLC connection with A, since Server
Channel number 1 has been used (corresponding DLCIs are 000010 (0x02) and 000011
(0x03)), a different Server Channel number needs to be used and corresponding
DLCIs can be determined with the appropriate D bits.
Note: see also 'DLCI Allocation
in Client/Server Applications 1'
|
