Cisco jabber for windows dns srv how to#
Cisco jabber for windows dns srv registration#

If this error is found and you have multiple Unified CM clusters defined in Expressway-Core In order to correct the issue, you will have to change the SIP port on the SIP Trunk Security Profile that is applied to the existing SIP trunk configured in CUCM. The error is usually due to an existing SIP trunk between Expressway-C and CUCM using port 5060/5061 (the trunk is not used for MRA, but usually is created for another feature of Expressway – B2B dialing).

Cisco jabber for windows dns srv registration#

If this error is found in the Core logs, it is in response to SIP registration request failure. The following identifies the two most common errors to look for in your diagnostic logs. These logs are the first thing that the Cisco TAC will require from you if you open a case with Cisco in regards to Expressway.Ĭ) Analyze the logs. There is also a > option available after diagnostic logging is complete. Note: there is an alarm active once you start your diagnostic log and it will disappear automatically when you stop the diagnostics. Make sure to check > which will generate a pcap file as well. This will help you see how the get_edge_config process between the Edge and Core servers is happening.ī) Now begin a diagnostic log and reproduce your problem.

STEP 3 Dig into the log files of Expressway.Ī) Start by digging into the Network logs and filter using >. NOTE: If both the main configuration and the Cisco Expressway-Edge and Core servers are active then proceed to Step 3 and start digging into the log files. STEP 2 Verify that the traversal zone between Cisco Expressway Edge and Core servers are >.ī) Verify the Cisco Expressway-Core server.Ĭ) Verify that Unified Communications status on Cisco Expressway-Core is enabled and configured. 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.

Cisco jabber for windows dns srv how to#

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.