This is obfuscator problem. I'm trying to solve it.
The only solution for now is to use source code license.

code is the same as for normal Submit. You need to specify one of the data codings DefaultFlashSMS or UnicodeFlashSMS. SubmitSm[] req = client.PrepareSubmit( mode, byte.Parse(tbSrcAdrTON.Text), byte.Parse(tbSrcAdrNPI.Text), tbSrcAdr.Text, byte.Parse(tbDestAdrTON.Text), byte.Parse(tbDestAdrNPI.Text),...

Please try last version 2.6.1.

Please test version 2.5.9
It has bug fix in SubmitSmResp

it waits 120 seconds (defined in the Timeout property)
after that Connect method returns false.

Hello,

Status code 1032 is reserved for SMSC vendor specific errors.
Please ask your SMSC side.

Could you describe steps to reproduce this exception?

yes, just send me a mail message with your invoice

You can try Wap Push described in thread
http://www.inetlab.ru/support/viewtopic.php?t=517

Sorry,
Since version 2.0.0 we do not support .NET 1.1 any more.
Please consider to upgrade your application to .NET 2.0.

Or you can order source code and modify it, so that it can work with VB.NET 2003.

Hi David,

Last version 2.5.8 already has DataCodings.Latin1 (3)
Please download it from
http://www.inetlab.ru/Products/ALT.SMS. ... x#download

In order to receive confirmation as DeliverSm, you have to enable registered_delivery field.
Please also try to set
This helps you to keep connection alive.

Please have a look at SubmitSm.UserDataPdu.Headers

Please try last version
Download from http://www.inetlab.ru/Products/ALT.SMS. ... x#download

Can you try with last version?
Download from http://www.inetlab.ru/Products/ALT.SMS. ... x#download