Hi,
I have a Fortigate 100D (v5.0,build0271 (GA Patch 6)) with two services Internet and SIPTRUNK private, this was working swell until i need to add a third service, one SIPTRUNK pointing to a Public address. The issue is with the SIPTRUNK private (when i mean private, the SIPTRUNK is offered by a MPLS VPN Layer3 i will add a graphic with the topology later) the SIPTRUNK with pointing to the public address is working OK, but not the private, the thing is with the NAT Policy that i've configured on the Fortigate, the private side is seeing the Private IP NAT int he contact header SIP. I've reorder the policies with no luck i've done debugs and all appears to be OK, but it's not. As soon as i disable the Policy for the SIP TRUNK with the public address the private one start to works ok.
Thank you advanced.
quevedo_lopez wrote:Uhm if you need to NAT to your siptrunk why not simply enable nat on policy Seq.# 1?but not the private, the thing is with the NAT Policy that i've configured on the Fortigate, the private side is seeing the Private IP NAT int he contact header SIP.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1740 | |
1108 | |
752 | |
447 | |
240 |
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.