They should not be recieving another call from the que while they are on a que call.

I have the busy triggers set to 1 but it still tries to send them another call and marks them not ready

for ring no answer 0 sec

You could check in the JTAPI traces if the RmCm Notifies the CUCM that the line been in use, that could be the issue.

HTH

Please rate this post if was helpful

Walter Solano

CCNA Voice

Cisco UCCX Specialist

I am having them log into the phone with extension mobility and using agent desktop.

Could this be an  issue the ques I have that are not using Ext mobility do not have this problem

I have run into this before on previous versions of UCCX.

1. Make sure your busy triggers are set to 1 (which it sounds like you have)

2. Make sure your device profiles have the IPCC extension as the first line.

3. Check your phones and make sure you do not have the agent's IPCC extension set on the phone that the agent is logging into.

In my case it was a misplaced step in the queuing process in my scripts.

HTH
Brett

When I removed ext mobility out of the process and tied the icd ext directly

to the phone the issue changes to the agent going back and forth between reserved and ready

for a couple of minutes or until they recieve a call or go not ready

I have read that you can only have one appearance of the DN for your IPCC extension (which would apply either with or without Extension Mobility). You mention Extension Mobiility, and it has the option of logging out other appearances when you log in to a new phone. That would probably be a good idea.  ...just thinking out loud. Curious if you already found a solution.