Long Message Receiving Issue - SMPP Server
Posted: Thu Mar 08, 2012 7:57 am
I am using both SMPP Client & SMPP server & i have the below scenario,
Using Inetlab SMPP client I am submitting a long message using SubmitMode.ShortMessage. From the SMPP server side i am receiving each portion of the message as seperate _smppServer_evClientSubmitSm events. Below is the Screenshot of the watch i have added to the SubmitSm data object.
It is clear from the UserDataPdu.Headers that there are 2 segments and the current is segment number and also a sequence number also(from above screenshot it is 158).
Is there a an easy way to parse the Header and get the Sequence number.
When the submit mode from SMPP Client is SubmitMode.Payload then i can traverse TLV parameters from Optional parameter. But when the submit mode is SubmitMode.ShortMessage then the data.Optional is null. Then the sequence and segment numbers comes with the data.UserdataPdu.Headers. My question is how do i parse this header to take out the sequence numbers. Isn't there a chance that the data.UserdataPdu.Headers can have other information too...
I am stuck at this point, hoping someone must have come across the same issue.
Using Inetlab SMPP client I am submitting a long message using SubmitMode.ShortMessage. From the SMPP server side i am receiving each portion of the message as seperate _smppServer_evClientSubmitSm events. Below is the Screenshot of the watch i have added to the SubmitSm data object.
It is clear from the UserDataPdu.Headers that there are 2 segments and the current is segment number and also a sequence number also(from above screenshot it is 158).
Is there a an easy way to parse the Header and get the Sequence number.
When the submit mode from SMPP Client is SubmitMode.Payload then i can traverse TLV parameters from Optional parameter. But when the submit mode is SubmitMode.ShortMessage then the data.Optional is null. Then the sequence and segment numbers comes with the data.UserdataPdu.Headers. My question is how do i parse this header to take out the sequence numbers. Isn't there a chance that the data.UserdataPdu.Headers can have other information too...
I am stuck at this point, hoping someone must have come across the same issue.