Search results

Just send a few hours of logs. We have to estimate state of RtspPortManager Also please temporary switch logs to info level if it is possible. log4j.rootLogger=info, stdout, fAppender It will give us more details.

Hello We assume that it is a kind of leak in RTSP port manager. Unfortunately RTSP ports are not listed in the Stats. So you have to gather logs. Please add a line into the config conf/log4j.properties It does not require server restart. log4j.logger.RtspPortManager=DEBUG The log4j.properties...

Hello. We believe that the first thing you should do is roll back — that is, downgrade to the version that was working for you. If version 5.2.1054 was working, then you should downgrade to that version. If, for some reason, the downgrade doesn’t help, then you need to restore from a backup...

When updating WCS from old version to a newer one, you should also care about WebSDK version update. For example, if you've updated WCS to 5.2.1921, you should also update WebSDK to 2.0.240, especially if you're still using 0.5.28.* builds. Please try to make a test calls via Phone Min example...

Seems like you've started two simultaneous SIP calls to the same callee namber in the same client session: So PBX declines the first one The client session was closed, and the second call was cancelled It seems like either client (web page) code issue or REST hook issue. You should not start...

We fixed the issue in build 5.2.2207.

We tested the build 5.2.1921 with your settings on our staging server. All the SIP calls are recodring successfully with the following settings rtp_force_synchronization=true rtp_activity_detecting=false,0 generate_av_for_ua=all stun_freshness_timeout=1000000000...

Seems like you're still using build 5.2.1054 on the server which we have access. Please update to 5.2.1921. You can also try to update to newer build 5.2.2183. In this build, SIP calls may be recorded to MKV container: SIP calls recording

Good day, Marc. Seems you've unpacked FlashphonerWebCallServer-5.2.1921.tar.gz archive to /usr/local folder directly. You should not do it. So you should do the following: 1. Backup the current installation 2. Uninstall WCS /usr/local/FlashphonerWebCallServer/bin/uninstall.sh 3. Download and...

This file seems to be used as background. It contains black square and silence So blank screen seems to be normal in this case between one inject stops and another inject starts. Also the background file bg.mp4 is too short, and loops frequently. Use at least 1 minute file.

You must decode the stream to apply watermark at server side. For example: 1. Set the following parameter in falshphoner.properties custom_watermark_filename=/media/13983.png 2. Play the stream with resolution set explicitly In this case the stream will be transcoded to the resolution set, and...

It was the bug. The watermark must be applied to transcoder output stream, not to the transcoder source stream. The bug was fixed, so you should change your flow: a viewers should play transcoder output stream, but not the original stream.

We checked the server. You have an issues with server settings 1. Server CPU load is too high for a couple of streams The server has 24 cores (actually it is 12c/24t). But you've set a twice more threads in all the thread pools: So you really have 48 threads which are just consume CPU but does...

The better channel quailty and bandwidth between publisher and server, the less its stream latency. It's applcable to player too. The longer the channel, the worse quality and bandwidth. in this case you should have US origin and Indian edge.

Please provide SSH access to the server using this form for our engineers to test.

Good day. We confirm the issue. The ticker WCS-4370 is raised. But webcallserver update command still works.

You can't achive an equal latency via a different publisher channels. So you will have a 1.5-2 secinds latency when publishing form India to US. Please consider a CDN with origin closer to publishers and edges closer to players. A simple configuration explained in this article, a technical...

We checked the server by credentials provided. Seems like the server too far from a clients. The instanse is in us-west AWS region, but you`re probably testing from India. In this case a minimal server ping will be 200 ms and more (from our test PC ping is 222 ms to intermediate hosts)...

Seems like you are continiously injecting the same file to the same stream: when file reaches the end (every 30 seconds), you make another /stream/inject2/startup call with the same parameters. According to video attached, the original stream has static picture. So when injected stream ends, and...

Please see the IP address to allow SSH connections here: Providing support engineer access to your server We do not arrange any remote sessions.