Question concerning a time window to forbid sending SMS

Question concerning a time window to forbid sending SMS SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through May 19, 2016 » Question concerning a time window to forbid sending SMS « Previous || Next »
Author Message
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5540
Registered: 08-2008
Posted on Tuesday, December 15, 2015 - 03:41 pm:   

From the support mailbox:


quote:

Hi xxxxx,

I hope you are well.
We are currently in the final stages of the project for xxxxxxxx and I would have a question for you regarding the hours to send SMS to the Provider.

I believe that you had implemented a feature on NowSMS to forbid NowSMS to send SMS to the provider during time window to be defined by the NowSMS Administrator. Am I right?
I can’t find on my version of NowSMS the location to configure this feature. Could you update my memory and tell me where I can configure this.

Thanks for your help.




Settings exist, but are well hidden.

The following settings exist in version 2014-05-11 and later:

* SMS Gateway: Add configuration settings to disable message traffic for all or selected SMSC connections during "quiet hours". QuietHourStart specifies the hour during which the quiet period should start and QuietHourEnd specifies the hour at which the quiet period ends. Hours are expressed in 24 hour format. For example QuietHourStart=14 and QuietHourEnd=16 means no messages will be sent between 14:00 (2:00pm) and 15:59 (3:59pm). QuietHourStart=20 and QuietHourEnd=8 means no messages will be sent between 20:00 (8:00pm) and 7:59 (7:59am). These settings can be added in the [SMSGW] section of SMSGW.INI to apply to all connections, or in an SMSC specific section to apply to a specific connection only.
rhandour saber
New member
Username: Rhandoursaber

Post Number: 1
Registered: 12-2015
Posted on Thursday, December 31, 2015 - 02:24 pm:   

Hi,
i have nossms 2015 installed and 2 android phones configured (by ip adress) , i'm using a php script to send sms using the nowsms, when i send multiple Sms simultaneously, i notice that nowsms use the two routes but it takes about one minute per message
is there any option to change to make it faster ?
thanks for your help
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5546
Registered: 08-2008
Posted on Thursday, December 31, 2015 - 04:15 pm:   

Hi,

Did you download NowSMS from this website, or from another site?

Is this a trial version or a purchased license?

The symptom of NowSMS sending only 1 message per minute is usually the result of an invalid serial number.

Make sure you have not installed one of the various license cracks that float around the internet. Or if you downloaded NowSMS from a web site other than ours, it might have even been included in the install.

If you are encountering this problem, I would suggest going to the "Serial #" page of the configuration dialog, and removing any listed serial numbers. A trial installation will not show any serial numbers in the list. If you remove a serial number, restart the service to get it back to trial mode.

If NowSMS was download from another web site, it may also be necessary to uninstall and reinstall using the version at http://www.nowsms.com/download-free-trial

--
Des
NowSMS Support
rhandour saber
New member
Username: Rhandoursaber

Post Number: 2
Registered: 12-2015
Posted on Monday, January 04, 2016 - 06:51 am:   

Hi,
Thank you for your support, actually i downloaded the soft from another website and it had a serial included already. i ll remove it and will use the trial version.
is the trial version a complete or limited version ?
because if it work for me i ll have to purchase a licence after the test
thanks again
Edmund
New member
Username: Edmund

Post Number: 3
Registered: 12-2015
Posted on Monday, January 04, 2016 - 08:28 am:   

Hi Des,

I am facing a similar issue regarding sms in delay. NowSMS only processes the 1st sms it receives in real-time, with the rest executed in batches in the following minute.

I am using the trial version downloaded from your website, with an android phone acting as modem. I tried using another phone but it didnt' solve the issue. Any idea why?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5547
Registered: 08-2008
Posted on Monday, January 04, 2016 - 04:51 pm:   

Hi rhandour,

The trial version is fully functional, it is just limited to 30 days of use. (Manually stop the services when not using it if you need to take a break during the trial period.)

The trial does have a maximum throughput of approximately 30 messages per minute (which is a speed you are unlikely able to reach with a single modem).

