Page 1 of 1

Matching Message Id form SubmitSm (hex) with delivery notification (decimal)

Posted: Tue Jul 11, 2023 4:06 pm
by arip
Hi

1st question:

From the log below, you can see, that the message id that is returned upon the SubmitSm Command is a string of hexadecimal characters. The message id that is received with the delivery receipt is a string of decimal characters. The value 0x5A530486 equals the decimal value of 1515390086.
Is there a reason why the value is first returned in hexadecimal format and later is returned in decimal format? Is this dependent on the SMPP provider (Swisscom)? In order to match the sent messages to the received delivery notifications I need to convert the hex value to the dec value.
SMPPLog.png
SMPPLog.png (24.25 KiB) Viewed 28033 times
2nd question:

The provider contract states, that up to 5 client sessions could be run in parallel. We only have one System Id to bind (login) with the provider. I like to know, if we can run multiple independent systems that each can send SMS messages and track their delivery notifications through Inetlab.SMPP separate from each other. Is this possible with only one System Id or would we need additional System Ids?

Kind regards,
André

Re: Matching Message Id form SubmitSm (hex) with delivery notification (decimal)

Posted: Thu Jul 13, 2023 12:12 pm
by alt
Hi arip,

1) This is an issue on the SMPP provider. Both MessageIds must use the same format for correlation purpose.

2) This approach may function properly when dealing with a single SystemId, as long as the SMPP provider remembers the SMPP session on which the SUBMIT_SM was received. By utilizing this session, they can successfully deliver the DELIVER_SM receipt. However, this method becomes ineffective if the SMPP session is closed, as the provider needs to deliver any pending delivery receipts to another session that shares the same SystemId.

Re: Matching Message Id form SubmitSm (hex) with delivery notification (decimal)

Posted: Fri Jul 14, 2023 3:11 pm
by arip
Hi alt,

thank you for the detailed explanation.

Kind regards,
André