v2.6.42Latest

Live transcription on Microsoft Teams no longer goes silent after its first event. Integrators streaming transcripts or audio into Teams meetings, and anyone relying on the bot's entry message in Teams chat, should read on; the API surface is unchanged.

⚡Improvements

• session.started on the live transcription stream is now sent when the transcription session actually opens, with the first audio from the meeting, instead of at connect time. Integrations that wait for it get a later but accurate readiness signal.
• If the transcription session drops repeatedly mid-meeting, the stream now emits an error event (transcription_session_failed) instead of staying open with no further events. See Streaming.

🐛Bug Fixes

• Live transcription (streaming_config.mode: "transcription") on Teams delivered a single session.started and then no transcript.segment for the rest of the meeting when the bot took more than 30 seconds to get into the call, for example through a waiting room or a signed-in account. The session now opens on the first audio and reopens automatically if the provider closes it, so segments arrive for the whole meeting.
• Audio streamed into a Teams meeting through the bot no longer sounds choppy when the sender pauses briefly. Playout starts with a 500 ms buffer, so short gaps in the incoming stream are absorbed instead of heard as silence by participants.
• Teams bots no longer skip the entry message when the meeting chat panel takes a few seconds to appear. The bot keeps looking for the chat control for up to 25 seconds before deciding chat is unavailable.

↩ All releases