From 899b6cac9c3346cdac61ef5b7dd580ee4ba83327 Mon Sep 17 00:00:00 2001 From: Philipp Date: Thu, 20 Oct 2016 13:55:21 +0200 Subject: OM2000: Throw error when MO can not be enabled Throw warning message in case the MO state does not change to enabled after sendeing an Enable-Request message. Change-Id: Idfde8d6f71526e8acfea51835732515a4bee858e --- openbsc/src/libbsc/abis_om2000.c | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'openbsc/src/libbsc') diff --git a/openbsc/src/libbsc/abis_om2000.c b/openbsc/src/libbsc/abis_om2000.c index 357e2e515..1ab77b192 100644 --- a/openbsc/src/libbsc/abis_om2000.c +++ b/openbsc/src/libbsc/abis_om2000.c @@ -2368,6 +2368,16 @@ static int process_mo_state(struct gsm_bts *bts, struct om2k_decoded_msg *odm) get_value_string(om2k_msgcode_vals, odm->msg_type), get_value_string(om2k_mostate_vals, mo_state)); + /* Throw error message in case we see an enable rsponse that does + * not yield an enabled mo-state */ + if (odm->msg_type == OM2K_MSGT_ENABLE_RES + && mo_state != OM2K_MO_S_ENABLED) { + LOGP(DNM, LOGL_ERROR, + "Rx MO=%s %s Failed to enable MO State!\n", + om2k_mo_name(&odm->o2h.mo), + get_value_string(om2k_msgcode_vals, odm->msg_type)); + } + update_mo_state(bts, &odm->o2h.mo, mo_state); return 0; -- cgit v1.2.3