[cisco-voip] Can MRA work with old UCM configured with IP addresses?

[Dana Tong]

I’ve reconfigured it all to use FQDN and re-configured my nodes. And I’m logged in okay now and MRA is working.

Cheers
Dana


From: NateCCIE <nateccie at gmail.com>
Sent: Thursday, 2 April 2020 12:45 PM
To: Dana Tong <dana.tong at yellit.com.au>
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Can MRA work with old UCM configured with IP addresses?

I know I have done one MRA with IPs, back when MRA was new. You still need the Cisco Uds srv record to be there and that record needs to be resolvable my the C.

That old system isn’t using MRA right now, so I don’t know if it’s changed in newer versions of expressway.
Sent from my iPhone


On Apr 1, 2020, at 8:13 PM, Dana Tong <dana.tong at yellit.com.au<mailto:dana.tong at yellit.com.au>> wrote:

Hi all,

I have a customer who was installed some 9 years ago and the hosts were all configured with IP address instead of FQDN. They’re up on UCM 10.5(2) now and I have spun up Expressway X12.5.7.
The UC Traversal zone is up and running. The Expressway’s have certificates installed.
However I am hitting issues with getting the edge config and signing in. I get the usual “cannot communicate with server” when I try to login with Jabber.

I’ve tried changing some things such as configuring the UCM, IM&P, Unity servers in Expressway-C by IP or FQDN and have had some varying results on the Collaboration Solution Analyser. Sometimes its downloads the user UDS configuration and sometimes it doesn’t.

Is MRA do-able with the UCM using IP address? Or am I going to have to bite the bullet and reconfigure all the devices to use FQDN for their clustering? Or is there some kind of easy fix?

Cheers
Dana

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200402/bfa8f0e0/attachment.htm>