Your submit_sm messages are ok.
Do you get ESME_RINVMSGLEN when you send short text?

Please try to find out if SMSC supports concatenated messages?
And try SubmitMode.Payload mode.

Do you always have this response?
It looks like server drops connection when you send SMPP packet.
Please check your connection parameters.

Please ask if SMSC defined restrictions for your ID.
Sometimes they are not allow to bind in Transceiver mode.
Or they allow to bind only one connection.

In order to tell you the reason why you got ESME_RINVMSGLEN I need to see what smpp client has sent. Please use code from SmppClientDemo client.evSendData +=new ALT.SMS.SmppClient.SendDataEventHandler(client_evSendData); ... private void client_evSendData(object sender, byte[] data) { AddToLog("Send...

Event evReceiveData raised when any data available from network stream. Sometimes SMSC sends (or client receives) one SMPP packet in two or more chunks. Usualy event evReceiveData used for debug purposes. In production system I disable such events in order to increase performance. Please use evSubmi...

Hi Oliver,

Last versions of the library made as thread-safe.

Alexey

Could you show the code you use?

SmppClient returns this status when it has no connection with SMSC or connection has been lost. You need to reestablish connection with SMSC using methods Connect and Bind.

Do you mean delivery_sm and submit_sm_resp from SMPP server?

Could you tell results for cases 1) SmppClient.MapEncoding(DataCodings.Default , new GSMEncoding()); 2) SmppClient.MapEncoding(DataCodings.Default , Encoding.Default); 3) SmppClient.MapEncoding(DataCodings.ASCII , new GSMEncoding()); 4) SmppClient.MapEncoding(DataCodings.ASCII , Encoding.Default) 5)...

Do you know vendor type of SMSC ? All symbols "{}\|[]~" are belong to extension table of GSM encoding. http://www.dreamfabric.com/sms/default_alphabet.html Possible SMSC doesn't properly convert your messages to packed GSM 03.38 encoding. Please also try to send with GSM encoding in data coding = 4 ...

Please try with version 2.10.0

Hello 3psil0N,

New version already released. Sorry, I had no time to publish it.
In this version deadlock should be fixed. Old version had bug in receive callback.

Please try this code: TLV messageState = dp.Optional[OptionalTags.MessageState]; MessageState state = MessageState.None; if (messageState != null) { state = (MessageState)messageState.Value[0]; } TLV receiptedMessageId = dp.Optional[OptionalTags.ReceiptedMessageId]; string messageId = null; if (rece...