如果视频流出，则电话会议的升级会挂起

本文介绍了如果视频流出，则电话会议的升级会挂起的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述 29岁程序员，3月因学历无情被辞！ 我正在针对UISuppression模式下的Lync 2013,32位客户端SDK开发自定义客户端。 Lync版本为15.0.4701.1000，而SDK DLL为15.0.4603.1000（ms.lync.model.dll）和15.0.4481.1000（MS.lync.utilities.dll）。测试是针对Office 365订阅的。双向音频和视频的点对点呼叫工作正常。如果我与两个以上的参与者一起开始或者我不播放我的视频，电话会议也可以正常工作。但是，如果我正在播放我的视频，并且如果我将第三个人添加到点对点通话，从而升级为电话会议，我的应用就会挂起。我可以使用SDK中的AudioVideoConversation示例重现这一点。I am developing a custom client against the Lync 2013, 32-bit client SDK in UISuppression mode. Lync version is 15.0.4701.1000 while the SDK DLLs are at 15.0.4603.1000(ms.lync.model.dll) and 15.0.4481.1000(MS.lync.utilities.dll). Testing is against an Office 365 subscription. Point-to-point calls with two-way audio and video work fine. Conference calls also work fine if I start them with more than two participants or if I don't stream my video out. However, if I am streaming my video out and if I add a third person to a point-to-point call, thus escalating to a conference call, my app hangs. I can reproduce this with the AudioVideoConversation sample from the SDK.无论我发起呼叫并添加第三人或是否有其他人给我打电话然后添加第三个参与者，都会发生这种情况。为简单起见，我正在测试后一种情况，即其他人打电话给我，然后添加第三个参与者。因此，为了重现，在MS Lync客户端和您自己的（或AudioVideoConversation示例客户端）之间建立双向视频呼叫，然后从MS lync客户端对话添加第三方。自定义客户端的lync进程将挂起。This happens whether I originate the call and add the third person or whether someone else calls me and then adds a third participant. For simplicity, I'm testing against the latter case, i.e. someone else calls me and then adds a third participant. So to reproduce, establish a two way video call between an MS Lync client and your own (or the AudioVideoConversation sample client) and then add a third party from the MS lync Client end of the conversation. The custom client's lync process will hang.我为ParticipantAdded，ModalityChanged和对话的PropertyChanged添加了一些调试。挂起似乎发生在会话的Reserved3属性更改后。如果我只查看音频对应物，那么接下来要发生的事情应该是是对话的ConferencingLocked属性的变化，应该变为False，所以我假设我的会议在某种程度上被锁定为True视频输出案例。请注意，在添加第三个参与者之前，这是相当多的，甚至在之前，原始的两个参与者的AV模态已转换为保持。I added some debugging for ParticipantAdded, ModalityChanged, and conversation's PropertyChanged. The hang seems to happen after the Reserved3 property of the conversation changes. If I look at the audio only counterpart, then the next thing to happen should be a change in the ConferencingLocked property of the conversation which should go to False, so I'm assuming somehow my conference is locked at True in the video out case. Note that this is quite a bit before the third participant is added and even before the original two participants have their AV modalities transitioned to Hold.这是两个序列的比较： 等....etc....对此的任何帮助将不胜感激。再次注意，我也可以使用SDK中的AudioVideoConversation示例重现这一点。如果我比较非视频流成功案例与视频流失败案例之间的* .UccApilog文件，lync进程似乎在两个方向的渲染上下文被缓存之后和CUccAudioVideoSessionParticcipant2之前挂起:: UpdateChannels电话。Any assistance with this will be greatly appreciated. Again, note that I can reproduce this with the AudioVideoConversation sample from the SDK as well. If I compare the *.UccApilog files between the non-video-streaming success case vs. the video-streaming failure case, the lync process seems to be hanging after render context for both directions have been cached and before the CUccAudioVideoSessionParticcipant2::UpdateChannels call.问候， RxJx0推荐答案 这是Lync 2013 SDK中的已知问题。 如果视频在p2p呼叫中处于活动状态并且添加了第三个参与者，则会将呼叫升级为会议，这将触发Lync客户端崩溃，并随后挂起SDK应用程序。This is a known issue within the Lync 2013 SDK.  If video is active in a p2p call and a 3rd participant is added, escalating the call to a conference, it will trigger a crash of the Lync client, and subsequently hang the SDK app too.解决方法是在SDK应用程序触发时，在升级之前停止视频。 当远程用户触发升级时，没有好办法防止崩溃。Workaround is to stop video before escalating, when triggered by the SDK app.  When escalation is triggered by the remote user there is no good way to prevent the crash.如果您可以与Microsoft打开支持案例并提供业务影响声明，则有助于确定优先级解决这个问题。If you can open a support case with Microsoft and provide the business impact statement, it will help to prioritize fixing this. 这篇关于如果视频流出，则电话会议的升级会挂起的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！ 上岸，阿里云！