Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: bulldozed on December 09, 2019, 03:30:50 AM

Title: Triggering an iHub request using a callflow step (connection.disconnect.hangup)?
Post by: bulldozed on December 09, 2019, 03:30:50 AM

Hi all,
Has anyone seen/utilized an example of calling an iHub request - not through an interceptor in the callflow, but by having a rolling background process of some kind detect that a call has hit an end-state result 'hangup' (connection.disconnect.hangup) I feel like there's something potentially in the example scripting command on the [url=https://docs.genesys.com/Documentation/GAAP/latest/iaHelp/UsingiHub]Using iHub[/url] documentation;

[color=maroon]context.sqlStoredProcedure(java.lang.String sConnectionName_p, int iTimeoutMillis_p, java.lang.String sStoredProcedureName_p, java.lang.Object... parameters_p)
[b]Run the specified stored procedure. [/b][/color]

but I honestly don't know enough about the ins-and-outs of custom scripting within this universe to know where to start playing.

Appreciate any direction that anyone can provide!

Title: Re: Triggering an iHub request using a callflow step (connection.disconnect.hangup)?
Post by: bulldozed on December 09, 2019, 04:55:08 AM

Rather than be one of those lurkers that asks and never circles back... a few hours passed and I tripped over the answer to my conundrum. Adding a [b]hangup[/b] action to the Defaults in default behaviour in my GAAP flow. That permits me to then call a routine at any occasion that the system catches the hangup outcome. Elegantly simple solution to my problem!