Bug #4285
closed
osmo-stp doesn't report routing context and traffic-mode to the SG when acting as AS/ASP
Added by roch over 4 years ago.
Updated over 4 years ago.
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.
Files
Read traffic mode type instead of just "load share"
- 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
- 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.
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.
- % Done changed from 30 to 70
- Status changed from In Progress to Resolved
- % Done changed from 70 to 100
Also available in: Atom
PDF
