Project

General

Profile

Bug #2749

OsmoBSC allows COMPLETE LAYER3 on SAPI !=0

Added by laforge about 1 month ago. Updated 14 days ago.

Status:
New
Priority:
Normal
Assignee:
Category:
A interface
Target version:
-
Start date:
12/13/2017
Due date:
% Done:

0%

Spec Reference:

Description

GSM only supports SAPI0 (signalling) and SAPI3 (SMS). Other SAPIs are not in use.

Furthermore,
  • the initial establishment of the channel towards the MSC must happen on SAPI0
  • the SABM command is only permitted to have L3 INFO on SAPI0 in uplink
  • the BSSMAP COMPLETE LAYER3 INFO (as opposed to DTAP) doesn't have a SAPI/DLCI field

Yet, OsmoBSC permits a MS to establish e.g. SAPI1 on RSL/RLL and will happily report this as a COMPLETE L3 INFO to the MSC.

I'm implementing TC_rll_est_ind_inval_sapi1 in the TTCN-3 testsuite for this. But TC_rll_est_ind_inval_sapi3 is also failing due to the same bug. SAPI3 can always only be established in addition to SAPI0 but never directly in a COMPLETE L3 INFO.

sapi1.pcapng (640 Bytes) laforge, 12/13/2017 09:12 PM

sapi3.pcap.pcapng (640 Bytes) laforge, 12/13/2017 09:14 PM


Related issues

Related to OsmoBSC - Bug #2750: OsmoBSC allows COMPLETE L3 INFO for SACCH New 12/13/2017

History

#1 Updated by laforge about 1 month ago

#2 Updated by laforge about 1 month ago

  • Related to Bug #2750: OsmoBSC allows COMPLETE L3 INFO for SACCH added

#3 Updated by laforge 14 days ago

  • Assignee set to dexter

Also available in: Atom PDF