PDF(395.9 KB) View with Adobe Reader on a variety of devices
ePub(397.3 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(617.9 KB) View on Kindle device or Kindle app on multiple devices
Updated:January 23, 2018
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
2017-04-19 16:30:35,913 INFO [0x000013b0] [ls\src\http\CurlAnswerEvaluator.cpp(115)] [csf.httpclient] [csf::http::CurlAnswerEvaluator::curlCodeToResult] - Request #20 got curlCode= curl error message="[Received HTTP code 503 from proxy after CONNECT]" HttpClientResult=[UNKNOWN_ERROR] fips enabled=[false] 2017-04-19 16:30:35,913 INFO [0x000013b0] [ls\src\http\BasicHttpClientImpl.cpp(452)] [csf.httpclient] [csf::http::executeImpl] - *-----* HTTP response code 0 for request #20 to https://cucm.cisco.com:8443/cucm-uds/version 2017-04-19 16:30:35,913 ERROR [0x000013b0] [ls\src\http\BasicHttpClientImpl.cpp(457)] [csf.httpclient] [csf::http::executeImpl] - There was an issue performing the call to curl_easy_perform for request #20: UNKNOWN_ERROR
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
You can define the exceptions by asterisk's (*) and then your domain, by an individual IP Address, or a range; e.g. *.MY.Domain; 192.168.1.1; 192.168.1.12-14.
Configure the Proxy to redirect traffic sourced from the Jabber Client to redirect to the appropriate Call Manager.
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. 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).
Check the proxy settings on the workstation.
Step 1. You verify the proxy configuration from the command line; navigate to command prompt and run the command netsh winhttp show proxy
Step 2. You can navigate to Control Panel > Network and Internet > Internet Options > Connections > LAN Settings.
When there is no proxy:
When there is a proxy:
Step 3. Run the command "regedit" and navigate to HKEY_CURRENT_USER > Software > Microsoft > Windows > CurrentVersion > Internet Settings