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" W

Question

Options

• ARich Media Session licenses are not activated on Expressway-E.
• BExpressway-E is listening on the wrong IP interface.
• CThe destination port for Expressway-E is set to 7400 instead of 8443 on the Expressway-C.
• DThe XCP Service is not activated on Expressway-E.

• A
  5% (2)
• B
  74% (32)
• C
  14% (6)
• D
  7% (3)

Explanation

Port 7400 is the internal TCP port used by the XCP (Extensible Communications Platform) service for XMPP traffic flowing between Expressway-C and Expressway-E. The error '(111) Connection refused' means Expressway-C successfully routed a TCP SYN to the correct IP address of Expressway-E, but nothing on Expressway-E accepted the connection on that port. This is characteristic of Expressway-E listening on a different IP interface than the one targeted - the service is running but not bound to the interface Expressway-C is trying to reach. Option C is a plausible distractor but is wrong because 7400 is the correct internal XCP port; 8443 is the external HTTPS port for client connections. Option D (XCP service not activated) would produce a similar symptom but would refuse connections on all interfaces, not just a specific IP. Option A (Rich Media Session licenses on Expressway-E) would not cause a port-level TCP connection refusal.

No community discussion yet for this question.