Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • FortiVoice Cookbook

    Home FortiVoice 6.4.10 FortiVoice Cookbook
    6.4.10
    7.0.5
    7.0.4
    7.0.3
    7.0.2
    7.0.1
    7.0.0
    6.4.10
    6.4.9
    6.4.8
    6.4.7
    6.4.6
    6.4.5
    6.4.4
    6.4.3
    6.4.2
    6.4.1
    6.4.0
    6.0.12
    6.0.11
    6.0.10
    6.0.9
    6.0.8
    6.0.7
    6.0.6
    6.0.5
    6.0.4

    Planning high availability

    Planning high availability

    For FortiVoice HA, apply the following planning guidelines:

    • Make sure that both FortiVoice units in the HA group are the same model and have the same firmware version. If you are using VM instances, you require two VM licenses.
    • For both primary and secondary FortiVoice units:
      • Connect port 1 to the network switch.
      • Connect port 2 or a secondary port (3, 4, or 5, depending on the model) to the network switch. This port takes on the role of the primary heartbeat interface.
    • Plan which interface ports to use for your voice traffic and heartbeat links:
      • Decide which port you want to use for your voice traffic, for example port 1.
      • Make sure to assign the secondary heartbeat status to port 1.
      • Make sure to assign the primary heartbeat status to port 2 (3, 4, or 5, depending on the model).
    • FortiVoice HA uses a secondary IP address on the interface ports. This secondary IP address is called a virtual IP address. You configure the primary and secondary units to use this virtual IP address but only the acting primary unit will use it to communicate. Any network traffic that is to be forwarded to the FortiVoice unit can be forwarded to this virtual IP address. If a failover occurs, the secondary unit assumes the role of primary and starts to use the virtual IP address. Your system is then able to continue operating as normal without having to change your port forwarding. For example, the primary unit has an IP address of 192.168.1.200 and the secondary unit has an IP address of 192.168.1.202. The virtual IP address is 192.168.1.210. Both primary and secondary units share this virtual IP address which is also used to receive all port forwarding to the FortiVoice unit.
    • Take note of the IP address of each interface port on both FortiVoice units. You will need this information to set up the heartbeat link.

    When you are ready to configure HA, go to Configuring high availability on FortiVoice units.

    Note

    If a failover occurs and you are using FortiVoice 200F8 or FortiVoice 300E-T, remember to swap the physical FXO and PRI connections to the secondary unit.

    Previous
    Next

    Planning high availability

    Planning high availability

    For FortiVoice HA, apply the following planning guidelines:

    • Make sure that both FortiVoice units in the HA group are the same model and have the same firmware version. If you are using VM instances, you require two VM licenses.
    • For both primary and secondary FortiVoice units:
      • Connect port 1 to the network switch.
      • Connect port 2 or a secondary port (3, 4, or 5, depending on the model) to the network switch. This port takes on the role of the primary heartbeat interface.
    • Plan which interface ports to use for your voice traffic and heartbeat links:
      • Decide which port you want to use for your voice traffic, for example port 1.
      • Make sure to assign the secondary heartbeat status to port 1.
      • Make sure to assign the primary heartbeat status to port 2 (3, 4, or 5, depending on the model).
    • FortiVoice HA uses a secondary IP address on the interface ports. This secondary IP address is called a virtual IP address. You configure the primary and secondary units to use this virtual IP address but only the acting primary unit will use it to communicate. Any network traffic that is to be forwarded to the FortiVoice unit can be forwarded to this virtual IP address. If a failover occurs, the secondary unit assumes the role of primary and starts to use the virtual IP address. Your system is then able to continue operating as normal without having to change your port forwarding. For example, the primary unit has an IP address of 192.168.1.200 and the secondary unit has an IP address of 192.168.1.202. The virtual IP address is 192.168.1.210. Both primary and secondary units share this virtual IP address which is also used to receive all port forwarding to the FortiVoice unit.
    • Take note of the IP address of each interface port on both FortiVoice units. You will need this information to set up the heartbeat link.

    When you are ready to configure HA, go to Configuring high availability on FortiVoice units.

    Note

    If a failover occurs and you are using FortiVoice 200F8 or FortiVoice 300E-T, remember to swap the physical FXO and PRI connections to the secondary unit.

    Previous
    Next