Actions
Bug #3993
closedMT-SMS over IuCS sent on SAPI=0, should be SAPI=3
Start date:
05/09/2019
Due date:
% Done:
100%
Resolution:
Spec Reference:
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.
Files
Updated by laforge almost 5 years ago
- Status changed from New to In Progress
- Assignee set to laforge
- % Done changed from 0 to 80
Updated by laforge almost 5 years 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.
Updated by laforge almost 5 years ago
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
I quickly merged the patch, it seemed trivial enough.
Actions
