More than one submit in the same network frame

[aordonez]

Hi, I'm using SMPP client v 2.8.6 and my SMS provider warning me about to send several submits in the same frame, but I can't find any option in the library to handle it.
It's possible to control it?
below a tcpdump as an example

[alt]

Hi aordonez,

Do you mean that the SMS provider requires to send each SMPP PDU in a single TCP packet?

This can significantly reduce the performance.

I could add the option in current beta version v.2.9.

[aordonez]

Hi, that's correct.

I'm assume it will impact directly in the performance.

There is any chance to set this new behavior by smppclient?, because there is no problem with the rest of the providers we have.

[alt]

Yes, this option will be defined in the SmppClient.

[aordonez]

Excellent!!!! When do you think, it will be released to test it?

[alt]

I have a question. What SMS provider is expecting from your client?
Do you need to wait for SubmitSmResp before sending next SubmitSm?

For batch sending it can happen that SMS provider application receives more than one PDU with the single socket.read(buffer) call, even when sender calls socket.write(pduBuffer) for each PDU.
It means from the receiver point of view there is no difference how sender sends the stream of PDUs.

Can your SMS provider tell us the reason why you need to send only one PDU in a single transmission unit (TCP packet)?

[myggan]

We have the same issue with Swedish Telia. More than one SubmitSM in the TCP packet will cause them to fail (Error Invalid Source Address).
Setting the TcpClient.NoDelay did not resolve our issue.
Note: We are not using the InetLab SMPP client (yet?), just scouting our options.

[alt]

Please try the version 2.9.5-beta-2298 with following code

Code: Select all

bool conected = await _client.ConnectAsync(new SmppConnectionOptions
            {
                RemoteEndPoint = remoteEndPoint,
                SinglePDUinTCPPacket = true
            });