MultiTech Developer Resources » Topic: Non-Polling Received – Timed Out

Non-Polling Received – Timed Out

This topic has 1 reply, 2 voices, and was last updated 10 years, 12 months ago by Bryon Davis.

Viewing 2 posts - 1 through 2 (of 2 total)

Author

Posts
May 1, 2014 at 7:24 am #5754

Kirk Bennett
Participant

Why do the logs show a “Timed out” message when it isn’t timing out?

May 1 07:09:09 boa: recvlivelog: Non-polling message [index: 1]: 07:09:04, 14/05/01
May 1 07:09:40 boa: recvlivelog: NON-POLLING RECEIVE API: No response from server , Timed out.
May 1 07:09:40 boa: recvlivelog: Non-Polling delivery response from server: HTTP/1.1 200 OK
May 1 07:09:40 boa: recvlivelog: Non-Polling Receive API Delivery was successful.

May 5, 2014 at 9:14 am #5759

Bryon Davis
Moderator

Hi Kirk,
There was a bug in the v1.50.7 firmware where sometimes the HTTP 200 OK wasn’t recognized and the response was flagged as timing out. This has been fixed in the newer firmware.

The latest firmware is v1.51.25, which can be found at the links below:

SF100:
https://webfiles.multitech.com/engineering/unofficial-releases/iSMS%20(Formerly%20SMSFinder)/Firmware/SF100/1.51.25/SF100-u-v1.51.25-13Jan2014.zip

SF400 and SF800:
https://webfiles.multitech.com/engineering/unofficial-releases/iSMS%20(Formerly%20SMSFinder)/Firmware/SF400_SF800/1.51.25/SF400-800-u-v1.51.25-13Jan2014.zip

Regards,
Bryon
Author

Posts

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.