If I use fwconsole to create an extension mapping in EPM, it successfully creates the mapping in the database because it shows up in the GUI and shows up green.
But if I look at the /tftpboot directory, there is no config file made.
If I subsequently click on the extension in the GUI and tell it to rebuild the file, it does create the file.
@lgaetz I am looking at these EPM functions because I have a site that wants user’s “main” phone to always work while having a login function on guest phones.
If I use the built in Login app, it removes the EPM entry for the main phone when a user logs in. To my understanding that is by design.
So It would be easier for me to have a custom function wrote in PHP that I can put on a button to add/remove the entry to EPM.
Only thing I don’t know yet is how to make a phone reload config that is not registered. I know the existing phone app does it. Figured it must be some type of notify but not that far yet.
@lgaetz your support team needs training on your own products.
They have now combined my two submitted tickets as the same issue when I reported two completely different things.
One being the Extensions module “Other” tab not working correctly.
The other being fwconsole epm not working correctly.
Then they clearly didn’t’ even understand what provisioning multiple devices on different contacts meant as they asked questions about “Line 1” and “Line 2”.
Note: if you use CHAN_SIP extensions or if you use PJSIP and you do not set Max Contacts to something greater than 1, there are zero issues with any of these commands to my knowledge.
The current --edge version of the Endpoint module (14.0.5.3) works for everything except removing an existing config via fwconsole for pjsip endpoints with max endpoints set greater than 1.
The command changed from fwconsole epm to fwconsole endpoint but works.
Adding the mapping, does not create the file. it is the same as adding the device in the GUI and choosing only the “Save” option.
Using the rebuild command from fwconsole generates the file, but as the root user. This will cause the web GUI to blow up if you try to rebuild it form there in the future.
In the web interface, there is a similar issue with this. If you choose delete frorm the main list of endpoints, it will only delete the mapping, but not the config file.
If you instead go into the extension mapping, there is a Delete and remove config option instead.
This is the only official in way to move a config file with either the GUI or fwconsole right now.
