Bug #4897
open
gbproxy2: Re-introduce handling of NS_AFF_CAUSE_FAILURE
Added by laforge over 3 years ago.
Updated about 3 years ago.
Description
We need to figure out what exactly to do in situatoins where NS is reporting failures of the underlying netowkr to us, and test those situations.
- Related to Feature #4472: Intra-domain connection of OsmoGBPROXY to multiple SGSNs (pooling) added
- Related to Bug #4952: Fix NRI routing in case SGSN is down added
- % Done changed from 0 to 50
SGSN-side is blocked now when the BSS goes down, see f96cac50
The other side is not implemented yet and the whole thing might change once we have one NSE for every BSS on the SGSN-side (see #4522). Then we don't need to block a BVC at all, we simply take the corresponding NSE down.
- Related to Bug #5040: Block all BSS-NSVC if no SGSNs are available added
Also available in: Atom
PDF
