Testing new version

Vico

Member
Hi Max!, I´m testing this new version but can´t make it work. I´m listening to a rtsp feed
and trying to generate a WebRTC player.
Super happy with my actual servers running v.2.0.225-5.2.1482 super good for years, really happy.

Anyway if you can help...

SSH sent from support page.

Thanks!
 

Max

Administrator
Staff member
Good day.
We reproduced the issue with RTSP stream playback in latest build and raised the ticket WCS-3708 to fix it. Will let you know about results here.
 

Vico

Member
Yesss, actually working by far, thanks team.
let us test this well, but looks super rock solid.
Congrats.
 

Vico

Member
Ok, almost perfect.

But, It´s possible to start Flashphoner when the instance start?, it´s not working like last version.
Also, we stop the instance, start again and we get this trying to start WCS:

[root@ip-172-31-20-102 ~]# sudo service webcallserver start
Redirecting to /bin/systemctl start webcallserver.service
Job for webcallserver.service failed because the control process exited with error code. See "systemctl status webcallserver.service" and "journalctl -xe" for details.
[root@ip-172-31-20-102 ~]# sudo systemctl start webcallserver
Job for webcallserver.service failed because the control process exited with error code. See "systemctl status webcallserver.service" and "journalctl -xe" for details.

Thanks Max!
 

Vico

Member
Please make sure you've done
Code:
systemctl enable webcallserver
Please provide SSH access to the instance using this form.
This works, it´s almost perfect for us.
Max, last year or so you help us tweaking a bit the Player.js, we want that the player auto reconect if suddenly lost the feed, to avoid the "FAILED: Failed to connect to rtsp stream" on the client side.
I try to do the same here copy pasting your old code:

var retryToRestartTimeout = 3000; //ms
var addMilesecondsToRestartTryOnEveryFailed = 1000; //ms
var retryMaxTimes = 100;

Obiusly no luck and I came to the backup version, I think I broke it, if you find time to take a look will be amazing
SSH thing sent
 

Max

Administrator
Staff member
Unfortunately we cannot connect to the server using private key you've sent:
1676508628542.png

You can download a ready to use Player and Embed Player examples with auto reconnect here:
Player
Embed Player
 

Vico

Member
Thanks Max, I tried, overwrite the files in /embed_player, but this works like the old player and also no auto start after interuption.

Unfortunately we cannot connect to the server using private key you've sent:
View attachment 3466
You can download a ready to use Player and Embed Player examples with auto reconnect here:
Player
Embed Player
No password, I send the same like last time, instance runing.

Thanks for your effort men,
Vico
 

Max

Administrator
Staff member
No password, I send the same like last time, instance runing.
You've not set username, so we could guess it's ec2-user
overwrite the files in /embed_player, but this works like the old player and also no auto start after interuption.
Embed player supports a special option to enable restart. So you should either pass the option
Code:
https://wcs:8888/embed_player?urlServer=wss://wcs:8443&streamName=test&mediaProviders=WebRTC&restart
or replace false to true in the string 15 of player.js file:
Code:
var restart = eval(getUrlParam("restart")) || true;
 

Vico

Member
Yep, sorry mate, it´s ec2user

This works suuuuper good, thanks a lot Max.

The only thing is that I feel this embed like the old version, it´s the one from the 5.2.1555 version?
 

Max

Administrator
Staff member
The only thing is that I feel this embed like the old version, it´s the one from the 5.2.1555 version?
Not yet. We raised the ticket WCS-3717 to update a ready to use examples. Will let you know about progress here.
 

Max

Administrator
Staff member
We updated a ready to use auto reconnect samples:
Player
Embed Player
Also there is a Restart switch in modified Embed Player example which adds the option restart=true to Embed Player URL
1676960104380.png
 

Vico

Member
Wow, seems to work super good, actually testing

Max, there is a way to avoid the "FAILED: failed to connect to rtsp..." message, or to change the message. it´s on the client side and it´s hard to explain.
Can´t find this thing in the Player.js

Thanks
 

Max

Administrator
Staff member
You can comment line 113
JavaScript:
    ...
    }).on(SESSION_STATUS.FAILED, function () {
        setStatus(SESSION_STATUS.FAILED); /// Comment this line
        onStopped();
        tryToRestart();
    });
    ...
and line 171
JavaScript:
    ...
    }).on(STREAM_STATUS.FAILED, function(stream) {
        setStatus(STREAM_STATUS.FAILED, stream); /// Comment this line
        onStopped();
        tryToRestart();
    }).on(STREAM_EVENT, function(streamEvent){
    ...
in player.js file. Then, no FAILED message should be displayed.
 

Vico

Member
Wow, really close to perfection.
24h testing and seems really reliable, maybe much more stable
Thanks Max

With an option for h265, we will touch the sky ;-)

Thanks for your help men
 
Top