What differences are there between Inetlab.SMPP and ALT.SMS.SmppClient? (excluding the SMPP server).

I have ALT.SMS.SmppClient.2.8.0 source code, I noticed a bug with the message throttling that I assume has been fixed by now :)
.Milliseconds were being used instead of .TotalMilliseconds to manage ...

Thanks.

Are these (4098 (0x1002) and 4099 (0x1003)) library specific response codes or have they been returned from the SMSC?

If the latter, any idea what they could mean?

I get them rarely when I send 'sm_submit's

We use mBlox and Sybase as SMSC.

mBlox uses default of Latin-1 encoding, but if you set encoding to ASCII/GSM they expect unpacked GSM 03.38 encoded data.

I'm unsure what default Sybase use, but for ASCII/GSM encoding they again expect unpacked GSM 03.38 encoded data.

This confused me for a long ...

Not a copy and paste error. It's missing in my encode code too. I'll edit the code, thanks for spotting it.

Is this what you need?

I've not tested it, but it's just the reverse of the encoder algorithm.

[Edit: Changed second line feed to carrier return.]
[Edit: § was not decoding, added § at 97 (0x5F)]

public static string GsmDecode(byte[] encodedData)
{
// ? is not a conversion, just a ...

Have you changed the EsmClass to flag there is a UDH?

ShortMessage has a maximum of 254bytes
Payload has a maximum of 64bytes

Since most telephony networks won't let you send more than 160 characters in one SM I believe you should usually use ShortMessage.

Payload I believe is for when you might be sending larger binary data such as Logos and ...

Aren't there Hex2Str and Str2Hex functions in the sample project?

If the message is the same and your SMSC supports it, you can use Submit_Multi to send the same message to multiple destination addresses.

you can use client.PrepareSubmit and pass in a list of DestinationAddresses to create a ...

My SMSC takes 7bit encoding with 8 bit characters (the 8th bit is always 0). As far as I know this is standard.

If your SMSC isn't following this, then you'll need to write an algorithm to concatenate the 7bit characters in a binary stream.

Is this payload problem a seperate problem?

Since you aren't suppose to use Payload and ShortMessage at the same time, this can cause problems.

I've used Latin-1 and ASCII in ShortMessage mode and both work fine with my SMSC. So alt is possibly right and it may be a problem with your SMSC.

What text are you trying to send? Is it alphanumeric characters only?

Also, what mode are you using? Payload/Shortmessage?

To use in concatenate messages,

// Encode as GSM 03.38
byte[] data = GsmEncode(/* Plain Text */);

List<SubmitSm> reqs = new List<SubmitSm>();

// If message needs to be concatenated (140 bytes (160 Gsm characters))
if (data.Length > 160)
{
byte concatMsgRef = // Generate new unique ...

Below is close to what I am using, so far I've had no problems with it.


// Encode as GSM 03.38
byte[] data = GsmEncode(/* Put Plain Text here */);

List<SubmitSm> reqs = new List<SubmitSm>();

// If message needs to be concatenated (140 bytes (160 Gsm characters))
if (data.Length > 160 ...

See http://www.inetlab.ru/support/viewtopic.php?t=631

If you set the Encoding to ASCII then use that algorithm to generate your ShortMessageBytes it should work.

I'm using this currently.

If you want to concatenated messages, it gets a bit more complicated. I can post this algorithm also if you ...