MPEG-TS RTP stream publishing via reserved ports

[vsl]

Good day,

I'm trying to configure WCS for MPEG-TS publishing via reserved ports, but I can not figure out what I'm doing wrong.

Version of WCS: 5.3.129

In the flashphoner.properties I have:

mpegts_reserved_port_from=39991
mpegts_reserved_port_to=40000

I've created the: /usr/local/FlashphonerWebCallServer/conf/mpegts_ingest.yml file with following content:

streams:
srt1:
port: 39992
transport: srt
timeout: 10000
hasAudio: true
hasVideo: true
maxTimeStampDiff: 90000
allowedList: []

Preview does not show correct indentation, but yml file should be formatted correctly, with two spaces indentation.

After the WCS restart, in the flashphoner.log I see this error:

08:42:31,830 ERROR B - main The required "port" parameter is missing for reserved agent with stream name: srt1 in the YAML settings file /usr/local/FlashphonerWebCallServer/conf/mpegts_ingest.yml

Can you please help?

Thanks

 

[Max]

Good day.
We checked the configuration on the latest build 5.3.131. With the correct indentation, it works perfectly

The stream is publishing

and playing on the test server

Please double check the indentation on your server

 

[vsl]

Hi,

Thanks a lot for checking! I'm going crazy here, I rechecked multiple times, here is how the file looks with "od -c" command, no weird characters, with correct spacing:

or

I still get the:
" ERROR B - main The required "port" parameter is missing for reserved agent with stream name: srt1 in the YAML settings file /usr/local/FlashphonerWebCallServer/conf/mpegts_ingest.yml"

Funny thing is, I have 2 servers where I can reproduce the same issue, so I'm definitely doing something wrong.
Are you willing to have a quick look at our config if I provide you the ssh access?

Thanks

 

[Max]

Please provide SSH access to the server using this form

 

[Max]

Seems you've installed WCS on the server by wrong way: unpacked the server distribution archive to /usr/local then installed. There can be undefined behaviour in this case
Please do the clean reinstallation:
1. Uninstall WCS completely

sudo /usr/local/FlashphonerWebCallServer/bin/unistall.sh
sudo rm -rf /usr/local/FlashphonerWebCallServer-*

2. Install WCS from a home folder

cd ~
wget https://flashphoner.com/downloads/builds/WCS/5.3/FlashphonerWebCallServer-5.3.146.tar.gz
tar -xzf FlashphonerWebCallServer-5.3.146.tar.gz
cd FlashphonerWebCallServer-5.3.146
sudo ./install.sh

 

[vsl]

Hi, I never got this working. In the meanwhile we were using the REST API (`/mpegts/startup`) approach, but it is hassle for our clients. Today I gave it another try, installed latest WCS locally, reproduced the same issue, then run Claude to try to analyze it. Can you have a look at the report, please?

 

[Max]

Good day.
We have installed latest WCS build 5.3.465 to Ubuntu 24.04.4 LTS in WSL2 instance on Windows 11 Pro 25H2 and configured it as described in docs. Seems its working: the reserved streams are up:

and reserver ports are listened:

But you're reporting about broken YAML file:

The error message means mpegts_ingest.yml file has no port keyword for the scope. If the file structure seems to be correct, there are probably an invisible characters in previous line end.
So it seems like Windows line endings (carriadge return + line feed) in LInux environment (which required line feeds only) issue. You have probably edited the file at Windows side and then copied it to WCS configuration folder.
Please check the file for this issue.
Please also note that allowedList should include an actual publisher address mask. You'd better remove this tag from mpegts_ingest.yml while testing

 

[vsl]

Hi, thanks for checking. It's not the line endings, file is created in Linux. I really wonder what the issue is.
I can setup a new VM on Azure with fresh install, and give you ssh access again.

 

[vsl]

Could it be you tested using internal build 5.3.465 which is not obfuscated?

 

[Max]

We reproduced the issue in obfuscated 5.3.465 build. Raised the ticket WCS-5013, will let you know about progress.

 

[Max]

We fixed the issue in build 5.3.466. Please update and check.

 

[vsl]

Awesome, thanks a lot! I'll check it today.

 

[vsl]

Tested, works like a charm. Thank you!