Forum Discussion
Azure Bot not joining meeting - Server Internal Error. DiagCode: 500#1203002.@
This problem has been bothering me for about two weeks and I haven’t found a solution yet. I’d really appreciate your help. Environment Setup 1.Development Tool: Visual Studio 2022 2.Deploym...
To make it easier to identify the issue, here are some excerpts from the logs:
Logs after joining the meeting:
Nivedipa-MSFT
Microsoft
Microsoft@guoxl -
- You have correctly updated ServiceFqdn to "signaling.bottest.com" and verified your Nginx, certificate, AWS security group, and Windows Server configurations.
- The persistent error 500#1203002 still points to a Teams media platform connectivity or TLS/certificate issue.
- Key troubleshooting steps:
- Ensure your certificate's Subject Alternative Name (SAN) includes both signaling.bottest.com and media.bottest.com, not just *.bottest.com, as Teams media platform may require explicit SAN entries.
- Confirm that Nginx stream block for port 14217 supports both TCP and UDP (Teams media may use DTLS/UDP for media negotiation).
- Double-check that your certificate chain is complete and trusted by Microsoft Teams.
- Make sure your bot's public IP (InstancePublicIPAddress) matches the DNS record for signaling.bottest.com and is accessible from the Teams cloud.
- Review Application Insights and bot logs for any additional error details or handshake failures.
- For further troubleshooting, see:
If all configuration steps are correct and the error persists, try regenerating the certificate with explicit SANs for all required hostnames and ensure UDP 14217 is open and routed correctly.