Search found 984 matches

by alt
Mon May 16, 2022 5:00 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Client server connection using proxy
Replies: 2
Views: 17694

Re: Client server connection using proxy

Hi,

What kind of proxy are you going to use? SOCKS5?
by alt
Mon Mar 14, 2022 4:13 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Multiple Clients bind to an SMPP server
Replies: 1
Views: 14844

Re: Multiple Clients bind to an SMPP server

Hello ojukwu24

For now 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 and attach event handler method to all instances.
by alt
Wed Mar 09, 2022 9:57 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: USSD implementation issue
Replies: 2
Views: 17738

Re: USSD implementation issue

It depends on the USSD service implementation on the provider side. I would ask the provider support how it should be sent. When you have an answer, I can help you to complete this with Inetlab.SMPP library. The answer can be also that the message text is limited to 140 octets. You can try to send t...
by alt
Thu Jan 20, 2022 5:02 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Insert the second part into DoneDate dlrBuilder
Replies: 1
Views: 15013

Re: Insert the second part into DoneDate dlrBuilder

Hi

The date and time format is defined in the SMPP protocol specification.
Screenshot 2022-01-20 175937.png
Screenshot 2022-01-20 175937.png (65.59 KiB) Viewed 15009 times
by alt
Wed Jan 19, 2022 12:45 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: 14819

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

Hello André, It should be normal. User data header for concatenation takes 6 octets in the short_message field. Possible one of the character in your text takes two octets, therefore 153 instead of 154. Or you use 16-bit reference number. Could you post an example for this case? Which code do you us...
by alt
Wed Dec 29, 2021 4:44 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Refresh the connectivity
Replies: 7
Views: 34294

Re: Refresh the connectivity

Could you please test this case with the recent version of the library. Some issues with connect/disconnect are already fixed. See ChangeLog
by alt
Tue Dec 28, 2021 4:30 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Refresh the connectivity
Replies: 7
Views: 34294

Re: Refresh the connectivity

What library version are you using?
by alt
Mon Dec 27, 2021 4:57 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Refresh the connectivity
Replies: 7
Views: 34294

Re: Refresh the connectivity

Which error do you mean? "Remote side has dropped connection." ? This error means that the provider didn't accept the TCP/IP connection from your IP. It can be a firewall issue. Why do you use local IP address 127.0.0.1:8887 to connect to SMPP provider? Consider connection recovery build-in feature ...
by alt
Tue Nov 30, 2021 7:53 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Pairing submited message with delivery recipet
Replies: 2
Views: 18109

Re: Pairing submited message with delivery recipet

Hi,

Did you send only one SubmitSm in this test? It seems the SMSC returns different MessageId in SubmitSmResp and in delivery receipt.

Could you create wireshark file for this test and send to support@ ?
by alt
Wed Nov 24, 2021 6:44 pm
Forum: Inetlab.MMS.MM7
Topic: The type initializer for 'Inetlab.MMS.MMSMessage' threw an exception
Replies: 4
Views: 35882

Re: The type initializer for 'Inetlab.MMS.MMSMessage' threw an exception

This issue is fixed in the version 1.0.0-beta-2580.

Please note: The method Submit in the MM7Client class is now Task-based.
by alt
Mon Nov 22, 2021 2:13 pm
Forum: Inetlab.MMS.MM7
Topic: The type initializer for 'Inetlab.MMS.MMSMessage' threw an exception
Replies: 4
Views: 35882

Re: The type initializer for 'Inetlab.MMS.MMSMessage' threw an exception

Thank you for reporting this bug. I'll try to fix it as soon as possible.
by alt
Mon Oct 11, 2021 12:16 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Concatenated in SMPP Server Load Balancing with multiple binds.
Replies: 2
Views: 18811

Re: Concatenated in SMPP Server Load Balancing with multiple binds.

Hi,

You may need to store SubmitSm in central storage (RDBMS or Redis) and concatenate the message parts when they are received from all binds.
Another solution is to publish all received SubmitSm to message broker and handle the concatenation in another subscriber process.