Hey everyone, our team has been working with Genesys AudioHook, and we’re facing a challenge when trying to detect when the user hangs up (i.e., the disconnect is initiated by Genesys).
Specifically, we need to catch this event in AudioConnector and send data accordingly—whether in the disconnect message or via events (which can hold metadata, business intelligence, etc.). We’ve tried the following approaches:
-
Responding to a “close reason: end” with a disconnect, including the data we need to send.
-
Responding to a “close reason: end” with events that include the data we need to send, then following up with a normal “closed” response.
However, in all these scenarios, we don’t see anything reflected in AudioConnector.
Has anyone successfully captured a user-initiated disconnect and sent data towards AudioConnector in the process?
Is there a specific way to listen to these disconnects/events on AudioConnector, or a different approach we should take?
Would love to hear any insights from those who’ve dealt with this before!
Relevant documentation: