Search found 8 matches

by didimo
Tue Apr 09, 2024 3:01 pm
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: Obtain the client IP over the proxy
Replies: 3
Views: 48197

Re: Obtain the client IP over the proxy

Does the Proxy supports Proxy protocol https://www.haproxy.com/blog/haproxy/proxy-protocol/ ? Hello alt, We are in the same situation as owlboo98. Our SMPPserver solution is deployed with HAProxy and proxy protocol enabled. Our goal is also obtain source IP without NAT (transparent IP) and without ...
by didimo
Wed Jul 19, 2023 10:29 am
Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
Topic: UserData Length Error sending DeliveryReceipt UCS2
Replies: 1
Views: 32182

UserData Length Error sending DeliveryReceipt UCS2

Hi, I've found the following error when sending DeliveryReceipt using DataCoding UCS2 from original SMS. "System.InvalidOperationException: UserData cannot be longer than 255 bytes. Current length is 296." When I don't set DataCoding con SMS builder it works. When I set DataCoding Default it works. ...
by didimo
Wed Jun 17, 2015 6:20 pm
Forum: Inetlab.SMPP v1.1 & v1.2
Topic: Concatenated messages with GSMPackedEncoding
Replies: 1
Views: 6590

Concatenated messages with GSMPackedEncoding

Hi, We have an issue: when we send a concatenated message with GSMPackedEncoding, the SMSC receive the message data with wrong chars. According with the support team of SMSC, the problem is: You missed „fill bits“ between UDH and content in front of every concatenated sms. Just look here: http://en....
by didimo
Thu Apr 10, 2014 1:17 pm
Forum: Inetlab.SMPP v1.1 & v1.2
Topic: How to convert septects to octets
Replies: 0
Views: 24517

How to convert septects to octets

Hi, We have to connect to a SMPP server that our SMSC operator specified to use DCS = 241 (Class1) and pack septets to octets . We initialize the smpp client MapEncoding and build Submit_sm as below: smppClient.MapEncoding(Inetlab.SMPP.Common.DataCodings.Class1, new Inetlab.SMPP.Encodings.GSMPackedE...
by didimo
Tue Feb 18, 2014 5:02 pm
Forum: Inetlab.SMPP v1.1 & v1.2
Topic: Bad Deliver_SM_Resp received
Replies: 3
Views: 11629

Re: Bad Deliver_SM_Resp received

thanks!
we will try this on new version...
by didimo
Tue Feb 18, 2014 5:01 pm
Forum: Inetlab.SMPP v1.1 & v1.2
Topic: Deliver_SM not received on client
Replies: 3
Views: 15646

Re: Deliver_SM not received on client

hi! we've found that sometimes perl client doesn't listen for dlr pdu so our server is raising a timeout after 120s we will implement dlr notifications retry to clients for these case and others for that we need to manage our dlr id when sending deliver_receipt pdu y receiving sending deliver_receip...
by didimo
Thu Jan 23, 2014 9:46 pm
Forum: Inetlab.SMPP v1.1 & v1.2
Topic: Deliver_SM not received on client
Replies: 3
Views: 15646

Deliver_SM not received on client

Hi, We have the following problem SMPP Perl client running on Linux doesn't receive all Deliver_SM, there are some lost packets We think it is network problem at client but we are not sure We captured 2 stream packets (posted bellow), first one received on client (trace1) and second lost (trace2) Co...
by didimo
Thu Jan 23, 2014 9:35 pm
Forum: Inetlab.SMPP v1.1 & v1.2
Topic: Bad Deliver_SM_Resp received
Replies: 3
Views: 11629

Bad Deliver_SM_Resp received

hi, we are experiencing something strange we have smpp server with some clients running on diferent platforms when sending Deliver_SM to almost they return Deliver_SM_Resp that server understand correctly and show status ESME_ROK but there is a Perl-SMPP client running on Linux that who's Deliver_SM...