Skip to content
← RingCX

How can we improve RingCX?

RingCX: Agent & supervisor experience

Categories

Expose API data when a call is connected

We recently ran into an issue where a configured Start Recording node in an Agent Script was triggering before the ADD SESSION event. This caused the recording event to fail, and the call would not be recorded. We solved this by adding a half second forced wait in the agent script. It would be beneficial to expose this information in Audit Logs or similar when the call connects, so that if this were to happen again it would be easily diagnosable.

3 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Colby Jestes shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
New  · 

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Todd commented  ·   ·  Report

    In addition to logging when the call connects or that the recording fails, please provide a way within the script to be sure the Session is properly built and the recording node will succeed. We've upped the time to 3/4 of a second and still miss around 2.5% of the calls due to the race condition.