Pairing submited message with delivery recipet

Post Reply
grobelsekn@gmail.com
Posts: 4
Joined: Tue Nov 30, 2021 12:19 pm

Pairing submited message with delivery recipet

Post by grobelsekn@gmail.com » Tue Nov 30, 2021 12:34 pm

Hi,
according to documentation https://docs.inetlab.com/smpp/v2.9/arti ... ceipt.html it should be easy to tie together sent message with delivery receipt, but I am not getting the same ids

Code: Select all

IList<SubmitSm> list = builder.Create(_client).ToList<SubmitSm>();
foreach(var item in list)
{
	item.Header.Sequence =_client.SequenceGenerator.NextSequenceNumber();
	log.Info($"TEST: id:{message.Id}:{item.Header.Sequence}");
}

	
var response = await _client.SubmitAsync(list);
foreach (SubmitSmResp resp in response)
{
	log.Info($"TEST2: id:{message.Id}:{resp.MessageId}");
}
	
.....

private void client_evDeliverSm(object sender, DeliverSm data)
{
	if (data.MessageType == MessageTypes.SMSCDeliveryReceipt)
	{
		log.Info($"TEST3: id:{data.Receipt.MessageId}");
	}
}
Checking the log file shows id's do not match:
TEST: id:1234:2
TEST2: id:1234:04D665E3
TEST3: id:0080993137

Am I doing something wrong or is this some kind of a bug.
version of component is: inetlab.SMPP.2.9.14
alt
Site Admin
Posts: 985
Joined: Tue Apr 25, 2006 9:45 am

Re: Pairing submited message with delivery recipet

Post by alt » Tue Nov 30, 2021 7:53 pm

Hi,

Did you send only one SubmitSm in this test? It seems the SMSC returns different MessageId in SubmitSmResp and in delivery receipt.

Could you create wireshark file for this test and send to support@ ?
grobelsekn@gmail.com
Posts: 4
Joined: Tue Nov 30, 2021 12:19 pm

Re: Pairing submited message with delivery recipet

Post by grobelsekn@gmail.com » Wed Dec 01, 2021 8:23 am

Yes it was only one, but now I also tried some other app available on the net and it seems this id probably problem on the provider side.
So for now it seems to me this is not a component problem.

Another test:
Message submited
+ MessageID(s): 05072D8A
Report received
+ MessageID: 0084356490
+ Destination: ***********
+ Originator: **********
Post Reply