https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092019-05-10T21:56:03ZOpen Source Mobile CommunicationsOsmoMSC - Bug #3993: MT-SMS over IuCS sent on SAPI=0, should be SAPI=3https://projects.osmocom.org/issues/3993?journal_id=144082019-05-10T21:56:03Zlaforge
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>laforge</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>80</i></li></ul> OsmoMSC - Bug #3993: MT-SMS over IuCS sent on SAPI=0, should be SAPI=3https://projects.osmocom.org/issues/3993?journal_id=144092019-05-10T21:57:44Zlaforge
<ul></ul><p>proposed (rather trivial) fix is in <a class="external" href="https://gerrit.osmocom.org/#/c/osmo-msc/+/13984">https://gerrit.osmocom.org/#/c/osmo-msc/+/13984</a> - we simply hard-coded the SAPI to 0 in the IuCS case, rather than using the SAPI stored in the msgb->cb.</p> OsmoMSC - Bug #3993: MT-SMS over IuCS sent on SAPI=0, should be SAPI=3https://projects.osmocom.org/issues/3993?journal_id=144102019-05-10T22:20:10Zlaforge
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>80</i> to <i>100</i></li></ul><p>I quickly merged the patch, it seemed trivial enough.</p>