aboutsummaryrefslogtreecommitdiffstats
path: root/src/ipaccess
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/ipaccess
parent26adddf1bfa37dbeff8e60594141e9fb3afdd46e (diff)
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
Diffstat (limited to 'src/ipaccess')
-rw-r--r--src/ipaccess/ipaccess-config.c6
-rw-r--r--src/ipaccess/ipaccess-proxy.c6
2 files changed, 12 insertions, 0 deletions
diff --git a/src/ipaccess/ipaccess-config.c b/src/ipaccess/ipaccess-config.c
index f8738091d..306cc8786 100644
--- a/src/ipaccess/ipaccess-config.c
+++ b/src/ipaccess/ipaccess-config.c
@@ -1141,3 +1141,9 @@ int osmo_bsc_sigtran_open_conn(struct gsm_subscriber_connection *conn, struct ms
{
return 0;
}
+
+/* Stub */
+int rsl_chan_ms_power_ctrl(struct gsm_lchan *lchan)
+{
+ return 0;
+}
diff --git a/src/ipaccess/ipaccess-proxy.c b/src/ipaccess/ipaccess-proxy.c
index a4ee10efc..3d5f301d8 100644
--- a/src/ipaccess/ipaccess-proxy.c
+++ b/src/ipaccess/ipaccess-proxy.c
@@ -1248,3 +1248,9 @@ int main(int argc, char **argv)
osmo_select_main(0);
}
}
+
+/* Stub */
+int rsl_chan_ms_power_ctrl(struct gsm_lchan *lchan)
+{
+ return 0;
+}