Search found 987 matches

by alt
Mon Jul 19, 2021 9:33 am
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: own messageID issue on long (multipart) Messages
Replies: 3
Views: 41889

Re: own messageID issue on long (multipart) Messages

In the server_evClientSubmitSm event handler method the property submitSm.Response defines the response on the SubmitSm request. Library sends this response after the method is executed. For the MessageComposer this doesn't work. You can disable automatically response sending and send it with SendRe...
by alt
Mon Jul 19, 2021 9:24 am
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: $ and @ characters data coding
Replies: 5
Views: 40320

Re: $ and @ characters data coding

If you want to send "$£¥€" as 0x24A3A5A4 in Default data coding, you need to change the mapping this way: client.EncodingMapper.MapEncoding(DataCodings.Default, new System.Text.Encoding(1252)); and when you send the message you need to use DataCodings.Default . The same way you can set the encoding ...
by alt
Fri Jul 16, 2021 10:54 am
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: $ and @ characters data coding
Replies: 5
Views: 40320

Re: $ and @ characters data coding

You need to change .NET encoding for Latin1 data coding in the client encoding mapper:

Code: Select all

client.EncodingMapper.MapEncoding(DataCodings.Latin1, new Inetlab.SMPP.Encodings.GSMEncoding());
by alt
Thu Jul 15, 2021 1:39 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: ESME_RSUBMITFAIL when trying to send SMS
Replies: 10
Views: 65747

Re: ESME_RSUBMITFAIL when trying to send SMS

The value of the user_message_reference parameter can take only 2 bytes. Please use ushort type:

Code: Select all

ushort value = 111;
byte[] data = new byte[2];
data[1] = (byte)(value & 255);
data[0] = (byte)((value >> 8) & 255);
by alt
Thu Jul 15, 2021 8:22 am
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: ESME_RSUBMITFAIL when trying to send SMS
Replies: 10
Views: 65747

Re: ESME_RSUBMITFAIL when trying to send SMS

The smpp stream looks correct. I will try to examine this case today and understand why wireshark considers it as malformed packet.
by alt
Tue Jul 13, 2021 1:29 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: SmppClient.DisconnectAsync lasts long time
Replies: 6
Views: 44638

Re: SmppClient.DisconnectAsync lasts long time

vikarius wrote:
Tue Jul 13, 2021 1:16 pm
How can I switch on and use logging functionality?
https://docs.inetlab.com/smpp/v2.9/arti ... gging.html

Samples with some popular logging frameworks https://gitlab.com/inetlab/smpp-samples/
vikarius wrote:
Tue Jul 13, 2021 1:16 pm
We use 2.9.9 version.
Please update to latest version 2.9.12
by alt
Tue Jul 13, 2021 10:53 am
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: SmppClient.DisconnectAsync lasts long time
Replies: 6
Views: 44638

Re: SmppClient.DisconnectAsync lasts long time

some possible reasons of such behavior:
- smpp client waits until all received PDUs are processed.
- evDisconnected event handler method in the application does some processing
by alt
Tue Jul 13, 2021 10:32 am
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: SmppClient.DisconnectAsync lasts long time
Replies: 6
Views: 44638

Re: SmppClient.DisconnectAsync lasts long time

Hi vikarius,

Which library version are you using now?
Is library logging enabled in your application?
by alt
Mon Jul 12, 2021 3:02 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: ESME_RSUBMITFAIL when trying to send SMS
Replies: 10
Views: 65747

Re: ESME_RSUBMITFAIL when trying to send SMS

I think the new SMSC doesn't support user_message_reference TLV parameter. Better to ask the SMSC directly.
by alt
Mon Jul 12, 2021 10:25 am
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: ESME_RSUBMITFAIL when trying to send SMS
Replies: 10
Views: 65747

Re: ESME_RSUBMITFAIL when trying to send SMS

Hi If you send test SMS to the server created with SmppServer class, you should subscribe on evClientSubmitSm event. The ESME_RSUBMITFAIL status is returned when the SmppServer instance is not subscribed on this event. If you send to the third-party SMPP server, you have to ask your provider for the...
by alt
Tue Jun 01, 2021 12:25 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Best practice for a client that connects to multiple servers
Replies: 8
Views: 56432

Re: Best practice for a client that connects to multiple servers

When you start UpdateMessageStatus task, the DeliverSmResp will be sent at the same time without waiting for task completion. If you want to send response after task completion you need to send it manually as it described in "Control SMPP responses" article. without blocking the main thread from con...
by alt
Tue Jun 01, 2021 10:17 am
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Best practice for a client that connects to multiple servers
Replies: 8
Views: 56432

Re: Best practice for a client that connects to multiple servers

The same way you can implement evDeliverSm event handler method.
by alt
Tue Jun 01, 2021 8:57 am
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: SmppClient thread safe
Replies: 2
Views: 25530

Re: SmppClient thread safe

Yes, SmppClient is thread-safe.
by alt
Wed May 26, 2021 7:21 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Best practice for a client that connects to multiple servers
Replies: 8
Views: 56432

Re: Best practice for a client that connects to multiple servers

Hi bencover, SmppClient represents a connection to the SMPP server. You need to create at least one SmppClient instance for each provider. In general you should keep the connection with SMPP server alive. The connection recovery feature helps you here. The extension method RetryUntilConnectedAsync h...