Hi hishhash2,
You need to traverse TLV parameters for sequence no.

Alt,
I am sending a long message, and hence used payload mode. But still each portion of the message is received in a separate smppServer_evClientSubmitSm event on server.

Moreover my 2nd important question is that, the return type ...

Kindly update me on the last post ASAP.
We are facing this issue in real time environment as well. Long messages are received in splitted parts at receiver's end.

The SMS details are entered in DB from application. There is a windows service which pulls the details from DB and send them to nos. saved in database against each sms. Now I am just looking for a method to which i pass my text message, and it tell me that, for example, the message is UC2 encoded ...

This is not my application flow. I was just trying to send messages from server to client and client to server in demo application. And everytime on sending a long message to client, the server gets crashed.

Is there any way to detect the submit mode & encoding of sending sms?
Actually I have a scenario in which sms details are saved in a database table, and my service is pulling the details from table and sending the sms to intended recipients. In this case, is there any way that I could detect that ...

Which file formats are supported to send/receive, through this API?

Thanks, the message can be seen now. But long messages are received in splitted parts.
SHould it not be a complete concatenated message? Or this is receiving end's responsibility to receive splitted messages and concat them by it self?

The is same as used in demo application server:

Inetlab.SMPP.PDU.DeliverSm data = new Inetlab.SMPP.PDU.DeliverSm();

data.SourceAddrTon = byte.Parse(tbSrcAdrTON.Text);
data.SourceAddrNpi = byte.Parse(tbSrcAdrTON.Text);
data.SourceAddr = tbSrcAdr.Text;

data.DestAddrTon = byte.Parse ...

One more problem ..Refer to the demo application available with trial, when i send shortmessage from client, the message is properly received on the server. But when i send Payload message from client, in the server_evClientSubmitSm() event of server, data.ShortMessage is null. I am unable to verify ...

Whenever I try to send a large message from demo server, to the client, the code crashes at client.Deliver(data) method with the following exception: "Value was either too large or too small for an unsigned byte".

Am I missing some attribute needing to be added in the sending message?
What is the ...

Whenever I try to send a large message from demo server, to the client, the code crashes at client.Deliver(data) method with the following exception: "Value was either too large or too small for an unsigned byte".

Am I missing some attribute needing to be added in the sending message?
What is the ...

Refer to the demo application available with trial, when i send shortmessage from client, the message is properly received on the server. But when i send Payload message from client, in the server_evClientSubmitSm() event of server, data.ShortMessage is null. I am unable to verify whether my long ...