Actions
Bug #2370
closedOsmoBTS accepts SAPI!=0 for LAPDm contention resolution
Start date:
07/17/2017
Due date:
% Done:
100%
Spec Reference:
Description
When the MS is sending the first SABM to the network, it must use SAPI=0, see 44.006 8.4.1.4 "According to sub-clause 9, the contention resolution procedure is only permitted with SAPI value 0." Howeer, OsmoBTS (or rather the libosmocore lapdm/lapd code) perform it also with other SAPI,s such as SAPI=3.
Found while working on http://git.osmocom.org/osmo-ttcn3-hacks/tree/lapd/L1CTL_Test.ttcn
Related issues
Updated by laforge almost 6 years ago
- Status changed from New to In Progress
- Assignee set to laforge
Updated by laforge almost 6 years ago
- % Done changed from 0 to 80
Updated by laforge almost 6 years ago
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
Updated by pespin almost 6 years ago
- Related to Bug #3252: osmo-bts-sysmo: lapdm issues during phone call establishment added
Actions