Genesys Cloud - Developer Community!

hi  @Jason Schlotterback, 

Based on my experience with the Embeddable Framework, I don't believe mute/unmute is exposed through the standard Interaction change events the same way that hold is. The HELD state is part of the interaction lifecycle, so it is surfaced through the Interaction subscription model, whereas mute appears to be handled as a client-side telephony control and not as an interaction state change. 

I've seen the same behavior where mute activity is visible in the browser console logging, but no corresponding event is delivered through the change subscription for type: "Interaction". 

Unless someone from Genesys can point to a newer API/event hook, my understanding is that there is currently no supported Embeddable Framework event specifically for mute state changes. If displaying mute status in a third-party application is a requirement, you may need to:

• Maintain the mute state yourself when triggering mute/unmute actions from your integration.
• Inspect available SDK/framework events beyond the standard Interaction subscriptions.
• Consider whether the use case would be better served through newer desktop extensibility options (such as Composable Desktop components) if available in your environment. 

I'd also be interested to hear if anyone from Genesys has found a supported way to subscribe to mute state changes directly.