RTMP pull

Radu

New Member
Hi Max,

Some months ago you said it will be possible to do a pull-based rtmp live streaming in the browsers using websockets.
Basically the client would say: "play rtmp://wowza-server/app/id.mp4" and the WCS5 would fetch the rtmp stream (h264+AAC), repackage it for MSE and play it in-browser. Something like described below:
Client <-- (websocket) --> WCS5 Server <-- (rtmp stream) -- >Wowza RTMP Server

Is it possible at the moment? What are the alternatives if not?
 

Radu

New Member
Ah great, we are already running a licensed WCS 5.0.2616 in production. Any instructions for a smooth upgrade? Also are there any potentially breaking changes between the two?
 

Radu

New Member
My bad, found the update process. However switching from 5.0.33 to 5.1 does not work with the ./webcallserver update?
 
Last edited:

Radu

New Member
Is there any changelog for 5.1? The server.properties line: wss.port = 443 was not being taken into consideration:

[root@phoner01 FlashphonerWebCallServer]# netstat -nlp | grep java
tcp 0 0 0.0.0.0:843 0.0.0.0:* LISTEN 1282/java
tcp 0 0 0.0.0.0:1099 0.0.0.0:* LISTEN 1222/java
tcp 0 0 0.0.0.0:1935 0.0.0.0:* LISTEN 1282/java
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 1282/java
tcp 0 0 0.0.0.0:2000 0.0.0.0:* LISTEN 1222/java
tcp 0 0 0.0.0.0:8081 0.0.0.0:* LISTEN 1282/java
tcp 0 0 0.0.0.0:8082 0.0.0.0:* LISTEN 1282/java
tcp 0 0 0.0.0.0:50999 0.0.0.0:* LISTEN 1282/java
tcp 0 0 0.0.0.0:8888 0.0.0.0:* LISTEN 1222/java
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 1282/java
tcp 0 0 0.0.0.0:8444 0.0.0.0:* LISTEN 1282/java
tcp 0 0 0.0.0.0:8445 0.0.0.0:* LISTEN 1282/java
tcp 0 0 0.0.0.0:12735 0.0.0.0:* LISTEN 1282/java
tcp 0 0 0.0.0.0:9091 0.0.0.0:* LISTEN 1222/java
tcp 0 0 0.0.0.0:554 0.0.0.0:* LISTEN 1282/java
tcp 0 0 0.0.0.0:1098 0.0.0.0:* LISTEN 1282/java
udp 0 0 0.0.0.0:1935 0.0.0.0:* 1282/java


While the 5.0 version, with the same configs says:

[root@phoner01 FlashphonerWebCallServer]# netstat -nlp | grep java
tcp 0 0 0.0.0.0:843 0.0.0.0:* LISTEN 5375/java
tcp 0 0 0.0.0.0:1099 0.0.0.0:* LISTEN 5321/java
tcp 0 0 0.0.0.0:1935 0.0.0.0:* LISTEN 5375/java
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 5375/java
tcp 0 0 0.0.0.0:2000 0.0.0.0:* LISTEN 5321/java
tcp 0 0 0.0.0.0:8081 0.0.0.0:* LISTEN 5375/java
tcp 0 0 0.0.0.0:8082 0.0.0.0:* LISTEN 5375/java
tcp 0 0 0.0.0.0:50999 0.0.0.0:* LISTEN 5375/java
tcp 0 0 0.0.0.0:8888 0.0.0.0:* LISTEN 5321/java
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 5375/java
tcp 0 0 0.0.0.0:8444 0.0.0.0:* LISTEN 5375/java
tcp 0 0 0.0.0.0:8445 0.0.0.0:* LISTEN 5375/java
tcp 0 0 0.0.0.0:20034 0.0.0.0:* LISTEN 5375/java
tcp 0 0 0.0.0.0:9091 0.0.0.0:* LISTEN 5321/java
tcp 0 0 0.0.0.0:554 0.0.0.0:* LISTEN 5375/java
tcp 0 0 0.0.0.0:1098 0.0.0.0:* LISTEN 5375/java
udp 0 0 0.0.0.0:1935 0.0.0.0:* 5375/java
 

Max

Administrator
Staff member
Hello

This is update instruction from WCS 5.0 to WCS 5.1
1. Convert existing WCS 5.0 structure for WCS 5.1.
Download 5.1 build, unzip.
Code:
cd FlashphonerWebCallServer-5.1.x/tools
./update.sh
2. Run install.sh

If you have any troubles, you have to downgrade back to 5.0 then repeat steps above.
Or you can install WCS 5.1 from scratch.

Only configuration difference - WCS 5.1 does not have server.properties config.
It was merged to flashphoner.properties. Documentation is in progress. We will inform once it is ready.
 

Stanley

Member
May I know how to pull streams like that what thread starter mention? Does it work on WSPlayer as well? Is the Wowza server require open port for public access or I can just allow communication between Wowza and Flashphoner?

Thank you.
 
Top