Device with IP Pool stops working when switching to SD-WAN

[Whiteoaks]

Fortigate Version 7.2.10

We have several internet facing devices that use virtual IPs and a phone system that uses SIP which has a one-to-one IP assigned to it. We have two ISPs with link-monitor setup. 

To match our new locations, we are attempting to migrate to SD-WAN. We made the necessary changes to add the WAN ports to SD-WAN (removing existing polices on the interfaces and readding them). 

Upon completion the internet was tested and worked - failover to second WAN worked. Our internet facing devices were able to be access via the virtual-IP mappings on their respective public IPs\ports. We are not using SLA targets - strictly a primary\failover scenario.

Our SIP device however was unable to register with the trunk provider. The Fortigate shows the IP was assigned and the SD-WAN was using the interface in the specific range. I don't believe the PBX system was able to access the internet with the one-to-one IP assignment. 

Restoring the previous configuration had this device work again without any further issues. 

What should we be looking for when moving from traditional WAN to SD-WAN that may interfere with a one-to-one IP pool? I was unable to capture any debugs before having to restore the old configuration but will be back in a few nights to try again.

[Stephen_G]

Hello,

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.

If anyone viewing this topic has any knowledge on this, I encourage you to reply.

Thanks,

[Whiteoaks]

Hi sorry to waste anyone's time but this seems to be a configuration issue - likely from some old config on the fortigate that I'm looking into. 

I configured this at our new location on a temporary PBX and it worked fine right away.  I thought perhaps the SD-WAN may be interfering so was reaching out to the community is case of any known issues. 

I've managed to reroute our ISPs so I don't have to wait until overnight hours to test and will work on tracking down what in the configuration is causing the issue.  

Thanks for your help Stephen