I’m asking that because how it works is the server sends meeting start time to the client, and the client works out the elapsed time locally. If local machine time is behind the time sent by the server, then “now - start_time” would be a negative value and it makes more sense for the timer to show 0:00 than a negative duration.
So perhaps your machine time is 1-3 minutes behind the server?
So everything else works as expected (everyone can see/hear each other), and conference duration counter is wrong from everyone?
I was asking about >1 users because what the conference duration module does is quite trivial – once there are more than 1 occupant (1st real person + focus) then the meeting start time is set and sent to everyone. So if this goes wrong, then it is possible that it is just a symptom of some other issue with your setup.
If you are sure that there is no clock inconsistency issues, and everything else works as expected, then I’m out of ideas. Sorry.