Project

General

Profile

Actions

Bug #3059

closed

System Information on SACCH missing L2 Pseudo-Length

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

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
-
Start date:
03/11/2018
Due date:
% Done:

100%

Resolution:
Spec Reference:

Description

Something seems odd about our SI5/SI6 messages.

The message on the downlink SACCH is structured as follows:

  • two octets L1 header
  • two octets "LAPDm B4" frame format: Address + Control Octet
  • 23-4=19 octets of L3 payload (as specified in TS 44.018), consisting of
    • one octet L2 pseudo-length
    • 18 octets of actual L3 message

It appears that the messages that we send from the Osmocom stack are missing the L2 pseudo-length. This maybe related to https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14105


Checklist

  • wireshark patch for RSL
  • wireshark patch for SACCH/LAPDm
  • patch for legacy openbsc.git

Related issues

Related to OsmoBTS - Bug #3057: OsmoBTS fails to schedule SACCH filling like SI5Resolvedlaforge03/11/2018

Actions
Related to Cellular Network Infrastructure - Bug #2963: Measurement Reports cease to be useful some time into a voice call / after handover (not sure which project has the bug / bugs yet)Resolvedneels02/19/2018

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)