Dear Jesri,
It can be the wrong DATA_CODING to .NET encoding mapping.
https://docs.inetlab.com/smpp/v2.9/arti ... oding.html
I need to check the SUBMIT_SM PDU you received from the client. Please send the Wireshark file to the support@ .
Search found 987 matches
- Mon Jun 13, 2022 4:01 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: SMPP Server receivied Strange characters
- Replies: 1
- Views: 39247
- Mon Jun 06, 2022 5:05 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: Scandinavian characters in incoming messages
- Replies: 3
- Views: 62401
Re: Scandinavian characters in incoming messages
Hi,
What value has data_coding field in the DELIVER_SM PDU?
I would use the same data_coding in the SUBMIT_SM PDU and set appropriate .NET Encoding in the EncodingMapper for the client.
https://docs.inetlab.com/smpp/v2.9/arti ... oding.html
What value has data_coding field in the DELIVER_SM PDU?
I would use the same data_coding in the SUBMIT_SM PDU and set appropriate .NET Encoding in the EncodingMapper for the client.
https://docs.inetlab.com/smpp/v2.9/arti ... oding.html
- Thu May 19, 2022 9:28 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: Sending BIND on receipt of an OUTBIND
- Replies: 3
- Views: 58099
Re: Sending BIND on receipt of an OUTBIND
The outbind was incomplete in the Inetlab.SMPP library. The version 2.9.18 has additional classes for this feature: - SmppOutbindClient class that can establish SMPP session with ESME using Outbind command. - SmppOutbindServerClient class, that passed down to the evClientOutBind event in the SmppSer...
- 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: 48676
Re: Client server connection using proxy
Hi,
What kind of proxy are you going to use? SOCKS5?
What kind of proxy are you going to use? SOCKS5?
- 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: 38415
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.
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.
- Wed Mar 09, 2022 9:57 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: USSD implementation issue
- Replies: 2
- Views: 48135
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...
- 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: 40344
Re: Insert the second part into DoneDate dlrBuilder
Hi
The date and time format is defined in the SMPP protocol specification.
The date and time format is defined in the SMPP protocol specification.
- 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: 38642
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...
- Wed Dec 29, 2021 4:44 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: Refresh the connectivity
- Replies: 7
- Views: 103307
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
- Tue Dec 28, 2021 4:30 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: Refresh the connectivity
- Replies: 7
- Views: 103307
Re: Refresh the connectivity
What library version are you using?
- Mon Dec 27, 2021 4:57 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: Refresh the connectivity
- Replies: 7
- Views: 103307
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 ...
- 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: 48863
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@ ?
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@ ?
- Tue Nov 30, 2021 7:28 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: How to send a message from Sever to Client event _client_evDeliverSm with MessageTypes = Default (0)
- Replies: 2
- Views: 56475
- 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: 89241
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.
Please note: The method Submit in the MM7Client class is now Task-based.
- 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: 89241
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.