Its been a while since I've set this up but I'm fairly certain the rmcm user just need to be associated with the device (IPC or phone) not the device profile, the agents extension (in the DP) obviously needs to be associated with the agents account as the IPCC extension or they won't show up as a resource in UCCX. Makes sure all the EM phones (IPC in your case) are associated and you should be fine. Also make certain that the DN in the EM profile is not a shared line in the system or its not going to work.<div>
HTH</div><div>Ted<br><br><div class="gmail_quote">On Mon, Jan 25, 2010 at 6:32 PM, Ratko Dodevski <span dir="ltr"><<a href="mailto:rade239@gmail.com">rade239@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi, I have a problem. We have several PCs with rotating agents in shifts. I've set extension mobility for them and they need to login to the IP Communicator in order to work. The problem is that in order to login do UCCX Desktop Agent application, there device needs to be associated with the RmCm application user. Well, I've found that device profiles for extension mobility can't be associated :((( any ideas on how can I resolve this issue???<div>
<br></div><div>Thanks<br clear="all"><br>-- <br>Ratko<br>
</div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>