Created on 07-07-2022 06:22 AM Edited on 10-25-2023 09:01 AM By Stephen_G
Description | This article describes the changes which were introduced in v7.0.0 and v7.2.0 in regards to the default operation on FortiGate's SIP ALG. | ||||||||||||||||||||||||||||||||
Scope | FortiOS v7.0 and v7.2 GA releases. | ||||||||||||||||||||||||||||||||
Solution |
In FortiOS versions up to v6.4, by default and regardless of the firewall policy inspection mode, SIP traffic was proxied by SIP ALG. This can be determined with the following settings:
config system settings set default-voip-alg-mode proxy-based * | kernel-helper-based end
The default setting was proxy-based.
Since v7.0.0, a new feature named Flow-Based SIP was introduced.
The particular feature brings optimization to CPU and memory because the VoIP traffic can now be inspected by the IPS engine itself.
However, the original SIP ALG has much more advanced capabilities for VoIP inspection.
After upgrading to v7.0.1+ or v7.2, Flow-Based SIP will now run by default in a firewall policy, which is configured as flow inspection mode.
For example, a FortiGate was configured in v6.4 as:
config system settings set default-voip-alg-mode proxy-based end
config firewall policy edit 1 set name "VoIP_Policy" set inspection-mode flow end
After upgrading to v7.0.1+ or v7.2, if the goal is to maintain the same behavior as v6.4, the inspection mode of the firewall policy should be configured as proxy-based.
config firewall policy edit 1 set name "VoIP_Policy" set inspection-mode proxy end
For firewall policies that were originally configured [in v6.4] with a VoIP profile attached to them, they will automatically be switched to proxy inspection during the upgrade process.
Related articles: |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.