pespin has uploaded this change for review.

View Change

Add specific log message for unimplemented LocationReportingControl

The message being used previously seemed to indicate something was
wrong with the message. The reality is that we are simply not handling
it.

Related: SYS#5573
Change-Id: If63d942496491f1e9ee454034ec97d25764fde65
---
M src/ranap_common_ran.c
1 file changed, 5 insertions(+), 0 deletions(-)

git pull ssh://gerrit.osmocom.org:29418/osmo-iuh refs/changes/08/28208/1

diff --git a/src/ranap_common_ran.c b/src/ranap_common_ran.c
index f3fa519..7986d65 100644
--- a/src/ranap_common_ran.c
+++ b/src/ranap_common_ran.c
@@ -49,6 +49,11 @@
 	case RANAP_ProcedureCode_id_Iu_Release:
 		rc = ranap_decode_iu_releasecommandies(&message->msg.iu_ReleaseCommandIEs, &imsg->value);
 		break;
+	case RANAP_ProcedureCode_id_LocationReportingControl:
+		LOGP(DRANAP, LOGL_INFO, "Received RANAP Procedure %s (CO, IM) from CN not implemented\n",
+			 get_value_string(ranap_procedure_code_vals, imsg->procedureCode));
+		rc = -1;
+		break;
 	default:
 		LOGP(DRANAP, LOGL_NOTICE, "Received suspicious RANAP Procedure %s (CO, IM) from CN, ignoring\n",
 		     get_value_string(ranap_procedure_code_vals, imsg->procedureCode));

To view, visit change 28208. To unsubscribe, or for help writing mail filters, visit settings.