Hi,

Did you send only one SubmitSm in this test? It seems the SMSC returns different MessageId in SubmitSmResp and in delivery receipt.

Could you create wireshark file for this test and send to support@ ?

Hi,

I hope the article Send Messages helps you.

This issue is fixed in the version 1.0.0-beta-2580.

Please note: The method Submit in the MM7Client class is now Task-based.

Thank you for reporting this bug. I'll try to fix it as soon as possible.

Hi,

Please try pre-release version 1.0.0-beta-190705

You need to set ReceiveSpeedLimit property.

Hi,

You may need to store SubmitSm in central storage (RDBMS or Redis) and concatenate the message parts when they are received from all binds.
Another solution is to publish all received SubmitSm to message broker and handle the concatenation in another subscriber process.

This format is GSM PDU . The Inetlab.SMPP library supports only SMPP PDU.

When provider limits your SMPP traffic, it doesn't make sense to implement load balancing for this direction.
In most cases you need only one process that reads messages from queue and sends to the provider.

The messages from clients you can also push into queue in broker for routing process or ...

The connection is triggered from outside. Internal SmppConnection object writes these log events when some TCP client connects/disconnects with your server.
The format {localIP}:{localPort} => {remoteIp}:{remotePort} is used to represent the connection in the log event.

Hi,

It depends on your application architecture. At first step you may start all clients in single process on the single server.
You can design your project code, so that it will be easy to migrate to "multiple sources" way and eventually run each client in its own docker container with ...

No, it is not the license restriction.

I think it is a firewall problem on the machine.

Hello Anil,

This is common problem MethodAsync().GetAwaiter().GetResult() lead to dead lock in windows form application .

I hope this article helps you to solve the issue.

Understanding Async, Avoiding Deadlocks in C#

Short answer: rewrite your classes to async await methods that return Task ...

Hello Asaf,

ConnectAsync method returns true when connection is successful and false when not. So your application knows the connection result. You can also check client.Status property, it should be Open when connected and Close when disconnected.

When you use connection recovery feature you ...

You need to create two SmppServer instances, one for normal connection and second for secure connection on different TCP port. You can attach to both instances the same event handler methods.