genbuilder | 2024-02-12 20:21:44 UTC | #1
Is there any best practice for following an AudioHook session on the server? The overview outlines that the conversation ID is given which is the existence of the parties such as IVR, agent, or even conference of agents.
https://developer.genesys.cloud/devapps/audiohook/session-walkthrough
There is this post from 2022 that outlines the conversation is the only info given and you need to query the API for more information.
https://developer.genesys.cloud/forum/t/genesys-audiohook-agent-details-conversation-api/16568
Is this the best practice to handle this? Session starts to the server from AudioHook and we keep querying the conversation ID to track changes? No push event in AudioHook that updates participants or webhook that notifies the server of a change to query?
tim.smith | 2024-02-12 20:26:33 UTC | #2
Yes, it is still the case that the audiohook feature is not an alternative to using the Platform API. The purpose of the audiohook feature is to deliver realtime audio streams. Looking up associated metadata remains the function of the Platform API. If you're looking to be notified to changes to certain things, use notifications and subscribe to the necessary topics.
genbuilder | 2024-02-12 21:08:04 UTC | #3
Thank you for the fast reply and confirming the assumption. It seems there maybe a few notifications topics that could alert of the conversation change vs having to over query multiple times for the status of the conversation.
system | 2024-03-13 21:08:35 UTC | #4
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 24601