The version 1.x is not supported anymore.

See the attached wireshark file and check for phonenumber : 917889570141 DeliverSM. we got this error on this Deliversm only not all deliversm sent by this vendor. In this wireshark capture there is only one i can find which gave us this error. i hope it will help you. The DeliverSm PDU with sequen...

There is no issue while sending a batch of 120000 Messages at once in V1 library. but when ever we switch to v2 library the vendor gets disconnected just after 1500-2000 submissions and rest of all the messages goes in SMPP_NOCONN error. please provide a solution for this because of this major issu...

The number of requests waiting for response you can read from metric: client.Metrics.Sent.Requests.WaitingForResponse i tried this it always shows 0 or 1. but my problem is i have submitted batch containing 50 messages. IEnumerable<SubmitSmResp> ResponseList = (await SMPPClient.SubmitAsync(batch))....

please suggest a value for SendQueueLimit if normally batch submission is around 15k-25k to avoid ESME_RMSGQFUL. And shouldn't send speed limit should delay the message sending regardless how many are begin fed in queue. You should find out by provider when he sends ESME_RMSGQFUL status and how man...

Hi vineet, 1. Event evFullMessageReceived failed Exception: System.ArgumentNullException: Array cannot be null. Parameter name: bytes at System.Text.Encoding.GetString(Byte[] bytes) at Inetlab.SMPP.Common.MessageComposer.OnFullMessageReceived[TSmppMessage](TSmppMessage message). (SMPP Server Message...

With the version 2.9-beta you can use client.SendQueueLimit property to limit number of requests waiting for response which limits memory consumption for a smpp connection. It helps also to avoid ESME_RMSGQFUL (Message queue full) response status from the SMPP server. The number of requests waiting ...

Hi vineet,

It means that library sends PDU immediately after serialization and remote side handles it fast enough.
SendSpeedLimit delays PDU before placing into the send queue.

Please don't use .Wait() method or .Result property for async methods

Task.Delay(60000).Wait();

replace with

await Task.Delay(60000);

I suggest to write in log all exception details with exception.ToString() instead of exception.Message;

Hi vineet, 1. An exception was thrown by a TaskScheduler. 4. Value cannot be null. Parameter name: scheduler Please provide all details for these exceptions. 2. Exception of type 'System.OutOfMemoryException' was thrown. Out of memory exception can occur in any part of the code. How many messages do...

Hi vineet,

It is normal case. SMPP is asynchronous protocol. When you cannot find MessageId in sent messages, you need to save received delivery receipts in some collection/dictionary and process it when you finish with batch sending.

Hi,

you need to subscribe on evDeliverSm event.

https://docs.inetlab.com/smpp/v2.8/arti ... ceive.html

You should set Logger property after setting Name property.

client.Name = "LOG_" & client.SystemId
client.Logger = New FileLogger("c:\Log\" & client.SystemID & "_CLI.log", TraceLevel.Verbose)

I cannot reproduce your issue. When I set FileLogger for the client it writes into the file as expected. Do you change _client.Name after setting FileLogger? Try to do it before. I found at "warnings" tab that information: "conflicts were found between different versions "System.IO.Compression" that...

Do you see any error in Console.Error ?

I would suggest to use NLog or any other logging framework.

https://gitlab.com/inetlab/smpp-samples ... ngWithNLog