I think I found where is the issue.

Please try the version https://www.inetlab.com/Download/2.9.0- ... b.SMPP.zip

How your project calculates the length?

Hi xhide,

Which version did you test?
Could you please try with latest https://www.inetlab.com/Download/2.9.0-beta-2271/Inetlab.SMPP.zip

Please always test Release version without attached debugger.

The TCP Windows Size should be scaled automatically.
You can check the size of the window with ...

Which versions did you test?

Could you please test with latest https://www.inetlab.com/Download/2.9.0- ... b.SMPP.zip

Turkish language has both Single and Locking shift tables.

I think in your case you need to use locking shift table.

thank you. I'll check this issue.

Using a shift table, a message can still use 7-bit encoding for the characters, but a different set can be chosen to correctly show accented and language specific characters. This allows up to 155 characters, encoded in 136 octets (140 octets, minus the 4-octets of User Data Header required to ...

Could you provide more details about the issue?

What text did you sent?

What message text the recipient sees on the phone?

What type of .NET encoding did you map to DataCoding.Latin1?
https://docs.inetlab.com/smpp/v2.8/articles/faq/map_encoding.html

Does your SMS provider support National ...

I have a question. What SMS provider is expecting from your client?
Do you need to wait for SubmitSmResp before sending next SubmitSm?

For batch sending it can happen that SMS provider application receives more than one PDU with the single socket.read(buffer) call, even when sender calls socket ...

Yes, this option will be defined in the SmppClient.

Hi aordonez,

Do you mean that the SMS provider requires to send each SMPP PDU in a single TCP packet?

This can significantly reduce the performance.

I could add the option in current beta version v.2.9.

Hi lolorosso,

what kind of problem are you facing?
how do you send the message? Could you post the code here?

Hi vineet,

I would like to ask you to test the version 2.9.0-beta-2249.
I did stress test for this version and made some improvements.
Please check ChangeLog for details.

MMS m-notification-ind is now implemented in the version 2.9

You can do it this way:


UserDataHeaderCollection headers = new UserDataHeaderCollection();
headers.Add(new ConcatenatedShortMessages8bit(0x55,2,1));
headers.Add(new UserDataHeader(0x60, new byte[0]));

submitSm.UserData.Headers = headers;



If you use SMS builder:



var pduList = SMS ...

There is no much difference in SubmitAsync method between 2.6 and 2.8. So it should work the same way.

What type is "batch" variable?

As far as I understood, you want the library to support CancelationToken parameter in SubmitAsync methods.