Non Polling Receive – Multiple calls to page for same message

[Todd McFarlane-Smith]

Hi,

I am implementing a service with the SMS server that will execute an ASP page when it receives an SMS. It seems that the ASP page is called many times at periodic intervals, even though the ASP page receives and processes the message.

I have tried to clear the Inbox, but the ASP page is still executed repeatedly for the same message. I have tried to restart the SMS server, but the same thing happens. In fact, after restart the same message is processed again repeatedly. Is there a cache that should be cleared?

Is there something I am missing here? As far as I know I am executing the code correctly.

Thanks.

Todd

[Todd McFarlane-Smith]

Hi,

Please ignore this post. I have found an error in my ASP page that gets called by the SMS server. If the ASP page errors, the SMS server continues to re-process until the error is fixed.

Thanks.

Todd

[Bryon Davis]

Hi Todd,

Glad you were able to fix the problem. If the Non-polling Receive API message wasn’t sent successfully then the iSMS will resend it repeatedly. Clearing the Inbox should’ve cleared this though.

Regards,

Bryon

[Edmundo Sanchez]

Please Help

I configure Non Polling with my test server and it works, but when i configure isms to send post message to my production server, it does not work.

Both servers responds with HTTP/1.1 200 OK.

Both says: NON-POLLING RECEIVE API DELIVERY FAILED: Error reading response from server.

But with the test server, says after the past error: Delivery Successfull, but with my production server says:

recvlivelog: HTTP NON-POLLING RECEIVE API DELIVERY FAILED: Failed to connect to server.

recvlivelog: Non-Polling Post Failed to Send. Will try again later

Both servers proceses the message, the difference is that isms continue sending the message with my production server.

Any help would be apreciate.

Sorry for my english

Edmundo

[Bryon Davis]

Hi Todd,

Please try the v1.51.14 firmware. There is a known issue in 1.50.7 where successful Non-polling HTTP deliveries are sometimes detected as failures, so they get resent.

SF100 v1.51.14:

https://webfiles.multitech.com/engineering/unofficial-releases/iSMS%20(Formerly%20SMSFinder)/Firmware/SF100/1.51.14/SF100-u-v1.51.14-02Apr2013.bin.zip

SF400 and SF800 v1.51.14:

https://webfiles.multitech.com/engineering/unofficial-releases/iSMS%20(Formerly%20SMSFinder)/Firmware/SF400_SF800/1.51.14/SF400-800-u-v1.51.14-02Apr2013.bin.zip

Regards,

Bryon

[Rob Watkins]

Hi, I am getting the same problem with an SF100-G-GB/IE and 1.50.7 firmware; response is HTTP/1.1 200 OK, but every time I get this in the log:

May 15 14:52:24 boa: recvfaillog: NON-POLLING RECEIVE API: Error reading response from server.

…and all messages are constantly resent (which obviously builds up pretty quickly!)

The link above to SF100 v1.51.14 firmware doesn’t work, but if I browse the FTP files I see I just need to remove the .bin – also there are newer releases though – which one is right for me – bearing in mind this other problem I am having: http://www.multitech.net/developer/forums/topic/receiving-messages-with-line-breaks/

Thanks,
Rob

• This reply was modified 10 years ago by Rob Watkins.

[Bryon Davis]

Please use v1.51.25 instead of v1.51.14, it has the non-polling fix as well as other fixes. See the readme file for more information on the changes.

SF100 v1.51.25
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 v1.51.25
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

[Author]

Posts