DLRMapNotFound when doing SMPP from Jasmin to Jasmin

494 views
Skip to first unread message

Alex

unread,
Dec 14, 2016, 2:00:43 AM12/14/16
to Jasmin SMS Gateway
Hi,

I'm sending from HTTP to Jasmin 1 to Jasmin 2 to carrier.

SMS is properly delivered but DLR stops on Jasmin 1.
I also noticed that "status" is blank in the info.

Jasmin 1 LOG

2016-12-14 15:40:13 INFO     988 DLR [cid:dddddds] [smpp-msgid:BEB0AFE1-570A-45E8-9206-E8DB4D342E5B] [status:] [submit date:201612141540] [done date:201612141540] [sub/dlvrd messages:ND/ND] [err:000] [content:'']
2016-12-14 15:40:15 ERROR    988 [msgid:BEB0AFE1-570A-45E8-9206-E8DB4D342E5B] (retrials: 1/2) DLRMapNotFound: Got a DLR for an unknown message id: beb0afe1-570a-45e8-9206-e8db4d342e5b (coded:BEB0AFE1-570A-45E8-9206-E8DB4D342E5B)
2016-12-14 15:40:25 ERROR    988 [msgid:BEB0AFE1-570A-45E8-9206-E8DB4D342E5B] (final) DLRMapNotFound: Got a DLR for an unknown message id: beb0afe1-570a-45e8-9206-e8db4d342e5b (coded:BEB0AFE1-570A-45E8-9206-E8DB4D342E5B)


Jasmin 2 LOG

2016-12-14 15:40:12 INFO     28456 SMS-MT [cid:fdfddha] [queue-msgid:beb0afe1-570a-45e8-9206-e8db4d342e5b] [smpp-msgid:32C7D7BF] [status:ESME_ROK] [prio:0] [dlr:SMSC_DELIVERY_RECEIPT_REQUESTED] [validity:none] [from:ffffffS] [to:328888888888] [content:'dgdfgdfdd']
2016-12-14 15:40:15 INFO     28456 DLR [cid:bigdgdfgha] [smpp-msgid:32C7D7BF] [status:DELIVRD] [submit date:1612140640] [done date:1612140640] [sub/dlvrd messages:001/001] [err:000] [content:'dgdfgdfdd']


Is there some configuration to connect 2 Jasmin servers through SMPP? (for dlr part)

Thanks

Alex

unread,
Dec 16, 2016, 1:27:34 AM12/16/16
to Jasmin SMS Gateway
Have some people tried HTTP->Jasmin->Jasmin->Provider case?

"accepted dlr returns well to the http original server but "delivered" is not returned. It means that it doesn't concern routing problem.
I also checked in redis that items are still present.

(Both jasmin are around 160ms apart)

Thanks a lot in advance!

Bruno C

unread,
Dec 19, 2016, 2:35:04 PM12/19/16
to Jasmin SMS Gateway
Confirmed issue in 0.9b15, tracking here.
Reply all
Reply to author
Forward
0 new messages