Possible Issue with ONVIF Test Tool 25.06 – Test Case DEVICE-3-1-7-v21.06 SYSTEM COMMAND FACTORY DEFAULT SOFT

[Queenie-vvtk]

Dear ONVIF Team,

When running Test Tool 25.06 on our camera with test case DEVICE-3-1-7 (Factory Default Soft), we observed inconsistent behavior compared with Test Tool 24.12:

25.06 behavior: After the camera reboots, a Hello message is sent. The next ProbeMatch is only seen ~44 seconds later. With the default reboot_timeout = 128000 ms, the test fails. If we extend the timeout to 188000 ms, the test passes.

24.12 behavior: After reboot, the ProbeMatch arrives about 1.5 seconds after Hello, so the test passes with the default timeout.

The camera behavior itself is consistent across both versions. The difference seems to come from Test Tool 25.06 handling of multicast Probe/ProbeMatch timing.

Could you please confirm if this change is intended or if it is a regression in 25.06?

SetSystemFactoryDefault.zip

[madhurao68]

Hi
We are investigating the issue and revert back shortly. Thanks for your patience and understanding!

[Queenie-vvtk]

Hi,

Thank you for the update.
We appreciate your support in looking into this.
Please let us know if any additional logs, packet captures, or test details from our side would be helpful for your investigation.

We look forward to your feedback.

Best regards,
Queenie

[SergeyGRSE]

Hello,
The main difference between these two versions is a migration to NET.Core. So some basic functionality works a bit different now. The early version uses Thread.Abort + Thread.Join to cancel the operation with a timeout, now this shorten to cts.Cancel() thread.Join() (sorry for technical details) but finally this lead to the fact that current execution cancelation is faster. Reboot time is 128 sec and 8 sec to wait for Discovery hello so in total it is 136, the 24.12 has some additional delay in Thread.Abort so it give time to receive the hello. Now timeout calculation starts early and 128 sec is not enough. I think if you can set timeout to 145 - 146 sec - this should be enough. Could you try this?

[Queenie-vvtk]

Hello,

Thank you for the detailed explanation regarding the migration to .NET Core and the updated timeout behavior.

We re-ran the test with Test Tool 25.06 and obtained the following results:

reboot_timeout = 128000 ms → FAIL
reboot_timeout = 146000 ms → FAIL
reboot_timeout = 147000 ms → PASS

We also verified the behavior with Test Tool 25.12 and observed the same timing characteristics and pass/fail boundary.

It appears that the minimum timeout required for our device to pass DEVICE-3-1-7 (Factory Default Soft) is approximately 147 seconds under both 25.06 and 25.12.

Based on your explanation, we understand that the timeout calculation now starts earlier compared to 24.12, which explains the difference in behavior. However, since 146 seconds was still insufficient in our case, could you please confirm whether 147 seconds (or slightly higher) would be the recommended safe minimum value for 25.06/25.12?

Additionally, will this adjusted timing requirement be reflected in future documentation or default settings of the Test Tool?

Thank you for your support.

Best regards,
Queenie

[SergeyGRSE]

Hi Queenie,
thank you for testing.
The default reboot timeout is actually 30000 ms. This must be adjusted for each customer because this is very device specific. I think you already did this in one of the older version. Now you need to change it once to 148000 and this will be saved for future runs.
Unfortunately settings done in older version will not automatically be loaded into the 25.12. You need to use "File"->"Save Settings" in old DTT and then "File"->"Load Settings" in a new version. We will address this in next release.

Yes documentation needs to be updated we will take care of this in 26.06