WebEx

WebEx does not support HTTPS connections through a proxy. Use one of the following bypass methods.

PAC file entry:	if (shExpMatch(url, ".webex.com/")) { return "DIRECT"; }
Static bypass rule:	This method requires creation of several bypass rules, one for each current IP address range. For each IP address range:
	Rule Type: Bypass
	Source IP: (empty)
	Destination IP: <IP address range>
	The list of IP addresses for Cisco Unified MeetingPlace version 8.5 is:
	64.68.96.0/19 (CIDR) or 64.68.96.0 - 64.68.127.255 (net range)
	66.114.160.0/20 (CIDR) or 66.114.160.0 - 66.114.175.255 (net range)
	66.163.32.0/20 (CIDR) or 66.163.32.0 - 66.163.47.255 (net range)
	209.197.192.0/19 (CIDR) or 209.197.192.0 - 209.197.223.255 (net range)
	208.8.81.0/24 (CIDR) or 208.8.81.0 - 208.8.81.255 (net range)
	210.4.192.0/20 (CIDR) or 210.4.192.0 - 210.4.207.255 (net range)
	62.109.192.0/18 (CIDR) or 62.109.192.0 - 62.109.255.255 (net range)
	173.243.0.0/20 (CIDR) or 173.243.0.0 - 173.243.15.255 (net range)
	114.29.192.0/19 (CIDR) or 114.29.192.0 - 114.29.223.255 (net range)
	More more information, see below.
SSL incident rule:	Add: URL *.webex.com TUNNEL

Troubleshooting: If after adding a bypass, the connection still fails, in some cases the WebEx site responds with an IP address or a domain name that doesn’t match *.webex.com. You can work around the problem by examining the inbound_access.log to find the unresolved connection and then add the IP address or domain name as an exception using the option employed above.

Note: When Content Gateway is on an appliance, this procedure requires the assistance of Technical Support.