removing the label will make it a 2 step process, disable the trunk and remove the label, then when the trunk is again available try to remember to add the label again. automation would be nice. we know the trunk exist and it is configured but disabled so dont show. when it comes back it shows again.
The fop2admin module does the button import ONCE, it does not check status of every device as freepbx does not have button types normalizes, they are scattered across tables so it is not possible to have a complete and correct idea of your config from the autoconfiguration scripts.
However, do not take my word, the autoconfiguration scripts are there for you to tweak, improve and modify. You can very well modify the sql queries to check for disabled state and avoid writing the config it that is the case. I recently did an update to use the mailbox information from freepbx instead of the initial snapshot that the fop2admin does, so it might be possible to do something similar with disable state.
Comments
Best regards,
However, do not take my word, the autoconfiguration scripts are there for you to tweak, improve and modify. You can very well modify the sql queries to check for disabled state and avoid writing the config it that is the case. I recently did an update to use the mailbox information from freepbx instead of the initial snapshot that the fop2admin does, so it might be possible to do something similar with disable state.
Best regards,