Dear stevep,

First of all you need to ask Mobile Network operator for access using MM7 protocol.

They should give you http url, username and password.

Sorry vasavi,

Here is support forum for ALT.SMS.SmppClient only.

Please try event evDeliverSmComplete. It is raised when DeliverSmResp already sent.

In the event evDeliverSm you can modify DeliverSmResp response. f.i. send non OK status.

I suggest you to use event evReceiveData to check if SubmitSmResp packet was received by SmppClient.
If you will find that response was not received in evReceiveData, you can take any network analyzer and check if SMSC sends response to you.

Hi fouad,

Sorry it is not implemented yet.
I'll notify you when it will be added.

SubmitSpeed defines number of SMS per minute. Some SMSC have limit of allowed SMS per minute. And when this limit is exceeded, SMSC returns status ESME_RTHROTTLED. SubmitSpeed property is used in the method AdvancedSubmit to prevent of receiving of this error status. In asynchronous methods this pro...

Yes, you can send SMS with async methods like SubmitTextAsync.
It is about 1000 SMS per minute.

These are library specific status codes

UDHI flag is set automatically when you use User Data Headers. chaoraksa, With Payload mode sm.UserDataPdu.Headers and sm.ShortMessageBytes cannot be used, because sm_length should be 0 for this mode. Please try with mode ShortMessage . But you need to add headers instead of overwrite it as in your ...

In version 2.8 I'm going to implement GSMEncoding class. But problem that several SMSC work in different ways. For Default SMSC coding (0x0) i know three ways - plain ASCII - unpacked GSM 03.38 - packed 7bit GSM 03.38 Would be good if all readers post here information about a way which their SMSC us...

hello,

Do you mean event evSubmitComplete ?

Why you use thread for SubmitAsync ? This method creates thread itself.

What version do you use?

Solution is
- to use Async methods,
- do not use events evReceiveData, evSendData,
- update library to last version.

Sorry,
but we talk about deliver_sm and problem with message_payload field content.

send you log from first post to vendor and ask why they encoded converted original bytes to hex string and then encoded it to 8 bit ASCII bytes array.

yes, I think so

you can use properties deliverSm.MessageReferenceNumber; deliverSm.TotalSegments; deliverSm.SegmentNumber; they have values when parts information can be retrieved from UDH or from SAR option fields. But in you case User Data is placed in message_payload and original byte array was prepresented as h...