No, it is not the license restriction.
I think it is a firewall problem on the machine.
Search found 995 matches
- Tue Sep 07, 2021 6:40 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: Running two SMMP Server on the same Computer
- Replies: 1
- Views: 82934
- Thu Aug 12, 2021 7:59 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: SMPP connection issue in VB.Net WinForms application
- Replies: 1
- Views: 79713
Re: SMPP connection issue in VB.Net WinForms application
Hello Anil,
This is common problem MethodAsync().GetAwaiter().GetResult() lead to dead lock in windows form application .
I hope this article helps you to solve the issue.
Understanding Async, Avoiding Deadlocks in C#
Short answer: rewrite your classes to async await methods that return Task ...
This is common problem MethodAsync().GetAwaiter().GetResult() lead to dead lock in windows form application .
I hope this article helps you to solve the issue.
Understanding Async, Avoiding Deadlocks in C#
Short answer: rewrite your classes to async await methods that return Task ...
- Thu Aug 12, 2021 7:48 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: evConnected event?
- Replies: 2
- Views: 106802
Re: evConnected event?
Hello Asaf,
ConnectAsync method returns true when connection is successful and false when not. So your application knows the connection result. You can also check client.Status property, it should be Open when connected and Close when disconnected.
When you use connection recovery feature you ...
ConnectAsync method returns true when connection is successful and false when not. So your application knows the connection result. You can also check client.Status property, it should be Open when connected and Close when disconnected.
When you use connection recovery feature you ...
- Mon Aug 09, 2021 7:07 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: SMPP Server
- Replies: 1
- Views: 73802
Re: SMPP Server
You need to create two SmppServer instances, one for normal connection and second for secure connection on different TCP port. You can attach to both instances the same event handler methods.
- Tue Aug 03, 2021 7:20 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: wrong message length custom user data header
- Replies: 2
- Views: 92354
Re: wrong message length custom user data header
It is not correct to use User Data Header concatenation and MessagePayload parameter. You need to use SAR TLV Parameters with MessagePayload.
https://docs.inetlab.com/smpp/v2.9/arti ... ation.html
https://docs.inetlab.com/smpp/v2.9/arti ... ation.html
- Sun Jul 25, 2021 12:30 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: Do I need to create task for multi-client?
- Replies: 1
- Views: 69853
Re: Do I need to create task for multi-client?
Which task do you mean?
SmppClient represents one SMPP session with SMS provider. Therefore if you need to establish multiple sessions with one or many providers you need to create the same number of SmppClient instances.
SmppClient represents one SMPP session with SMS provider. Therefore if you need to establish multiple sessions with one or many providers you need to create the same number of SmppClient instances.
- Mon Jul 19, 2021 4:34 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: own messageID issue on long (multipart) Messages
- Replies: 3
- Views: 114866
Re: own messageID issue on long (multipart) Messages
If you want to set MessageId for the SubmitSmResp in the method OnFullMessageReceived you need:
1. to disable response sending as it described in the link above in the server_evClientSubmitSm method;
submitSm.Response = null;
2. to create responses in the OnFullMessageReceived method for each ...
1. to disable response sending as it described in the link above in the server_evClientSubmitSm method;
submitSm.Response = null;
2. to create responses in the OnFullMessageReceived method for each ...
- Mon Jul 19, 2021 4:18 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: $ and @ characters data coding
- Replies: 5
- Views: 146541
- 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: 114866
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 ...
You can disable automatically response sending and send it with ...
- Mon Jul 19, 2021 9:24 am
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: $ and @ characters data coding
- Replies: 5
- Views: 146541
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 ...
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 ...
- Fri Jul 16, 2021 10:54 am
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: $ and @ characters data coding
- Replies: 5
- Views: 146541
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());- 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: 284497
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);- 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: 284497
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.
- 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: 133901
Re: SmppClient.DisconnectAsync lasts long time
https://docs.inetlab.com/smpp/v2.9/arti ... gging.html
Samples with some popular logging frameworks https://gitlab.com/inetlab/smpp-samples/
Please update to latest version 2.9.12
- 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: 133901
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
- smpp client waits until all received PDUs are processed.
- evDisconnected event handler method in the application does some processing