[reSIProcate] DUM ClientSubscription WaitForNotify timer

[Scott Godin]

It's not that clear to me what you are asking for.  Are you asking to have
a configuration setting for the duration of WaitForNotify timer?

Please note that sending an initial notify is a requirement of RFC3265 - it
is illegal for that NOTIFY to be missing.  I assume you want this in order
to be able to handle a misbehaving endpoint that fails to send the initial
NOTIFY?

Scott

On Fri, Nov 21, 2014 at 6:26 AM, palladin <p-aladin at yandex.ru> wrote:

> Dear resip devels,
> resiprocate 1.9.2
>
> please consider next piece of ClientSubscription.cxx:167
>
> mDum.addTimer(DumTimeout::WaitForNotify,
>                  64*Timer::T1,
>                  getBaseHandle(),
>                  ++mTimerSeq);
>
> Now rutil/Timer.hxx
>
> // These values can be changed but it is not recommended to do so after a
>       // stack is up and running since they are not mutexed
>       // These times are all in ms
>       static unsigned long T1;
>       static unsigned long T2;
>       static unsigned long T4;
>       static unsigned long T100;
>
> I this place ClientSubscription schedules WaitForNotify timer for ~9 hours
> instead of 32 seconds. Could you please improve this place?
>
> Sincerely, Taras
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20141121/25a3d28a/attachment.htm>