cellular-infrastructure
/
osmo-bsc
mirror of https://gerrit.osmocom.org/osmo-bsc
9
0
Fork 0
Code Issues Releases Wiki Activity

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
This commit is contained in:
Philipp Maier 2016-10-20 13:55:21 +02:00 committed by Harald Welte
parent 6bbcfbb78c
commit b4ecc1d43b
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
openbsc/src/libbsc/abis_om2000.c
View File

@ -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;