Feature #5213
closed
cannot set bts-timers without a BTS being actively connected
Added by neels over 2 years ago.
Updated over 2 years ago.
Description
In the PCU VTY, doing 'show bts-timers' only works when a BTS is actually connected.
So there is no way to configure T timers for individual BTS from the config file -- is that intentional?
We would probably need to add 'bts N' nodes to the VTY config?
On Thu, Aug 12, 2021 at 01:07:06PM +0000, neels [REDMINE] wrote:
In the PCU VTY, doing 'show bts-timers' only works when a BTS is actually connected.
So there is no way to configure T timers for individual BTS from the config file -- is that intentional?
We would probably need to add 'bts N' nodes to the VTY config?
In case this was not clear - a lot of GPRS timers are set via Abis OML in the GPRS related OML MOs. This is how ip.access did it, and we implemented it in identical fashion.
So for those timers communicated via OML and pcu_sock in the BSC -> BTS -> PCU path,
there shouldn't be any local configuration in the PCU config file.
If there are additional timers beyond what can be configured that way, then those might be
in the OsmoPCU config. However, for consistency I would actually suggest also to specify
them in the BSC and extend OML / pcu_sock accordingly.
- Status changed from New to Rejected
Ah, BTS timers come in from the BSC, it all makes sense now.
Also available in: Atom
PDF
