Search found 4 matches

by abrdeco2
Thu Feb 15, 2024 4:49 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: SMPPServer SendSpeed limit below than the remote and receiving ESME_RMSGQFUL
Replies: 1
Views: 375

SMPPServer SendSpeed limit below than the remote and receiving ESME_RMSGQFUL

Hello. I´ve set the SendLimit speed below the remote receive limit and I´m receiving ESME_RMSGQFUL. We are using library version 2.9.32 and setting the limit speed with command: _server.SendSpeedLimit = new LimitRate(50, TimeSpan.FromSeconds(1)); I can´t send over 50 messages per second. Anybody can...
by abrdeco2
Sat Feb 10, 2024 12:12 am
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Coding issue using SMPP Server sending DLR do client.
Replies: 1
Views: 375

Coding issue using SMPP Server sending DLR do client.

How could I get the status of a sent DLR using DeliverAsync to an remote client without use await on the code ? I deal with a large ammount of messages. Does the library has any event that I can check if had any error on the DLR sent ? Currently I´m sending the dlr using the command item.DeliverAsyn...
by abrdeco2
Mon Jun 12, 2023 6:54 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Dynamic encode and convertion to UTF-8
Replies: 1
Views: 22476

Dynamic encode and convertion to UTF-8

Hello.

I´m currently stuck dealing with different encodings received.

Anyone can help with some snippet to identify the current encode and correctly convert to UTF-8 to permit store in a database ?

Thankyou,
André
by abrdeco2
Tue Jan 18, 2022 11:08 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Strange behavior with messages with lenght greater than 160(default encoding)
Replies: 1
Views: 19970

Strange behavior with messages with lenght greater than 160(default encoding)

Hello all! When I send an message to my system up to 160 characters in lenght everything works fine, bet when the message is greater like 161 it splits into the message with 153 characters. Can anyone tell me if this behavior is normal ? I´m using the release 2.9.15 and saw an old bug that was solve...