> On 11 Jul 2018, at 23:20, Anthony Holloway
> wrote:
>
> Put a piece of black tape on your monitor where the IP should be; that's what
> my dad did to fix the check engine light.
Well, we happened to have a complete shutdown of our datacenter last night,
which meant the whole cluster was r
I have several clusters, all of them I can go to
https://x.x.x.x:8443/cucm-uds/version and get back
https://10.132.160.20:8443/cucm-uds/version";
version="11.5.1">11.5.1false
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-ud
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)
Subject: CallManager 11.5.1SU4 UDS web page times out
I have several clusters,
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 b
To all the people who say: "What is this, a Windows server that I have to
reboot?", yes, sometimes you have to reboot these things. It may not be
the direct fault of the OS, but at the same time, you are not given the
full access/knowledge necessary to restart specific problematic processes
Cisco
Did someone say "reboot?"
On Thu, Jul 12, 2018 at 8:31 AM Brian Meade wrote:
> 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) <
https://www.zdnet.com/article/a-lesson-for-the-cloud-100-percent-uptime-achieved-for-16-years/
---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56
Hallo Group
What are the steps, challanges and risks if I switch a CUCM 10.5 cluster
from mixed mode back to no secure.
I have to do that because I need IP phone autregistration back.
Thanks a lot
Regards Reto
___
cisco-voip mailing list
cisco-voip@puck
What about upgrading to 11.5? from 11.5 auto-registration in mixed mode is
supported.
https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200716-CUCM-Auto-registration-Process-In-Mixed.html
2018-07-12 19:24 GMT+02:00 Reto Gassmann :
> Ha
Hi Daniele
I‘d love to upgrade to 11.5 but there are some compatibility issues (eg
UCCE) that do not allow me to upgrade right away.
daniele visaggio schrieb am Do. 12. Juli 2018
um 22:14:
> What about upgrading to 11.5? from 11.5 auto-registration in mixed mode is
> supported.
>
>
> https://w
Did you use tokens or the tokenless process?
On Thu, Jul 12, 2018 at 4:40 PM Reto Gassmann wrote:
> Hi Daniele
>
> I‘d love to upgrade to 11.5 but there are some compatibility issues (eg
> UCCE) that do not allow me to upgrade right away.
>
> daniele visaggio schrieb am Do. 12. Juli
> 2018 um
I changed from Token to tokenless a few weeks ago. So now it‘s tokenless
Brian Meade schrieb am Do. 12. Juli 2018 um 23:31:
> Did you use tokens or the tokenless process?
>
> On Thu, Jul 12, 2018 at 4:40 PM Reto Gassmann wrote:
>
>> Hi Daniele
>>
>> I‘d love to upgrade to 11.5 but there are som
All IP phones have a no secure profile.
We replace the old 7960/61 with 8851 and plan to use MigrationFX to ease
the process. Our integrator now informed us, that we have to set the
cluster to no secure for that.
Brian Meade schrieb am Do. 12. Juli 2018 um 23:31:
> Did you use tokens or the toke
13 matches
Mail list logo