Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2013-01-28 | bts: Allow to exclude a BTS from the global RF lock handling | Holger Hans Peter Freyther | 1 | -3/+25 | |
Some BTS might be in locations where they can run all the time, allow to exclude them from the global lock handling. | |||||
2013-01-15 | bsc: Auto RF Off in case of missing MSC connection | Holger Hans Peter Freyther | 1 | -0/+53 | |
For short IP failures we want the RF to stay up and wait for the re-connect but in case the A-link is gone too long it is good to switch off the RF and wait for commands to enable it again. | |||||
2013-01-15 | bsc: Use the BSC RF CTRL to change the RF state of the TRXs | Holger Hans Peter Freyther | 1 | -3/+7 | |
Use the delayed scheduling feature of the osmo_bsc_rf class to avoid crashing the site controller of the nanoBTS. | |||||
2013-01-15 | bsc: Do not re-start the grace timer when we are in the grace period | Holger Hans Peter Freyther | 1 | -0/+5 | |
2012-09-11 | osmo-bsc: Include rf statistics in the location-state TRAP as well | Daniel Willmann | 1 | -0/+81 | |
The first fields are still the location up to the height. The next field is "operational" if any of the trx are operational, otherwise "inoperational" The second to last field contains "locked" if all of the trx are in the admin state, otherwise "unlocked". The last field represents the rf policy currently in effect. It is one of (on|off|grace|unknown). <tstamp>,<valid>,<lat>,<lon>,<height>,<oper>,<admin>,<policy> | |||||
2012-05-17 | bsc: Move the osmo_bsc_rf file into the libbsc code and rename | Holger Hans Peter Freyther | 1 | -0/+365 | |
The nitb will provide the RF interface as well. |