This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Harald Welte laforge at gnumonks.orgOn Thu, Jan 28, 2010 at 10:34:11AM +0100, Holger Freyther wrote: > I'm currently implementing Early Assignment in the On Waves branch and as part > of this I will have to take care of RSL channel releases as well. > > Someone else was pointing this out as well but I could not find the email. Our > channel release is a bit sloppy and I will fix it and start using T3111 and > T3109 in the rsl code for doing so. great. > I'm going to change that into the following way. > > "normal" case: > 1.) Release the established SAPIs > 2.) After their ACKs release the Channel > Have all this guarded by T3109 (or whatever is more appropriate) > > "abnormal" case: > 1.) Start T3109 > 2.) Then do the normal case. makes perfect sense. > During the shutdown sequence I need to make sure that we are not allocating > the channel again. I'm thinking of either using the chan mode Harald was > introducing while doing the hand over work, or just a "locked" flag to not > assign the channel. are you referring to gsm_lchan_state? if yes, then there alrady is a LCHAN_S_REL_REQ state, i.e. release has been requested but not acknowleged yet, while the channel will not be allocated again. -- - Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)