Retry pending error

Retry pending error SearchSearch
Author Message
David Carlson
New member
Username: Kannel

Post Number: 17
Registered: 06-2016
Posted on Friday, March 24, 2017 - 11:13 am:   

I got the following error from smsout log.

nowsms version
gateway 2016.3.28
apk 2016.3.28

Retry Pending - HTTPSMSC: Unable to connect to server nowsmsmodem_x.x.x.x:80


Pls tell me what's happen and how to avoid.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5809
Registered: 08-2008
Posted on Friday, March 24, 2017 - 11:29 am:   

Is this affecting all messages or only a specific message? If all, does stop/start on the app bring it back? If yes, try leaving the app active on the display.

How is the modem defined in NowSMS....by name or by IP? Based on the error message, it looks like by IP....so I assume static IP....verify you don't have a configuration error with a changed IP. Try pinging the IP.

--
Des
NowSMS Support
David Carlson
New member
Username: Kannel

Post Number: 18
Registered: 06-2016
Posted on Friday, March 24, 2017 - 11:48 am:   

it affects all messages.

modem name defined is IP address
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5810
Registered: 08-2008
Posted on Friday, March 24, 2017 - 12:50 pm:   

OK...do you have any feedback on my other questions?

Since you are connecting based on IP address...I assume you have a static IP configured? How? I assume in DHCP server? Verify you don't have a configuration error with a changed IP. Try pinging the IP.

It is generally better to configure the modem connection by name, so that you do not have to be concerned with DHCP and IP addresses.

--
Des
NowSMS Support
David Carlson
New member
Username: Kannel

Post Number: 19
Registered: 06-2016
Posted on Saturday, March 25, 2017 - 04:37 am:   

Is there any difference between these two errors below?

1. Retry Pending - HTTPSMSC: Unable to connect to NowSMS modem x.x.x.x

2. Retry Pending - HTTPSMSC: Unable to connect to server nowsmsmodem_x.x.x.x:80


for above 1st error, it will happen when gateway lose connection to mobile.

for above 2nd error, I have never seen before until I switch to android 6 mobile instead of android 5 mobile
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 8166
Registered: 10-2002
Posted on Wednesday, March 29, 2017 - 03:05 am:   

Hi David,

Sorry for the delay in response. We needed to confirm the exact difference with engineering.

Basically, there is no difference...it is just timing of when the error is detected.

Every x minutes (varies between 3 and 10 minutes depending on the version), NowSMS checks to see if it can communicate with the modem. Error 1 is reported here.

In between these checks, if there is a message to be sent out, and NowSMS cannot communicate with the modem, Error 2 is reported.

You might want to try lowering the check interval to see if this helps keep the device on line, try ModemAppCheckInterval=90 (value is seconds) under the [SMSGW] section of SMSGW.INI.

We are currently putting the final touches on a new release which will add another configuration option, where the device can initiate and maintain a persistent connection to the server. This update is expected in the next 2-3 weeks.

-bn

Bryce Norwood
Now SMS/MMS Support
David Carlson
New member
Username: Kannel

Post Number: 20
Registered: 06-2016
Posted on Friday, March 31, 2017 - 10:17 am:   

I find out the reason for retrying error on android 6 - samgung

When screen is going to sleep , wifi will be stopped automatically that causing gateway disconnected to apps. disconnected duration is ranging from 5 mins to 30 mins.

android 5 is no such problem.

Pls advise how to avoid this problem
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5814
Registered: 08-2008
Posted on Friday, March 31, 2017 - 02:33 pm:   

Hi David,

Assuming the device is connected to power, the app tells the device to keep the screen on, as this is a common issue with many devices.

Look at your SMSGW.INI file and make sure that in the [NowSMSModem - name] section that there is not a setting to turn the screen off.

--
Des
NowSMS Support
David Carlson
New member
Username: Kannel

Post Number: 21
Registered: 06-2016
Posted on Monday, April 03, 2017 - 08:25 am:   

In smsgw.ini, no setting related to the screen off. Actually, I don't know how to set it.

when screen is off , wifi is still active for android 5, but not for android 6.

I don't have to set power saving mode. How to keep wifi alive all the time?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5817
Registered: 08-2008
Posted on Wednesday, April 12, 2017 - 03:20 am:   

Hi David,

Sorry again for the lengthy delay in response. We were expecting an update to be made available last week, but it took a few extra days.

The problem you are describing is not Android version specific, but rather device+version specific. Not all Android devices turn off WiFi when the screen is off (the app explicitly asks for WiFi to stay on full power). And not all Android 6 devices ignore the app's request to keep the screen on.

That said, I think you'll get better results from the updated app that was posted to https://www.nowsms.com/apk this week.

There are multiple Android APIs for an app to keep power to the screen. Previous versions used an API that keeps the screen on, but dim. That API has been deprecated (no longer supported) by Google, but most devices still support it anyway, including Android 7.x on the Google Pixel and Nexus 5X.

The new version of the app uses this and another API to keep the screen on. Note that this other API only keeps the screen on if the NowSMS Modem app is the foreground app.

There is also a new version of the NowSMS server which, combined with the new app, also supports device initiated connections that can use either WiFi or cellular data.

--
Des
NowSMS Support

Add Your Message Here, or click here to start a new topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Options: Automatically activate URLs in message
Action: