Category: API, Informational
Summary: Voice interactions have two ending states. "disconnected" which is used when an interaction has ended but audio may still be connected, and "terminated" when audio has ended and the interaction is officially complete. Historically the "terminated" state has been suppressed for interactions that ended normally. To support a wider variety of clients, including soft-phones and WebRTC clients, we are correcting the suppression of the "terminated" state to allow it to be present in all cases. All voice interactions will initially go through the "disconnected" state as the interaction ends, but will now also finish in the "terminated" state once audio has been terminated, regardless of how the call ends.
Impact: Since clients have always had to handle both "disconnected" and "terminated" there is no impact expected. As long as the client is able to interpret either correctly there are no changes needed. This change will cause all voice interactions to end in the "terminated" state regardless of whether they end in error. Any clients that were distinguishing between these two states, particularly on the error vs. no-error difference should recheck to ensure that they have the correct behavior.
Date of Change: October 15th 2018
Impacted APIs:
Any conversation or analytics APIs that are used to return data about voice media, particularly after that media has disconnected.