Nomadic 911 private subnets optional

[vgonzalez]

Is there any way to toggle private subnets required for location detection? we have multiple sites that egress our datacenter via private MPLS and have the same public IP address but the private range is different.

Since the private range is optional, when on VPN, using the same public range as our internal sites, it randomly detects you at these locations for your 911, also locking the end users out from specifying a custom location because their location has been detected by a published location in the E911 database in zoom.

[Arps]

Hello!

Thank you for your feedback.

This is something that's being address with the Zoom Phone product team.  In the meantime, we would recommend split-tunneling for Zoom and Zoom Phone traffic.  This will not only help with the e911 situation, but will also give the user a lower latency link to the Zoom cloud for a better overall experience.

Hope that helps and please make sure to mark the solution as accepted if this information is what you needed.

Thanks! Rick

[vgonzalez]

Any updates internally with any progress with this getting added with the zoom phone product team?

Currently we do not have a good way to split tunnel out just the zoom application, and for security reasons we do not allow split tunneling for all networks besides ours, however we are going to bring this up with our governing body to see if this is even something we can do under regulations.

Currently a more urgent issue, as we have a remote satellite office that is not on network, and no plans for it that VPN in and can not set their 911 location because of subnets being optional