v2.6.6
Fewer unknown speakers, and proper status codes on Teams invitation errors
- 2improved
- 2fixed
Transcripts that lost a real speaker to the bot's own timeline now fall back to the transcription provider's view, and a meeting's opening utterances are attributed rather than left unknown. Teams invitation failures also return a meaningful HTTP status instead of a generic server error.
Improvements
- When the bot's own speaker timeline collapsed two people into one, the transcription provider's speaker separation is used instead. This works with whichever provider you have configured.
- The final speaker timeline is assembled from the best source for each stretch of the meeting, which removes the run of unattributed utterances that could open a transcript.
Bug Fixes
- Errors from the Microsoft Teams invitation API are returned as
401,403or404with detail, instead of a500that said nothing about the cause. - Links in support notification emails point at the right ticket.