Bug #2370: OsmoBTS accepts SAPI!=0 for LAPDm contention resolution - OsmoBTS - Open Source Mobile Communications

Actions

Copy link

Bug #2370

closed

OsmoBTS accepts SAPI!=0 for LAPDm contention resolution

Added by laforge almost 7 years ago. Updated almost 6 years ago.

Status:

Resolved

Priority:

Low

Assignee:

laforge

Category:

Target version:

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