Dear list, At the moment setting up the RSL lapd link and start its bootstrap (BCCH info and SACCH filling) is done in one go (as much as I can see).
The issue with this is for the Nokia Site family: per spec. we should let the RSL lapd link to be initiated by the BTS and once that lapd link is up, the BTS sends a BTS_STATE_CHANGED message with "TRX, enabled" object id and object current state, and only after this we should start sending the BCCH info and SACCH filling (the "actual" bootstrap of the RSL). For this to work, we need the Object Identity and Object Current State attributes (which is a WIP atm), but somehow it should be possible to separate the RSL bootstrap to RSL lapd only and RSL bcch info + sacch filling. I am unaware if the above separation is possible with the current codebase, but if someone can shed some light on this, that would be appreciated. Adding the Object Identity and Object Current State will also allow us to detect the actual state changes of various BTS objects (mostly the TRX), and we can also use the BTS_CHA_ADM_STATE to actually lock/unlock TRXes, so we dont need to fake the 12.21 state anymore. Regards, Csaba
