Invalid Session" Errors, URL Decoding, and Time Discrepancies

1

Hello
I am currently experiencing three issues with my GenieACS setup and would appreciate any assistance or guidance:

Issue 1: Invalid Session Errors

I am frequently seeing “Invalid session” errors in the ACS logs, despite the device appearing to register correctly:

2024-07-15T06:45:34.724Z [INFO] 41.xx.xx.xx 000789-X31-00%3A07%3A89%3A83%3A8C%3A46: Inform; cpeRequestId="3" informEvent="0 BOOTSTRAP" informRetryCount=2
2024-07-15T06:45:34.809Z [ERROR] 41.xx.xx.xx 000789-X31-00%3A07%3A89%3A83%3A8C%3A46: Invalid session
2024-07-15T06:45:34.815Z [INFO] 41.xx.xx.xx 000789-X31-00%3A07%3A89%3A83%3A8C%3A46: New device registered
2024-07-15T06:45:35.559Z [ERROR] 41.xx.xx.xx: Invalid session
2024-07-15T06:45:36.301Z [ERROR] 41.xx.xx.xx: Invalid session

Issue 2: URL Decoding of Device ID

The device IDs are URL-encoded when sent to the ACS and need to be correctly decoded. For example:

  • Encoded Device ID: 000789-X31-00%3A07%3A89%3A83%3A8C%3A46
  • Decoded Device ID: 000789-X31-00:07:89:83:8C:46

Issue 3: Time Discrepancies

There is a discrepancy between the timestamps stored by the device in ACS and the timestamps of the error codes. This might be contributing to the “Invalid session” errors.

Request for Assistance

  1. Invalid Session Handling:

    • What steps can I take to ensure that session handling is correctly managed?
    • Are there specific configurations or best practices that can help resolve these “Invalid session” errors?

  2. URL Decoding Confirmation:

    • Is there a recommended way to ensure the device ID is correctly decoded and stored in ACS?

  3. Time Discrepancy Resolution:

    • How can I ensure that the time stored by the device and the ACS logs are synchronized to avoid session-related errors?

I appreciate any guidance or suggestions from the community on how to address these issues.

GenieACS v1.2.13+240606fc80

Thank you!

Best regards,
Muhammad

2

After all i found out that the devices are not updating timedate

this is clearly stated in the https POST request to CWMP server.
<CurrentTime>1970-01-01T09:01:05+09:00</CurrentTime>

any way i could update the time with GenieACS ?
As NTP seems to fail on all these devices.

3

Unless the device is using a vendor extension; or not following the spec; then the answer is no.
Time.CurrentLocalTime is marked as read only in both the TR-069 and TR-181 specs.

You should reach out to your vendor to resovle why NTP isn’t working.

1 Like
4

Thank you for clarification

it is too complicated.
simply i am trying to setup my own ACS to change devices firmware with my custom one.

so vendor will not be happy

i will use another method if TR-069 is too complicated.

Thanks.