Fortinet Document Library

Version:


Table of Contents

5.3.0
Download PDF
Copy Link

Verifying the heartbeat status

Use this procedure to verify that the heartbeat between the FortiVoice LSG unit at the branch office and the FortiVoice phone system at the main office is healthy.

  1. Connect to the web-based manager of the FortiVoice LSG unit at the branch office
  2. Go to Status > Dashboard, and click the Console tab.

    The Console window opens.

  3. To connect, click the console window.

    The Console window shows a system prompt.

  4. Enter the following command:

    diagnose debug application proxyd status summary

  5. Review the system output.

    The following system output is an example:

    System Time: 2019-11-04 10:06:53 EST (Uptime: 3d 19h 5m)

    200 OK

    Status:: mode: proxy (local survival is enabled), central office status=up, call handle location=central

  6. If the system output shows central office status=up, then you have completed this procedure. Go to Connecting the phones to the network.

    If the system output shows central office status=down, you need to troubleshoot the setup. You can start by verifying the IP address and port configuration (see Configuring administrator and network settings and Adding a survivability branch) and the heartbeat status again. Make sure that the heartbeat between the FortiVoice LSG unit at the branch office and the FortiVoice phone system at the main office is healthy before connecting the phones to the network.

Verifying the heartbeat status

Use this procedure to verify that the heartbeat between the FortiVoice LSG unit at the branch office and the FortiVoice phone system at the main office is healthy.

  1. Connect to the web-based manager of the FortiVoice LSG unit at the branch office
  2. Go to Status > Dashboard, and click the Console tab.

    The Console window opens.

  3. To connect, click the console window.

    The Console window shows a system prompt.

  4. Enter the following command:

    diagnose debug application proxyd status summary

  5. Review the system output.

    The following system output is an example:

    System Time: 2019-11-04 10:06:53 EST (Uptime: 3d 19h 5m)

    200 OK

    Status:: mode: proxy (local survival is enabled), central office status=up, call handle location=central

  6. If the system output shows central office status=up, then you have completed this procedure. Go to Connecting the phones to the network.

    If the system output shows central office status=down, you need to troubleshoot the setup. You can start by verifying the IP address and port configuration (see Configuring administrator and network settings and Adding a survivability branch) and the heartbeat status again. Make sure that the heartbeat between the FortiVoice LSG unit at the branch office and the FortiVoice phone system at the main office is healthy before connecting the phones to the network.