--
Des
NowSMS Support



==

Hi Edmund,

Please check the Serial # page. Make sure there are no serial #'s listed.

There are rogue internet sites that bootleg our software, and they preload invalid serial numbers which have a 1 message per minute limitation.

If you are encountering this problem, I would suggest going to the "Serial #" page of the configuration dialog, and removing any listed serial numbers. A trial installation will not show any serial numbers in the list. If you remove a serial number, restart the service to get it back to trial mode.

If NowSMS was download from another web site, it may also be necessary to uninstall and reinstall using the version at http://www.nowsms.com/download-free-trial

--
Des
NowSMS Support
rhandour saber
New member
Username: Rhandoursaber

Post Number: 3
Registered: 12-2015
Posted on Tuesday, February 16, 2016 - 09:37 am:   

hi Des
i have downloaded the trial version and tested it.
i used 3 android phones for a massive sms sending. the problem is i have received only from 2 phones and nothing from the third one.
is there any limites of the connected phones or a specific configuration to use all the phones.
i have to be sure before the acquisition.
best regards
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5568
Registered: 08-2008
Posted on Wednesday, February 17, 2016 - 04:21 pm:   

Hi,

The first thing I'd suggest is to try sending a test message via that 3rd modem to make sure it is working. In NowSMS, go to the SMSC list, highlight the modem and press the Test button, which will allow you to send a test SMS or MMS via that modem.

If the test works, but outbound messages are only using the other two modems, go to the Properties button for that modem and make sure that "Support any outbound message traffic" is checked...that means the modem is eligible to send messages.

--
Des
NowSMS Support
rhandour saber
New member
Username: Rhandoursaber

Post Number: 4
Registered: 12-2015
Posted on Wednesday, February 17, 2016 - 04:48 pm:   

Hi,
i have sent a test message and it worked, i ll check this option "Support any outbound message traffic" if it is checked or not.
i ll let you know if something go wrong
thank you for your support
rhandour saber
New member
Username: Rhandoursaber

Post Number: 5
Registered: 12-2015
Posted on Tuesday, March 01, 2016 - 03:35 pm:   

hi,
i have now three routes in the NOWSMS:
the first one is a modem (FCT-333)connect directly to the COM port, for the two others i used 2 android phones connected with wifi to the same local network.
i started the sending test with 13 shorts SMS , i have received equaly from every route and it was verry quick, but when i did the same test with a long SMS (the sms is devided in 3 parts) it took more than 10 minute to receive only 10 SMS , 9 from the Modem route, one from an android phone and nothing from the other one.
any help please.
best regards
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5587
Registered: 08-2008
Posted on Tuesday, March 01, 2016 - 07:29 pm:   

Hi,

Can I see the timing for the sending out from SMSOUT-yyyymmdd.LOG? (For both the short and long tests.)

The log would also show me the routes selected, so that I have a better understanding.

There is some difference in how long messages are processed with a conventional GSM modem, but I am very surprised 9/10 went that route.

--
Des
NowSMS Support
rhandour saber
New member
Username: Rhandoursaber

Post Number: 6
Registered: 12-2015
Posted on Wednesday, March 02, 2016 - 08:50 am:   

