Hi,
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.
BR Dhananjay
On 20 Sep 2016, at 12:35, Dhananjay kumar dhananjay.cse@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
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@freyther.de wrote:
On 20 Sep 2016, at 12:35, Dhananjay kumar dhananjay.cse@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
On 21 Sep 2016, at 14:17, Dhananjay kumar dhananjay.cse@gmail.com wrote:
Dear Holger,
Hi!
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",
please consider contributing this to our manual. Together the software is moving forward.
thank you
holger
On Wed, Sep 21, 2016 at 05:47:34PM +0530, Dhananjay kumar wrote:
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.
This command only sets a loopback flag on a given lchan and does not actually initiate a call. IIUC after setting the loopback, the loopback should happen when you make a voice call using that time slot and lchan. It might make more sense to start a call and set the loopback on the lchan while the call is active. So this does not replace the other MS.
From the code it seems the loopback flag is not cleared before / after a voice call, so it looks like the given lchan will remain a loopback for any number of calls (that end up on that lchan).
I'm not 100% sure though, only skimmed the code briefly, I've never used this before.
~Neels
Thanks Neels.
Where we can get more information on this? We would like to use this loopback for BER measurements.
Is it suitable to do that?
On Wed, Sep 21, 2016 at 8:46 PM, Neels Hofmeyr nhofmeyr@sysmocom.de wrote:
On Wed, Sep 21, 2016 at 05:47:34PM +0530, Dhananjay kumar wrote:
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.
This command only sets a loopback flag on a given lchan and does not actually initiate a call. IIUC after setting the loopback, the loopback should happen when you make a voice call using that time slot and lchan. It might make more sense to start a call and set the loopback on the lchan while the call is active. So this does not replace the other MS.
From the code it seems the loopback flag is not cleared before / after a voice call, so it looks like the given lchan will remain a loopback for any number of calls (that end up on that lchan).
I'm not 100% sure though, only skimmed the code briefly, I've never used this before.
~Neels
On 30 Sep 2016, at 21:20, Mayuri Tendulkar mayuri.tendulkar@gmail.com wrote:
Thanks Neels.
Dear Mayuri,
Where we can get more information on this? We would like to use this loopback for BER measurements.
Is it suitable to do that?
a Free Software project like Osmocom exists because developers want to collaborate and it survives by people donating some (or a lot) of their time to make it better and companies (like Sysmocom) allowing developers to work on it. In your position I think you have the following options:
a.) Your company contracts someone that knows how to modify osmo-trx to do what you want for your measurement.
b.) You make yourself familiar with osmo-trx, fix/extend the code, write documentation and share it with the community.
either way, please share your findings and result with us.
thank you holger