Hi Harald,
I think maybe it is the bootstrap_om_trx() point where we should do some extra checks:
case S_L_INP_TEI_UP: switch (isd->link_type) { case E1INP_SIGN_OML: if (isd->trx->bts->type != GSM_BTS_TYPE_NOKIA_SITE) break;
if (isd->tei == isd->trx->bts->oml_tei) bootstrap_om_bts(isd->trx->bts); else bootstrap_om_trx(isd->trx); <----- HERE ?? break; default: break; }
?
Can we reuse the 12.21 state and make a simple check if the TRX is unlocked already (triggered by the BTS_STATE_CHANGE (trx, enabled) OML message)?
The other problem I am having is that the Object Identity size is bigger than all the examples I can find in the code:
00 01 02 FF
00 is some leading zeroes (not specified actually). 01 is the object type (for example BCF, BTS, TRX etc.) 02 is the object number (mostly TRX, or TRE in some bigger installs on UltraSite for example) FF is mostly not relevant.
How to process this with the find_element() function? I can only read and check the first byte.
Regards, Csaba
Harald Welte laforge@osmocom.org ezt írta (időpont: 2025. jan. 16., Cs, 17:30):
Hi Csaba,
On Thu, Jan 16, 2025 at 01:15:08PM +0100, Sipos Csaba wrote:
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).
that's true. You would have to add that somehow. I don't recall the details of the code off my head, but it shouldn't be too hard to split that in two steps and let the bts model decide when to start the RSL bootstrap?
--
- Harald Welte laforge@osmocom.org https://laforge.gnumonks.org/
============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)