I might be going blind but I see no way to apply changes made to a basefile and cause the provisioning files to be regenerated. Where did the submit button go?
You need to go to extension mapping and pick which phones you want to rebuild the config for.
I appreciate that this thing is in beta and that there has been a recent revamp of the user interface. That said I have a PBX that is taking far too much of my time to get a simple change in place and the CEPM was brought purposely to avoid that issue.
I can only find documentation respecting CEPM for the version that shipped with FreePBX-2.x. And I am finding navigation in the new version unintuitive. If there is up-to-date documentation then I very much would appreciate being given the reference.
However, regardless of navigation and user interface issues, I have only a confused idea what happened to my existing settings. I followed your advice to select all extensions and rebuilt the configuration files. This is what I got:
cat snom870.htm <!--# Created on 2015/03/20 08:32:59 #Configuration automatically generated via the EndPoint Module #DO NOT HAND MODIFY THIS FILE!--> <?xml version="1.0" encoding="utf-8"?> <setting-files> <file url=""/> </setting-files>
I had a very large customised basefile for these phones and as far as I can tell from this it simply disappeared. I eventually found where it went. It is in something the new GUI calls model-mac.htm (three levels down) and generated into a file called snome-.htm. I infer that this is used as the basefile for extensions that are identified by their MAC numbers. Which is fine. Excepting that we do not use the MAC number at all. So converting to this version has effectively erased my configs. Which, if I had not kept copies of the preceding provisioning files, would have brought down my entire phone system.
All I wanted to do was to modify this line to append ;transport=tls to the user_outbound sip proxy setting.
<user_outbound idx="1" perm="RW">__line1Dest__:__line1sipPort__;transport=tls</user_outbound idx="1">
And what I got was an empty configuration file.
I made the modification to the model-mac page since that is where I found all of my previous settings. Which, given the inferences I draw above means that it likely will have no effect at all. I also note that following the edit this entry in model-mac is coloured red, I anticipate that means that this change is not going to work in any case since red probably indicates it does not pass some internal edit. Which condition, left unamended, would have really unpleasant consequences for us. Which means that I perforce must manually edit the resulting config files, assuming they they are produced as I anticipate.
To generate those files I thought that I could manually move the setting from model-mac to model. But I note that the format for model.htm differs significantly from model-mac.htm. And in the absence of documentation I am unsure as to how I should proceed.
The files created by the new generation process appear to be these:
-rwxr-xr-x 2 asterisk asterisk 224 Mar 20 08:32 snom870-.htm -rwxr-xr-x 2 asterisk asterisk 224 Mar 20 08:32 snom870.htm -rwxr-xr-x 1 asterisk asterisk 126 Mar 20 08:33 snomne--firmware.xml -rwxr-xr-x 1 asterisk asterisk 110657 Mar 20 08:33 snomne-.htm -rwxr-xr-x 1 asterisk asterisk 224 Mar 20 08:33 snomne.htm
I cannot tell what snomne-.htm is for or how it is used. I do find that at least some of the missing customised parameters are located therein so I will presume that they all are. But I have no clue as to how this file is related to the editing that I do in CEPM or how it is made available to the phones when they re-provision. I do see this however:
snomne-.htm:<user_outbound idx="1" perm="RW">:</user_outbound idx="1">
Which seems to confirm my suspicions respecting the red-lined entries in model-mac.htm. For I also discovered that:
<rtp_port_start perm="">10011</rtp_port_start> #Also red-lined in model-mac
evidently produces this in snome-.htm:
I looked into snome.htm to see if it called snome-.htm but see only this:
cat snomne.htm <!--# Created on 2015/03/20 08:33:07 #Configuration automatically generated via the EndPoint Module #DO NOT HAND MODIFY THIS FILE!--> <?xml version="1.0" encoding="utf-8"?> <setting-files> <file url=""/> </setting-files>
Perhaps you could provide some guidance as to how I proceed to generate the correct provisioning files for these phones using CEPM?