SMS Connector Throughput Error

[HasanJa]

Hey All,

The above is the SMS connection settings for one of our clients who are on a hybrid mid-sourcing build.

For this client we are observing that a portion of our SMS's have the following error:

SMPP command submit_sm failed. SMPP channel has a limited throughput. (58).

From the information we have from our SMS partner the connection has 10 TPS per SMPP Session with a maximum of 5 sessions but when we had observed these errors our config from above remained the same, with the number of MTA child connections =1.

To fix this we tried to change the Number of MTA Child connections from 1 to 2 as detailed in the screenshot but the errors had persisted. Our SMS partner had said that their setting is 10 submit pdus per second, however the fact its going over this suggests the throttle config adobe side is not respecting that even though it's visible in our settings. From Adobe we have information that the mta child connection from Adobe is equal to 8 at the moment with this configuration.

Reverting the number of Connections back from 2 to 1 will just take us back from where we started, with which I'm still unsure why we would be observing throughput errros.

Has anyone observed something like this before or have any insight to share regarding this?

[ShashankNigam02]

Well, in a typical production setup, this TPS looks very less.

However, there is another way to control this is by configuring Waves setting in delivery properties. Try to send the message by creating low volume wave size.

[costa_n11 · Accepted solution]

Hi @HasanJa 

Check this page to get the furmula for the MT Throughtput

SMS connector protocol and settings, especially the connection settings where you've got the formula for the MT Throughput parameter.

Two parameters that you do not see are

• Number of MTA child processes: this parameter is set in the serverConfig. xml of the mid-sourcing instance, default from memory is 2 or 4. Adobe Support will give you the number
• Number of MTAs: this is the number of containers/app servers the mid-sourcing instance has, this depends of email volume I would expect you might have at last 2 containers but if you;ve got large contractual volume it can go up to 4...

As you will see with the formula, the 10 MT throughput from the external account can be multiplied by 2 (number of MTAs) and another 2 or 4 Number of MTA Chail processes, you'll go above the 58 limit from the SMS provider...

1. It is a common mistake to leave the default configuration on Adobe side thinking the SMS provider will match. To setup SMS channel properly, you must work with your SMS provider to align the configuration with their configuration and it all starts with the SMS provider giving their configuration from there, you setup Campaign, not the other way round...if you need throughput incrase you must work wiht your SMS provider FIRST and then align Campaign, not the other way round...
2. The 2nd mistake is that SMS should have its own channel affinity because any slowness of sending SMS can have dramatic impact on  other channels, email, push, etc... SO you need to setup delivery affinity for SSM whihc in a nutshell, you will have a dedicated set of MTAs (aka app servers aka containers) to send just SMS deliveries while other will send other channels...

I would suggest to get contact to Adobe Support that they can give you the back-up configuration and from there knowing the formula and knowing that you also need delivery affinity to be set up, you act accordingly.

Thanks

Denis

[HasanJa]

Thank you for this, it's worked just as you've explained. Much appreciated.