Project

General

Profile

Bug #4285

osmo-stp doesn't report routing context and traffic-mode to the SG when acting as AS/ASP

Added by roch over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
11/28/2019
Due date:
% Done:

100%

Spec Reference:

Description

Hi,

I compared traces between Holger's implementation of M3UA in cellmgr-ng and osmo-stp
and it looks like osmo-stp doesn't report routing context and load-share to the SG (it might be normal
for load-share).

I've attached both traces and configuration.

Many thanks

Roch.

osmo-stp.pcapng osmo-stp.pcapng 867 KB roch, 11/28/2019 11:28 AM
cellmgr-ng-m3ua.pcapng cellmgr-ng-m3ua.pcapng 1.11 KB roch, 11/28/2019 11:28 AM
osmo-stp.cfg osmo-stp.cfg 1.35 KB roch, 11/28/2019 11:28 AM

Associated revisions

Revision ac2e715f (diff)
Added by laforge over 1 year ago

xua_asp_fsm: Ensure xUA client includes traffic-mode if configured

When a client (ASP) sends an ASPAC to the server (SG), it should include
the traffic-mode configured for it's ASs, if any.

Change-Id: Ia850df22df529dab74959e8666f85976002c482c
Related: OS#4285

Revision ee6e43a6 (diff)
Added by laforge over 1 year ago

xua_asp_fsm: Ensure xUA client includes routing contexts in ASPAC/ASPIA

If we are running in ASP (client) role, and we are about to transmit an
ASPAC or ASPIA to the SG, we must make sure to include any applicable
routing contexts.

Change-Id: Iee4f0d553d6845a9ae08cb5e4f57fdec443e4ef9
Related: OS#4285

History

#1 Updated by roch over 1 year ago

Read traffic mode type instead of just "load share"

#2 Updated by laforge over 1 year ago

  • Subject changed from osmo-stp doesn't report routing context and load-share to the SG when acting as AS/ASP to osmo-stp doesn't report routing context and traffic-mode to the SG when acting as AS/ASP
  • Assignee set to laforge

#3 Updated by laforge over 1 year ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 30

I have some local patches, will create TTCN3 test cases for this tomorrow.

#4 Updated by laforge over 1 year ago

Note from the spec point of view: At least in theory, not listing any routing context in the ASPAC means "all routing contexts". The routing context IE in the message IMHO only exists for situations where you want to explicitly activate the ASP only for some of the routing contexts (i.e. some of the AS) which are served by this ASP.

#6 Updated by laforge over 1 year ago

#7 Updated by laforge over 1 year ago

  • Status changed from In Progress to Resolved
  • % Done changed from 70 to 100

all patches merged.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)