Refer to the exhibit. A collaboration engineer is troubleshooting Cisco Jabber for Windows login issues for clients on a corporate network with an on-premises Cisco IM and Presence server. This issue

Question

Exhibit

Options

• AAdd the host "imp-pub" to the proxy exceptions list on the users' Windows computers.
• BRestore network connectivity to host "imp-pub".
• CRestart the IM and Presence services on the host "imp-pub".
• DChange the DNS SRV record to point to the Cisco UCM node instead of the IM and Presence

• A
  81% (30)
• B
  5% (2)
• C
  3% (1)
• D
  11% (4)

Explanation

Since all users are affected, the issue is likely environmental rather than account-specific. The exhibit indicates that Jabber clients are routing traffic to the IM and Presence server (host 'imp-pub') through the corporate proxy server. Jabber's XMPP and SIP signaling traffic to internal servers should bypass the proxy. Adding 'imp-pub' to the proxy exceptions list on the users' Windows computers forces Jabber to connect directly to the IM&P server without proxy interception, resolving the login failure. Option B (network connectivity) is ruled out since the server is reachable but through the wrong path. Option C (restarting services) would not fix a client-side proxy routing issue. Option D (changing DNS SRV) would disrupt IM&P functionality entirely.

No community discussion yet for this question.