Jabber cannot log in via Mobile and Remote Access.
You inspect Expressway-C logs and see this error message: XCP_JABBERD Detail="Unable to connect to host '%IP%', port 7400:(111) Connection refused" Which is the cause of this issue?
Click on the arrows to vote for the correct answer
A. B. C. D.B.
The error message indicates that Jabber is unable to connect to the host %IP% on port 7400 due to a "Connection refused" error. This error message suggests that there is an issue with the connection between the Jabber client and the Expressway-C server.
In this scenario, the most likely cause of the issue is that Expressway-C is not able to establish a connection with Expressway-E, which is preventing Jabber from logging in via Mobile and Remote Access. The error message indicates that the issue may be related to the XCP_JABBERD service.
Given the answer options provided, we can eliminate option A (Rich Media Session licenses are not activated on Expressway) as the cause of the issue because the error message does not reference licensing.
Option B (Expressway-E is listening on the wrong IP interface) is also unlikely to be the cause of the issue because the error message specifically indicates that the issue is related to the XCP_JABBERD service, which is not affected by the IP interface configuration.
Option C (The destination port for Expressway-E is set to 7400 instead of 8443 on the Expressway) is a plausible cause of the issue because it suggests that the Expressway-E server may not be configured to listen on the correct port. However, this would result in a different error message (e.g., "connection timed out" or "connection refused on port 8443"), so we can also eliminate this option.
Therefore, the most likely cause of the issue is option D: The XCP Service is not activated on Expressway-C. This is because the error message specifically references the XCP_JABBERD service, which is responsible for handling Jabber traffic on Expressway-C. If this service is not activated, Jabber will be unable to connect to the server, which would result in the error message seen in the logs.