EX SSLVPN: Publishing Static Routes for Subnet resources to support VOIP/WRA environments in split tunnel mode.
To support VOIP and new Windows WRA environments, subnet resources are required to be published as static routes instead of individual host routes. As of now Subnet resources are processed based on the client side traffic requests coming in through the tunnel. Not all Subnet Resources are published as Static routes on the tunnel adapter. Whereas for Host IP Resources, their routes are published during the tunnel initiation and thereby not required when the client initiates the traffic. For VOIP and WRA environments involving Subnet resources, if the subnet based routes are available before the traffic hits the adapter, it will fail.
Adding Individual Host/IP Resources for these backend VOIP and WRA servers will resolve this issue as they will have static routes published during the tunnel creation. In large server environments, configuring Subnet resources is more helpful and easy to manage than Individual Host/IP resources.
There is a Configuration Extension Mechanism (CEM) that will force the windows client to receive subnet resources.
If you have any issue with a CEM configuration please contact support.