cellular-infrastructure
/
osmo-bsc-nat
mirror of https://gerrit.osmocom.org/osmo-bsc-nat
10
1
Fork 1
Code Issues Releases Wiki Activity

msc_fsm: log level NOTICE for "could not send reset" 

It is expected that sending the reset may not work right away. Set the
log level to NOTICE, so when filtering for error we only see real
errors. If a MSC isn't configured properly, the message will be printed
over and over so users should see it even with the NOTICE log level.

Related: SYS#5560
Change-Id: I9586e1773d377ca457ab1d786df8fdbd8c8f899f
This commit is contained in:
Oliver Smith 2022-06-20 11:15:01 +02:00
parent 5cab5a4403
commit f812f3c0d4
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/osmo-bsc-nat/msc_fsm.c
View File

@ -73,7 +73,7 @@ static void st_disconnected(struct osmo_fsm_inst *fi, uint32_t event, void *data
LOGP(DMAIN, LOGL_DEBUG, "Tx RESET to %s\n", talloc_get_name(msc));
if (bssmap_tx_reset(g_bsc_nat->cn.sccp_inst, &msc->addr) < 0) {
LOGP(DMAIN, LOGL_ERROR, "Could not send RESET to MSC (SCCP not up yet?)\n");
LOGP(DMAIN, LOGL_NOTICE, "Could not send RESET to MSC (SCCP not up yet?)\n");
}
/* Retry if RESET ACK was not received from MSC */