What each phone model is sent is now data you can see, override and copy.
What a desk phone is sent used to be buried in code. It is now a catalog you can see.
Families and models
A family is a group of phones that take the same kind of settings file. A model is one phone in a family, and knows the things that differ:
- how many programmable keys it has,
- whether it can encrypt,
- which codecs it supports,
- the size of its screen.
So a phone with six keys is not sent thirty, and a model without encryption is set up plain even if the extension asks for it.
Layers
A phone's settings file is built in layers, each able to override the one before:
- the family's template,
- lines for that model,
- an administrator's overrides for the model,
- an override chosen for that one phone,
- and anything typed on the phone's own page.
Need every phone of one model to use a different ringtone? One override. Need the lobby phone to be different from the rest? One more.
What you see is what is sent
Each phone has a link that shows the exact file it would receive, with the passwords hidden. No guessing what a setting turned into.
Built-in and your own
The models that come with Kahevo are corrected by updates and cannot be edited directly. To change one, add an override, or copy it and make the copy yours. Updates never touch what you made.
Unknown phones get nothing
A phone the catalog does not recognize is sent no settings, and a note goes in the system log saying what it claimed to be. A file written for a different phone is a guess, and a guess is worse than a question. Pick a model for it and it gets its file.