10-19-2016 10:54 PM - edited 03-17-2019 06:26 PM
Hi Community,
We have implemented Jabber clients and works internally.
We want to deploy also users outside the company. We deploy Expressway Core and Edge and integrated with CUCM. B2B calls are working fine but MRA doesn't work. We tested Jabber for windows PC to login outside the network via Expressway but fails. On the Expressway Edge, i cannot see any logs that the user is trying to login. Required certificates for Expressway-C and E were loaded. UCM traversal zone for MRA is active on Expressway.
We have created SRV records on the external DNS and did test on TAC tool and shows result below: (Domain and FQDN for Edge masked)
_collab-edge SRV record was created and pointed to Expressway Edge FQDN. Do we need to create SRV records _cisco-uds and _cuplogin on the external DNS also? What troubleshooting steps need to take? Please advice. Thank you.
10-20-2016 01:35 AM
Hi,
Please complete the checks as per the following guide for troubleshooting MRA login issues
http://www.cisco.com/c/en/us/support/docs/unified-communications/expressway/118798-technote-cucm-00.html#anc5
Manish
10-20-2016 09:29 AM
Thank toy for your reply. I'm little bit confused with the item 1?? It says the _cisco-uds and _cuplogin SRV records should be created on external DNS pointing Expressway Edge FQDN?
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:
10-20-2016 09:48 AM
No, you don't need those SRVs on the external network, the MRA configuration guide explains what SRVs are required, and where they're needed.
What you need to review are the EXP-E and EXP-C logs when you try to login, as well as a PRT from that Jabber client.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide