<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-size: 14px; font-family: Calibri, sans-serif; ">
<div>
<div>
<div>Hi Scott, </div>
<div><br>
</div>
<div>I filed the bug you reference, so am familiar with it. There were a couple of changes in the CUCM versions since 8.x. </div>
<div><br>
</div>
<div>The first is what you've described whereby you should now associate an EM profile to a CTI Provider Application User instead of the physical phone. This was added in 8.x. You have already stumbled upon the first use for recording users, but it was also
intended to be more efficient when configuring large Contact Center deployments where there were many agents that could use multiple phones but only certain amounts on shift at a time, etc. The reasoning behind the improvement is the same in both cases. </div>
<div><br>
</div>
<div>Under the hood, CUCM actually associates the physical device to the Application User upon EM login, so the application (recording server, UCC) gets notified the same as if you associated the physical phone to the user in prior versions. This hoteling scenario
is reversed upon EM logout. </div>
<div><br>
</div>
<div>Hope this helps. </div>
<div><br>
</div>
<div>
<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><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<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>Scott Voll <<a href="mailto:svoll.voip@gmail.com">svoll.voip@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, November 20, 2012 1:28 PM<br>
<span style="font-weight:bold">To: </span>"<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] CTI architectural Change? 8.x<br>
</div>
<div><br>
</div>
<div>
<div>When I was at Cisco Live this year, unfortunately I didn't spend much time with UC stuff so I'm guessing I missed it.
<div><br>
</div>
<div>Was there an architectural change in 8.x with CTI integration where cisco moved away from associated phone and moved to using EM profiles?</div>
<div><br>
</div>
<div>I stumbled across this with a Bug in CCx (CSCtx48427) where that was the work around.</div>
<div><br>
</div>
<div>We were greatly concerned about a problem we are having with recording users, were we only need about 200 users to have recording capability but they want to use any phone. So we though we were going to have to associate over 1600 phones and were concerned about
taxing the CM in the process.</div>
<div><br>
</div>
<div>All testing so far shows that just using the EM Profile works. This would decrease the Load on our CM cluster and stream line the setup process significantly.</div>
<div><br>
</div>
<div>This this a Real change I can bank on moving forward?</div>
<div><br>
</div>
<div>TIA</div>
<div><br>
</div>
<div>Scott</div>
</div>
</div>
</span>
</body>
</html>