VTY: always print MNCC handler type (internal/external)

... so that it's clear which MNCC handler is used by looking
at the output of `show running-config`.

Change-Id: Id1fe7aecc1c8445db48ff5fddcf6df0f05ba5e2e
This commit is contained in:
Vadim Yanitskiy 2023-12-22 01:53:53 +07:00 committed by fixeria
parent d0880faf79
commit 4fa6c2f636
2 changed files with 9 additions and 2 deletions

View File

@ -763,6 +763,8 @@ static int config_write_msc(struct vty *vty)
vty_out(vty, "msc%s", VTY_NEWLINE);
if (gsmnet->mncc_sock_path)
vty_out(vty, " mncc external %s%s", gsmnet->mncc_sock_path, VTY_NEWLINE);
else
vty_out(vty, " mncc internal%s", VTY_NEWLINE);
vty_out(vty, " mncc guard-timeout %i%s",
gsmnet->mncc_guard_timeout, VTY_NEWLINE);
vty_out(vty, " ncss guard-timeout %i%s",

View File

@ -99,12 +99,16 @@ OsmoMSC(config-msc)# mncc external /path/not/used
OsmoMSC(config-msc)# show running-config
...
msc
...
... ! mncc internal
mncc external /path/not/used
...
... ! mncc internal
OsmoMSC(config-msc)# mncc internal
OsmoMSC(config-msc)# show running-config
...
msc
... ! mncc external
mncc internal
... ! mncc external
OsmoMSC(config-msc)# exit
@ -157,6 +161,7 @@ network
mm info 1
...
msc
mncc internal
mncc guard-timeout 180
ncss guard-timeout 30
assign-tmsi