issue with certain devices not registering after reboot

[Diego Garcia del Rio]

Thanks! If the spec calls for an empty message, I'll check back with the
manufacturer about this.

Disregard my second comment... Indeed, if the spec calls for this, then
GenieACS behavior is correct.

I'll look into more detail to see what's different for the device in theses
different behaviors.


Cheers,
Diego



On Wed, Jan 31, 2018 at 6:11 PM, Zaid Abdulla <zaid at genieacs.com> wrote:

> On Wed, 2018-01-31 at 17:35 -0300, Diego Garcia del Rio wrote:
> > Is a subsequent response from the device missing? I'm having a hard
> > time following the TR69 spec to know if this is cleanly closed or
> > not. Or is it only that the connection should be closed from their
> > side instead of timing out.
>
> Yes. After InformResponse the device should send an RPC request or an
> empty message. It's possible that the device is actually sending a
> request but not properly including the cookie header required for
> session identification. However I doubt that is the case because as you
> previously stated it normally works fine.
>
> > Also, even if the connection is timing out, shouldn't GenieACS commit
> > the received info to the DB?
>
> As per the spec, changes in a given session should only be comitted if
> the session is successfully terminated.
>
> --
> Zaid Abdulla <zaid at genieacs.com>
> _______________________________________________
> 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/20180131/88e646be/attachment.html>