osmo-stp doesn't report routing context and traffic-mode to the SG when acting as AS/ASP
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
I've attached both traces and configuration.
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.
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
#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
likewise, there are now commits https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/16395 and https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/16396 for the TTCN-3 test suite.