Bug #5236
closedSGSN-side BVC still exists if corresponding BSS-NSE goes down
100%
Description
When a BSS-NSE goes down the corresponding BVCs on the SGSN-side are getting blocked, but still the BVC with all its information (BVCI, CELL, FSM, ...) is still present. If the SGSN later decides to BVC-RESET the BVC the FSM will answer with a RESET-ACK (as well as the correct cell id) and the BVC will then appear to be in working order from the SGSN point of view.
Instead of simply sending a BVC-BLOCK we should also free the sgsn-side BVC. Then the gbproxy will catch the RESET in rx_bvc_reset_from_sgsn() and answer with a STATUS cause "unknown BVCI".
Updated by daniel over 2 years ago
- % Done changed from 10 to 60
Proposed fix and test are here:
https://gerrit.osmocom.org/c/osmo-gbproxy/+/25576
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/25575
Updated by daniel over 2 years ago
- % Done changed from 60 to 90
Patches merged
https://gerrit.osmocom.org/c/osmo-gbproxy/+/25577 is still pending
Updated by daniel over 2 years ago
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
The remaining patch has been merged now as well.
