- Ya
- 27 Agosti 2026, 19:22 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 24aeaee
"Test connection" reported "no master account id" on a phone server whose provisioning had just succeeded, minutes earlier, using that same id. Two sources disagreed about one setting. KamoPBXBeanConfig resolves the platform settings DATABASE FIRST from the SYSTEM_CONFIGURATION singleton the platform settings UI writes — which is why provisioning, going through that class, saw the saved id. PhoneProviderFactory instead declared its own **************** reading application properties, which are empty in this cluster. So the id was simultaneously set and unset depending on which code asked. The factory now asks KamoPBXClient for the id it was actually built with, so the check cannot disagree with the credential the calls are made under. The same bug was latent in kamo.pbx.wss-url — it would have handed softphones the compiled-in default while ignoring a saved platform setting — so that is now a DB-first bean from KamoPBXBeanConfig too. Tests cover both directions of the master-id check and assert that an unprovisioned server still says so rather than claiming it was not found. 297 pass.