Actions
Feature #5148
closedwork-around broken implementations sending SSNM in ASP-INACTIVE
Start date:
05/10/2021
Due date:
% Done:
100%
Spec Reference:
Description
As per RFC4666, Section 4.3.1 ASP/IPSP states:
ASP-INACTIVE: ... In this state, the ASP/IPSP SHOULD NOT be sent any DATA or SSNM messages for the AS for which the ASP/IPSP is inactive.
Still, there are some implementations out there which are sending SSNM traffic (specifically DAUD) while the ASP is in ASP-INACTIVE state.
It may be required to introduce a wokr-around to accept such SSNM traffic even though it is invalid.
Updated by laforge almost 3 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 80
https://gerrit.osmocom.org/c/libosmo-sccp/+/24216
TTCN3 test still missing
Updated by laforge almost 3 years ago
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
patch and test case merged
Actions
