Project

General

Profile

Bug #2370

OsmoBTS accepts SAPI!=0 for LAPDm contention resolution

Added by laforge over 1 year ago. Updated 5 months ago.

Status:
Resolved
Priority:
Low
Assignee:
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

Related to OsmoBTS - Bug #3252: osmo-bts-sysmo: lapdm issues during phone call establishmentResolved2018-05-09

History

#1 Updated by laforge 6 months ago

  • Status changed from New to In Progress
  • Assignee set to laforge

#2 Updated by laforge 6 months ago

  • % Done changed from 0 to 80

#3 Updated by laforge 5 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 80 to 100

#4 Updated by pespin 5 months ago

  • Related to Bug #3252: osmo-bts-sysmo: lapdm issues during phone call establishment added

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)