- Shipped
- 27 ஆகஸ்ட், 2026 அன்று 7:46 AM UTC
- Author
- Kamo
- Commit
- aa7cbf5
Adding a KamoPBX phone server now creates the underlying account and writes the account id and realm back to configJson. Any configJson the client sent is DISCARDED rather than merged: there is no legitimate field for it to carry, and accepting one would be a way to point an org at another tenant's account. A provisioning failure leaves the row behind marked not-connected with the reason, rather than deleting it — the id may already have an account created against it, and the operator can retry from the instance page. The client is a shared bean so the token cache is reused; constructing one per call would re-authenticate against KamoPBX on every request. kamo.pbx.* are platform settings with blank credential defaults, so an unconfigured platform reports 'not configured' instead of failing open. 246 tests pass.