aboutsummaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorVadim Yanitskiy <axilirator@gmail.com>2018-11-20 06:20:53 +0700
committerVadim Yanitskiy <axilirator@gmail.com>2018-12-30 11:48:22 +0100
commitf40e46fdf4b727f415e6308ecaac4399896f51f1 (patch)
tree3e18c439963830f923df381098dfb0f8c25a9c12 /include
parent3332ac44308e54b0f55466757730a93e2294028b (diff)
libmsc/VTY: introduce kill-switch for routing SMS over GSUP
As a rudiment of OsmoNiTB, OsmoMSC is still involved in SMS processing, storage (in SQLite DB), and routing (via SMPP). In real networks this is done by the external entity called SMSC (SMS Centre), while the MSC is doing re-encapsulation of GSM 04.11 SM-TL (Transport Layer) payload (i.e. TPDU) between SM-RL (Relay Layer) and MAP. Since OsmoMSC itself is not a 'Network in The Box' anymore, it makes sense to replicate the 'traditional' behaviour of MSC. The problem is that this behaviour cannot co-exist with the current implementation, so the key idea is to rip out the local SMS storage and routing from OsmoMSC, and (re)implement it in a separate process (OsmoSMSC?). As a temporary solution, this change introduces a 'kill-switch' VTY option that enables routing of SMS messages over GSUP towards ESME (through VLR and HLR), but breaks the local storage and routing. This is why it's disabled by default. As soon as we move the SMS processing and storage away from OsmoMSC, this behaviour would be enabled by default, and the VTY option would be hidden and deprecated. At the moment, this option basically does nothing, and will take an effect in the follow-up changes. Change-Id: Ie57685ed2ce1e4c978e775b68fdffe58de44882b Related: OS#3587
Diffstat (limited to 'include')
-rw-r--r--include/osmocom/msc/gsm_data.h8
1 files changed, 8 insertions, 0 deletions
diff --git a/include/osmocom/msc/gsm_data.h b/include/osmocom/msc/gsm_data.h
index d2511cb7b..dab082d82 100644
--- a/include/osmocom/msc/gsm_data.h
+++ b/include/osmocom/msc/gsm_data.h
@@ -160,6 +160,14 @@ struct gsm_network {
struct gsm_sms_queue *sms_queue;
+ /* The "SMS over GSUP" kill-switch that basically breaks internal
+ * SMS routing (i.e. SQLite DB and SMPP), and enables forwarding
+ * of short messages over GSUP towards ESME (through VLR and HLR).
+ * Please see OS#3587 for details. This is a temporary solution,
+ * so it should be removed as soon as we move the SMS processing
+ * logic to an external process (OsmoSMSC?). REMOVE ME! */
+ bool sms_over_gsup;
+
/* control interface */
struct ctrl_handle *ctrl;