osmo-bsc[master]: trigger acc ramping on state-changed-event reports

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.

Stefan Sperling gerrit-no-reply at lists.osmocom.org
Thu Apr 12 07:38:15 UTC 2018


Patch Set 1:

> Please also test with osmo-bts

A sysmobts reports TRX lock/unlock only via Change Administrative State ACK.

Its State Changed Event Reports only contain information about operational and availability states (as we would expect from reading the GSM spec).

Unlike the nanobts, a sysmobts does not send a State Changed event Report when trx 0 is locked or unlocked. It looks like these messages do not trigger for administrative state changes.

Regardless, ACC ramping still works as expected with a sysmobts.

-- 
To view, visit https://gerrit.osmocom.org/7770
To unsubscribe, visit https://gerrit.osmocom.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I097a113a3a63de02bcb8277020beb59cf485b176
Gerrit-PatchSet: 1
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Owner: Stefan Sperling <ssperling at sysmocom.de>
Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: Stefan Sperling <ssperling at sysmocom.de>
Gerrit-HasComments: No



More information about the gerrit-log mailing list