Share via

Microsoft Skype Bots Media .NET Framework 4.8 compatibility

CG 40 Reputation points
2026-03-04T00:20:34.7233333+00:00

Hi,

We are building a Microsoft Teams compliance recording bot using the Graph Communications Calling SDK and BotMedia SDK (v1.31.0.225).8

We have a working implementation on .NET Core 6 and .NET Core (Kestrel), but we need to integrate the Teams recording functionality into an existing .NET Framework 4.8 application.

During testing we found that the BotMedia native media engine does not bind its UDP port (8445) when running under .NET Framework 4.8, even though all signaling works correctly. The call is answered successfully but Teams drops it after ~4 seconds with DiagCode 3003#7106 (media connectivity failure).

We confirmed this by checking active UDP listeners - the port is never bound under .NET Framework 4.8, but works correctly under .NET 6.

Our questions:

  1. Is the BotMedia SDK (Microsoft.Skype.Bots.Media) officially supported on .NET Framework 4.8, or is .NET Core/.NET 6+ required?
  2. Is there a supported way to host the BotMedia SDK in a .NET Framework 4.8 process?
  3. If .NET Framework is not supported, is out-of-process hosting (separate .NET 6 executable communicating via IPC) the recommended integration pattern for mixed-runtime environments?

Thank you

Microsoft Teams | Development
Microsoft Teams | Development

Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs

0 comments
Answer accepted by question author
  1. Teddie-D 12,845 Reputation points Microsoft External Staff Moderator
    2026-03-04T02:18:55.16+00:00

    Hi @CG 

    Thank you for posting your question in the Microsoft Q&A forum. 

    The BotMedia SDK (Microsoft.Skype.Bots.Media) targets net472, which includes .NET Framework 4.7.2 and later versions such as .NET Framework 4.8. Therefore, .NET Framework 4.8 is within the supported target framework range. This can be confirmed on the NuGet package page: NuGet Gallery | Microsoft.Skype.Bots.Media 1.33.0.258-preview. 

    This information is provided as a convenience to you. These sites are not controlled by Microsoft, and Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please ensure that you fully understand the risks before using any suggestions from the above link. 

    While .NET Framework 4.8 is supported from a targeting perspective, most current samples and production deployments use .NET 6+, which is the modern and recommended runtime. 

    There is no Microsoft documentation prohibiting hosting the Media SDK inside a .NET Framework 4.8 process. However, you must comply with the application-hosted media bot constraints: 

    -Must run on Windows Server.  

    -Must run in supported Azure hosting models (VM, VMSS, Service Fabric, AKS).  

    -Cannot run as Azure Web App.  

    -Must have public internet accessibility.  

    -Must allow required UDP port ranges.  

    Although .NET Framework is supported within the target framework range, out-of-process hosting (for example, running the media stack as a dedicated .NET 6 service and integrating via IPC) is a commonly adopted production architecture in mixed-runtime systems. Microsoft does not mandate this pattern explicitly, but it aligns with their guidance that media bots are resource-intensive, calls are pinned to a single machine, and media services should scale and operate independently.  

    Reference: Build Application-hosted Media Bots - Teams | Microsoft Learn.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".    

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.