Description |
This article describes how to apply VoIP profile where SIP inspection is not required for specific traffic crossing IPv4 policy.
The latest FortiGate versions have by default VoIP SIP ALG enabled globally and sometimes the FortiGate needs to handle more than one VoIP solutions where one solution will need SIP ALG active and other VoIP solutions will not be required.
Default FortiGate configuration:
config system settings
Note: If ALG mode is set in Kernel mode, Firewall policy is still required in Proxy mode to use a different VOIP profile. The below change need to apply in the Kernel Mode.
config firewall service custom
If a specific traffic flow is required to pass without SIP ALG inspection active, this can also be accomplished by adding the following VoIP profile to the IPv4 policy which allows this traffic. Note that the VoIP profile that is applied has the SIP inspection disabled. If such a profile is not used, FortiGate will detect the SIP traffic and apply the 'default' VoIP profile even if not applied in the policy:
config voip profile config sip set status disable <----- Disable SIP inspection. set rtp disable <----- Avoid RTP pinholes creation. end
To maintain SIP inspection while disabling SDP, the configuration of the VoIP profile changes as follows.
config voip profile edit "Disable-SDP" config sip set no-sdp-fixup enable <----- Disable SDP modification/translation next
Turns off FortiGate's automatic modification of SDP information in SIP packets. Prevents the firewall from rewriting:
The configuration tells the FortiGate not to modify or translate SDP messages in SIP traffic.
It can be helpful when:
By CLI:
config firewall policy
Note: Enable VoIP feature from System -> Feature Visibility -> VoIP.
|
Scope | FortiGate. |
Solution |
Having different VoIP profiles where one has SIP ALG disabled and the other enabled, provides granularity to to decide which traffic needs SIP inspection active and which is not active at the Firewall Policy desired.
|