Success! Subscription added.
Success! Subscription removed.
Sorry, you must verify to complete this action. Please click the verification link in your email. You may re-send via your profile.
代码如下:
//IceServer ice;
//ice.urls.push_back("stun:61.152.239.56");
//ice.username = "";
//ice.password = "";
//std::vector<IceServer> ice_servers;
//ice_servers.push_back(ice);
// configuration_.ice_servers = ice_servers;
std::string token = getToken(myUrl); // http://192.168.1.92:3001/CreateToken
if (token != "") {
std::lock_guard<std::mutex> lock(callback_mutex_);
room->Join(token,
[=](std::shared_ptr<User> user) {
//cout << "Join succeeded!" << endl;
SetDlgItemText(IDC_EDIT1, L"Join succeeded!");
},
[=](unique_ptr<ConferenceException> err) {
SetDlgItemText(IDC_EDIT1, L"Join failed!");
}
);
}
Link Copied
Hi
对于Join 方法的successful callback or error callback 都是工作正常的, 3.4 包括最新的3.5 都是好的。
不清楚你那边还有什么特殊的配置吗? 能提供一下MCU 的配置, Client 的配置 和测试场景复现步骤。
Yanbin Z. (Intel) wrote:
Hi
对于Join 方法的successful callback or error callback 都是工作正常的, 3.4 包括最新的3.5 都是好的。
不清楚你那边还有什么特殊的配置吗? 能提供一下MCU 的配置, Client 的配置 和测试场景复现步骤。
我也遇到这个问题了。我的特殊配置是用demo去调用getToken访问非https的场景
您好,我也遇到相同的問題。
目前Client端採用版本是 : CS_WebRTC_Client_SDK_Windows.v4.0,於介面端輸入 MCU 位址 : http://192.168.0.199:3001/CreateToken,介面端無任何反應。於程式端,發現出錯於ConfSampleMFCDlg.cpp 程式中第501行 "room->Join(token, ",如附件影片。
另外已建置MCU Server (CS_WebRTC_Conference_Server_MCU.v4.0.Ubuntu) ,透過 Chrome 輸入 https://192.168.0.199:3004 ,可接收到攝影機畫面資訊。
目前用了 CS_WebRTC_Client_SDK_Windows.v4.1,遇到同样问题,链接的是sioclient.lib。例子程序中访问3001端口,但调试输出日志里面显示 “(conferencesocketsignalingchannel.cc:166): Socket.IO reconnecting”。
Community support is provided Monday to Friday. Other contact methods are available here.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
For more complete information about compiler optimizations, see our Optimization Notice.