Thanks.

Thanks!


You can send 160 chars per SMS only when you use packed GSM encoding. You can enable it with code

CODE: SELECT ALL
client.MapEncoding(DataCodings.Latin1, new Inetlab.SMPP.Encodings.GSMPackedEncoding());



Does this feature depends on the provider?

BTW, it is a very important piece ...

because in version 1.1 properties SubmitSM.ShortMessage and SubmitSM.ShortMessageBytes are obsolete.

Thanks. Good to know.

If I define the DataCoding in the ShortMessage, do I need to define it again in the SubmitSM.DataCoding property?


And please remember that you cannot send message longer ...

BTW, a workaround will be to use this:
SubmitSM.ShortMessageBytes = Client.GetMessageBytes([message], [DataCoding])

Hi,

I'm trying to send a single message using SubmitAsync So I have created a SubmitSM object using this constructor:
SubmitSm Constructor (String, Byte, Byte, String, Byte, Byte, String)
then I fill the various fields like RegisteredDelivery, DataCoding, PriorityFlag, ValidityPeriod and ...

Thank you!

Hi Alt,

Can you elaborate a bit about this subject? I'm evaluating your product and trying to understand if it suits my needs...
The scenario I'm looking for is storing every outgoing SMS (MT) in my DB and update its status (DELIVER_SM) as it changes. What will be the best way to do it?
I mean ...

Hi,

What will be the minimum specs of the server to run SMPP server? Client? (OS architecture (x86, x64), OS version, CPU, RAM, etc).
How much RAM will it require when sending lets say 100 SMS in "oneshot"?

Thank you.

Alon