URS switchover in hotstandby mode

[New...]

Hi,

We have sipserver + GVP behind switch deployment. All components run in hot standby mode. When URS is restarted, the backup server becomes primery and once the primary is UP - we would like to know whether the calls waiting in queue would be still handled by backup URS or will it be dropped? In the backup URS, eventerror is thrown with "Invald Connection ID"

PRIMARY URS:
=========
1:41:20.544 Std 04505 Disconnected from TServer 'SIPTServer_Primary'
1:41:20.544_G_I_ [14:1] server SIPTServer_Primary is being closed, socket xxxxx
1:41:20.560_T_W_ [14:13] calls for tserver SIPTServer_Primary[SIPSwitch] will be deleted
1:41:20.560_M_I_00f401ef10000e1d [17:11] VQ 03fad980 first available call: 00f401ef10000e1d, reason=treatment
1:41:20.560_M_I_00f401ef10000e1d [17:11] VQ 03fad980 first available call: 00f401ef10000e1d, reason=treatment
1:41:20.560_M_I_00f401ef10000e1d [13:03] call (virtual queue 04acd0b0, id=154595, priority 132) doesn't wait for VQ 03fad980 (name="English") now
1:41:20.560_M_I_00f401ef10000e1d [17:11] VQ 03fad980 first available call: none, reason=binding
1:41:20.560_M_I_00f401ef10000e1d [13:03] call (virtual queue 04a0e480, id=154596, priority 142) doesn't wait for VQ 03fad980 (name="English") now
1:41:20.560_I_I_00f401ef10000e1d [01:08] call deleting truly
CALL (00f401ef10000e1d) HISTORY ( Dropped ):

[René]

Hi,

Backup URS should pick up these calls and restart routing strategy assigned to Routing Point on which call sits. It may happen in some situations that call is default routed.

Please look at URS Deployment Guide when you can find more details about URS behavior.


R.

[New...]

Thanks, Rene. From the guide, i understood that default routing / ignore is applicable only in warm standby mode and in hot standby mode, if we have the HA license and the option pickup calls set to true, then the strategy would be replayed. We have set up these settings. Correct me if my understanding is wrong

[René]

If you post here logs of primary and backup URS (debug level) then I can check for you what's happened.

R.

[René]

Hi,

I did quick scan of provided logs and it looks OK. See my comments below:

1/ 'Invalid connection id' error is caused by URS trying to delete 'RTargetAgentGroup' User Data key after a call was released/abandoned. There is an article in Genesys Knowledge base saying that this error can be safely ignored... Things are not perfect

2/ I found lot of calls being default routed as there is no strategy loaded on target RP (look for text 'routed to default'). You should check your configuration and fix this unless it's by purpose

3/ I checked a few interactions and backup URS replays routing strategy after switchover so HA works correctly.

R.

[Learnmore]

Thanks, Rene. The Initial RPs are same as the PRI numbers and in all RP - we have given default DN as one particular RP and only in that the strategy is loaded. Thats the reason there are so many default routing messages.