Search results

Hello Each running and activated server sends pings. 3-4 pings per hour. If at least one ping sent within the hour, the billing system will calculate this as a unit. Example1 10:01 AM - Server A sends ping 10:15 AM - Server B sends ping 10:30 AM - Server A was crashed 10:45 AM - Server B...

Hello Could you provide the RTSP link? We will check. You can also send RTSP link via the private form.

Good day. You can implement a custom Java class to intercept every frame and crop it programmatically: Decoded frames interception and handling Another way is to use stream mixer with a special cropping layout, but this only crops a central area of the stream picture: Crop around center zero...

Good day. A typical stream flow is: 1. PENDING - WebRTC connection is establishing, no media traffic yet, stream codecs is unknown 2. PUBLISHING - WebRTC connection is established, media traffic is sent from client, stream codec can be detected 3. UNPUBLISHED or FAILED - streaming is stopped by...

Привет. Мы не тестировали запуск под Windows 11 в Docker. Потребуется некоторое время чтобы проверить запуск. Для Windows обычно рекомендуем запуск WSL

We've updated demo server to the latest build 5.2.1131 and WebSDK 2.0.212. In this case, the problem is reproducing randomly in Chrome 98.0.4758.80 on MacOS 12.2. Seems like the issue is ih hardware H264 encoder parameters. There are the following workarounds: 1. Publish VP8 codec instead of...

Good day Please reproduce the issue in Two Way Streaming example. If it's reproducing please provide Chrome Dev Tools console screenshot.

Please clarify: what exactly result you've got on every step (1, 2, 3, 4)? Also check if examples are built correctly with Gradle from command line.

Yes, ICE connection is establishing only for WebRTC publishing/playback. And seems this is broken yet on some of Samsung devices (but on good old flagships like S10/S10+ ICE works correctly both in Chrome and Samsung browser). So, we have to wait for Samsung fix and use Firefox as workaround.

Thank you for investigation. Please, check if the problem is reproducing in latest Samsung browser build (they may fix it in proprietary browser). If this is not fixed yet, try also to publish VP8 in Media Devices example: If codec stripping does not help, seems like Firefox is the only...

As you mentioned in this post, other WebRTC examples (AppRTC, TrickleICE) also does not work properly in Samsung browser. We use the standard WebRTC API (getUsersMedia, PeerConnection etc) in all the browsers. So the problem is not in WebSDK, but in WebRTC implementation in the browser. Also, we...

The examples should be configured for building: a special script adds the downloaded library version to dependencies, sets the minimal targetSDK etc.

Hello We don't have access to your instance. Please send SSH access details using this form. Then we will be able to check.

Hello WCS server sends REST request http://localhost:8081/EchoApp/connect upon each websocket connection attempt This REST request contains IP of user who is trying to establish the websocket connection. 1. You can configure your own REST URL , i .e. http://myhost/myapp 2. You can handle such...

Good day. Please make sure you've done all the steps described here: Preparing examples for building. Than you can build examples with Gradle from commad line or with Android Studio.

In this case, you have to wait for our CallKit usage example release (ticket WCS-3420). To resolve the issue, we need a reproduction. So, we implement the example and check if the issue is reproducing. We let you know results here.

It is recommended to restart WCS after changing license key.

Now, GPU transcoding is on testing and debugging stage. It's not ready yet for production use. Please be patient.

Hello All related threads are tagged https://forum.flashphoner.com/tags/wcs-3106 Once the issue is resolved or if we have early builds, we will update all tagged threads. The ticket is internal and activity is not visible.

In the latest WCS builds it is possible to set layout and other mixer parameters while creating mixer via REST API: Mixer configuration while creating the instance using REST API