aboutsummaryrefslogtreecommitdiffstats
path: root/src/osmo-bsc/osmo_bsc_bssap.c
diff options
context:
space:
mode:
authorPau Espin Pedrol <pespin@sysmocom.de>2019-11-12 16:30:30 +0100
committerPau Espin Pedrol <pespin@sysmocom.de>2019-11-20 15:35:05 +0100
commitf8d0389c70ed97cbb0488c0b7e5ac594d566fdb5 (patch)
tree80ade7bb419c27e2b6557c9e31e6ec38aa9ed6fa /src/osmo-bsc/osmo_bsc_bssap.c
parent26adddf1bfa37dbeff8e60594141e9fb3afdd46e (diff)
bsc: Send MS Power Control msg upon max MS power changeHEADmaster
Lots of times, the MS power class is unknown until after the first channel has been activated, at which point the MS power class is received in messages such as LU update or CM Service Requet. Since the MS Power level is sent upon CHAN ACT, the only way to communicate the change of maximum MS Power (based on MS power class) after CHAN ACT is to send a MS Power Control msg. Let's do that. Related: OS#4244 Change-Id: I3d6b75578e5cb9b2ad474a0ad01362d846ebe135
Diffstat (limited to 'src/osmo-bsc/osmo_bsc_bssap.c')
0 files changed, 0 insertions, 0 deletions