diff options
| author | Neels Hofmeyr <neels@hofmeyr.de> | 2019-10-08 01:11:55 +0200 |
|---|---|---|
| committer | Neels Hofmeyr <neels@hofmeyr.de> | 2019-10-08 08:20:16 +0200 |
| commit | 287063d56e55304ee9b4a56fdeeadf28d21328a2 (patch) | |
| tree | fa4b93e586568bd729b547281dcabd12180e5d62 /src/libmsc/ran_msg_a.c | |
| parent | 88102322a05479b1af5ef7e93a58e40d81a867d9 (diff) | |
fsm: use deferred deallocation and term_stops_actions
Since osmo-bsc uses the MGCP client FSMs, it is required to enable these new
features to guarantee safe operation. The issue is described in detail in
commit logs linked below.
Notably, osmo-msc currently chooses to omit error handling during MGCP events
(marked "FIXME"). An upcoming patch implements this error handling, and would
make osmo-msc vulnerable to crash from unexpected MGCP messages.
Depends: Ief4dba9ea587c9b4aea69993e965fbb20fb80e78 (libosmocore),
I0adc13a1a998e953b6c850efa2761350dd07e03a (libosmocore)
Related: I7df2e9202b04e7ca7366bb0a8ec53cf3bb14faf3 (osmo-mgw)
Change-Id: I08c03946605aa12e0a5ce8b3c773704ef5327a7a
Diffstat (limited to 'src/libmsc/ran_msg_a.c')
0 files changed, 0 insertions, 0 deletions