Weird.  You can try updating the _cisco-uds DNS entries to use 443 as a
workaround.

I'm guessing rebooting doesn't get the service to listen on 8443?

On Thu, Jul 12, 2018 at 9:07 AM Jason Aarons (Americas) <
jason.aar...@dimensiondata.com> wrote:

>
>
> More info, I see UDS is listening on :443 but not :8443 as the Jabber PRT
> shows client is requesting
>
>
>
>
>
> *From:* Jason Aarons (Americas)
> *Sent:* Thursday, July 12, 2018 6:40 AM
> *To:* cisco-voip (cisco-voip@puck.nether.net) <cisco-voip@puck.nether.net>
> *Subject:* CallManager 11.5.1SU4 UDS web page times out
>
>
>
> I have several clusters, all of them I can go to
> https://x.x.x.x:8443/cucm-uds/version and get back
>
> <versionInformation uri="https://10.132.160.20:8443/cucm-uds/version";
> version="11.5.1"><version>11.5.1</version><capabilities><usersResourceAuthEnabled>false</usersResourceAuthEnabled></capabilities></versionInformation>
>
>
>
> However I have a new cluster I just built and instead I get back
> Connection Timed Out on https://x.x.x.x:8443/cucm-uds/version
>
>
>
> What am I missing?  Jabber clients won’t connect was the start to this
> problem.
>
>
>
> Jason Aarons, CCIEx2 No. 38564
>
> Advanced Technology Consultant
>
> Dimension Data
>
> 904-338-3245
>
>
>
>
> This email and all contents are subject to the following disclaimer:
> "http://www.dimensiondata.com/emaildisclaimer";
> <http://www.dimensiondata.com/Global/Policies/Pages/Email-Disclaimer.aspx>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to