Apply Configurations

The option Apply Configurations is crucial in IPBrick. All configurations done in IPBRICK through the web interface, are saved in a Postgres database. This way any changes the configuration will only be effective in the system after clicking on Apply Configurations.

Most changes don't make the IPBrick server go to reboot, so a screen like Figure 8.2 will appear. IPBrick only needs to reboot in these cases:

• Network interfaces configuration;
• Domain name and server name configuration;
• Changes in authentication mode (LDAP).

NOTE: The IPBrick Administrator will be notified should the VoIP service requires restart, in order to apply the configurations. This will imply the momentary loss of VoIP service, thus terminating all current calls. Please bear in mind this when deciding to apply the changes.

And a screen like Figure 8.1 will be shown. It's important to inform that IPBrick will go to reboot, so the administration has the option to apply configurations in that momment or at non work hours.

As we can see, we only need to change this type of configurations to get the server in production at the costumer network. From the momment IPBrick is in production, is becames very rare to go to a reboot because we don't need to change anymore of the network definitions, domain/server name and LDAP mode.

When applying configurations two extra options are presented:

• Description: Each time we apply configurations we can make a description of what we did;
• Cancel all changes: Choosing that option, instead of Apply, will rollback all configurations that were made. So IPBrick will stay with the settings from the last time someone applied configurations, i.e. the last configuration file that appears at Advanced Configurations - Disaster Recovery - Configurations.

Figure 8.1: Apply Configurations and reboot

Figure 8.2: Apply Configurations

NOTE: Applying configurations on an IPBrick Master automatically forces the apply configurations on its IPBrick Clients and Slaves.