Presets vs Tasks to set per CPE attribute

[Zaid Abdulla]

On Sat, Sep 19, 2015, at 04:39 PM, Agustín Bertamoni wrote:
> Hi all, For SIP services some IGD tree values and attributes must be
> per CPE (like SIP.AuthUserName) and the rest of values are global.
> Specifically for per CPE attributes, if use presets must create a
> preset entry per each CPE. Isn't it?  the question is, if can use task
> to set specific attributes? and can create this scheduled task even
> before the first device hit? BR

You should never use per CPE presets as that doesn't scale. And you
can't queue individual tasks before the device is registered because the
task queue is cleared whenever there's a bootstrap event (e.g. when the
device contacts the ACS for the first time).

The way I work around this limitation is by patching the back end to
support "dynamic" values in presets. Though you may not want to go
through that route because you'll have to rebase your changes whenever
there's an upstream update. A more elegant solution is coming in a
future release.

Alternatively, you could have an external process that pushes tasks
whenever a new device contacts the ACS. That can either be a cron job
that queries the devices on _lastBootstrap field periodically; or you
use Dan's fork in which he implemented some kind of notification
mechanism (https://github.com/akcoder/genieacs/). He described how it
works a while ago so you can search the mailing list if you want to use
that approach: http://dir.gmane.org/gmane.network.genieacs.user

Zaid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.genieacs.com/pipermail/users/attachments/20150920/397813a2/attachment.html>