Sms delivery speed and sessions

Sms delivery speed and sessions SearchSearch
Author Message
medium kuriboh
Posted on Monday, November 24, 2008 - 03:42 am:   

We have a bulk account that we're having trouble with, the problem is that we need more speed for sending messages. the connection is via SMPP. we contacted the provider to increase the speed, he told us that he already provided 10 sessions for us, and we don't need more.
If i bind several sessions, is it faster really, or one connection will use the 10 sessions?

Thanks
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 251
Registered: 08-2008
Posted on Monday, November 24, 2008 - 10:27 pm:   

Hi,

There are two solutions for faster speed on SMPP connections.

1.) Enabling "Async mode" for SMPP windowing. This is a configuration setting on the "Advanced Settings" under "Properties" for an SMPP connection.

Generally speaking, I recommend setting the window size to twice the number of messages per second you are trying to achieve (but there is little, if any benefit setting this higher than 100).

Determining the optimum window size, unfortunately, is a trial and error process.

And not, all providers support SMPP async mode, so if you enable this setting and see large numbers of throttling errors and retries, then you may need to go back and disable SMPP async mode (or set the window size to 1, which offers a minor performance improvement in NowSMS compared to the default mode).

2.) Multiple sessions (binds). This will absolutely provide you with improved throughput.

If your provider allows you to have up to 10 sessions with them, and you are not taking advantage of it, you should.

How to do this?

Well, first let me explain a little about how NowSMS works with an SMPP connection.

This link has a good explanation of SMPP connection types:

http://blog.nowsms.com/2008/07/smpp-connection-types-sender-receiver.html

By default, if you are both sending and receiving messages, NowSMS will create 2 connections to your provider, one sender and one receiver.

Under "Advanced Settings" in the "Properties" for an SMPP connection, there is an "Single Connection/Transceiver" option to tell NowSMS to use a single "Transceiver" connection instead of one sender + one receiver.

To add additional connections to the same SMSC, you need to add the SMPP connection to the NowSMS "SMSC" list multiple times.

If you are doing more sending than receiving, you may want to define some connections for sending only.

When you do this, the additional connections to the same SMSC will appear in the NowSMS SMSC list with "#2" or "#3" ... etc ... following the SMPP host name.

NowSMS will send simultaneously over the multiple SMSC connections ... whether they be to the same provider, or whether they be to other providers.

--
Des
NowSMS Support
medium kuriboh
New member
Username: Mediumkuriboh

Post Number: 2
Registered: 04-2008
Posted on Tuesday, November 25, 2008 - 08:54 am:   

Thanks for your support, i have an additional question: usually if i wanted nowsms to use a specific route, i add for the connection routename=shortcode, then while posting to the webinterface i add the smcroute=shortcode, this way i will be using multiple connection "randomally", based on availability. Is this the right way to do it here, has this method any problem, and is there a better way to do it ?
By the way, i have only 1 bulk shortcode on the nowsms gateway.
thanks
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 256
Registered: 08-2008
Posted on Tuesday, November 25, 2008 - 05:46 pm:   

Hi,

When you define multiple connections to the same SMSC in this way, there will be multiple section headers in SMSGW.INI.

For example:

[SMPP - 1.2.3.4:5678]

[SMPP - 1.2.3.4#2:5678]

You can include the same "RouteName=" parameter for each of the connections to have them treated as the same logical route for an "&SMSCRoute=" match.

--
Des
NowSMS Support
medium kuriboh
New member
Username: Mediumkuriboh

Post Number: 3
Registered: 04-2008
Posted on Thursday, November 27, 2008 - 12:28 am:   

Thanks, i tried to bind 10 session like you mentioned it appears that there is only 4 sessions estabilished, and 6 refuse to do so. i found out about this by 2 ways: command prompt-->netstat -a, and wireshark trafic analyser, i stopped and started nowsms, i found out that only 4 sessions get a bind success, the 6 rest get bind failed... Could this be a normal behavior, or something wrong in my side, or it is just the provider giving me only 4 and saying otherwise ?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 268
Registered: 08-2008
Posted on Thursday, November 27, 2008 - 03:09 pm:   

It sounds like the provider is only giving you 4 sessions, unless maybe there is a typo in a username or password for one of the additional sessions. (This is somewhat normal, as it is quite unusual for a provider to allow that many sessions.)

The SMSOUT-yyyymmdd.LOG file should have some more information about the reason for the bind failure.

While you inquire with them about that, you may want to go back and try enabling SMPP async mode windowing, as that can have a significant performance impact if supported by the provider.

--
Des
NowSMS Suppport
medium kuriboh
New member
Username: Mediumkuriboh

Post Number: 5
Registered: 04-2008
Posted on Friday, November 28, 2008 - 06:28 pm:   

I checked the log file, and it appears that there is lot of these "bind failed" with "Unable to login to SMPP server with specified parameters", however the parameters are the same for all connections, more than this the connection will work sometimes (messages go using this connection), sometimes it shows the error above.
About the number of sessions, i think that i should address with my provider to solve the issue.
Using the asynchronous mode sounds like a good idea, what could be the best value to use for the window size ? (in my case it seems like a session give 7-8 msgs/sec, total 4 = 28 msgs/sec)

Thanks
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 275
Registered: 08-2008
Posted on Monday, December 01, 2008 - 05:02 pm:   

The error code is a generic login failure, so it is very likely that they are limiting the number of concurrent connections allowed.

For the window size, I generally recommend twice the desired number of messages per second.

Keep in mind that your provider might not support async windowing. Or that they may impose their own speed limits that could interfere with async mode.

The primary difference between normal mode and async mode is that NowSMS will queue up multiple message submissions (up to the specified window size) without waiting for an acknowledgment from the provider.

If your provider supports it, and allows the higher speed, then async mode is a much more effective use of bandwidth.

--
Des
NowSMS Support
medium kuriboh
New member
Username: Mediumkuriboh

Post Number: 6
Registered: 04-2008
Posted on Monday, December 01, 2008 - 06:46 pm:   

Thanks for your support
IAMIMDAD
New member
Username: Iasiddiqui

Post Number: 1
Registered: 01-2010
Posted on Tuesday, January 12, 2010 - 02:10 pm:   

Hi
Des NowSMS support
I am using nowsms version 2006.03.09 i am facing msg sending problem time to time can you please help me how to fix this in details we have a news subscription service and we daily send more then ten sending related to this but some time our Q size become big & nowsms application slow down in normal conidition its shows more then 250 msg post per second but when Q become big its shows 1 or 10 or 30 like that as i asked our service provider SMSC about our window size is 1 and no msg sending limit but i am still facing this problem can you please help me to solve this
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1658
Registered: 08-2008
Posted on Tuesday, January 12, 2010 - 04:12 pm:   

Hi,

You probably could benefit from an upgrade. There have been a lot of changes to NowSMS since 2006.03.09 to deal with larger queues.

In particular, there have been updates related to the use of separate user queues, and the way that NowSMS creates additional directories when a large number of messages have been submitted.

NowSMS 2006 did have support for separate outbound user queues. If you can change how you submit messages to submit using different user accounts, this may help.

Additionally, if you do not keep the NowSMS configuration window open, this may also help. There was an issue where the configuration program kept scanning the queues to report the queue size, and doing this would slow down queue processing.

--
Des
NowSMS Support



For more information on upgrading, please contact our sales people at http://www.nowsms.com/contact.htm.