diff options
| author | Neels Hofmeyr <nhofmeyr@sysmocom.de> | 2022-03-03 01:50:50 +0100 |
|---|---|---|
| committer | Neels Hofmeyr <nhofmeyr@sysmocom.de> | 2022-03-04 00:32:05 +0100 |
| commit | 95bbe3c41b652b069448f862e18875fcd2b204a3 (patch) | |
| tree | edb097363a974b2a9b8d97918324c0b609554788 /src/osmo-bsc/abis_bs11.c | |
| parent | c254b9e00ddc601f4cfdd6adc9a3768a69d53a14 (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 'src/osmo-bsc/abis_bs11.c')
0 files changed, 0 insertions, 0 deletions