diff options
| author | Neels Hofmeyr <neels@hofmeyr.de> | 2021-08-02 01:41:49 +0200 |
|---|---|---|
| committer | Neels Hofmeyr <nhofmeyr@sysmocom.de> | 2022-03-04 00:32:05 +0100 |
| commit | 727dd6827167c9c792f770ec6ffee53f3f6816a7 (patch) | |
| tree | a5c797e3e85953509d0eb4c5469efba404d8b00b /tests/handover | |
| parent | 0a67e55835ea12bb6f20f03f62f8e6629e8820e4 (diff) | |
fix gscon clear 2/n: proper state transition to ST_CLEARING
The way the ST_CLEARING is entered before this patch has various
symptoms of how I / we used osmo_fsm when we were still FSM amateurs in
Osmocom. Patch that up:
- In gscon_bssmap_clear(), ask for a state transition to ST_CLEARING
first. Go ahead only if it is allowed.
- move the Clear Request messaging to ST_CLEARING's onenter function.
- Fix the timeout behavior: by using conn_fsm_state_chg(), use the
actual proper X4 timer value for ST_CLEARING from VTY configuration
instead of hardcoded magic numbers.
Related: OS#5337
Change-Id: I234b2a754d0c98031056981823cdbc187e977741
Diffstat (limited to 'tests/handover')
0 files changed, 0 insertions, 0 deletions