I just wondered if anyone had configured this in their environment? We have a number of different URS, with a 1-1 relationship with T Servers for inbound calls in a Network environment, eg my environment has 4 NTS, each NTS connected to a single URS. There are multiple premise sites, with a common pool of virtual agents.
Load balancing is carried out on a ‘round robin’ basis, so I don’t necessarily need to load balance with the URS…
HOWEVER, when an agent becomes available, obviously each URS will attempt to reserve the agent for a call they have in the queue, so self-awareness would (if I’ve read it correctly) seek to reduce the number of clashing reservations.
yeah, you are missing something… transition_time is fine on a single URS… but in the latest v7.6 incarnation, URS now supports telling OTHER connected URS about certain things, including broadcasting out agent reservations, to prevent other URS from trying to reserve the same agents…
Thanks though, but transition_time wasn’t what I meant!
I am actually reading upon it right now. It sounds like something really interesting. Until now, I relied on agent_reservation; however, it does cause several URS to vie for the same agent and we see quite a few reservation fails in T-Server logs. I just took it for granted, since I figured URS would just find another agent right away… Other than sounding like a cool feature, I still cannot get my mind wrapped around how this would actually improve something…