The Queue to Agent node is easy to use. In your case, set it to "explicit" and choose agent 1 explicitly from the drop-down box.
Both ports (the X and the check) would lead to the next Queue to Agent which would be set to agent 2. Don't check the box that says "queue to agent even if logged out".
So you will be queuing to agent1, but since the check port (success) does not incorporate any Run Ext Script, it will not wait for agent1 - if agent1 is not available it will just move on to agent2. Same thing here with Queue to Agent (agent2), with both ports going to a Queue to Agent (agent3).
Now both ports go to a Queue to Skill Group with a skill group which each of your three agents belong to - with the Run Ext Scripts in a loop thus waiting until someone becomes available.
So the preferential treatment will target a free agent, but queue if all are busy, and then any of the three will get the call.
Just check the scripting guide for Queue to Agent usage.
Queue to Agent as Geoff mentioned is a great option but there are reporting ramifications in an environment where everyone expects reporting at the SkillGroup level. If that doesn't apply than it's a moot point and definitely the quickest to deploy. If that is an issue an alternative is below.
You could build 3 distinct skills and then use separate Queue to SkillGroup nodes? This way if the pool of agents increases and you have for example 2 agents that can take those calls first you would simply update their skill rather than updating scripting. Of course the flipside to that is if you add a 4th agent who needs to be selected as the last resort on availability.
When you refer to LAA are you using the actual LAA node? What version of UCCE are you running?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...