microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Bot fails to establish call – 500#1203002 after Establishing (app-hosted media)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
Product: Microsoft Graph Cloud Communications API / Teams Calls & Meetings – Application-hosted media bot
Issue: Call joins (state: Establishing) but immediately terminates with Server Internal Error. DiagCode: 500#1203002. The bot never reaches state Established and does not appear in the meeting.
Request: Please confirm whether 500#1203002 indicates a service-side restriction or certificate/CA requirement for app-hosted media, and what we need to change (if anything) on our side.
3. Environment & Versions
| Item | Value |
|---|---|
| OS | Windows (Azure VM) |
| .NET | .NET 8.0 |
| Microsoft.Graph | 5.103.0 |
| Microsoft.Graph.Communications.Calls | 1.2.0.15690 |
| Microsoft.Graph.Communications.Calls.Media | 1.2.0.15690 |
| Microsoft.Graph.Communications.Client | 1.2.0.15690 |
| Microsoft.Skype.Bots.Media | 1.33.0.258-preview |
| Hosting | Azure VM (Windows), app listening on HTTPS 443 and media port 8445 |
4. Bot / Tenant Configuration (redact secrets)
| Setting | Value |
|---|---|
| Tenant ID | df94721f-849a-4439-bac1-3575268e60f5 |
| App (Client) ID | bf954344-4a7c-487f-8783-97ff96268da4 |
| App Secret | (configured in app – do not include in ticket) |
| Bot base URL | https://vidur-bot-dns.eastus.cloudapp.azure.com |
| Callback URL | https://vidur-bot-dns.eastus.cloudapp.azure.com/callback |
| Media instance public IP | 20.120.23.47 |
| Media instance public port | 8445 |
| Media instance internal port | 8445 |
| Certificate thumbprint | 63FAA24B9D6FA49304E865B6199B39DEF1AEDF8B |
| Certificate subject | CN=vidur-bot-dns.eastus.cloudapp.azure.com |
| Certificate key type | CSP (RSACryptoServiceProvider) |
Graph permissions (application, admin-consented):
Calls.JoinGroupCall.All, Calls.AccessMedia.All (and any other calling permissions you have added).
Azure Bot / Teams channel:
Calling enabled; Webhook (for calling) = https://vidur-bot-dns.eastus.cloudapp.azure.com/callback.
5. Error Details
| Field | Value |
|---|---|
| Result code | 500 |
| Subcode | 1203002 |
| Message | Server Internal Error. DiagCode: 500#1203002.@ |
| Call state when it occurs | Call is in Establishing, then transitions to Terminated with the above resultInfo. |
Example call ID (from our logs):
25005d80-b798-4edc-bdc5-cb3fde570439
(You can include the most recent call ID from your logs.)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the application-hosted media configuration, including the HTTPS callback on port 443, media endpoint on port 8445, certificate details, and the Microsoft Graph Communications package versions listed in the issue. Compare the Establishing-to-Terminated transition and resultInfo 500#1203002 with the relevant service or SDK guidance; done means identifying whether the cause is service-side or configuration-related and documenting the required change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- api, backend, cloud
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100