SGSN-side BVC still exists if corresponding BSS-NSE goes down
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".
gbproxy: Remove SGSN-side BVC after sending BVC-BLOCK
If we keep the bvc around the SGSN could send a BVC-RESET which the
gbproxy would ACK. This will reestablish the BVC only between the gbproxy and
SGSN which can lead to all sorts of issues.
With this patch the gbproxy will respond with a BVC-STATUS cause BVCI
#1 Updated by daniel about 1 month ago
- % Done changed from 10 to 60
Proposed fix and test are here: