From 22edbf3f846b13a404dd4e49c3ed25d757d3f527 Mon Sep 17 00:00:00 2001 From: Vadim Yanitskiy Date: Mon, 11 Dec 2017 04:26:12 +0700 Subject: mobile: add MNCC handler selection to settings Since the mobile application is potentionally able to work with multiple MS instances, it's better to have a possibility to choose an MNCC (Call Control) handler per each MS separately. This change cleans up the code, removing a dedicated command-line option '-m' intended for enabling extarnal MNCC. Now it's possible to set an MNCC-handler for each MS via VTY interface and settings. The following MNCC-handlers are available: - mobile - build-in MNCC-handler (default); - socket - external MNCC-handler via UNIX-socket (e.g. LCR); - dummy - dummy handler without CC support. Change-Id: I2df91c7a79ba5c39bc6ceae900ef649129dd0346 --- src/host/layer23/include/osmocom/bb/mobile/settings.h | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'src/host/layer23/include/osmocom/bb/mobile/settings.h') diff --git a/src/host/layer23/include/osmocom/bb/mobile/settings.h b/src/host/layer23/include/osmocom/bb/mobile/settings.h index 30e88258..99bbbdae 100644 --- a/src/host/layer23/include/osmocom/bb/mobile/settings.h +++ b/src/host/layer23/include/osmocom/bb/mobile/settings.h @@ -3,11 +3,24 @@ #define MOB_C7_DEFLT_ANY_TIMEOUT 30 +/* How CC (Call Control) messages should be handled? */ +enum mncc_handler_t { + /* by built-in mobile MNCC */ + MNCC_HANDLER_MOBILE, + /* by external MNCC application via UNIX-socket */ + MNCC_HANDLER_SOCKET, + /* no call support */ + MNCC_HANDLER_DUMMY, +}; + struct gsm_settings { char layer2_socket_path[128]; char sap_socket_path[128]; char mncc_socket_path[128]; + /* MNCC handler */ + enum mncc_handler_t mncc_handler; + /* IMEI */ char imei[16]; char imeisv[17]; -- cgit v1.2.3