Project

General

Profile

Bug #3993

MT-SMS over IuCS sent on SAPI=0, should be SAPI=3

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

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

100%

Resolution:
Tags:
3G

Description

When trying to send a MT-SMS via GSUP from MSC_Tests_Iu.TC_iu_lu_and_mt_sms, we need to send it (like any SMS) over SAPI=3.

However, the RANAP DirectTransfer indicates "SAPI: sapi-0", as can be seen in the attached pcap file.

The TTCN3 test case fails like this:

13:33:20.385361 18 BSC_ConnectionHandler.ttcn:1323 Matching on port BSSAP .dlci := '00'O with '03'O unmatched: First message in the queue does not match the template: 

don't be worried by 'BSSAP' and 'DLCI'. we translate those from RANAP to make the existing test cases happy.

iucs-sms-mt-sapi0.pcap iucs-sms-mt-sapi0.pcap 3.31 KB laforge, 05/09/2019 11:38 AM

History

#1 Updated by laforge about 1 month ago

  • Status changed from New to In Progress
  • Assignee set to laforge
  • % Done changed from 0 to 80

#2 Updated by laforge about 1 month ago

proposed (rather trivial) fix is in https://gerrit.osmocom.org/#/c/osmo-msc/+/13984 - we simply hard-coded the SAPI to 0 in the IuCS case, rather than using the SAPI stored in the msgb->cb.

#3 Updated by laforge about 1 month ago

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

I quickly merged the patch, it seemed trivial enough.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)