I've been working on the sccp_manager app this week and I'm almost finished with it.
The original program read and wrote information out of the sccpline and sccpdevice database tables. It still does that. In addition, I added two more new modules - one that reads and modifies the sccp.conf file and one that reads and modifies the SEPDefault.cnf.xml file.
Both files are modified "in place", so if you have additional stuff in the files (comment blocks, etc.), it will largely be retained (individual line comments don't survive - everything else does). The sccp.conf file, for example, allows for the retention of custom softkey sets and allows the keysets to be modified for each phone.
The manager for the XMLDefault.cnf.xml file has me wondering about a couple of questions I have for anyone that would like to chime in:
1) The way the manager program works right now is that if the SEPDefault.cnf.xml file exists in /tftpboot, phone specific configuration files are not produced and the "default" is used as the XML Configuration source for all phones. As I was working on the manager program, I realized that this might not be an optimal solution for everyone, so I added a program to manage the XMLDefault file and allow the creation of phone specific SEPXXXXXXXXXXXX.cnf.xml files for unusual cases.
The way this new program works is, if you specify that you want to edit the config file for a specific phone and the SEPXXX...xml file doesn't exist, it creates one from the Default and makes it easy to change several of the "commonly changed" settings (different URLs, the add on status, possibly loadimage versions). I'm in the process of picking and choosing which options show up on the management webpage. Would anyone like to offer some suggestions for the fields that need to be modifiable.
2) Would a special program for modifying local softkey sets be useful? I can add something to help manage those without very much trouble, but if no one wants to use it, there's no point.
Note that neither of these modules is going to be used a lot anyway. The SEPDefault.cnf.xml file that comes with the distribution is usually more than adequate for what chan-sccp-b needs to set up. The sccp.conf file, likewise, doesn't get edited very often (if ever).
3) Since I'm in here, would it make sense to add a feature that sets up the "OS???.txt" files based on the settings in the program? I mean, I'm here and have all the information. Is this something that people would find useful? It is one of the things that I know I had trouble with, but once I got it working, it's never needed modified...
I'm planning on knocking out the last of the features this weekend.