Allow Maximum Ring Timer Configurability for IVA Integration Workflow Nodes

Allow Maximum Ring Timer Configurability for IVA Integration Workflow Nodes. 

There is currently no ability to configure or limit the amount of time the RingCX platform attempts to connect to an IVA Integration Workflow node. The "Route" node includes a "Ring Duration" setting. This same setting would be very helpful to be configured for IVA integration nodes or within the admin portal IVA integration settings. 

Use case: If an IVA integration is working as normal and has no issues, the RingCX platform will hand the contact off to the IVA integration in milliseconds. However, if there is a connectivity issue with the IVA integration, the RingCX platform will attempt to connect to the IVA integration for 25-30 seconds before the workflow moves through the failure path. 

Impact: In the event of a connectivity issue with an IVA and a contact attempts to contact us via a workflow that includes the broken IVA integration, the contact is left waiting for nearly 30 seconds before their contact takes a workflow path that allows for the contact to be serviced by the workflow's fallback / failure path. This leads to an increase in abandons. 

Testing: I verified the 25-30 second connection attempts to a broken IVA integration by creating an intentionally broken IVA integration (With an intentionally incorrect SIP URI in the IVA Integration settings) and implemented that IVA integration in a RCX workflow. On each connection attempt, I had to wait 25 - 30 seconds before my contact would move down the failure / fallback path. 

Please allow for a maximum ring timer or maximum connection attempts setting for IVA integrations in either the RingCX Workflow IVA Integration Node or in the Admin Portal IVA Integration Settings.