Thanks Zaid, 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.
Also, even if the connection is timing out, shouldn't GenieACS commit the received info to the DB? Just wondering. thanks in advance, On Wed, Jan 31, 2018 at 4:40 PM, Zaid Abdulla <[email protected]> wrote: > On Mon, 2018-01-29 at 23:38 -0300, Diego Garcia del Rio wrote: > > 2018-01-30T02:22:35.693Z [INFO] 186.182.172.218 F4068D-PLC%201200- > > F4068DA36F5A: Inform; cpeRequestId="818014743" informEvent="1 BOOT" > > informRetryCount=0 > > 2018-01-30T02:23:06.728Z [ERROR] 186.182.172.218 F4068D-PLC%201200- > > F4068DA36F5A: Session timeout; sessionTimestamp=1517278955668 > > > > And the device's "last seen" time does not update on the DB > > > > Somwhere on the list it was mentioned that the changes are not > > written to the DB in case of a timeout, so that explains why im not > > seeing the device updated. But any clue why the connection might not > > be closing and instead timing out? . > > I don't know if there's anything you can do other than get a Wireshark > or tcpdump capture and report it to the device manufacturer. > > -- > Zaid Abdulla <[email protected]> > _______________________________________________ > Users mailing list > [email protected] > http://lists.genieacs.com/mailman/listinfo/users >
_______________________________________________ Users mailing list [email protected] http://lists.genieacs.com/mailman/listinfo/users
