Project

General

Profile

Actions

Bug #4897

open

gbproxy2: Re-introduce handling of NS_AFF_CAUSE_FAILURE

Added by laforge 12 months ago. Updated 9 months ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
Start date:
12/08/2020
Due date:
% Done:

50%

Spec Reference:

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 issues

Related to osmo-gbproxy - Feature #4472: Intra-domain connection of OsmoGBPROXY to multiple SGSNs (pooling)Resolveddaniel03/29/2020

Actions
Related to osmo-gbproxy - Bug #4952: Fix NRI routing in case SGSN is downResolveddaniel01/15/2021

Actions
Related to osmo-gbproxy - Bug #5040: Block all BSS-NSVC if no SGSNs are availableRejecteddaniel02/23/2021

Actions
Actions #1

Updated by laforge 12 months ago

  • Related to Feature #4472: Intra-domain connection of OsmoGBPROXY to multiple SGSNs (pooling) added
Actions #2

Updated by daniel 10 months ago

  • Related to Bug #4952: Fix NRI routing in case SGSN is down added
Actions #3

Updated by daniel 9 months ago

  • % 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.

Actions #4

Updated by daniel 6 months ago

  • Related to Bug #5040: Block all BSS-NSVC if no SGSNs are available added
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)