InetLab - Mobile Internet Solutions

The problem may be related to your payment provider or bank declining the transaction. Some common reasons for this include:

- Insufficient funds
- Bank security flags (possible fraudulent transaction)
- Incorrect CVV or card details
- Generic declines from the bank

Please check if your card ...

Hi,

In this context, "message" refers to a single SubmitSm PDU.

To evaluate performance, you can use the following metrics:

_smppClient.Metrics.Sent.Request.PerSecond;
//or
_smppClient.Metrics.Sent.Request.AvgPerSecond;

For more details about built-in metrics, please visit the
https://docs ...

Hi Luis,

Yes, you can create a single instance of the MessageComposer class for the SMPP server. The class is thread-safe, allowing you to add different messages concurrently.
The composer uses a combination of the source address, destination address, and message reference number as a unique key ...

Hi Ben,

The code is correct.

I would check the captured PDUs in wireshark.

If you still has this issue please write me to e-mail support@

You need to enable ProxyProtocolEnabled for the client in the handler method for the event evClientConnected

smppServer.evClientConnected += (sender, client) =>
{
client.ProxyProtocolEnabled = true;
};

after that the RemoteEndPoint of the client returns the IP address behind the proxy.

SendSpeedLimit can only help to prevent the throttling error ESME_RTHROTTLED

When you get the Message Queue Full error status ESME_RMSGQFUL, you have to limit the number of SMPP requests waiting for response with the property SendQueueLimit

You can use

Code: Select all

 DeliverAsync(..).ContinueWith(..)

See example

It looks like the property ScheduledDeliveryTime or ValidityPeriod has incorrect value in SubmirSm instance.

Could you help me to reproduce the error?

I think the same exception should be thrown when you set the values for SubmitSm instance and try to serialize it

ver byteArray = submitSm ...

Hello,

Inetlab.SMPP library provides two extension methods CanBeDecoded , CanBeEncoded

https://docs.inetlab.com/smpp/v2.9/api/Inetlab.SMPP.Encodings.EncodingExtensions.html

With these methods you can check if text can be encoded with specified encoding or if the byte array can be decoded with ...

Hi didimo,

Why do you need to send Delivery Receipt in UCS2 data coding?
Library sends DLR as single PDU. The Receipt you created is to long. Maybe you have to remove receipt.Text or make it shorter.

Hi arip,

1) This is an issue on the SMPP provider. Both MessageIds must use the same format for correlation purpose.

2) This approach may function properly when dealing with a single SystemId, as long as the SMPP provider remembers the SMPP session on which the SUBMIT_SM was received. By utilizing ...

for the SmppServer you can change this option with code

Code: Select all

_server.ConnectionOptions.SinglePDUinTCPPacket = true;

Hello ritik,

You can disable this feature with following code:

Code: Select all

bool conected = await _client.ConnectAsync(new SmppConnectionOptions
            {
                RemoteEndPoint = remoteEndPoint,
                SinglePDUinTCPPacket = true
            });

Does the Proxy supports Proxy protocol https://www.haproxy.com/blog/haproxy/proxy-protocol/ ?

If all the responses are present in the library log, then they have been processed correctly.
It looks like there is a deadlock in your application. Is it a Windows Forms or an ASP.NET application?

I hope this article helps. Understanding Async, Avoiding Deadlocks in C#

Search found 991 matches

Re: Unable to Purchase License — What Should I Do

Re: SendSpeedLimit has no effect

Re: MessageComposer in SMPP Server

Re: Adding optional TLV parameters to payload

Re: Obtain the client IP over the proxy

Re: SMPPServer SendSpeed limit below than the remote and receiving ESME_RMSGQFUL

Re: Coding issue using SMPP Server sending DLR do client.

Re: System.ArgumentOutOfRangeException : Too long (Parameter 'S')

Re: Dynamic encode and convertion to UTF-8

Re: UserData Length Error sending DeliveryReceipt UCS2

Re: Matching Message Id form SubmitSm (hex) with delivery notification (decimal)

Re: Why multiple submit_sm-resp in one packet

Re: Why multiple submit_sm-resp in one packet

Re: Obtain the client IP over the proxy

Re: SubmitAsync never ends