-
-
Notifications
You must be signed in to change notification settings - Fork 540
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hexadecimal SMS ID not taken in count on DLR #1129
Comments
Tried setting an MO Interceptor that strips de zeroes from the received message id like this:
On the logs it's shows the correct values when "comparing" but the DLR is still discarded because it doesn't match. `==> /var/log/jasmin/dlrlookupd-messages.log <== 2023-09-03 03:22:08 ERROR 29510 [msgid:BB42DD] (final) DLRMapNotFound: Got a DLR for an unknown message id: BB42DD (coded:BB42DD)` Any ideas? |
What's the original submit message id from the log ? |
Please share jasmin log including the sms-mt and the dlr. |
==> /var/log/jasmin/messages.log <== ==> /var/log/jasmin/dlrlookupd-messages.log <== |
Can you check if you have a key "queue-msgid:BBA622" or "queue-msgid:00BBA622" in redis ? (using redis console). If you find it, please share it's content. |
I'm not familiar with redis, but is this ok? redis-cli127.0.0.1:6379> keys queue-msgid:BBA622 |
Am not sure how the key is stored, please list all keys and find any reference for your msgid, bba622 or BBA622 |
I issued the command "keys *" but it shows empty array, so I googled a bit to check how to debug and found the MONITOR command on redis-cli. 127.0.0.1:6379> monitor So, it's discarding the zeroes when passing it to redis... |
HGETALL is executed on dlr lookup (triggered by deliver_sm), you need to check how the key were saved (triggered on submit_sm sendout). |
Thanks for your help @farirat |
are you sure you are asking for the delivery report ? if not, then jasmin will not save anything to redis. |
Yes, over http client I'm requesting with dlr=yes and dlr-url= an endpoint
I can monitor
…On Fri, Sep 8, 2023, 4:20 AM The Z ***@***.***> wrote:
are you sure you are asking for the delivery report ? if not, then jasmin
will not save anything to redis.
—
Reply to this email directly, view it on GitHub
<#1129 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMPHOGXDZJXZ56NJKGWAPHTXZLWNZANCNFSM6AAAAAA35OMX7Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
and dlr-level=3 ? |
Thanks @farirat ! That was it! :) |
Hello guys!
I'm using version 0.10.13 and SMPP connection with a provider gives message ID in hex format/encoding
For example: 00B8BE19
When getting the corresponding DLR I get error on Jasmin:
Got a DLR for an unknown message id: 00B8BE19 (coded:B8BE19)
The "Deliver Msg ID" parameter is configured = 0
Also tried setting on 1 and 2, but then it gets worse because it's not a decimal converted to hex or the other way around.
I'm guessing it's a bug, in which it discards the fist couple of zeroes and it doesn't match with previous ID.
Any ideas how can I fix this?
Thanks in advance ;)
The text was updated successfully, but these errors were encountered: