简体   繁体   English

在Android上使用WebRTC实施Kurento Client

[英]Implementing Kurento Client with WebRTC on Android

I'm trying to implement WebRTC on an android device supporting API 22 and I'm trying to connect to Kurento Media Server to establish media server capabilities. 我正在尝试在支持API 22的Android设备上实现WebRTC,并且试图连接到Kurento Media Server以建立媒体服务器功能。 For my application Server layer, I'm trying to utilize a Java Server based on Tomcat, and this is implementing a Kurento Client API to connect to the Kurento Media Server. 对于我的应用程序服务器层,我正在尝试利用基于Tomcat的Java Server,并且这正在实现Kurento Client API以连接到Kurento Media Server。 The issue I am having is understanding how to go about establishing a connection between the Android device and Kurento and doing a media transfer after the connection has been authorized by the Application Server and a SDP response has been processed by the Kurento Client initialized on the Application/Signaling Server. 我遇到的问题是了解如何在Android设备和Kurento之间建立连接以及在应用程序服务器授权了连接并且Kurento客户端已在应用程序上初始化处理了SDP响应之后进行媒体传输/信令服务器。 I came across Kurento Android SDK (Kands) but the repositories are missing sources on Maven and Gradle. 我遇到了Kurento Android SDK(Kands),但是存储库缺少Maven和Gradle上的源。 Any help here in implementing the WebRtc.org stack with Kurento would be appreciated! 在这里用Kurento实现WebRtc.org堆栈的任何帮助将不胜感激!

KANDS will not help you much for several reasons. KANDS不能提供多大帮助,有几个原因。 First, it is an outdated and unmaintained project. 首先,这是一个过时且未维护的项目。 Second, with the setup you describe, I think you'd be barking at the wrong tree. 其次,使用您描述的设置,我想您会误入歧途。 In your case, the signalling that should be implemented in your Android client, should be between the client and your app server. 在您的情况下,应在您的Android客户端中实施的信号应该在客户端和您的应用服务器之间。 As you can see in the following image, which depicts your proposed setup, your client will be connecting to an app server using your own signalling protocol, and it is you app server the one in charge of controlling KSM. 如下图所示(描述了建议的设置),您的客户端将使用您自己的信令协议连接到应用服务器,并且应用服务器是控制KSM的负责人。

带有控制KMS的应用服务器的描述架构

In this way, you can implement all your business logic in the app-server, and you'll be able to make upgrades in the media part, shielding your clients by hiding the underlying implementation. 这样,您可以在应用程序服务器中实现所有业务逻辑,并且可以在媒体部分进行升级,通过隐藏基础实现来保护客户。 The only thing that you'll need, is to get the SDP offer from your client to the KMS (going through your app server), have the KMS process that offer, and send the answer back to your client. 您唯一需要做的就是将SDP报价从客户端发送到KMS(通过您的应用服务器),进行KMS报价,然后将答案发送回客户端。

With this setup, you'll also have the posibillity to connect Android clients to any other type of webrtc capable clients, such as browsers. 通过此设置,您还可以将Android客户端连接到其他任何具有webrtc功能的客户端,例如浏览器。

KANDS was discontinued and SDk for android is only used for them to develop customized apps. KANDS已停产,SDk for android仅用于他们开发定制的应用程序。 Then we switched to webview also. 然后我们也切换到了webview。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM