The 500-level error is specific to bug below. This bug is not yet available externally but will be within 24-48 hours. This is actively being investigated and I'd recommend opening up a Cisco TAC case for tracking.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvr11557
... View more
I had a look at the jabber logs that were provided and the issue appears to be host name resolution. (atleast in this login attempt) The client is able to successfully retrieve the collab-edge record for the "telkom.co.id" domain. DNS query succeeded for '_collab-edge._tls.telkom.co.id.' The client then tries to send the get_edge_config to the following address: https://ewedge-4-uc-st.telkom.co.id.telkom.co.id:8443/dGVsa29tLmNvLmlk/get_edge_config What's odd about this is that the request has the domain listed twice. Due to this the login is failing with a "Could not resolve host" error. 2014-08-19 16:35:47,444 INFO [0x000025a8] [ls\src\http\CurlAnswerEvaluator.cpp(108)] [csf.httpclient] [http::CurlAnswerEvaluator::curlCodeToResult] - curlCode=[6] error message=[Could not resolve host: ewedge-2-uc-st.telkom.co.id.telkom.co.id] result=[UNRESOLVED_HOST_ERROR] 2014-08-19 16:35:47,444 ERROR [0x000025a8] [ls\src\http\BasicHttpClientImpl.cpp(382)] [csf.httpclient] [http::executeImpl] - There was an issue performing the call to curl_easy_perform: UNRESOLVED_HOST_ERROR These logs suggest that there is an error with the collab-edge response. For some reason it's listed with the domain twice. I would double check your collab-edge SRV to see how you have it formatted. I hope this helps.
... View more
