[PsiBot Example] Bot call getting deleted automatically after getting established.
还没有人认领这个 Issue。
评估
调研方向
从 Samples/PublicSamples/PsiBot 开始，复现本地加入会议的流程，然后检查 Deleted 通知及其 resultInfo 代码。将设置和调查结果与 issue #828 进行比较。完成标准是确定已建立的通话为何会被删除，并记录经过验证的修复方案或所需配置。
由索引模型根据 Issue 内容生成。
描述
We are trying to solve for a business problem, where we need to generate real-time captions/transcript for an ongoing teams meeting. For this I am using PsiBot example. I am trying to set this up first on my local following steps described here https://github.com/microsoftgraph/microsoft-graph-comms-samples/tree/master/Samples/PublicSamples/PsiBot.
When I try to join the meeting, as soon as call is established it is deleted with error message "Server Internal Error. DiagCode: 500#1203002.@".
I found a thread with similar issues here "https://github.com/microsoftgraph/microsoft-graph-comms-samples/issues/828" and have followed suggestions provided by ssulzer but no luck.
Sharing below notification message that I got as part of "Deleted" call. Please let me know if more details are needed I will be happy to help:
Accept: application/json
Accept-Encoding: (redacted)
Authorization: (redacted)
Host: 6d6b2eb931f6.ngrok-free.app
User-Agent: Microsoft-Skype/3.0,(Calling/1.0)
Scenario-Id: 9bc666c4-6902-49fb-be32-5a2cb202e9da
Traceparent: (redacted)
X-Forwarded-For: (redacted)
X-Forwarded-Host: 6d6b2eb931f6.ngrok-free.app
X-Forwarded-Proto: https
X-Microsoft-Skype-Chain-Id: fcecd617-77b5-4e5b-81d1-15f3f15f49a6
X-Microsoft-Skype-Message-Id: 9872d750-4b1b-4d9f-aee8-66501bc0f7ed
Content-Type: application/json
Content-Length: 979
{
"value": [
{
"changeType": "Deleted",
"resourceUrl": "/communications/calls/06004580-2a58-4f6e-a599-e7361515ee21",
"resource": "/app/calls/06004580-2a58-4f6e-a599-e7361515ee21",
"resourceData": {
"@odata.type": "#microsoft.graph.call",
"callChainId": "fcecd617-77b5-4e5b-81d1-15f3f15f49a6",
"chatInfo": {
"@odata.type": "#microsoft.graph.chatInfo",
"messageId": "0",
"threadId": "19:meeting_OTc1YmY3NzgtZTE2ZS00OGIzLTkwMDYtYzNhODZlNjNjMWU1@thread.v2"
},
"meetingInfo": {
"@odata.type": "#microsoft.graph.organizerMeetingInfo",
"organizer": {
"@odata.type": "#microsoft.graph.identitySet",
"user": {
"@odata.type": "#microsoft.graph.identity",
"tenantId": "599254d5-5f95-4f88-9bda-70ccd1dfe125",
"id": "5f9a1b6c-2dc7-4875-a5df-d6c3fb15399f"
}
}
},
"resultInfo": {
"@odata.type": "#microsoft.graph.resultInfo",
"code": 500,
"message": "Server Internal Error. DiagCode: 500#1203002.@",
"subcode": 1203002
},
"state": 8
}
}
]
}
- 主要语言
- 没有语言数据
- 星标
- 252
- 派生
- 276
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
microsoftgraph/microsoft-graph-comms-samples 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 5/5 一周以上 新手友好度 25/100
microsoftgraph/microsoft-graph-comms-samples#871 · 5 条评论 ·
-
难度 4/5 3-5 天 新手友好度 30/100
microsoftgraph/microsoft-graph-comms-samples#870 · 11 条评论 ·
-
难度 5/5 一周以上 新手友好度 20/100
microsoftgraph/microsoft-graph-comms-samples#869 · 1 条评论 · 1 个 reaction ·
-
难度 4/5 3-5 天 新手友好度 45/100
microsoftgraph/microsoft-graph-comms-samples#868 · 1 条评论 ·
查看 microsoftgraph/microsoft-graph-comms-samples 的全部 Issue
相似的 Issue
-
[Bug]: Telegram bot (v3.11.0): "Ban log" no longer sends the current 3xipl-banned.log可能已有人在做 @HamedSanaei 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
developmentseed/titiler-cmr#270 ·
维护者通常 1 天内回复
-
agent-butler-finding bug
难度 2/5 1-3 小时 新手友好度 82/100
jordansmall/spindrift#6107 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复