From 7ac0c3a8e0a7e54dc0212a7e6216da9d794c3a6c Mon Sep 17 00:00:00 2001 From: Andre Puschmann Date: Tue, 9 Feb 2021 21:06:05 +0100 Subject: [PATCH] epc,s1ap: don't log error when receiving UE capability info from eNB this fixes a warning that we had in the epc.log because we don't explicitly handle the UE capability info message received over S1AP from the eNB. Since we have a strict no-error policy in many PR tests, we can't log an error here. --- srsepc/src/mme/s1ap.cc | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/srsepc/src/mme/s1ap.cc b/srsepc/src/mme/s1ap.cc index 9b05d6015..68c6a73aa 100644 --- a/srsepc/src/mme/s1ap.cc +++ b/srsepc/src/mme/s1ap.cc @@ -261,9 +261,12 @@ void s1ap::handle_initiating_message(const asn1::s1ap::init_msg_s& msg, struct s m_logger.info("Received UE Context Release Request Message."); m_s1ap_ctx_mngmt_proc->handle_ue_context_release_request(msg.value.ue_context_release_request(), enb_sri); break; + case init_msg_type_opts_t::ue_cap_info_ind: + m_logger.info("Ignoring UE capability Info Indication."); + break; default: - m_logger.error("Unhandled S1AP intiating message: %s", msg.value.type().to_string().c_str()); - srslte::console("Unhandled S1APintiating message: %s\n", msg.value.type().to_string().c_str()); + m_logger.error("Unhandled S1AP initiating message: %s", msg.value.type().to_string().c_str()); + srslte::console("Unhandled S1APinitiating message: %s\n", msg.value.type().to_string().c_str()); } }