hi,
i have attached the log file you requested
best regards
application/octet-stream
SMSOUT-20160301.LOG (34.7 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5590
Registered: 08-2008
Posted on Wednesday, March 02, 2016 - 07:12 pm:   

Hi,

I think there is a character set problem.

Your short message is fine:

*** Léon Profs *** Léon Africain : A M. ACHEHBOUNE - Rappel Conseils de classe Mardi 8 mars : 6-1 à 16h, 6-2 à 17h et 6-3 à 18h.

But the long message contains Chinese characters, which are likely confusing the Android device. The first part of the long message is:

L鯮 l'Africain - Aux parents de GHITA : Les r鳵ltats du conseil de classe du 1e trimestre sont actuellement consultables sur l'Extranet L鯮 l'Africain - Aux parents de GHITA :


How are you submitting the message to NowSMS? If you are using our web form, it should work. If you are creating your own HTTP request, by default, NowSMS expects the text encoded with utf-8. I suspect the long message text was encoded with iso-8859-1...adding &charset=iso-8859-1 to the URL would tell NowSMS which character set is being used.

--
Des
NowSMS Support
rhandour saber
New member
Username: Rhandoursaber

Post Number: 7
Registered: 12-2015
Posted on Thursday, March 03, 2016 - 04:16 pm:   

hi,
i m using a php script to send to nowsms and i found out that there was a problem with the encription, the text wasn't encoded with utf-8, i did another test without using any special character and the result is the same i have received only from the modem this time, in the log file it said that there was a problem to reach the 2 routes (2 phones connected with wifi) but when i ping the adresses at the exact same time i'm sending the SMS the ping goes well. after that i sent 2 SMS directly from the interface of nowsms, it worked
i attached the log file and a screen shot of the ping

best regards
Saber
application/octet-stream
SMSOUT-20160303.LOG (14.5 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5591
Registered: 08-2008
Posted on Thursday, March 03, 2016 - 06:21 pm:   

Hi,

There is no need to run ping tests.

The 503 error code means that NowSMS can connect to the phone, but the phone is failing to send the SMS.

The character encoding looks fine this time, so there is not an obvious problem.

Here are my suggestions and questions:

1. Send the same text using the web form in the NowSMS web interface.



As long as "Display message route selection" is enabled, you will have the option to choose which modem to use for your test messages, which will make testing easier.

2. Are the Android phones connected to the same operator as the modem?

3. Use the built-in Android messages client and try to send the same long text. Does that work?

--
Des
NowSMS Support
rhandour saber
New member
Username: Rhandoursaber

Post Number: 8
Registered: 12-2015
Posted on Friday, March 04, 2016 - 08:41 am:   

Hi,
i sent the same text using the web interface and i sent from the 2 routes, it worked without any problem when i send to only one user but when i sent to a distribution list that contain 3 users, i got the same error code "503" (see the log file attached).
to answer to your question, yes the android phones are connected to the same operator as the modem.
application/octet-stream
SMSOUT-20160304.LOG (3.6 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5593
Registered: 08-2008
Posted on Friday, March 04, 2016 - 03:43 pm:   

Hmm...NowSMS always sends SMS one-at-a-time, so the number of recipients should not matter. If you submit another long message to a single recipient does it get sent?

I'm almost out of ideas..

The next step is to get an idea of what the underlying failure code is, so please enable the SMSDEBUG.LOG. There should be a log of an HTTP transaction with the device. I am specifically interested in details of the HTTP response from the device, which is reporting this as a 503 error. A normal response looks like this:

18:57:07:597 [18] ThreadProcessModem: HTTP/1.1 200 OK
X-NowSMS-DeviceID: xxxxxxxxxx
X-NowSMS-DeviceName: yyyyyyyy
Content-Type: text/html
Date: Wed, 4 Mar 2016 23:57:08 GMT+00:00
Content-Length: 71
Connection: close

<html><head></head><body><p>OK,Recipient=zzzzzzzzzzz</p></body></html>

The 503 response should have an additional error code in the HTML section of the response. What do you see?

BTW, make su=re you have the 2015.08.07 version of the Android app, at the bottom of http://www.nowsms.com/download-free-trial, as it includes more debug info.

Do you see similar problems if you try sending long messages via the built-in messaging app? (Test sending to 1 recipient at a time, otherwise that app may use MMS instead.)

What is the device and version of Android?

From some internet searching, it seems some people are having this type of problem with some Samsung devices on 4.4.x Android versions, and it can be recreated using the built-in messaging app, suggesting it is a system level bug.

If this is the case, check to see if there is an Android app available for the device. If there is not, the only work-around (other than a firmware update) we could potentially explore would be to divide the message and send the parts separately. But then the receiver would not see a single long message.

Do you have another Android device (different model) you can try?

--
Des
NowSMS Support

Login Login / Register Logout Logout Search Last 30 Days Topics Topics