For details, see Cisco’s Defect CSCuo82526.ĭ) Verify that the corporate firewall has a rule for port 8443 that forwards traffic to the DMZ LAN interface of the Expressway-Edge server. In the example below, we use a well-known public DNS server.ī) Verify that the returned FQDN of the Expressway-Edge server from the SRV record is resolving to an IP address.Ĭ) Verify that the Cisco Expressway-Edge server’s FQDN name matches exactly the value created in the collab-edge SRV record. Please note that it is important to set the type to SRV.

STEP 1 Verify the DNS and firewall-related configurations.Ī) Verify that the SRV type DNS record is present.

In this scenario, we will assume that the user is able to log in to Jabber from inside the corporate LAN and focus our troubleshooting efforts on Expressway pair servers. The following three steps outline what to do when troubleshooting the Cisco Jabber login error “Cannot communicate with server” while trying to communicate using MRA via Cisco Expressway. This is the Cisco Jabber login error when trying to communicate using Mobile and Remote Access (MRA) via Cisco Expressway: “Cannot communicate with the server”. However, there are times when this seamless mobility can run into one of the most common errors while using Jabber in MRA mode via Cisco Expressway: “Cannot communicate with the server“. Being able to use Cisco Jabber and IM&P can help bring mobile collaboration to another level. To help maximize efficiency and make this mobility seamless to individuals and entire teams, MRA via Cisco Expressway is the key.

More and more companies have mobile workforces – teams that work on the road and/or who have the ability to work from home. Today’s tip is about how to effectively troubleshoot this problem. The Cisco Jabber “Cannot communicate with the server” error commonly occurs when using Mobile and Remote Access (MRA) via Cisco Expressway.

Cisco jabber pc automatic configuration