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.
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 I
Alex, I'm not sure if you were that night on Barcelona with Alejandro,
Stipe, etc, but I asked him to ask you guys about DLR retries...
DLR retries don't look at all into http-request-retry and
http-queue-delay, or at least don't follow the expected behavior.
Instead, each DLR that failed to be po
Hi Juan,
as far as I see in source code, DLRs handled the same. So please try with those
2 config options.
Thanks,
Alexander Malysh
Am 25.02.2010 um 14:54 schrieb Juan Nin:
> Alex, I'm not sure if you were that night on Barcelona with Alejandro,
> Stipe, etc, but I asked him to ask you guys ab
Alex,
We have those parameters configured, and what Juan describes is what's actually
happening:
If you configure it to retry X times every 30 seconds, and the app handling the
DLR's doesn't answer, the DLR's are kept _in memory_ (not the store, so if you
shutdown smsbox you lose them) and whe
-Original Message-
> From: devel-boun...@kannel.org [mailto:devel-boun...@kannel.org] On Behalf Of
> Alejandro Guerrieri
> Sent: 25 February 2010 19:26
> To: Arkadiy Kulev
> Cc: kannel_dev_mailinglist Devel
> Subject: Re: Re[2]: reenable HTTP_MAX_RETRIES and HTTP_RETRY_DELAY
Hi!
Just wanted to know if there has been any further discussion on this
issue and if there are any plans regarding it on the roadmap.
Thanks in advance.
Juan
On Thu, Feb 25, 2010 at 1:42 PM, Alejandro Guerrieri
wrote:
> Alex,
>
> We have those parameters configured, and what Juan describes i
Title: Re[2]: reenable HTTP_MAX_RETRIES and HTTP_RETRY_DELAY for dlr-url
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
Hello Alejandro,
1. Can this be fixed? (only one in 30 seconds is not good).
2. Can you put DLRs in store just in case smsbox dies?
I suppose reliability in problem cases should be a issue here.
Thursday, February 25, 2010, 7:42:20 PM, you wrote:
> Alex,
> We have those parameters configu
ot;kannel_dev_mailinglist Devel"
> Sent: Thursday, February 25, 2010 7:26 PM
> Subject: Re: Re[2]: reenable HTTP_MAX_RETRIES and HTTP_RETRY_DELAY for
> dlr-url
> 1. I hope so! At this stage we're just researching if is this actually a bug
> or maybe some misconfiguration on our
architecture. A db storage for DLRs wouldn't help either, because
>>> DLRs are deleted (memory, db) as soon as they are matched in bb, so
>>> messages are kept in smsbox memory, not dlrs.
>>
>>> BR,
>>> Nikos
>>> ----- Original Message -
list Devel"
Sent: Thursday, February 25, 2010 7:26 PM
Subject: Re: Re[2]: reenable HTTP_MAX_RETRIES and HTTP_RETRY_DELAY for
dlr-url
1. I hope so! At this stage we're just researching if is this actually a bug
or maybe some misconfiguration on our side. If it proves to be a bug I'
oon as they are matched in bb, so messages
> are kept in smsbox memory, not dlrs.
>
> BR,
> Nikos
> - Original Message - From: "Alejandro Guerrieri"
>
> To: "Arkadiy Kulev"
> Cc: "kannel_dev_mailinglist Devel"
> Sent: Thursda
t help either, because
>> DLRs are deleted (memory, db) as soon as they are matched in bb, so
>> messages are kept in smsbox memory, not dlrs.
>
>> BR,
>> Nikos
>> - Original Message -
>> From: "Alejandro Guerrieri"
>> To: "Arkad
-
From: "Arkadiy Kulev"
To: "Alejandro Guerrieri"
Cc: "Nikos Balkanas" ;
Sent: Friday, February 26, 2010 9:43 AM
Subject: Re[6]: reenable HTTP_MAX_RETRIES and HTTP_RETRY_DELAY for dlr-url
Hello Alejandro,
smsblox.log is overloaded with too much information,
; "Alejandro Guerrieri"
Cc:
Sent: Friday, February 26, 2010 10:14 AM
Subject: Re: Re[6]: reenable HTTP_MAX_RETRIES and HTTP_RETRY_DELAY for
dlr-url
Hi,
Yes, I could add this option to custom logs, but it would never make it to
CVS if a better persistent solution is in the works.
dev_mailinglist Devel
Subject: Re: Re[2]: reenable HTTP_MAX_RETRIES and HTTP_RETRY_DELAY for dlr-url
1. I hope so! At this stage we're just researching if is this actually a bug or
maybe some misconfiguration on our side. If it proves to be a bug I'll try to
fix it of course.
2. Afaik,
Hi,
Another possible solution could come in the form of a trigger or
store_procedure, if you store your DLRs in a RDBMS, to catch a delete
and insert a new record with the DLR status in another table.
Just a thought.
Kind regards, Javier
18 matches
Mail list logo
