osmo-bsc/tests
Pau Espin f8d0389c70 bsc: Send MS Power Control msg upon max MS power change
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
2019-11-20 15:35:05 +01:00
..
abis bsc: Send MS Power Control msg upon max MS power change 2019-11-20 15:35:05 +01:00
bsc bsc: Send MS Power Control msg upon max MS power change 2019-11-20 15:35:05 +01:00
codec_pref Fix some typos 2019-11-13 22:10:41 +01:00
gsm0408 bsc: Send MS Power Control msg upon max MS power change 2019-11-20 15:35:05 +01:00
handover Fix some typos 2019-11-13 22:10:41 +01:00
nanobts_omlattr bsc: Send MS Power Control msg upon max MS power change 2019-11-20 15:35:05 +01:00
subscr cosmetic: bsc_subscr_alloc: log initial get 2018-06-08 16:16:42 +00:00
Makefile.am make: allow vty-tests without configure 2018-09-27 03:32:35 +02:00
atlocal.in Fix repo split aftermath 2017-10-02 08:38:34 +00:00
ctrl_test_runner.py osmo-bsc.cfg: work with osmo-bts example cfg 2019-07-24 19:31:24 +00:00
handover_cfg.vty doc/manuals, vty doc: more handover doc clarifications 2019-07-09 15:42:38 +00:00
neighbor_ident.vty add vty 'no neighbors' to remove all HO targets 2019-08-13 21:45:34 +00:00
osmo-bsc.vty resurrect meas_feed.c: vty, vty-test 2018-05-04 15:02:24 +00:00
testsuite.at inter-BSC HO: add neighbor_ident API to manage neighbor-BSS-cells 2018-07-28 12:18:23 +02:00
vty_test_runner.py remove remaining bits of osmo-bsc_nat 2018-05-27 17:48:49 +02:00