You can navigate to Control Panel > Network and Internet > Internet Options > Connections > LAN Settings. Step 1. You verify the proxy configuration from the command line navigate to command prompt and run the command netsh winhttp show proxy VerifyĬheck the proxy settings on the workstation.
This is dependant on the network flow from the client to the Call Manager and would be nullified if the infrastructure inbetween is sends web traffic via Web Cache Communication Protocol (WCCP). Remove the proxy configuration from the windows client, then have the HTTP GET method from Jabber bypass the proxy and all other traffic sourced from the PC. Solution 2Ĭonfigure the Proxy to redirect traffic sourced from the Jabber Client to redirect to the appropriate Call Manager. You can define the exceptions by asterisk's (*) and then your domain, by an individual IP Address, or a range e.g. You can configure the client to bypass the proxy and go directly to Call Manager in the exceptions section of proxy settings naviagate to Control Panel > Network and Internet > Internet Options > Connection > LAN Settings > Advanced 16:30:35,913 ERROR - There was an issue performing the call to curl_easy_perform for request #20: UNKNOWN_ERROR Solution 1
16:30:35,913 INFO - *-* HTTP response code 0 for request #20 to 16:30:35,913 INFO - Request #20 got curlCode= curl error message="" HttpClientResult= fips enabled= 16:30:35,913 DEBUG - Request #20 got status line: HTTP/1.1 503 Service Unavailable 16:30:35,229 INFO - Enter - hangDetectionCallback() 16:30:30,565 DEBUG - Request #20 configured with: connection timeout 10000 msec, transfer timeout 0 msec Cisco Web Security Applicance (WSA) 9.1Ĭisco Jabber Log in fails when a system proxy is defined and does not allow traffic to reach the Call Managers to download it's configuration.The information in this document is based on these software and hardware versions: Cisco Unified Communications Manager (CUCM).Cisco Unified Instant Messaging & Presence (IM&P).
Prerequisites RequirementĬisco recommends that you have knowledge of these topics: This document describes the reasons for the Cisco Jabber log in failure which is due to a proxy defined on the workstation.
0 kommentar(er)
