Hello Alexander,
Oh thanks. One more thing - what is considered a non-failing request? A request that returns 200 OK?
Or any other?
Would be cool, if a user could also configure kannel to search for a specific keyword inside the server's reply.
Something like "OKDONE", that would tell kannel that the script ran OK.
Sometimes the server can return 200 OK even if PHP is dead, kannel would think that the request went through,
but actually it didn't.
Thursday, February 25, 2010, 12:43:43 PM, you wrote:
|
> |
Hi Arkadiy, why don't you read userguide? http-request-retry integer If set, specifies how many retries should be performed for failing HTTP requests of sms-services. Defaults to 0, which means no retries should be performed and hence no HTTP request queuing is done. http-queue-delay integer If set, specifies how many seconds should pass within the HTTP queuing thread for retrying a failed HTTP request. Defaults to 10 sec. and is only obeyed if http-request-retry is set to a non-zero value. Thanks, Alexander Malysh Am 25.02.2010 um 10:26 schrieb Arkadiy Kulev: Hello Guys, I am wondering, why are HTTP_MAX_RETRIES and HTTP_RETRY_DELAY disabled in gw/smsbox.c? For instance, I use dlr-url to keep track of my deliveries (the url itself has an internal ID of the message that I use in my software). What if my HTTP server goes down? I loose the notification. The access.log doesn't show the dlr-url, so I can't understand which of the messages correspond to which message ids in my software. It would be cool, if I could configure kannel to keep resending the DLR to my HTTP server every N seconds for Y times (or maybe forever), until it gets through. So why is it disabled? Arkadiy Kulev mailto:[email protected] +7 495 5070602 Moscow, Russia |
Arkadiy Kulev mailto:[email protected]
+7 495 5070602
Moscow, Russia
