aboutsummaryrefslogtreecommitdiffstats
path: root/src/libmsc
diff options
context:
space:
mode:
authorPau Espin Pedrol <pespin@sysmocom.de>2021-07-12 13:37:24 +0200
committerPau Espin Pedrol <pespin@sysmocom.de>2021-07-12 16:37:24 +0200
commite53ecde83e4fb2470209e818e9ad76a2d6a19190 (patch)
tree47cbc9dbeab95975a64232bcec83e971e69ca827 /src/libmsc
parent42ac3665c8e179a3a33a25da9aeff6df385bdc06 (diff)
msc_a.c: Allow MSC_A_EV_CN_CLOSE in state MSC_A_ST_RELEASING
As seen in a running osmo-msc: "vlr_access_req_fsm.c:153 msc_a(IMSI-....:MSISDN-...:TMSI-0x...:GERAN-A-8:CM_SERVICE_REQ){MSC_A_ST_RELEASING}: Event MSC_A_EV_CN_CLOSE not permitted" Also seen in several unit tests, which need update. The action event handler for that state is actually already expecting/handling the event by ignoring it, so we should allow it. Change-Id: I4d30cffab693529aab3ba736419dec116a4dd7ef
Diffstat (limited to 'src/libmsc')
-rw-r--r--src/libmsc/msc_a.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/libmsc/msc_a.c b/src/libmsc/msc_a.c
index 451220a11..0bc7b2697 100644
--- a/src/libmsc/msc_a.c
+++ b/src/libmsc/msc_a.c
@@ -1002,6 +1002,7 @@ static const struct osmo_fsm_state msc_a_fsm_states[] = {
| S(MSC_EV_CALL_LEG_TERM)
| S(MSC_MNCC_EV_CALL_ENDED)
| S(MSC_A_EV_HANDOVER_END)
+ | S(MSC_A_EV_CN_CLOSE)
,
.out_state_mask = 0
| S(MSC_A_ST_RELEASED)