Dear Holger,
Many thanks for your mail.
Based on your suggestion we did experiment on B210 with osmo-stack for
run-time network parameter control from VTY.
- Parameter change related to MS takes effects when New MS is latches
to Network. Example : MS_Max_Power
- Parameter change related to TRX takes effects when TRX is re-started.
Example : RF_Lock 0
- Parameter change related to BTS takes effects when BTS and TRX is
restared. Example : Band/ARFCN
One more query regarding loop-back call :
"bts <0-0> trx <0-0> ts <0-7> lchan <0-1> loopback",
we tried this command to start loop-back call once MS is registered to the
network.
But we are not seeing any loop-back call happening in nitb and osmo-bts
logs.
Could you please let us know more on this loop-back call. How we can use
this ?
BR
Dhananjay
On Tue, Sep 20, 2016 at 7:35 PM, Holger Freyther <holger(a)freyther.de> wrote:
On 20 Sep 2016, at 12:35, Dhananjay kumar
<dhananjay.cse(a)gmail.com>
wrote:
Dear Dhananjay,
While ruining osmo-bts and osmo-trx via VTY we
tried to change
parameter like Band ,ARFCN MS max power.
> We observed that once ARFCN is
changed on VTY TRX does not switch to new
ARFCN.
Same behavior has been observed with Band and
MS-Max-Power and RF-Locked
0/1 parameter.
> Request someone who is running
osmo-stack has controlled network ,please
reply or any document/pointer is appreciated.
few VTY parameters are applied right-away. We have:
* Some parameters are applied on restart only (e.g. channel combination of
a BTS)
* Some on new BTS connection (e.g. arfcn)
* Some on next MS connection
It would be nice if you could help us by first documenting when/which
change is applied and maybe help on creating a concept for consistent
handling. E.g. a lot of other equipment requires to bring a system into a
"lock" state, do the modification, unlock (the time things will be applied).
holger