diff options
author | Harald Welte <laforge@gnumonks.org> | 2018-02-14 00:14:58 +0100 |
---|---|---|
committer | Harald Welte <laforge@gnumonks.org> | 2018-02-14 00:28:10 +0100 |
commit | 7421a6e4b7b7c9f4f0a529c7aa05ad801c0cae1d (patch) | |
tree | 480fc0314a18cc28af2d6e9b2dab36b3fb220d0b /src/osmo-msc | |
parent | 9199f8b60ddf0821e2df7ddafee4bf27b1c454a8 (diff) |
remove unused dyn_ts_allow_tch_f VTY option
This belongs into the BSC and has no relevance in the MSC, as the MSC
has no clue about dynamic timeslots.
Related: OS#2528
Change-Id: Iaa41d22db81120572d4cd2c0c4c75d258947a42f
Diffstat (limited to 'src/osmo-msc')
-rw-r--r-- | src/osmo-msc/msc_main.c | 14 |
1 files changed, 0 insertions, 14 deletions
diff --git a/src/osmo-msc/msc_main.c b/src/osmo-msc/msc_main.c index 2413c4328..b0b78be31 100644 --- a/src/osmo-msc/msc_main.c +++ b/src/osmo-msc/msc_main.c @@ -402,20 +402,6 @@ int main(int argc, char **argv) return -1; #endif - /* - * For osmo-nitb, skip TCH/F for now, because otherwise dyn TS - * always imply the possibility to have a mix of TCH/F and - * TCH/H channels; if two phones request a TCH/F and a TCH/H, - * respectively, they cannot call each other. If we deny TCH/F, - * they will both fall back to TCH/H, and dynamic channels are - * usable. See OS#1778. - * - * A third-party MSC may well be able to handle a TCH/H TCH/F - * mismatch. Moreover, this option may be overwritten in the - * config file or in VTY. - */ - msc_network->dyn_ts_allow_tch_f = false; - rc = vty_read_config_file(msc_cmdline_config.config_file, NULL); if (rc < 0) { LOGP(DMSC, LOGL_FATAL, "Failed to parse the config file: '%s'\n", |