Actions
Bug #4594
closedM3UA routing context used in ASPAC, but not in DATA
Start date:
06/08/2020
Due date:
% Done:
100%
Spec Reference:
Description
There are some M3UA implementations out there who use a routing context during the ASPAC
procedure, but who then don't use it in subsequent DATA transmission.
This behavior seems to be at the edge of what's possible within the spec:
Routing Context: 32 bits (unsigned integer) The Routing Context parameter contains the Routing Context value associated with the DATA message. Where a Routing Key has not been coordinated between the SGP and ASP, sending of Routing Context is not required. Where multiple Routing Keys and Routing Contexts are used across a common association, the Routing Context MUST be sent to identify the traffic flow, assisting in the internal distribution of Data messages.
So if you don't configure a routing context, it is not required to be sent. And if you have multiple routing contexts, it must be sent. But the situation where a routing context has been configured (but not multiple) is not really covered.
Updated by laforge almost 4 years ago
- Status changed from New to In Progress
- Assignee changed from herlesupreeth to laforge
Updated by laforge almost 4 years ago
- % Done changed from 0 to 80
- testcase: https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/18817
- implementation: https://gerrit.osmocom.org/c/libosmo-sccp/+/18818
test case fails before the implementation and passes afterwards.
Updated by laforge almost 4 years ago
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
patch merged
Actions