Project

General

Profile

Bug #2353

SMSC: ESME sending an sms with registered_delivery=0x01 not receiving delivery_sn message

Added by pespin 3 months ago. Updated about 3 hours ago.

Status:
Feedback
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
07/06/2017
Due date:
% Done:

0%

Spec Reference:

Description

While writing osmo-gsm-tester smpp test to check use of Store&Forward mode, I run into the following scenario:

  1. Core network + BTS is turned on, no MS available yet
  2. An esme connects to the SMSC, and sends an SMS ("submit_sm" message with mode="Store&Forward" and registered_delivery=0x01) to an MS which is still not registered into the network.
  3. Power on the MS, it registers with the network
  4. The MS receives the stored SMS
  5. NO Delivery Receipt is received at the ESME side

The ESME should receive a Delivery Receipt (deliver_sm message) as shown in SMPP Protocol Reference v3.4: "Figure 2-7: Typical SMPP sequence for a registered store and forward message".


Related issues

Related to OsmoNITB - Bug #2429: SMSC: deiverSM message with bad user_message_reference Resolved 08/10/2017

History

#1 Updated by laforge 2 months ago

  • Assignee set to pespin
  • Priority changed from Normal to Low

#2 Updated by pespin about 1 month ago

  • Related to Bug #2429: SMSC: deiverSM message with bad user_message_reference added

#3 Updated by pespin about 1 month ago

  • Status changed from New to Feedback

Once openbsc patch from #2429 is merged, we can close this task.

Then patch for osmo-gsm-tester https://gerrit.osmocom.org/#/c/3557/ has to be merged.

#4 Updated by pespin about 1 month ago

  • Assignee changed from pespin to neels

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.

Assigning to Neels as he may provide better feedback on what's needed to have this fixed in AoIP builds.

#5 Updated by neels 29 days ago

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.

#6 Updated by neels 23 days ago

The most recent patches are now applied to osmo-msc.git master.

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.
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.

#7 Updated by neels about 3 hours ago

  • Assignee changed from neels to pespin

@pespin, 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.

Also available in: Atom PDF