URS Failover - Stat Server Connectivity Best Practice

Hi All,

I have an ORS strategy in which I interact with stat server and URS directly for routing. I attempt to fetch statistics from both primary and backup stat servers and that works fine. However when I fail URS over to the backup while Stat server is in primary mode URS backup tries to communicate with Stat server primary and routing starts to fail b/c no agents appear available. Is there a way to keep these in sync so that when URS goes into backup it looks to the stat server backup ?

My first thought was to try both URS primary and backup by injecting a fully qualified http URL in srcexpr for a fetch to URS.
But then I will be making all routing calls 2X and it seems dirty.

<session:fetch requestid=“App_setAgentOrderExpression[‘requestid’]” srcexpr=“‘urs/call/@’ + system.InteractionID + ‘/func/SetIdealAgent’” method=“‘urs’” timeout=“30”>

</session:fetch>

I was curious how other people are handling this situation in an ORS strategy ? How to you keep URS/Stat server HA failover in sync ?

I aprreciate any feedback.

Thanks!

Hi,

“However when I fail URS over to the backup while Stat server is in primary mode URS backup tries to communicate with Stat server primary and routing starts to fail b/c no agents appear available”

The Data in Stat server is not related to the dependent applications (URS. Agent Desktop application) Mode of working.
For Example , When Primary URS is switched over, Obviously as you mentioned , the Backup URS Becomes Primary . The Backup URS Requests the Same Primary Stat server for Statistical Data. There should not be any Wrong data communicated by Primary stat server when requested by Backup URS.

If So, then Check the connections between backup URS and Stat server , so that communications are happening fine.

Regards,
Raja.

After working with genesys support I found the solution was a setting in URS

pickup_calls = true

when this is true, after a urs failover the next backup node starts to answer the calls.