aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPau Espin Pedrol <pespin@sysmocom.de>2021-07-29 14:40:23 +0200
committerPau Espin Pedrol <pespin@sysmocom.de>2021-07-29 14:40:26 +0200
commitfc842fba246fd22d6bcc6f05d4c297fc8c82f317 (patch)
treee9cc353a53c40cf72e789f78d724a48709d21ce9
parent9612a7c23e40491916301eee7cb795c32fc03cc8 (diff)
Clarify string name for GSM_CHREQ_REASON_CALL
The previous naming was confusing since when appearing on log files it seemed to mean the reason was mainly only call reestablishment, when it actually means either call establishment (the usual reason) OR call re-establishment (should happen seldomly). Let's add some parenthesis to make it clearer. Related: SYS#5548 Change-Id: Id2dccd71803335c284a5ba271fa7f7890d253c27
-rw-r--r--src/osmo-bsc/gsm_data.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/osmo-bsc/gsm_data.c b/src/osmo-bsc/gsm_data.c
index 7140ad70a..4db70f060 100644
--- a/src/osmo-bsc/gsm_data.c
+++ b/src/osmo-bsc/gsm_data.c
@@ -172,7 +172,7 @@ void gsm_mo_init(struct gsm_abis_mo *mo, struct gsm_bts *bts,
const struct value_string gsm_chreq_descs[] = {
{ GSM_CHREQ_REASON_EMERG, "emergency call" },
{ GSM_CHREQ_REASON_PAG, "answer to paging" },
- { GSM_CHREQ_REASON_CALL, "call re-establishment" },
+ { GSM_CHREQ_REASON_CALL, "call (re-)establishment" },
{ GSM_CHREQ_REASON_LOCATION_UPD,"Location updating" },
{ GSM_CHREQ_REASON_PDCH, "one phase packet access" },
{ GSM_CHREQ_REASON_OTHER, "other" },