Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: cmpark on February 14, 2017, 05:37:40 AM

Title: How to configure Business Continuity?
Post by: cmpark on February 14, 2017, 05:37:40 AM
hi
How to configure Business Continuity?
dr-forward not working.
Title: Re: How to configure Business Continuity?
Post by: Kubig on February 14, 2017, 07:01:41 AM
According to available documentation  ;)
Title: Re: How to configure Business Continuity?
Post by: Adam G on February 14, 2017, 09:08:05 AM
[quote author=cmpark link=topic=10135.msg45943#msg45943 date=1487050660]
hi
How to configure Business Continuity?
dr-forward not working.
[/quote]

A very broad question - please be more specific
Title: Re: How to configure Business Continuity?
Post by: cmpark on March 02, 2017, 05:27:16 AM
2 SIPServers, 2 URServers - HQSIPServer, S1SIPServer, S1SIPServer, S1URServer

SIP Endpoint registerd 2 SIPServers with Dual Registration.

First call arrived Routing Point at HQSIPServer, and waiting agents
Second call arrived Routing Point at S1SIPServer, and wiating agents,

Agent changed status to 'Ready'

2SIPServer(2URServer) attempt to routing call at same time

one call routed correctly, but other call routing failed.


Title: Re: How to configure Business Continuity?
Post by: Dionysis on March 02, 2017, 03:46:40 PM
That sounds like it's your URS configuration, not necessarily BCP.

Search the documentation for setting up multi site URS, you need to have agent reservation configured, and URS's connected to a dedicated message server so the 2 can communicate with each other about which agents they are targeting.

A second option would be to have your 2 URS's configured as an HA pair and then only 1 URS would control both SIP Servers (but that's not technically correct BCP config).


Title: Re: How to configure Business Continuity?
Post by: n3vek7 on March 02, 2017, 04:35:43 PM
Agree with Dionysis, the best thing would be to have a HA Pair of URS instead of 2 different URS running. They will always compete for the same interaction if they receive a RouteRequest for the same interaction.
Title: Re: How to configure Business Continuity?
Post by: Dionysis on March 02, 2017, 06:16:27 PM
That's not quite what I meant.  The correct way is to have an HA pair of URS's for each BCP site, and use agent reservation and dedicated message servers to make sure there is no issue with both pairs trying to route to the same agent.  It is similar to configuring URS for load balancing.

But... you can get away with only 1 HA pair with one on each site... For a production environment this is not the recommended approach though.

Title: Re: How to configure Business Continuity?
Post by: cmpark on March 03, 2017, 01:28:56 AM
Thanks Dionysis.
I will test it.

But other problem happened.

Call arrived at HQSipServer,

Endpoint is registerd only S1SipServer (single registration)

How to check other SipServer  endpoint status - is thant dr-forwading?

in my lab test, HQSIPServer occured 404 not found
Title: Re: How to configure Business Continuity?
Post by: cmpark on March 06, 2017, 06:08:20 AM
2 URServers connected each SIPServer.

Option agent_reservation=implicit

The problem is that URS does not communicate with each other.

If SIPServer is configured uniquely, you can use agent reservation.
However, since there are two SIPServers each, there is no agent reservation.
Title: Re: How to configure Business Continuity?
Post by: cmpark on March 06, 2017, 06:11:39 AM
If there are waiting calls on different sipservers, and the agent changes to the ready state,
one call is routing normaly, but other call routing failed.

received from 65203(hqsip1)hqsip1.nhis.com:3000(fd=) message EventError
(This agent is already reserved by some other server)
AttributeErrorMessage 'This agent is already reserved by some other server'
AttributeErrorCode 1700
AttributeReferenceID 34
AttributeThisDN '15771000'
AttributeTimeinSecs 1488780021 (15:00:21)
AttributeTimeinuSecs 136652
AttributeEventSequenceNumber 0000000000000107

request to 65203(hqsip1) message RequestUpdateUserData
AttributeReferenceID 36
AttributeUserData [17] 00 01 01 00..
'PegDEF' 1
AttributeConnID 007d029b69600002
AttributeThisDN '15771000'

request to 65203(hqsip1) message RequestRouteCall
AttributeReferenceID 37
AttributeReason [14] 00 01 01 00..
'RTR' 132
AttributeRouteType 1 (RouteTypeDefault)
AttributeExtensions [49] 00 02 00 00..
'CUSTOMER_ID' 'Resources'
'SWITCH' 'Switch_본부'
AttributeOtherDN ''
AttributeConnID 007d029b69600002
AttributeThisDN '15771000'