microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

Bot deployed in AKS bot doesn't join the meeting with the MediaControllerConversationAddParticipantFailed error

Open
#380 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
253
Forks
275
Avg merge
1d 5h
Merged PRs (30d)
1

Description

Describe the issue
Hi all,
We try to deploy our bot to AKS by guide
https://github.com/microsoftgraph/microsoft-graph-comms-samples/blob/master/Samples/V1.0Samples/AksSamples/teams-recording-bot/docs/deploy/aks.md#create-bot-channels-registration

We had configured it, the bot is accessible by HTTP and can receive incoming events. When we try to send a join request on /joincall endpoint, we get a response 200 - OK. But then the Bot doesn't join the meeting. We get a MediaControllerConversationAddParticipantFailed error. But locally the Bot in a container works via ngrok.

Logs of the call attached below

Expected behavior
Bot joins to the meeting.

Graph SDK (please complete the following information):
Microsoft.Graph.Communications.Calls.Media v1.2.0.850
Microsoft.Skype.Bots.Media v1.17.0.39-alpha

Call ID
421f6800-891f-4653-b699-68c00f271beb
2020-12-01T13:23:22.0377961Z

Logs
$>2020-12-01T13:23:22.0377961Z Info: CommunicationsClientExtensions.cs:151 LogAndCreateResponse
ScenarioId: 7525100c-c9a6-46d5-95ea-60e6f3184edd
AppId: 6f1c9bf8-7c2f-4948-8cf9-0a36a0f0a5a5
AppName: InterprefyBot.Api
TransactionDirection: Incoming
TraceType: HttpRequest
request: POST https://teams-recording-bot-0.teams-recording-bot.teams-recording-bot.svc.cluster.local:9441/0/api/calling
headers:
X-Microsoft-Skype-Chain-ID: 63eb8077-af10-458a-be8d-6b8346609d1b
Scenario-Id: 7525100c-c9a6-46d5-95ea-60e6f3184edd
X-Microsoft-Skype-Message-ID: b7a2f3e8-dcd1-407e-aebf-5e65434b779c
Connection: close
Accept: application/json
Authorization: (redacted)
Host: teams-recording-bot-0.teams-recording-bot.teams-recording-bot.svc.cluster.local:9441
User-Agent: Microsoft-Skype/3.0,(Calling/1.0)
Content-Length: 977
Content-Type: application/json
{
"@odata.type": "#microsoft.graph.commsNotifications",
"value": [
{
"@odata.type": "#microsoft.graph.commsNotification",
"changeType": "deleted",
"resourceUrl": "/communications/calls/421f6800-891f-4653-b699-68c00f271beb",
"resource": "/app/calls/421f6800-891f-4653-b699-68c00f271beb",
"resourceData": {
"@odata.type": "#microsoft.graph.call",
"state": "terminated",
"resultInfo": {
"@odata.type": "#microsoft.graph.resultInfo",
"code": 500,
"subcode": 7112,
"message": "MediaControllerConversationAddParticipantFailed"
},
"chatInfo": {
"@odata.type": "#microsoft.graph.chatInfo",
"threadId": "19:meeting_NDI0ZDNjNWUtYmRiMy00YjI0LTkyY2EtODBkYTI2ZWZkNzBm@thread.v2",
"messageId": "0"
},
"meetingInfo": {
"@odata.type": "#microsoft.graph.organizerMeetingInfo",
"organizer": {
"@odata.type": "#microsoft.graph.identitySet",
"user": {
"@odata.type": "#microsoft.graph.identity",
"id": "c70c131e-a6fa-4055-b31a-6becebda54c9",
"tenantId": "1a33b323-4724-41a6-aef3-9645e3e92b3d"
}
}
},
"callChainId": "63eb8077-af10-458a-be8d-6b8346609d1b",
"id": "421f6800-891f-4653-b699-68c00f271beb"
}
}
]
}
$>2020-12-01T13:23:22.0248526Z Warning: NotificationDispatcher.cs:171 ProcessNotification
ScenarioId: 7525100c-c9a6-46d5-95ea-60e6f3184edd
AppId: 6f1c9bf8-7c2f-4948-8cf9-0a36a0f0a5a5
AppName: InterprefyBot.Api
No queue or registered callbacks for
Deleted: /communications/calls/421f6800-891f-4653-b699-68c00f271beb
$>2020-12-01T13:23:15.6816860Z Info: CommunicationsClientExtensions.cs:151 LogAndCreateResponse
ScenarioId: 7525100c-c9a6-46d5-95ea-60e6f3184edd
AppId: 6f1c9bf8-7c2f-4948-8cf9-0a36a0f0a5a5
AppName: InterprefyBot.Api
TransactionDirection: Incoming
TraceType: HttpRequest
request: POST https://teams-recording-bot-0.teams-recording-bot.teams-recording-bot.svc.cluster.local:9441/0/api/calling
headers:
X-Microsoft-Skype-Chain-ID: 63eb8077-af10-458a-be8d-6b8346609d1b
Scenario-Id: 7525100c-c9a6-46d5-95ea-60e6f3184edd
X-Microsoft-Skype-Message-ID: bbd4d985-40bf-48b0-b6de-5aebbfe892d5
Connection: close
Accept: application/json
Authorization: (redacted)
Host: teams-recording-bot-0.teams-recording-bot.teams-recording-bot.svc.cluster.local:9441
User-Agent: Microsoft-Skype/3.0,(Calling/1.0)
Content-Length: 834
Content-Type: application/json
{
"@odata.type": "#microsoft.graph.commsNotifications",
"value": [
{
"@odata.type": "#microsoft.graph.commsNotification",
"changeType": "updated",
"resourceUrl": "/communications/calls/421f6800-891f-4653-b699-68c00f271beb",
"resource": "/app/calls/421f6800-891f-4653-b699-68c00f271beb",
"resourceData": {
"@odata.type": "#microsoft.graph.call",
"state": "establishing",
"chatInfo": {
"@odata.type": "#microsoft.graph.chatInfo",
"threadId": "19:meeting_NDI0ZDNjNWUtYmRiMy00YjI0LTkyY2EtODBkYTI2ZWZkNzBm@thread.v2",
"messageId": "0"
},
"meetingInfo": {
"@odata.type": "#microsoft.graph.organizerMeetingInfo",
"organizer": {
"@odata.type": "#microsoft.graph.identitySet",
"user": {
"@odata.type": "#microsoft.graph.identity",
"id": "c70c131e-a6fa-4055-b31a-6becebda54c9",
"tenantId": "1a33b323-4724-41a6-aef3-9645e3e92b3d"
}
}
},
"callChainId": "63eb8077-af10-458a-be8d-6b8346609d1b",
"id": "421f6800-891f-4653-b699-68c00f271beb"
}
}
]
}
$>2020-12-01T13:23:15.5679426Z Warning: NotificationDispatcher.cs:171 ProcessNotification
ScenarioId: 7525100c-c9a6-46d5-95ea-60e6f3184edd
AppId: 6f1c9bf8-7c2f-4948-8cf9-0a36a0f0a5a5
AppName: InterprefyBot.Api
No queue or registered callbacks for
Updated: /communications/calls/421f6800-891f-4653-b699-68c00f271beb

Please help to resolve that issue. That is stopping us from going to prod. Thank you.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the deployment guide at Samples/V1.0Samples/AksSamples/teams-recording-bot/docs/deploy/aks.md, then trace the /joincall request and the attached MediaControllerConversationAddParticipantFailed logs. Compare the AKS deployment with the working local container setup; done means the deployed bot joins the meeting successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, kubernetes
Domain
cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.