Skip to main content
ezhupa
Staff
ezhupa
Staff
June 23, 2026

Troubleshooting Tip: FortiGate high memory usage due to VoIP daemon

  • June 23, 2026
  • 0 replies
  • 45 views

Description

This article describes a technical issue where a FortiGate device experiences high memory usage due to the VoIP daemon. It may be noticed that the device's memory usage is increasing over time, potentially leading to conserve mode and dropped traffic sessions.

Scope

FortiGate.

Solution

Monitor the device's memory usage and collect logs when the memory usage reaches 70-75%. Use the following commands to collect logs:

fnsysctl date
diagnose sys sip-proxy call list
diagnose debug disable
diagnose debug reset
diagnose debug application sip -1
diagnose debug enable
fnsysctl date


Use a script to continuously monitor the device's memory usage and collect logs. The script can be run by using a tool like TeraTerm.

Collect sniffer logs on a different CLI session when collecting SIP call list and debug logs. Use the following command to collect sniffer logs:

fnsysctl date
diagnose sniffer packet any 'port 5060' 6 0 l


Press Ctrl+C to stop the processes when done.

Kill the VoIP daemon when the memory usage reaches 75-76%. Use the following command to kill the VoIP daemon. In the example below, XXX is the PID of the VoIP daemon.

diagnose sys process pidof voipd
fnsysctl kill 11 XXX


Monitor the devices and voipd resource usage after killing the process and check if it continues to rise steadily.

If so, the process can be killed when the usage becomes high as a workaround.

Note:

  • The fix for this issue will be included in FortiOS v8.0.1.

  • The fix is also expected to be released on v7.6.8.

    Terms & ConditionsAccessibility statement