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/.
Mike McTernan (wavemobile) mike.mcternan at wavemobile.com> The current behavior is not consistent (we have attributes that apply > immediately, after a BTS restart or even only after the restart of the system). ... > So when/how do we want to apply changes? Should all changes be abpplied > after an “apply” command? How is it done by other vendors that offer a VTY > like interface? I think it is sometimes tied into the admin lock/unlock functionality. So for example, a cell maybe 'locked' and the transmitter disabled, at which point parameters can be changed as required. Then when the cell is unlocked, the new parameter set is then applied before the transmitter is re-enabled. For co-dependent parameters there may be a validation step prior to unlock to ensure that the whole configuration is consistent and valid, though I can't think of many such parameters in this situation. An alternative method is to 'lock' a cell by leaving it transmitting but marking it as barred in the SI. Such a locking scheme does raise some questions as to the granularity i.e. do we lock at a BTS, BSC, MSC level or each one. And therefore the vty needs to know which parameters can be changed according to which network entities are locked - though the command hierarchy could lend some description to that. Kind Regards, Mike