Make logging message about received RANAP message more meaningful

The message being used previously seemed to indicate something was
wrong with the message. The reality is that we are simply not handling
most of them, and they will end up being forwarded as they come in
osmo-hnbgw.

Related: SYS#5573
Change-Id: If63d942496491f1e9ee454034ec97d25764fde65
This commit is contained in:
Pau Espin 2022-05-30 16:12:12 +02:00
parent c6e118af7a
commit 1d5c67aea5
2 changed files with 4 additions and 3 deletions

View File

@ -74,8 +74,8 @@ static int cn_ranap_rx_initiating_msg_co(void *ctx, RANAP_InitiatingMessage_t *i
rc = ranap_decode_iu_releasecommandies(&message->msg.iu_ReleaseCommandIEs, &imsg->value);
break;
default:
LOGP(DRANAP, LOGL_NOTICE, "Received suspicious RANAP "
"Procedure %s (CO, IM) from RNC, ignoring\n",
LOGP(DRANAP, LOGL_INFO,
"Received RANAP Procedure %s (CO, IM) from RNC. Decode not implemented\n",
get_value_string(ranap_procedure_code_vals, imsg->procedureCode));
rc = -1;
break;

View File

@ -50,7 +50,8 @@ static int ran_ranap_rx_initiating_msg_co(void *ctx, RANAP_InitiatingMessage_t *
rc = ranap_decode_iu_releasecommandies(&message->msg.iu_ReleaseCommandIEs, &imsg->value);
break;
default:
LOGP(DRANAP, LOGL_NOTICE, "Received suspicious RANAP Procedure %s (CO, IM) from CN, ignoring\n",
LOGP(DRANAP, LOGL_INFO,
"Received RANAP Procedure %s (CO, IM) from CN. Decode not implemented\n",
get_value_string(ranap_procedure_code_vals, imsg->procedureCode));
rc = -1;
break;