限制临时会议的MCU访问 [英] Limit MCU access of ad-hoc conferences

查看:92
本文介绍了限制临时会议的MCU访问的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

是否可以限制对会议的多个MCU的访问,以及如何?

Is it possible to limit the access to multiple MCUs of a conference, and how??

我的应用正在创建一个临时会议,我想要仅允许IM!对于预定的会议,我知道可以使用ConferenceScheduleInformation完成此操作并添加特定的McuType。但是,临时会议怎么可能呢?

My app is creating an ad-hoc conference, for which I want to allow IMs only! For a scheduled conference, I know that this can be done with ConferenceScheduleInformation and add a specific McuType. But how is it possible fo ad-hoc conferences??

推荐答案

我不相信。从根本上讲,安排会议然后加入会议之间没有太大区别,而不是在会话中进行临时会议。临时会议有8小时到期,因此您可以将
ConferenceScheduleInformation中的内容与其他设置进行匹配,然后在安排后立即加入。
I don't believe so. Fundamentally there is not much difference between scheduling a conference and then joining it, as opposed to doing an ad-hoc conference on a conversation. Ad-hoc conferences have an 8 hour expiry so you can match that in your ConferenceScheduleInformation, along with your other settings, and then join it immediately after scheduling it.


这篇关于限制临时会议的MCU访问的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