Project

General

Profile

Actions

Bug #3150

closed

OsmoMSC sends SMS-related DTAP with DLCI(SAPI=0) instead of DLCI(SAPI=3)

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

Status:
Resolved
Priority:
Normal
Assignee:
Category:
SMS
Target version:
-
Start date:
04/09/2018
Due date:
% Done:

80%

Resolution:
Spec Reference:

Description

See attached pcap file:

  • MS sends CP-DATA (RP-DATA) using BSSAP.DLCI.SAPI=3 (SMS)
  • MSC responds with CP-ACK (and other messages) using BSSAP.DLCI.SAPI=0 (RR/MM/CC)

this is clearly wrong. SMS related communication always happens on SAPI3

Can be reproduced with upcoming MSC_Tests.TC_lu_and_mo_sms


Files


Checklist

  • check what we need to do for IuCS
Actions #1

Updated by laforge almost 6 years ago

  • Checklist item check what we need to do for IuCS added
  • Status changed from New to In Progress
  • Assignee changed from 4368 to laforge
  • % Done changed from 0 to 70

Proposed fix submitted in https://gerrit.osmocom.org/7690

Actions #2

Updated by laforge almost 6 years ago

  • % Done changed from 70 to 80

patch merged. IuCS implications still pending

Actions #3

Updated by laforge almost 6 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)