NethVoice: simultaneous phonebook-update timers cause resource spikes

[Amygos]

Steps to reproduce

• Deploy multiple NethVoice instances with phonebook-update.timer enabled in user systemd.
• Ensure each timer uses the default configuration (OnCalendar=hourly, no randomized delay).
• Observe system resource usage at the scheduled timer trigger (e.g., every hour on the hour).

Expected behavior

Each instance should update the phonebook independently without causing significant simultaneous load on the system.

Actual behavior

All instances trigger phonebook-update at the same time, resulting in resource spikes and potential performance degradation.
For example:

[root@n1 ~]# runagent -m  nethvoice2 systemctl --user status  phonebook-update.timer
● phonebook-update.timer - Timer for phonebook source update
     Loaded: loaded (/home/nethvoice2/.config/systemd/user/phonebook-update.timer; enabled; preset: disabled)
     Active: active (waiting) since Tue 2024-12-17 09:01:41 UTC; 6 months 27 days ago
      Until: Tue 2024-12-17 09:01:41 UTC; 6 months 27 days ago
    Trigger: Tue 2025-07-15 13:00:00 UTC; 8min left
   Triggers: ● phonebook-update.service
[root@n1 ~]# runagent -m  nethvoice3 systemctl --user status  phonebook-update.timer
● phonebook-update.timer - Timer for phonebook source update
     Loaded: loaded (/home/nethvoice3/.config/systemd/user/phonebook-update.timer; enabled; preset: disabled)
     Active: active (waiting) since Tue 2025-01-07 10:33:24 UTC; 6 months 6 days ago
      Until: Tue 2025-01-07 10:33:24 UTC; 6 months 6 days ago
    Trigger: Tue 2025-07-15 13:00:00 UTC; 8min left
   Triggers: ● phonebook-update.service

Components

• ns8-nethvoice

See also

• Private Mattermost discussion: https://mattermost.nethesis.it/nethesis/pl/wcpajjydctycif3wk1h7a6zczc
• Helpdesk ticket: https://helpdesk.nethesis.it/a/tickets/191458

[Amygos]

Testing release nethesis/ns8-nethvoice 1.4.5-testing.3

[Amygos]

QA

Check if the issue is reproducible