Message ID for SMS submission and delivery not the same

[mehdi.c...@tritux.com]

Is it correct that the Message ID returned as part of the SUBMIT_SM_RESP does not match the Message ID returned in the DELIVER_SM delivery receipt?
like it's shown in the pcap below

in the first submit_sm the messageId = 196166 and in the second submit_sm the messageID = 67... and when I receive the delivery receipt in deliver_Sm
the message body contains ="id:67 sub:001 dlvrd:001 submit date:1609211533 done date:1609211533 stat:UNDELIV err:000 Text:Hello 2 ".

thank you.

[Sergey Vetyutnev]

Hello Mehdi,

please explain more which scenario do you test, which results do you expect and which results do you get.
Also which server / version do you test ?

Messages #68 and #72 in your pcap file: are they the same message ? I can see that they are with different IP addresses. So they are from different servers / ESMEs ?

[mehdi.c...@tritux.com]

Hello Sergey,

Context :

-----------

I want to search the submitted message (submit_sm) for a given delivered message (deliver_sm).

the problem that I can't find a matching between the submitted message and the received delivery message from

the Cassandra table Message_DD_MM_YY. 

Environment:

-------

I'm using restcomm 7.0.49, I'm using also restcomm-smpp-simulator to simulate emse server systemID(test) , and to simulate esme client I'm using SMPPSIM simulator systemID(smppclient1).

Scenario

-------------

I’m sending an MT message from test to smppclient1,and I want to match this message with its delivery receipt.

Expected result :that the messageID of the delivery receipt message_text will be the same as the messageID generated in the first submit_sm (between esme server(test) and restComm ).

Result that i got : the delivery receipt contains the id of the second submit sm (between restcomm and esme client (smppclient1)).so I can't match the message with its delivery.

I attached a detail flow graph and a dump traffic of wireshark, also a file "message.csv" containing the content of the cassandra table "MESSAGE_xxx" during the pervious scenario.   

[Sergey Vetyutnev]

Hello,

I suppose that the described case is: https://github.com/RestComm/smscgateway/issues/23
It is not fully implemented yet.

[mehdi.c...@tritux.com]

Thank you Sir for your reply

I hoped that it would be a simple configuration change, but since it’s not, we’ll try to implement it and commit in case of success. 

Can you please provide me with spec or informations i can start with

[Sergey Vetyutnev]

Hello Mehdi,

> I hoped that it would be a simple configuration change, but since it’s not,
Unfortunately this is just missed (:

> we’ll try to implement it and commit in case of success.

Much thank you for help. We are working of this case now, it needs some database update too.
Fill free to contribute some other issue.