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/.
Dieter Spaar spaar at mirider.augusta.deHello Harald, On Mon, 23 Mar 2009 15:05:09 -0300, "Harald Welte" <laforge at gnumonks.org> wrote: > > yes, DELETE OBJECT is currently not working in bs11_config. I or somebody else > with LMT (Dieter?) need to look at a LMT when deleting an object and compare > the binary data with what bs11_config generates in order to check for differences > and fix them. I think the DELETE OBJECT message is fine, the problem is that an object has to be locked before it can be deleted. This is how locking/unlocking looks in LMT (its basically the CHG_ADM_STATE message): ; Lock BBSIG 1 Tx 69A50200010401 Rx 61A5020001040124010701071C0100 Rx 6AA50200010401 ; Lock PA 1 Tx 69A50900010401 Rx 61A5090001040124010701071C0100 Rx 6AA50900010401 ; Unlock PA 1 Tx 69A50900010402 Rx 61A5090001040224010701071C0100 Rx 6AA50900010402 ; Unlock BBSIG 1 Tx 69A50200010402 Rx 61A5020001040224010701071C0100 Rx 6AA50200010402 After the object is locked, it can be deleted: ; Delete BBSIG 1 Tx ACA5020001 Rx ADA5020001 Please note that locking for deleting is enough, unlocking the deleted object is of course not needed. Best regards, Dieter -- Dieter Spaar, Germany spaar at mirider.augusta.de