GVP Behind, IPCS Crash

[Gui75]

Hi Guys,

I was suprised to discover that when I use GVP Behind Sip Server, Voice Treatment Ports are always available even if IPCS crashes or IVR Server crashes.

So that my strategy considers the ports of this IPCS to be still available.

What is the best practice to handle such a case?

Regards

[René]

Hi,

Based on your description I assume Resource Manager is not used. In that case you should enable checking of port availability on SIP Server. There is a feature called "Active Out-Of-Service Detection" that allows SIP Server checking for availability of particular DNs (=IVR ports registered by IPCS). Please check SIP Server Deployment Guide for more information (option is called "oos-check"). OOS could be used for checking availability of IPCS only.

Handling IVR TServer crash isn't so easy as it doesn't affect GVP functionality directly - you will lose CTI features (Attached Data, CTI transfer etc.) on GVP side "only". The easier way to handle such situation (IVR TServer is down) is deployment of backup IVR TServer as it supports HA (warm standby only). Theoretically, you can try use IRD function "ServerStatus" to check status of IVR TServer from the strategy. I have no experience with that function but assume IVR TServer should be listed on Connection tab of URS application to make this function working properly.

Hope it helps you a bit
R.

[Gui75]

Thank you very much Rene. I did not know that it was possible to set oos-check in a voice treatment port.
And honestly , I did not think of using it ;-)

[Gui75]

But thinking of it. Is it really a good practive to have 150 voice treatment ports doing polling of IPCS.
Did you already saw such configuration  in production

[René]

Hi Gui75,

I have to apologize as I posted incorrect information . OOS checking isn't available for DN of type Voice Treatment Port thus can't be used for checking of availability of IPCS. Sorry for that. I thought it is supported for such scenario.

There is one solution left you can use - Resource Manager. It's GVP component that maintains status of IPCS and thus is able to detect failure of IPCS. Unfortunately, there is a delay between failure of IPCS and detection of it on Resource Manager side so it could happen that some calls will be routed to failed IPCS. It is necessary to modify routing strategy to use RM as well. You can find detailed "how-to" in the white paper "SIP Server 7.5.0 / GVP Integration
Behind Mode" available on Genesys TechSupport website.

Sorry again for confusing you
R.

[Gui75]

Thanks Rene, It is a pity to have to use Resource Manager just because of a limitation of IVR Server.
I saw that some option report-dn-status exist on IVR Server side to put IVR Port out of service when IPCS is lost.
But it only is supported in In Front Mode and it does not support IVR Load balancing...

I really think it would deserve a Feature Request to make it possible to use such an option in behind mode.

[René]

I think Genesys knows about that limitation and it has been solved in release 8.x. Resource Manager is mandatory component as it plays different and more important role than in release 7.6 allowing almost immediate detection of IPCS failure.

If there is no Resource Manager SIP Server has no way to detect failure of IPCS as IPCS subscribes for DNs provisioned as IVR ports only. You can try following but I can't guarantee it will work. It's just an idea:

1/ Create a new DN of type "Trunk" (you can try type "Voice over IP Service" as well) with contact address of IPCS
2/ Enable OOS checking for this trunk

Once SIP Server will detect failure of the trunk/VoIP service = IPCS is down - it might put DNs subscribed by this trunk/service as OutOfService. But it just an idea... Maybe IPCS will ignore OOS check messages thus failure detection won't be possible... Maybe SIP Server will ignore the fact subscriber isn't available...

R.