What if you would like to have all of your routing rules, logs, call records, and call records in one centralized location for easier access and configuration? By establishing a survivability branch you can do just that.
A survivable branch is a local PBX containing local lines that are part of a larger centralized deployment. These systems would be deployed at branch offices and provide access to lines in the event that extensions at the branch office cannot reach the central system. The central system handles all normal calls and will push the configuration down to the branch office systems.
This recipe guides you through the process of setting up and configuring local survivability.
Before you can deploy your local survivability network you’ll need to perform a few configurations, if you have not already configured some of these requirements before.
You’ll need to establish your HA with the correct virtual IP, since it is used throughout the local survivability setup. For more information on HA deployment, consult “Using high availability” in the FortiVoice Administrator Guide.
Once each branch unit is added you will need to add or import their extensions to the central unit. See “Configuring IP extensions” in the FortiVoice Administrator Guide.
To add a survivability branch on the central unit
Next you’ll need to configure the survivability settings, which we’ll cover in more detail in the next section.
Configuring Survivability Settings
The survivability section controls exactly how the branch system operates.
To configure the survivability section
Once you’re finished configuring the settings you need, go back to the Survivability Branch tab and select your newly created branch and select Apply configuration.
Latest posts by Mike Mielke (see all)
- Configuring Call Services using Station Managing Detail Record (SMDR) in FortiVoice - July 11, 2018
- Configuring Systems as Survivable Branches in FortiVoice - July 11, 2018
- FXO Gateway Management in FortiVoice - July 11, 2018