Lync 2013 Edge Config

Hi Vegas588, I guess you've implemented now using Public IPs, however I have the same question and I'm a newbie to F5. Can anyone confirm whether the below is supported or works... or if I'm talking horsedung. I've seen posts by users saying that some have implemented F5 and Lync using NAT at the firewall successfully. We are going through the same issues, and are looking at redeploying the edge servers with Public rather than Private IPs to ensure a supported config. My understanding is that if Lync is deployed and the "use NAT" option for AV services is enabled on the Edge Servers then provided the Edge server has a route out it "should work" using a private IP. AV Clients would connect using their Public IP to the Firewall assigned Public AV IP which nats to internal Edge server directly (bypassing the F5). Return traffic from the edge would embedd the public IP in the packet as its NAT aware. The Edge server would require a route back via the Firewall as SNAT isnt used. The Access and Web Conferencing clients connect via the F5 to the edge using SNAT. So the Firewall should be able to be set as the default gateway on the edge - whereas I've seen posts saying the Floating IP of the F5 DMZ should be the default gateway (which I don't get as this wouldn't forward unless it was setup to VIP back to the Firewall???). Keen to here from anyone doing things this way. Thanks - Phil