https://osmocom.org/https://osmocom.org/favicon.ico?16647414092017-07-10T18:34:14ZOpen Source Mobile CommunicationsOsmoNITB - Bug #2353: SMSC: ESME sending an sms with registered_delivery=0x01 not receiving delivery_sn messagehttps://osmocom.org/issues/2353?journal_id=44782017-07-10T18:34:14Zlaforge
<ul><li><strong>Assignee</strong> set to <i>pespin</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul> OsmoNITB - Bug #2353: SMSC: ESME sending an sms with registered_delivery=0x01 not receiving delivery_sn messagehttps://osmocom.org/issues/2353?journal_id=49222017-08-10T10:39:38Zpespin
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-2 priority-default closed" href="/issues/2429">Bug #2429</a>: SMSC: deiverSM message with bad user_message_reference</i> added</li></ul> OsmoNITB - Bug #2353: SMSC: ESME sending an sms with registered_delivery=0x01 not receiving delivery_sn messagehttps://osmocom.org/issues/2353?journal_id=51082017-08-18T15:32:32Zpespin
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p>Once openbsc patch from <a class="issue tracker-1 status-5 priority-2 priority-default closed" title="Bug: SMSC: deiverSM message with bad user_message_reference (Closed)" href="https://osmocom.org/issues/2429">#2429</a> is merged, we can close this task.</p>
<p>Then patch for osmo-gsm-tester <a class="external" href="https://gerrit.osmocom.org/#/c/3557/">https://gerrit.osmocom.org/#/c/3557/</a> has to be merged.</p> OsmoNITB - Bug #2353: SMSC: ESME sending an sms with registered_delivery=0x01 not receiving delivery_sn messagehttps://osmocom.org/issues/2353?journal_id=51182017-08-18T19:42:00Zpespin
<ul><li><strong>Assignee</strong> changed from <i>pespin</i> to <i>neels</i></li></ul><p>Test passes on smpp suite, but it still fails on aoip_smpp, probably because the fork of osmo-msc from osmo-nitb still doesn't include latest patches applied recently in osmo-nitb.</p>
<p>Assigning to Neels as he may provide better feedback on what's needed to have this fixed in AoIP builds.</p> OsmoNITB - Bug #2353: SMSC: ESME sending an sms with registered_delivery=0x01 not receiving delivery_sn messagehttps://osmocom.org/issues/2353?journal_id=51452017-08-21T23:49:04Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>ack that a bunch of openbsc.git patches still needs to be applied to the new osmo-*.git repositories that are relevant to the AoIP builds. Will try to complete that soon.</p> OsmoNITB - Bug #2353: SMSC: ESME sending an sms with registered_delivery=0x01 not receiving delivery_sn messagehttps://osmocom.org/issues/2353?journal_id=52102017-08-28T12:08:56Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>The most recent patches are now applied to osmo-msc.git master.</p>
<p>Instead of applying the SMPP fixes to openbsc.git's aoip branch, we should move osmo-gsm-tester to the new osmo-msc.git repository for the AoIP builds.<br />We could do so now using the pre_release branch, but when the last eight patches waiting on gerrit are merged we can use master.</p> OsmoNITB - Bug #2353: SMSC: ESME sending an sms with registered_delivery=0x01 not receiving delivery_sn messagehttps://osmocom.org/issues/2353?journal_id=54422017-09-19T23:12:21Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Assignee</strong> changed from <i>neels</i> to <i>pespin</i></li></ul><p><a class="user active" href="https://osmocom.org/users/30187">pespin</a>, I know that the patches as merged to osmo-msc.git work on the osmo-gsm-tester, but since this is issue was generally yours, handing back to you to confirm resolution.</p> OsmoNITB - Bug #2353: SMSC: ESME sending an sms with registered_delivery=0x01 not receiving delivery_sn messagehttps://osmocom.org/issues/2353?journal_id=65992017-12-07T13:50:26Zpespin
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul> OsmoNITB - Bug #2353: SMSC: ESME sending an sms with registered_delivery=0x01 not receiving delivery_sn messagehttps://osmocom.org/issues/2353?journal_id=74892018-02-06T08:26:40Zlaforge
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>