Search results

If you're using AWS Marketplace AMI, you have not pay additional charges, just hourly payment for instance. If you're deploy Amazon Linux for example and install WCS manually, you should buy a license.

Good day. Please provide SSH access to the instance using this form

Good day. You can achieve this using REST API /pull/rtmp/pull: POST /rest-api/pull/rtmp/pull HTTP/1.1 Host: localhost:8081 Content-Type: application/json { "uri":"rtmp://abc.xyz:1935/live/ch_1", "localStreamName":"ch1_for_viewers" } In this case you should use localStreamName...

Good day. Seems m5.2xlarge should be enough. Please also make a tuning steps described in this article, chapter Preparing for testing, points 1-5

Добрый день. WCS работает только на Linux x86_64. Поэтому нет, на Android устройстве WCS запустить нельзя, нужен отдельный сервер. Минимальные требования приведены здесь.

This depends on streams published count. You will have as many subscribers on this server as streams published. Please read this article about one-to-one streaming testing. The server with 24 CPU cores, 80 Gb RAM is enough to handle 200 720p 2500 kbps streams in this case.

Это ограничение библиотеки WebRTC, код внутри которой мы не меняем. iOS SDK обеспечивает только websocket сигналинг и вызовы для установки WebRTC соединения.

Добрый день. Нет, к сожалению, iOS такого не позволяет. Например, нельзя играть WebRTC поток одновременно с Youtube. Это касается как видео, так и аудио.

Добрый день. По тикету WCS-2738. В сборке 5.2.1036 добавлена возможность передачи custom объекта из /publishStream в /unpublishStream, а также для пары /playStream-/stopStream.

Good day. We added session custom object to /ConnectionStatusEvent with DISCONNECTED status since build 5.2.1036. Also it is now possible to receive /publishStream or /playStream custom object in /unpublishStream or /stopStream respectively.

Добрый день. В Ваших настройках сразу несколько ошибок: 1. Параметр cdn_origin_allowed_to_transcode устанавливается только на Edge серверах, о чем написано здесь 2. Параметр force_client_requested_video_resolution не имеет отношения к транскодингу 3. Параметры hls_player_width=1280...

We received the dump. Will check.

In this case, use the scheme above: Origins are behind LB, and one Edge is permanent (and powerful enough to collect all streams, c5.4xlarge for example). You can also place Edges behind a separate LB (not the same as publish LB) if you play streams only as RTMP because ffmpeg uses one port to...

Good day. Yes, this changed in all examples since build 2.0.179 (on GitHub and in NPM package too). We added Browser object aexport from Flashphoner namespace and removed dubbing code from dependencies, so this change is necessary fro backward compatibility.

If you want to collect all the streams to one ffmpeg server before republishing to FB, you should place Origin servers behind load balancer, and get streams by RTMP from one Edge server powerful enough to collect al the published streams. Please clarify: how much publishers you plan to handle...

Good day. You use a wrong link, this doc is avaliable here https://docs.flashphoner.com/display/WCS52EN/Load+balancing But this function is obsoleted and is not supported any more. Use third party load balancer instead.

Сейчас имя стрима и mediaSessionId записывабтся в атом tnam для конкретной дорожки: [ftyp] size=8+24 ... [moov] size=8+56602 [mvhd] size=12+96 ... [trak] size=8+25060 [tkhd] size=12+80, flags=1 enabled = 1 id = 1 duration = 35453 width = 0.000000...

This is definitely not a configuration issue. Seems like this is Elastic IP issue: if Elastic IP is configured for the instance, it should be set as external IP in WCS settings because WCS adds external IP to WebRTC candidates list when sending SDP to client. Anyway, glad to hear the problem is...

The message Autoplay detected... means only the first play() call for preloader file is failed. Usually, this may be due to automatic playback without user action. Then, the second play() is called. In your case, it's also failed. So this is not autoplay issue. May be this is browser thread...

To answer this question you would need a monitoring tool like Grafana + Prometheus https://flashphoner.com/10-important-webrtc-streaming-metrics-and-configuring-prometheus-grafana-monitoring/ Once you have metrics from all of your servers you can find a possible cause why a server is unhealth.