" /> Central Agent Reservation - Genesys CTI User Forum

Author Topic: Central Agent Reservation  (Read 2814 times)

Offline Dimitry

  • Newbie
  • *
  • Posts: 41
  • Karma: -1
Central Agent Reservation
« on: December 01, 2016, 05:15:42 PM »
Advertisement
Hi Genesys wizards

I would like to implement agent reservation for blend handling . Currently the setup handles Voice routing in a separate URS Server and Email Routing in a separate URS. Because of this when a agent is of blend mode , the same agent is reserved for same place and race condition occurs.

The Voice has a 4 URS connecting and load balanced by LDS which connects to T-server.  THe IXN has one URS  connected . Now the plan is to have a central T-server which will handle all the agent route request.  What all the connections I need to establish ?  and what are the options i need to set in the Central T-server ?  Please help

Offline terry

  • Sr. Member
  • ****
  • Posts: 328
  • Karma: 35
Re: Central Agent Reservation
« Reply #1 on: December 01, 2016, 10:18:31 PM »
If it is about "central T-server which will handle all the agent RESERVATION requests" then
this tserver
- must be in connection list of all URSes,
- must have option agent_reservation (in section __ROUTER__) set to true

If this tserver has switch with RPs then measures need to be taken to block URSes from attempt to route
this tserver's calls (and use tserver only for agent reservation).
Blocking for example can be done by making URS not see calls on this tserver (option event_arrive=none on tserver in section with name __ROUTER__ ) or my making URS ignore calls on this tserver (do not load any strategy on this tserver's RPs for the routers and set option unloaded_cdn=ignore on tserver in section with name __ROUTER__ )



Offline Dimitry

  • Newbie
  • *
  • Posts: 41
  • Karma: -1
Re: Central Agent Reservation
« Reply #2 on: December 02, 2016, 05:39:36 AM »
Thanks Terry

Is _ROUTER_ section essential .. I guess it is for router awareness . Would Option agent_reservation =true alone is not sufficient?

Also do I need to connect the routing stat servers to this dedicate T-Server?
« Last Edit: December 02, 2016, 07:09:48 AM by Dimitry »

Offline terry

  • Sr. Member
  • ****
  • Posts: 328
  • Karma: 35
Re: Central Agent Reservation
« Reply #3 on: December 02, 2016, 09:17:36 PM »
section name __ROUTER__ must be with 2 underscores on every side.
Using of this section is sort of shortcut - when URS looks for some option in other application (like TServer)
it checks first the section with the same name as URS application itself and if not found it tries section with name __ROUTER__.  Either you need to create in tserver applications the section for every involved URS where you put the option or instead use generic URS section (__ROUTER__). 

No need to change any statserver connections.

Offline Dimitry

  • Newbie
  • *
  • Posts: 41
  • Karma: -1
Re: Central Agent Reservation
« Reply #4 on: December 26, 2016, 12:40:47 PM »
Will there be any impact to ICON reporting when we do central agent reservation ?  Is any additional reports that will be sent to ICON ?