Hi guys
I am facing an issue and only solution seems to be different URS for each segment of agent groups. Why? Because of verification-time and other URS unique parameters.
So, what should I have to consider? I have never done this scenario. So far I know I have to take care of event_arrive option on each RP that I want to control for each TServer/URS combination
[/size]
[/size]Any suggestions?
Of course, agent groups for each one would be unique, like one URS for Inbound and other for Outbound
Regards[size=15px]
Hey,
we used to use LDS for distribution of load with URS as well as just having stand-alone URS for different groups. On top of the verification time, it is important that you use agent-reservation and the same Stat Server! I cannot emphasize this enough: same Stat Server is a must.
As for event_arrive, it is not mandatory. At least, I do not recall it being so, unless you want to set up priority for your URS so that in case one URS crashes, you have your other URS pick it up. I would definitely suggest looking into it.
But, in practice, why in the world would you want to have two URS target the same agent group?
I believe event_arrive would help him actually, since he wants different URS acting on different RPs, right Cav? In that case, you set event_arrive to “none” on the RP under the section containing the name of the URS that you DONT want to route on that RP.
And what about licenses?
Will both share the same flexlm and won’t be rejected?
Enviado de meu E6633 usando o Tapatalk
There shoudn’t be any issues. As per Licensing Guide, page 70:
- The value of router_seats corresponds to the maximum number of concurrently enabled places for routing of interactions.
- This comprises agent places and also IVR ports in cases when they are represented as places for the purpose of routing.
- Each URS instance has the whole amount of router_seats licenses to its disposal.
Oh
Duh
Thanks! Forgot to read my documentation [emoji14]
Enviado de meu E6633 usando o Tapatalk