Cisco Cisco TelePresence Video Communication Server Expressway
Cisco Jabber sign in issues
Jabber cannot sign in due to XMPP bind failure
The Jabber client may be unable to sign in ("Cannot communicate with the server” error messages) due to
XMPP bind failures.
XMPP bind failures.
This will be indicated by resource bind errors in the Jabber client logs, for example:
XmppSDK.dll #0, 201, Recv:<iq id='uid:527a7fe7:00000cfe:00000000' type='error'><bind
xmlns='urn:ietf:params:xml:ns:xmpp-bind'/><error code='409' type='cancel'><conflict
xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>
XmppSDK.dll #0, CXmppClient::onResourceBindError
XmppSDK.dll #0, 39, CTriClient::HandleDisconnect, reason:16
Jabber cannot sign in due to SSH tunnels failure
Jabber can fail to sign in due to the SSH tunnels failing to be established. The traversal zone between the
VCS Control and VCS Expressway will work normally in all other respects. VCS will report 'Application failed
- An unexpected software error was detected in portforwarding.pyc'.
VCS Control and VCS Expressway will work normally in all other respects. VCS will report 'Application failed
- An unexpected software error was detected in portforwarding.pyc'.
This can occur if the VCS Expressway DNS hostname contains underscore characters. Go to
System
> DNS
and ensure that the System host name only contains letters, digits and hyphens.
Jabber cannot sign in when connecting to different peers in a cluster of
VCS Expressways
VCS Expressways
Jabber sign in failures have been seen when there is inconsistency of the DNS domain name between VCS
Expressway peers. The domain names must be identical, even with respect to case, on all peers in the
cluster.
Expressway peers. The domain names must be identical, even with respect to case, on all peers in the
cluster.
Go to
System > DNS
on each peer to make sure that Domain name is identical on all peers.
VCS returns "401 unauthorized" failure messages
A "401 unauthorized" failure message can occur when the VCS attempts to authenticate the credentials
presented by the endpoint client.The reasons for this include:
presented by the endpoint client.The reasons for this include:
n
The client is supplying an unknown username or the wrong password.
n
ILS (Intercluster Lookup Service) has not been set up on all of the Unified CM clusters. This may result in
intermittent failures, depending upon which Unified CM node is being used by VCS for its UDS query to
discover the client's home cluster.
intermittent failures, depending upon which Unified CM node is being used by VCS for its UDS query to
discover the client's home cluster.
Call failures due to "407 proxy authentication required" or
"500 Internal Server Error" errors
"500 Internal Server Error" errors
Call failures can occur if the traversal zones on VCS are configured with an Authentication policy of Check
credentials. Ensure that the Authentication policy on the traversal zones used for mobile and remote
credentials. Ensure that the Authentication policy on the traversal zones used for mobile and remote
Unified Communications Mobile and Remote Access via Cisco VCS Deployment Guide (X8.5.2)
Page 50 of 54
Appendix 1: Troubleshooting