Search found 7 matches

by bencover
Wed Aug 03, 2022 8:49 am
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Using Wireshark with TLS1.2 connection
Replies: 3
Views: 28677

Re: Using Wireshark with TLS1.2 connection

There no way to get the MasterSecret from the .NET SslStream. You can enable verbose logging for the library and find "Received data:" records with received PDUs in hex format. The data can be decoded on the website https://www.sysop.fr/smpp-decoder/ Thanks, alt! After looking into it deeper, it se...
by bencover
Tue Aug 02, 2022 9:47 am
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Using Wireshark with TLS1.2 connection
Replies: 3
Views: 28677

Using Wireshark with TLS1.2 connection

Hey, I'm currently working with a new provider and for some reason his DLR is all being received with a default Message-Id - "1111111111" In the SubmitResponse the MessageId is fine. example of DLR - ``` {"MessageId":"1111111111","Submitted":0,"Delivered":0,"SubmitDate":"2022-07-31T13:22:00","DoneDa...
by bencover
Tue Jun 01, 2021 1:51 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Best practice for a client that connects to multiple servers
Replies: 8
Views: 56768

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 co...
by bencover
Tue Jun 01, 2021 10:37 am
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Best practice for a client that connects to multiple servers
Replies: 8
Views: 56768

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

The same way you can implement evDeliverSm event handler method. Sorry I'm uncertain on what you mean and how exactly it fits my needs. evDeliverSm is an event triggered when request is being made from the server to my client (either incoming message or a DLR). This event only accepts SYNC void sig...
by bencover
Tue Jun 01, 2021 9:38 am
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Best practice for a client that connects to multiple servers
Replies: 8
Views: 56768

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

In this case I would implement manual response sending https://docs.inetlab.com/smpp/v2.9/articles/smpp-server/control-smpp-responses.html The link you've shared is strictly for SMPP servers isn't it? I'm running an SMPP Client, and simply willing to receive DLR and incoming replies to messages I s...
by bencover
Mon May 31, 2021 8:22 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Best practice for a client that connects to multiple servers
Replies: 8
Views: 56768

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 ...
by bencover
Wed May 26, 2021 1:01 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Best practice for a client that connects to multiple servers
Replies: 8
Views: 56768

Best practice for a client that connects to multiple servers

Hey, We currently got a system that has multiple HTTP API integrations to SMS providers. In order to improve scalability and to make it easier to integrate with other providers we are willing to develop an SMPP client using InetLab as all of the providers we work with also has an SMPP credentials in...