diff options
| author | Neels Hofmeyr <nhofmeyr@sysmocom.de> | 2022-03-03 01:50:50 +0100 |
|---|---|---|
| committer | Neels Hofmeyr <nhofmeyr@sysmocom.de> | 2022-03-09 00:01:06 +0100 |
| commit | 908f014f0967cf8a26260e4e35745835e780c603 (patch) | |
| tree | 8b2eacd920324582398b70ec62e60276fc7f1e30 /include | |
| parent | bdead6e87ab6bb07c662dc2f27a0b41359b0f576 (diff) | |
support "empty" SCCP N-Connect from MSC
Teach osmo-bsc to handle empty N-Connect. So far we were always
expecting user data in an SCCP N-Connect from an MSC. However, it is
perfectly valid for an initial BSSMAP request to follow later.
This is relevant for:
- Handover Request (incoming inter-BSC handover)
- Perform Location Request (query physical location of the MS)
Add state WAIT_INITIAL_USER_DATA with new timeout net X25. Always enter
this state so that we don't have two separate code paths for handling
initial user data.
Related: SYS#5864
Change-Id: I535c791fa01e99a2226392eb05f676ba6c3cc16e
Diffstat (limited to 'include')
| -rw-r--r-- | include/osmocom/bsc/bsc_subscr_conn_fsm.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/include/osmocom/bsc/bsc_subscr_conn_fsm.h b/include/osmocom/bsc/bsc_subscr_conn_fsm.h index d7deb06a8..0e495aae2 100644 --- a/include/osmocom/bsc/bsc_subscr_conn_fsm.h +++ b/include/osmocom/bsc/bsc_subscr_conn_fsm.h @@ -9,6 +9,7 @@ enum gscon_fsm_event { /* local SCCP stack tells us incoming conn from MSC */ GSCON_EV_A_CONN_IND, + GSCON_EV_A_INITIAL_USER_DATA, /* RSL side requests CONNECT to MSC */ GSCON_EV_MO_COMPL_L3, /* MSC confirms the SCCP connection */ |