Project

General

Profile

Actions

Bug #4954

closed

Fix routing of RADIO-STATUS by TMSI

Added by laforge almost 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
01/17/2021
Due date:
% Done:

100%

Spec Reference:

Description

While development of test cases (specifically TC_radio_status_tmsi) it has shown that routing the uplink RADIO-STATUS by TMSI is broken. osmo-gbproxy consistently selects a "wrong" SGSN.

The expectation is that we treat the TMSI identical to a TLLI and extract the NRI value from that. However, that somehow fails as the TMSI upper bits are not well-defined and could indicate an unexpected TLLI type. In my examples, it's tMSI_Value := '42180023'O, whihc contains NRI=3 and hence is expected to end up on SGSN0. However, it gets routed to SGSN1 in all test invocations.


Related issues

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

Actions
Actions #2

Updated by daniel almost 2 years ago

  • Status changed from New to In Progress
Actions #3

Updated by daniel almost 2 years ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 90
Actions #4

Updated by daniel almost 2 years ago

  • Status changed from Feedback to Resolved
  • % Done changed from 90 to 100
Actions #5

Updated by daniel almost 2 years ago

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

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)