Background Task Watcher

[Spencer Lambert]

No, not just provisioning.  It can happen when two NBI request happen within 15 seconds of each other; say set this data, then update that data.  The first set data is fine, the second is done on the next periodic inform.

Thanks,
Spence

> 
>     On March 31, 2017 at 8:10 AM Dan Morphis <dan at milkcarton.com> wrote:
> 
>     Does this happen on provisioning? None of my cpes do this throttling, but one easy way to solve this is set your periodic inform interval to 10 seconds during the setup process, and when the provisioned tag is added the inform interval is changed to 10 mins.
> 
>     -dan
> 
>         > > 
> >         On Mar 30, 2017, at 4:44 PM, Spencer Lambert <spence at isphelper.com> wrote:
> > 
> >         Some of my CPEs ignore Connection Requests if they come in too fast, like more than one in 15 seconds. I think it's a protection against attacks. Do any of you have this issue? It's frustrating because tasks end up sitting until the next periodic inform, which is usually hours.
> > 
> >         I've used some commercial ACS' and they have a background process that re-tires the CPE connection. After a first initial failed request to check in for tasks, every 30-60 seconds this background watcher will re-ask the CPE to check, giving up after five minutes or so.
> > 
> >         Would a background task watcher be useful to any of you?
> > 
> >         I've coded up a simple fix for my installation and I'm wondering if it would be worth working on a proper pull request.
> > 
> >         Thanks,
> >         Spence
> > 
> >         _______________________________________________
> >         Users mailing list
> >         Users at lists.genieacs.com
> >         http://lists.genieacs.com/mailman/listinfo/users
> > 
> >     > 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.genieacs.com/pipermail/users/attachments/20170331/e854600d/attachment.html>