Thank you for your reply.Yes, we have tested and found that change in LAC is truly
effective when BTS is restarted.
But we cannot understand the behavior of user (user1) which is attached to say LAC=1 and
when LAC is changed to say LAC=2 , without restarting the whole system(osmo-nitb, osmo-bts
and osmo-trx), only silent call stops working for user1 and rest of the functions keep
working. We have found that in this case, The user1 already attached to the Old LAC will
now be considered unattached for calls onlyThis user1 is however seen to be semi attached
with the network as the network still logs its channel requests if a call i made by this
userThis user1 can still receive SMS from the system only when it requests any channel
from the systemThis user1 does not go to its real network for a long period of time
Can someone explain this behavior, that a user attached to an old LAC cannot be sent a
silent call but can be sent an sms and its logs and call requests are being processed too
under new lac by same network when its LAC is changed without restarting the BTS?
P.S. Sorry for the long email. It's done for proper understanding of the scenario.
Regards,
Amber & Sarosh
Date: Tue, 10 Nov 2015 20:50:52 +0100
From: laforge(a)gnumonks.org
To: amber_sarosh(a)hotmail.com
CC: openbsc(a)lists.osmocom.org
Subject: Re: Changing Configuration Parameters Dynamically - OpenBSC
On Wed, Nov 04, 2015 at 11:32:59AM +0500, Amber and Sarosh wrote:
Hi,Can someone inform us if the VTY configuration
commands to change
parameters e.g. cell id, location area code, MS power etc. that are
run on OpenBSC VTY telnet interface take effect on next restart of
the OpenBSC session or during the same session? If former is the case,
is there any way to dynamically change Cell ID, LAC, MS TX power etc
i.e. without restarting the OpenBSC session?
* you don't need to restart openbsc to change any parameter
* some parameters (almost all under the bts/trx/ts nodes) are
communicated via A-bis OML at BTS connection time.
Those parameters are not becoming effective until the BTS re-connects
and thus goes throug OML initialization. There is a vty command that
you can use to drop the a-bis OML connection for a specific BTS.
* other parameters (affecting OpenBSC behavior directly) become
effectively immediately.
--
- Harald Welte <laforge(a)gnumonks.org>
http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)