Configuring Systems as Survivable Branches in FortiVoice

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.


Adding Survivability

To add a survivability branch on the central unit

  1. Go to Managed System > Survivability > Survivability Branch.
  2. Select New.
  3. Enter the name for the branch unit and enable it if required.
  4. Enter the name displaying on the branch unit, such as ABC Company PBX.
  5. Enter the hostname and IP address as well as all admin details.
  6. Enter the serial number and type of the model

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

  1. Expand the survivability section.
  2. Select the management mode. Fully managed is good for centralized configurations. Partially managed only creates configurations for extensions.
  3. Select the IP address the branch office system uses to check connectivity with the central system via the Heartbeat server address.
  4. Enter the Brach SIP server, which will be the IP address you wish the phones to talk directly to and the Branch SIP port.
  5. Select the Sip phone registration interval. This will only affect extensions allocated to the branch system. If you set the interval too high, you could end up with a delay when detecting a network outage. 
  6. Select whether emergency calls are handled by branch or central. A branch system intercepts the EMS call and sends it to local lines, while the central system handles the EMS call based on its configurations.
  7. Enable central trunk fallback to have the branch system handle calls if the central office cannot process the call. 
  8. Enter the trunks in the branch failover trunk section that will be used for outbound calls in a failover scenario.
  9. Select the FXO port the paging system is plugged into in the branch office if applicable.
  10. Enter the paging number to activate the paging system if applicable.
  11. Select the extensions that reside at the branch location. These can be any extensions already configured on the system.
  12. Select Create.

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.