Cisco Cisco Expressway Fehlerbehebungsanleitung

customers face during the deployment phrase.

Cisco recommends that you have knowledge of these topics:

Cisco Unified Communications Manager (CUCM)

• 

Cisco Expressway Core

• 

Cisco Expressway Edge

• 

Cisco IM and Presence (IM&P)

• 

Cisco Jabber for Windows

• 

Cisco Jabber for MAC

• 

Cisco Jabber for Android

• 

Cisco Jabber for iOS

• 

Security Certificates

• 

Domain Name System (DNS)

• 

The information in this document is based on these software and hardware versions:

Video Communication Server (VCS) Version X8.1.1 or later

• 

VCS Control & Expressway/Expressway Core & Edge

• 

CUCM Release 9.1(2)SU1 or later and IM & P Version 9.1(1) or later

• 

Cisco Jabber Version 9.7 or later

• 

This symptom can be caused by a wide range of issues, a few of which are outlined here.

For a Jabber client to be able to log in successfully with MRA, a specific collaboration edge SRV record must
be created and accessible externally. When a Jabber client is initially started, it makes DNS SRV queries:

_cisco−uds: This SRV record is used in order to determine if a CUCM server is available.

1. 

_cuplogin: This SRV record is used in order to determine if an IM&P server is available.

2. 

_collab−edge: This SRV record is used in order to determine if MRA is available.

3. 

If the Jabber client is started and does not receive an SRV answer for _cisco−uds and _cuplogin and does
receive an answer for _collab−edge, then it uses this answer to try to contact the Expressway−E listed in the
SRV answer.

The _collab−edge SRV record should point to the Fully Qualified Domain Name (FQDN) of Expressway−E
with port 8443. If the _collab−edge SRV is not created, or is not externally available, or if it is available, but