<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-family: Calibri, sans-serif; ">
<div>
<div>
<div style="font-size: 14px; ">Hi Jason, </div>
<div><br>
</div>
<div>627583127 looks to be a WAAS SR. Is there a UCCX/CUCM SR? I'll take a look. </div>
<div><br>
</div>
<div>At any rate, when the phone registers, CTI Manager should send a message to the JTAPI client on UCCX. JTAPI will update its state machine to recognize that the phone is now in service. At any time later, if you come along and login to CAD, the state machine
is checked. CUCM is not contacted to verify phone state upon logging into CAD. Since you're on 8.6(2a)SU2, you're past many of the well know CTI bugs that may cause this. </div>
<div><br>
</div>
<div>If you want to enable the JTAPI debugs (Unified CM Telephony Client) with DEBUG in the top box and all EXCEPT MISC_DEBUGGING in the bottom box and just bounce the phone, you can search by the device name and see if UCCX is being notified of the phone going
down and then back up. If there is nothing in the JTAPI client logs for the device name, look into the CM/CTI Manager traces on CUCM as there may be a disconnect between CCM and CTI services especially if the phone is registered to another node than the primary
CTI provider for UCCX. </div>
<div><br>
</div>
<div>Send me the JTAPI logs and the device name/DN and I'll take a look. </div>
<div style="font-size: 14px; "><span class="Apple-style-span" style="font-size: 15px; "><br>
</span></div>
<div style="font-size: 14px; ">
<div>Thank you, </div>
<div><br>
</div>
<div>Ryan LaFountain</div>
<div>Unified Contact Center</div>
<div>Cisco Services</div>
<div>Direct: +1 919 392 9898</div>
<div>Email: rlafount@cisco.com</div>
<div>Hours: M – F 9:00am – 5:00pm</div>
</div>
</div>
</div>
<div style="font-size: 14px; "><br>
</div>
<span id="OLK_SRC_BODY_SECTION" style="font-size: 14px; ">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>"Jason Aarons (AM)" <<a href="mailto:jason.aarons@dimensiondata.com">jason.aarons@dimensiondata.com</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, October 8, 2013 2:04 PM<br>
<span style="font-weight:bold">To: </span>"cisco-voip (<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>)" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
<span style="font-weight:bold">Subject: </span>[cisco-voip] Anyone running 8961s with UCCX 8.5.1SU3?<br>
</div>
<div><br>
</div>
<div xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Anyone running 8961s with UCCX 8.5.1SU3?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Customer indicated they setup some 8961s and after logging into CAD they get an error;<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><img width="533" height="270" id="Picture_x0020_2" src="cid:image001.png@01CEC42D.8CBB7170" alt="cid:image001.png@01CEC42D.8CBB7170"><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">CCM 8.6.2.22900-9 and UCCX 8.5.1SU3<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">These are 8961s running sip8961.9-3-4-24<span style="color:#1F497D"> seems other model phone’s are fine.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">They’ve had TAC case 627583127 open for awhile.<o:p></o:p></p>
</div>
</div>
</div>
</span>
</body>
</html>