Library creates concatenated parts with SMS.ForSubmit chained methods.

Examples you can find at
https://docs.inetlab.com/smpp/v1/articl ... ation.html

https://docs.inetlab.com/smpp/v1/articl ... arted.html

The description how to receive SMS messages you can find at

https://docs.inetlab.com/smpp/v1/articl ... s-messages

https://docs.inetlab.com/smpp/v1/articl ... poser.html

You can also change InactivityTimeout for connected clients. It helps to save server resources.

I suppose the client establishes new connection after receiving the response with status ESME_RALYBND, but doesn't disconnect previous connection. When it happens too often you get out of memory exception. Could you tell me how many maximal connections your server had? It should be a lot of connecti...

Could you provide more details on your context? What library version do you use? How many concurrent connections your server accepts? Consider to create memory dump with ProcDump . procdump -ma -e 1 -f OutOfMemoryException -w "YourProcessName" Once you have a dump file, use DebugDiag to analyze it.

Could you provide more information so that I can reproduce this.

What kind of conatenation do you use ?
- SAR in optional parameters
- UDH 8bit
- UDH 16bit

Do you set the reference number with your code or let you do it the library?

when i use client.DeliverAsync, without await first, Could you explain in details? When you send a DLR? What does continuation task after DeliverAsync? is it possible that there is some queue that wait for release ? It can be any reason. The customer can block reading from network and you get SMPPC...

Please note that Thread.Sleep method blocks all worker threads in the ThreadPool. Moreover the InternalSendMessageAsync method overloads the ThreadPool queue with unnecessary Tasks. As the result your application and library cannot do real work. It would be better if your loop waits from connection ...

Do you use .Result or .Wait for the Task?

Could you test the version 2.8.1-beta-2021 as well? There are some improvements for connection recovery.

Please test with version 2.8.1-beta-2021.

I have made ComposeItem non-disposable. The test pass where MessageComposer receives 7 parts with 100 duplicates for each of them from 700 different threads at the same time.

Please test with version 2.8.1-beta-2021.

Hi shane, I think it was an error in starting reconnect task from disconnect event. SmppClient has started new reconnect task every time when it disconnects. The previous reconnect task waits for connection and when client connects all tasks sends bind request. I'm going to fix this bug in the versi...

You need to get an access from your SMPP provider or local mobile network operator.

You can also test your application with SmppServerDemo.

https://docs.inetlab.com/smpp/v2.8/arti ... brary.html

I have published pre-release version 2.8.1-beta-2015.
You can download it from your Inetlab Account or as NuGet package.

Please test it.