DLRLookupMessages problem

[Farid Jafarof]

Hello Jasmin Support Team,

We are running Jasmin SMS Gateway on:

• Operating System: Ubuntu 24.04.1 LTS

• Jasmin Version: 0.11 (release 0.11.1)

• Redis: default configuration

• SMPP connections: multiple (provider1,prodiver2,provider3)

We are experiencing a persistent DLR issue specifically with multipart SMS (SAR).

Problem Description

When sending multipart messages (3 parts) through HTTP API, Jasmin correctly sends all parts to the operator, and all messages are delivered to the handset. However:

1. DLRs are returned only for one part of the multipart message.

2. The other parts fail with the following errors in dlrlookupd-messages.log:

DLRMapNotFound: Got a DLR for an unknown message id

Example log:

ERROR DLRMapNotFound: Got a DLR for an unknown message id: 252183AB ERROR DLRMapNotFound: Got a DLR for an unknown message id: 3313851815

We confirmed via Redis:

HGETALL dlr:<msgid> (empty array)

So the DLR map is not being created for all segments.

Additional Observations

• SMS arrives successfully on the handset.

• Multipart messages sometimes arrive in wrong order (1-3-2).

• UDH-split seems OK, but SAR mapping is failing.

• The issue is identical to previously reported GitHub issue (#???), but no solution was provided.

Request

Could you please advise:

1. Is this a known issue with Jasmin 0.11.x SAR DLR handling?

2. Is there a recommended configuration workaround?

3. Would upgrading to a newer version fix this behavior?

4. Is there a patch for correct multipart DLR mapping in this release?

Thank you.

Kind Regards.