Some SMSC has limits on message throughput. In ALT.SMS.SmppClient you can specify SubmitSpeed value (messages per minute).
AdvancedSubmit checks SubmitSpeed value and limits repeated submits in order to avoid ESME_RTHROTTLED status.

SubmitText method supports concatenated messages, if message longer then one SubmitSm packet it returns an array of responses from SMSC.
You should check status of all responses in array to make sure that all packets was sent correctly.

Yes, all upgrades are free

Hello, Steve.

Yes, you can use SubmitSm.Optional property.

I've released version 1.2.2
I hope I solved these two issues.

Strange, this pdu has both UDHI and Reply Path flags, but User Data Header
has incorrect UDHL length = 30 (48 dec).
What do you expect in this user data?

It looks like ordinary SMS message.
Can you check if client raises evDeliverSm and evSendData events after evReceiveData event?

Could you send me a hex dump of such message?

Second issue will be fixed in the next version.

Thank you a lot.
I've sent you source code.
Let me know if it works for you now.

Please try version 1.2.1. I've added support of AlertNotification message.
Sorry for long delay.

I've turned off this sleep. Try version 1.2.1.

Sorry I have no ready to use code.
You have to prepare User Data your self. Refer to 3GPP TS 23.040 http://www.3gpp.org/ftp/Specs/archive/2 ... 40-660.zip
Read chapter 9.2.3.24. There is a description how to create EMS messages.

Could you show me the values of the following variables:
orgTon, orgNpi, destination, desTon, desNpi, msisdn, msgBody

yes, you can detect it by checking property MessageType in a DataSm or DeliverySm opertaions.

It looks like everything correct.
Any problems?