Turning on AnyConnect killed our VoIP

[JonP]

Hello Community,

I just want to sanity-check something with you all.

We turned on Any Connect on our two MX's (MX105's in HA) and this killed our VoIP. We couldn't make or receive calls from any handset behind the firewalls until we turned the feature off again.

The AnyConnect subnet is completely different from any of our other production subnets, so we don't understand why this happened, and we think that it shouldn't have happened because the AnyConnect setup is independent of any other firewall features. Even if the MXs needed to re-provision (like Ubiquiti calls it) surely the spare should have taken over duties whilst the primary appliance did its thing?

It doesn't look like internet traffic was disrupted, just VoIP. We're a little hesitant to re-enable this feature because we need our VoIP as a key component of our business.

Any thoughts?

Thanks 🙂

[alemabrahao]

You should probably open a support case.

[Brash]

My only guess would be if the Anyconnect inbound port overlaps with any DNAT rules/inbound ports you have for VOIP.

Failing that, definitely open a support case.

[JonP]

The ports are a good point. There's a whole list of VoIP ports that we have to enable to get through the firewall. @CameronS