apprtc | Please use the Dockerfile to run your own test/dev instance | Continuous Deployment library

 by   webrtc JavaScript Version: v1.1 License: BSD-3-Clause

kandi X-RAY | apprtc Summary

kandi X-RAY | apprtc Summary

apprtc is a JavaScript library typically used in Telecommunications, Media, Media, Entertainment, Devops, Continuous Deployment, Nodejs, Docker applications. apprtc has no vulnerabilities, it has a Permissive License and it has medium support. However apprtc has 11 bugs. You can download it from GitHub.

NOTE: This project is no longer served via See Docker for local dev/testing deployment.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              apprtc has a medium active ecosystem.
              It has 3957 star(s) with 1371 fork(s). There are 242 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              There are 111 open issues and 343 have been closed. On average issues are closed in 163 days. There are 12 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of apprtc is v1.1

            kandi-Quality Quality

              apprtc has 11 bugs (0 blocker, 0 critical, 8 major, 3 minor) and 233 code smells.

            kandi-Security Security

              apprtc has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              apprtc code analysis shows 0 unresolved vulnerabilities.
              There are 24 security hotspots that need review.

            kandi-License License

              apprtc is licensed under the BSD-3-Clause License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              apprtc releases are available to install and integrate.
              Installation instructions, examples and code snippets are available.
              apprtc saves you 4344 person hours of effort in developing the same functionality from scratch.
              It has 9204 lines of code, 712 functions and 103 files.
              It has medium code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of apprtc
            Get all kandi verified functions for this library.

            apprtc Key Features

            No Key Features are available at this moment for apprtc.

            apprtc Examples and Code Snippets

            No Code Snippets are available at this moment for apprtc.

            Community Discussions

            QUESTION

            API Documentation for WebRTC Android Library
            Asked 2020-Oct-19 at 14:23

            I'm learning WebRTC and I have found its JavaScript documentation quiet good. But then, I want to work with webrtc on Android. So I found this page. After Adding the libraries I cannot find documentation like it is for JS. There is AppRTC but then I find it confusing rather than expressive (that might be my own problem, not sure).

            So where do I go for documentation for Android WebRTC library? Is there any tutorial or simple reference that is valid as of 2020? Many data I have found are 5 or more years, and seems outdated.

            ...

            ANSWER

            Answered 2020-Jun-01 at 15:25

            I found very useful Github Project. Two years old as of 2020, but very informative and simple. Once you get the basics of WebRTC you can dive on the code. This works well in conjuction with WebRTC Codelab

            Source https://stackoverflow.com/questions/62099618

            QUESTION

            AppRTC: iOS to Android Call is not working
            Asked 2020-Jul-13 at 09:07

            We are developing an app using AppRTC. Audio and Video call from iOS-iOS and Android-Android are working fine but whenever we try to call from android to iOS or iOS to android, nothing happens after the call is accepted.

            We have tried using the same Video codec (H264) on both android and iOS but the issue still persists.

            Any assistance in this matter is highly appreciated.

            ...

            ANSWER

            Answered 2020-Jul-13 at 09:07

            There are couple of things you can do to solve this issue:

            1. See if you are using https://apprtc.appspot.com instead of https://appr.tc, you should use https://appr.tc for latest AppRTC.
            2. Make sure you use "H264 Baseline" or "H264 High" video codec on android side as iOS supports H264 codec only.
            3. Keep the following class updated with AppRTC github code PeerConnectionClient.java on android
            4. Use latest AppRTC code on both iOS and Android

            Source https://stackoverflow.com/questions/62219309

            QUESTION

            Can't access camera from Android webView (chrome frame) in context of webRTC
            Asked 2020-May-22 at 18:53

            App is based on webRTC vs websocket . Android studio 2.3.2 last version.

            I already use:

            https protocol , autoplay , android version 7.0 (min > android 5.0) . App works on all supported browsers only android webview generate error.

            This is first lines of errors log in logcat (android studio last ver):

            E/chromium: [ERROR:audio_manager_android.cc(264)] Unable to select audio device! E/cr_VideoCapture: allocate: manager.openCamera: SecurityException: validateConnectLocked:1112: Caller "com.testwebrtc.nikola.myapplication" cannot open camera "1" without camera permission at android.hardware.camera2.CameraManager.throwAsPublicException(CameraManager.java:628) at android.hardware.camera2.CameraManager.openCameraDeviceUserAsync(CameraManager.java:347) at android.hardware.camera2.CameraManager.openCamera(CameraManager.java:450) at org.chromium.media.VideoCaptureCamera2.startCapture(VideoCaptureCamera2.java:661)

            Other variant for error:

            [ERROR:web_contents_delegate.cc(199)] WebContentsDelegate::CheckMediaAccessPermission: Not supported.

            This is error log from chrome/webview (from errorCallBack - getUserMedia ):

            ...

            ANSWER

            Answered 2017-May-25 at 15:00

            Your app need request permission before use camera

            Source https://stackoverflow.com/questions/44180093

            QUESTION

            Local Video Renderer in Android WebRTC
            Asked 2020-Feb-14 at 10:52

            I am using this library: https://bintray.com/google/webrtc/google-webrtc

            What I want to achieve (at least, at the beginning of my project) is render video locally. I am using this tutorial (which is the only one around the Internet) https://vivekc.xyz/getting-started-with-webrtc-for-android-daab1e268ff4. Unfortunately, the last line of code is not up-to-date anymore. The constructor needs a callback which I have no idea how to implement:

            localVideoTrack.addRenderer(new VideoRenderer(i420Frame -> { // no idea what to put here }));

            My code is exactly the same as in the posted tutorial. This is the very first step to make familiar with WebRTC technology in Android which I cannot figure out. My camera is capturing the video because I can see it in my log:

            I/org.webrtc.Logging: CameraStatistics: Camera fps: 28.

            The main issue is that I have no idea how to pass it to my SurfaceViewRenderer through a callback. Did anyone meet that problem? I'll really appreciate any help or suggestions.

            Here is the official example app which is the only source but it is done differently than one in the tutorial, it's much more complicated: https://webrtc.googlesource.com/src/+/master/examples/androidapp/src/org/appspot/apprtc

            ...

            ANSWER

            Answered 2018-May-20 at 15:25

            You are right, the API no longer matches that in the tutorial, but it's close.

            The VideoTrack, has an addRenderer(VideoRenderer renderer) method, that requires you to create a VideoRenderer, with the SurfaceViewRenderer as parameter. But that is not possible anymore, so instead you should use the addSink(VideoSink sink) method, of the VideoTrack. The SurfaceViewRenderer object implement the VideoSink onFrame(VideoFrame frame) method to make this work.

            Source https://stackoverflow.com/questions/50291497

            QUESTION

            Replacing content of an iframe
            Asked 2019-Dec-19 at 23:53

            The index.html file:

            ...

            ANSWER

            Answered 2019-Dec-19 at 23:52

            JS Same Origin Policy:

            Perhaps you have encountered access denied or similar error messages when using JavaScript to interact with iframes. This will occur if the containing document and the iframed document are not from the same domain and they attempt to reference each other's objects.

            The same origin policy is a security feature of JavaScript that prevents access to properties and methods of documents from different domains.However, there are ways to ease or circumvent this restriction.

            Read more: dyn-web.com

            Source https://stackoverflow.com/questions/59417825

            QUESTION

            Anyone success in config collinder for apprtc
            Asked 2019-Apr-04 at 15:48

            My question in github: https://github.com/webrtc/apprtc/issues/615 I can't config apprtc for signal server, just call video ok via wifi but via mobile network has no luck. Please view my config, I can't find any example for constands.py in anywhere. Here is my config:

            ...

            ANSWER

            Answered 2019-Apr-04 at 15:48

            I found the error during two years ago to config apprtc: Just config ICE servers like this:

            Source https://stackoverflow.com/questions/55372070

            QUESTION

            Xamarin Form iOS WebRTC
            Asked 2019-Mar-01 at 23:27

            I'm pretty new to forum and I really appreciate the passion that all of you use to solve the questions.

            So I'm here because I'm struggling to integrate the GoogleWebRTC in my Xamarin Form project in the iOS part (I'm been able to make a native objC test app ), I've try to integrate it via CocoaPods with Sharpie Pod and bind it, but I'm not be able to resolve all the errors created in the bind on ApiDefinitions.cs.

            After some time I found this project https://github.com/valentingrigorean/apprtc-ios-xamarin that has successfully bind the library and after some bug fix ( editing WebRTCBinding.csproj and remove the -lstdc++.6 linker and removed some errors in code) but when I try to add that binding library into my project and try to run return me :

            ...

            ANSWER

            Answered 2019-Mar-01 at 23:27

            I was also looking for a solution and spent a lot of time to get it running.
            What I did and what helped me with the project you mentioned
            - add both projects WebRTC and AppRTC into your project
            - link from your project to this both projects
            - Deleted lstdc++.6 as you did already
            - Add both delegate IARDAppClientDelegate, IRTCEAGLVideoViewDelegate into
            the class where you want to use it. You can add "RTCPeerConnectionFactory.InitializeSSL();" as test into for example ViewDidLoad and compile it for simulator and device.

            Does it work or do you still get erros?

            Source https://stackoverflow.com/questions/54927064

            QUESTION

            Why WebRTC only support H264 in Chrome but not in native application with some devices
            Asked 2018-Dec-16 at 10:53

            I use official sample to create offer SDP in Android Chrome, we can find a=rtpmap:100 H264/90000 that meant it can support H264.

            But if I build AppRTC(official Android sample) and use official prebuilt libraries version 1.0.25821, call createOffer then receive SDP in SdpObserver::onCreateSuccess, the SDP did not contain H264.

            My test device is Oppo R15 (with MTK Helio P60, Android 8.1).

            So, why WebRTC only support H264 in Chrome but not in native application with some Android devices?

            ...

            ANSWER

            Answered 2018-Dec-16 at 10:28

            Chrome build uses openh264 which is not used by regular **WebRTC. What I meant by regular is that there is variant with software h.264 encoder from the chrome build which you may use but I wouldn't recommend it.

            On Android WebRTC, H.264 is supported only if

            1. device hardware supports it, AND
            2. WebRTC hardware encoder glue logic supports that hardware encoder. Currently only QCOM and EXYNOS devices are supported. So any other devices even if they support h.264 HW encoder, won't be used and won't be added as part of codec factory and you won't see in SDP generated from WebRTC sample apps.

            At Java level, you can see that in HardwareVideoEncoderFactory.java which checks for QCOM and EXYNOS devices in isHardwareSupportedInCurrentSdkH264 function.

            Interestingly, if you are using native code, even QCOM and EXYNOS hardware encoders are not supported (there is bug filed on Webrtc issue tracker). This is because of tight integration of HW encoding code with JNI code - definitely not a good modular code.

            Source https://stackoverflow.com/questions/53795986

            QUESTION

            WebSocket - Status Code 403 and status message - Forbidden
            Asked 2018-Aug-21 at 10:04

            I am working on video call app using Apprtc.Follow below mention libraries.

            1. https://github.com/njovy/AppRTCDemo
            2. https://github.com/Piasy/AppRTC-Android

            When I change url to my custom server instead of apprtc server then video call is disconnected after 1 minute. I have lost connection with server.

            To avoid the connection lost with server, we need to ping server in regular interval approx 30 sec.

            But above mention AppRTC project are using jar file(autobanh.jar) to websocket connection, but in library sendPing mentod is private so not accessible.

            Question 1 - There is nay way to ping websocket server.

            Try after replace websocet library I had changed websocket library with below mention libraries

            1. https://github.com/Koredotcom/android-kore-sdk/tree/master/BotsSDK/korebotsdklib/src/main/java/kore/botssdk/autobahn
            2. https://github.com/martindale/soundtrack.io-android/tree/master/src/de/tavendo/autobahn

            After recplacing websocket library, Now I am able to access sendPing method. But still I have connection lost after 60 seconds during video call.

            Ping Method-

            ...

            ANSWER

            Answered 2018-Aug-21 at 10:04

            I had changed the websocket library to https://github.com/crossbario/autobahn-java

            This library has functionality of auto ping to server on regular time interval. After adding it, i have modified only one class of ApprtcDemo- WebSocketChannelClient

            Source https://stackoverflow.com/questions/51907298

            QUESTION

            use InAppBrowser.open() to get “failed to access to local media” about apprtc
            Asked 2018-May-17 at 08:58

            I build a cordova app,and want to use apprtc in app.

            Environment:

            ...

            ANSWER

            Answered 2018-May-17 at 08:58

            I use iframe instead of InAppBrowser,iframe can work well.

            Source https://stackoverflow.com/questions/50345323

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install apprtc

            Instructions were performed on Ubuntu 14.04 using Python 2.7.6 and Go 1.6.3.
            Clone the AppRTC repository
            Do all the steps in the Collider instructions then continue on step 3.
            Install and start a Coturn TURN server according to the instructions on the project page.
            Open src/app_engine/constants.py and do the following:
            If using Google Cloud Engine VM's for Collider Change WSS_INSTANCE_HOST_KEY, WSS_INSTANCE_NAME_KEY and WSS_INSTANCE_ZONE_KEY to corresponding values for your VM instances which can be found in the Google Cloud Engine management console.
            Else if using other VM hosting solution Change WSS_INSTANCE_HOST_KEY to the hostname and port Collider is listening too, e.g. localhost:8089 or otherHost:443.
            If using TURN and STUN servers directly Either: Comment out ICE_SERVER_OVERRIDE = None and then uncomment ICE_SERVER_OVERRIDE = [ { "urls":...] three lines below and fill your TURN server details in src/app_engine/constants.py. e.g. ICE_SERVER_OVERRIDE = [ { "urls": [ "turn:hostnameForYourTurnServer:19305?transport=udp", "turn:hostnameForYourTurnServer:19305?transport=tcp" ], "username": "TurnServerUsername", "credential": "TurnServerCredentials" }, { "urls": [ "stun:hostnameForYourStunServer:19302" ] } ] Or: Set the the comma-separated list of STUN servers in app.yaml. e.g. ICE_SERVER_URLS: "stun:hostnameForYourStunServer,stun:hostnameForYourSecondStunServer"
            Else if using ICE Server provider [1] Change ICE_SERVER_BASE_URL to your ICE server provider host. Change ICE_SERVER_URL_TEMPLATE to a path or empty string depending if your ICE server provider has a specific URL path or not. Change ICE_SERVER_API_KEY to an API key or empty string depending if your ICE server provider requires an API key to access it or not. ICE_SERVER_BASE_URL = 'https://appr.tc' ICE_SERVER_URL_TEMPLATE = '%s/v1alpha/iceconfig?key=%s' ICE_SERVER_API_KEY = os.environ.get('ICE_SERVER_API_KEY')
            If running locally using the Google App Engine dev server (dev/testing purposes) Start it using dev appserver provided by the Google app engine SDK pathToGcloudSDK/platform/google_appengine/dev_appserver.py out/app_engine/.
            Else if running on Google App Engine in the Google Cloud (production) Make sure you have a Google Cloud Account and Google App Engine enabled. Download the Google Cloud SDK and initialize it. Deploy your AppRTC app by executing the following in the out/app_engine directory gcloud app deploy --project [YOUR_PROJECT_ID] -v [YOUR_VERSION_ID] (You can find the [YOUR_PROJECT_ID] and [YOUR_VERSION_ID] in your Google cloud console).

            Support

            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/webrtc/apprtc.git

          • CLI

            gh repo clone webrtc/apprtc

          • sshUrl

            git@github.com:webrtc/apprtc.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link