Bug #3205
closed
dynamic timeslots initialized at the wrong time
Added by neels about 6 years ago.
Updated almost 6 years ago.
Description
dyn_ts_init() is called before the OPSTART ACK for the channel is received.
So far we got away with it, but should rather wait for OPSTART ACK before setting the initial Chan Activ of a dynamic timeslot.
(I have a patch for that ready, written on OsmoDevCon, that needs to be tested once dyn ts are fixed again)
- Related to Bug #3197: dyn TS not configured properly during OML startup added
- Status changed from New to In Progress
- % Done changed from 0 to 50
Doing the dyn TS init on Channel Opstart Ack seemed a good idea, since on BTS models that I tried, the RSL link is already established on OML Opstart.
Looking at the ttcn3-bsc-tests however makes abundantly clear that there may not be any RSL link yet.
So I actually need to check for dyn TS init in both places:
- upon opstart, if RSL is up, do dyn TS init. If no RSL link is present, don't.
- upon RSL bootstrap, if opstart has already taken place, do dyn TS init.
- upon OML restart, dyn TS init state needs to be cleared so that PDCH is activated again.
If the RSL link were taken down and re-established, I do not need to re-init PDCH, or do I?
- Status changed from In Progress to Resolved
- % Done changed from 50 to 100
Also available in: Atom
PDF
