path: root/include/osmocom/msc/gsm_data.h
diff options
authorKeith Whyte <keith@rhizomatica.org>2019-08-08 15:43:40 +0200
committergsmevent admin <admin@gsmevent.box>2019-08-24 15:48:42 +0200
commit5b47ac2bf6c97cc4fbbbd5567bcec61478a2eb55 (patch)
treed24d641c9b77c0b58539e3cc28ba695a05021198 /include/osmocom/msc/gsm_data.h
parent9e6ec575879050db9878e31fe801017222be5542 (diff)
Implement a global switch on the network to disable call waiting.cccamp2019
Add a network -> callwaiting VTY command as boolean. When this is enabled (default) there is no change to operation previous to this commit. When this switch is disabled with "no call-waiting" in vty then when a call arrives, we will check if we have an active call transaction for this subscriber, no matter if it is establishing, established, or alerting, in any of these cases we will return USER BUSY to the calling party. Change-Id: I3eb6f23f7103e3002874fb5d3a30c9de952202ae
Diffstat (limited to 'include/osmocom/msc/gsm_data.h')
1 files changed, 3 insertions, 0 deletions
diff --git a/include/osmocom/msc/gsm_data.h b/include/osmocom/msc/gsm_data.h
index a90b732af..11b6e8237 100644
--- a/include/osmocom/msc/gsm_data.h
+++ b/include/osmocom/msc/gsm_data.h
@@ -258,6 +258,9 @@ struct gsm_network {
/* Whether we want to use Osmux against BSCs. Controlled via VTY */
enum osmux_usage use_osmux;
+ /* Whether to use call waiting on the network */
+ bool call_waiting;
struct osmo_esme;