[cisco-voip] UCCX 10.6 | CUCM 10.5.2 | CAD Extension out of service

[Ryan Huff]

Hi Abhiram, thank you for your reply.

No mixed mode has not been enabled. This is a new stock build of 10.6, so the COP file hasn't even been installed.

So far, I have taken Justin's advice and disabled LRO and and added a 2nd vCPU to each CUCM node. In my local testing, I haven't had the issue happen yet. So we'll have to see going forward.

Thanks,

Ryan 
From: akramadh at cisco.com
To: ryanhuff at outlook.com; jsteinberg at gmail.com
CC: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] UCCX 10.6 | CUCM 10.5.2 | CAD Extension out of service
Date: Wed, 10 Jun 2015 01:15:06 +0000






Hi Ryan,



CAD support shouldn’t be an issue and I don’t see this to be related to the mixed mode too. Either way, do you have agents(not the same) running both CAD and Finesse in your system? If the issue started after mixed mode was enabled, can you shut down Finesse
 and monitor this?



The error you are talking about is typical when the CTI handle on the phone is lost/removed. So a TAC case should be the best way forward, and CAD ‘support' is not going away anytime soon :) Let me know how it goes. 





Regards,
Abhiram Kramadhati
Technical Solutions Manager, CBABU
CCIE Collaboration # 40065







From: Ryan Huff <ryanhuff at outlook.com>

Date: Tuesday, 9 June 2015 10:40 pm

To: Justin Steinberg <jsteinberg at gmail.com>

Cc: Cisco VOIP <cisco-voip at puck.nether.net>

Subject: Re: [cisco-voip] UCCX 10.6 | CUCM 10.5.2 | CAD Extension out of service







Hi Justin, thank you for your reply.



CUCM 10.5.2su1 is in the active partition on all nodes (10.5.2.11900-3). 



LRO is interesting; my elastic sky version is 5.5 and according to the DocWiki (http://docwiki.cisco.com/wiki/Disable_LRO) it seems to only be an issue with 4.1 and more specifically, with CUCM < 8.6 with
 ESXi 4.1. I've also seen several UC evangelical sites proclaim that LRO needs to be disabled where ever Virtual Cisco UC runs, versions be damned.



I'm in pre-flight, so now is definitely the time to power down and knock LRO off.



I guess I am more interested in the why at this point (plight of an engineer). I suppose this issue (if it is even an issue) will self-heal itself in v11 when CAD is no longer an option, but still plenty of need to support existing CAD.



This is the first time I used this version mix (UCCX 10.6 | CUCM 10.5.2su1 | CAD), and I haven't ran into this issue before.



Thanks for any thoughts you put into this.



-Ryan







Date: Tue, 9 Jun 2015 07:41:46 -0400

Subject: Re: [cisco-voip] UCCX 10.6 | CUCM 10.5.2 | CAD Extension out of service

From: jsteinberg at gmail.com

To: ryanhuff at outlook.com

CC: cisco-voip at puck.nether.net



Are you on UCM 10.5.2su1 ?   I haven't seen that issue at all.
Is your VMware LRO disabled ?
Do your UCMs have one or two vCPU ?
On Jun 9, 2015 12:42 AM, "Ryan Huff" <ryanhuff at outlook.com> wrote:



Has anyone been noticing that in this environment (UCCX 10.6 | CUCM 10.5.2 | CAD); extensions will sometimes report as OutOfService (and subsequently cause CAD login issues) when in fact, the phone is registered, associated to the jTAPI/RMCMSubsys
 user, has CTI Control enabled (and is setup correctly in all other respects)?



What seems to resolve this issue for me; is to super copy the phone to a fake mac address, delete the original and then re-mac the newly created device. Doing a cluster reboot seems to address this as well.



This is a new 2 cluster build. Everything about the phone seems to function fine within call manager when CAD is having a login issue. I've changed the addressing mode on the phone (and CTI ports) to ipv4 only, turned JAL off on the phone. Just really odd and
 not very easy to define.



I know CAD is near death and Finesse is the future, but I have to support CAD in this scenario.



Thanks,



Ryan





_______________________________________________

cisco-voip mailing list

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/20150610/e28c317b/attachment.html>