Non Polling API net failure

Home › Forums › iSMS › Non Polling API net failure

Tagged: 

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • May 23, 2011 at 2:16 pm #2568
    Campbell Elder
    Participant

    How does the iSMS deal with a recipient net server failure used for the NON-Polling API solution?

    Is the SMS stored and re-queued?

    In event of the recipient server being unavailable before the iSMS reaches memory capacity will the iSMS stop receiving untill it can deliver the SMS?

    May 23, 2011 at 2:59 pm #3170
    Jeff Blees
    Blocked

    Upon receipt of the SMS from the wireless cloud, this iSMS server will try 3 times in a row to POST the message to the server. If the POST attempts are unsuccessful, the message will be placed into the Receive API Failure log and is not be re-sent / re-queued. The message is also placed in the Inbox and Received SMS trace log. The originator will have to resend once the net server is back up or the net server administrator will have to manually review the iSMS server to learn what messages came in while the net server was down.

    The Polling method of Receive API was implemented to address this concern.

    Sincerely

    Jeff

  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.