From f812f3c0d4610c1a1447ac0137de5d27ef757281 Mon Sep 17 00:00:00 2001 From: Oliver Smith Date: Mon, 20 Jun 2022 11:15:01 +0200 Subject: [PATCH] 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 --- src/osmo-bsc-nat/msc_fsm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/osmo-bsc-nat/msc_fsm.c b/src/osmo-bsc-nat/msc_fsm.c index 039c7cf..71bc736 100644 --- a/src/osmo-bsc-nat/msc_fsm.c +++ b/src/osmo-bsc-nat/msc_fsm.c @@ -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 */