Table of Contents

Media Bridge

The Cloud Communications "application-hosted media" path — receiving raw RTP audio for a call — is Windows-only. A non-Windows engine therefore cannot terminate the media session itself. The media bridge is the Windows-hosted component that does the media work while the engine keeps doing Graph call control over plain HTTPS.

What it does

  1. Accepts a media session: POST {mediaHostUrl}/media/sessions.
  2. Returns the opaque appHostedMediaConfig.blob that Graph requires on the call.
  3. Opens an audio WebSocket and streams decoded 16 kHz mono 16-bit PCM frames.
  4. Feeds the PCM into Azure Speech Services continuous recognition.
  5. Publishes settled, speaker-diarized transcript segments onto an in-process live feed.
flowchart LR
  Graph["Microsoft Graph call control"] --> Bot["Meeting bot"]
  MediaBridge["Media Bridge"] --> Bot
  Bot --> Feed["MeetingTranscriptFeed"]
  MediaBridge --> Speech["Azure Speech recognizer"]
  Speech --> Feed

The bridge was extracted from Automaton's TypeScript meeting-* modules as a .NET 8 service. It is a language migration and repository extraction, not a feature build-out. Teams is the only provider.

Deployment shape

  • The media bridge must run on a Windows host.
  • The call-control engine can run elsewhere; it joins and leaves the call over HTTPS and delegates the media session to the bridge.
  • The bridge needs network access to Microsoft Graph, the Teams media endpoint and Azure Speech.

Security

  • Treat the media session blob and the bridge URL as short-lived secrets.
  • Scope Graph permissions to the minimum needed for the call-control path.
  • Audio is production customer content. Do not log raw PCM, transcripts or speaker identities beyond what the feature requires.
  • Never commit the Teams app credentials or the Azure Speech key.

Operational notes

  • A missing or expired media session should fail the call cleanly; do not leave a ghost participant in the meeting.
  • The transcript feed is in-process. If the consuming service restarts, the feed is lost; the call-control engine must re-establish the session.
  • Choose a Windows App Service plan or a Windows VM with enough network egress for the audio stream.