RTSP Stream with URI Authentication

[InTeleSync]

Evaluating v.0.5.28.2753-5.2.454-. Fresh install on an AWS CentOS 7 instance.
Attempting to connect to a Grandstream GXV3611_HD in the Flashphoner Player demo. When connecting via RTSP without a password on the camera (allow anonymous viewing), all is well. Ex: rtsp://myIP:10081/0

But if try to connect with credentials for the camera in the URL (do not allow anonymous viewing), get a "Failed to connect to rtsp stream" error. Ex: rtsp://username:mypassword@myIP:10081/0

What has been missed?

 

[Max]

Good day.
Please check if your credentials contain any special characters like this:

rtsp://username:p@ssword@myIP:100081/0

In this case, the special character should be escaped like this:

rtsp://username:p%40ssword@myIP:10081/0

If this tip does not help, please collect a report as described here and send to support@flashphoner.com, we will check.

 

[Max]

In the received log, the failure was due to other reason: "Back-end has returned 401 Unauthorized on connect". The server has

disable_rest_auth=false

in the config - REST hooks should be used for authorization.

 

[InTeleSync]

Yes I wanted to make sure all REST requests require authentication as a standard security measure. Why this isn't a default setting is concerning and debatable.
In https://docs.flashphoner.com/display/WCS52EN/Using+REST+hook+to+authorize+user+by+domain
there is a reference to: update app -l http://yourhost/rest-hooks defaultApp
What is "yourhost"? The host of WCS5, or the host where the camera resides?
What is "defaultApp"?

 

[Max]

defaultApp is one of the server-side applications. An application stores a REST URL of back-end web server ("yourhost" in the URL example above).
By default, it is configured to work out of the box without additional back-end setup. The URL can be changed (using the "update app" CLI command) to send requests to your back-end.
Here is a similar question.

 

[Max]

The issue has been reproduced with the latest received credentials to the stream - submitted internal ticket WCS-2456, will notify when there is an update.

 

[Max]

The RTSP authentication issue has been fixed in WCS v. 5.2.470.

 

[InTeleSync]

Excellent. Is there a simple way (CLI or GUI) to do minor version updates without fetching the tarball and installing?

 

[Max]

Is there a simple way (CLI or GUI) to do minor version updates without fetching the tarball and installing?

You should either update with commands

cd /usr/local/FlashphonerWebCallServer/bin
webcallserver stop
webcallserver update
webcallserver start

or update by downloading archive and installing over previous version

cd ~
curl -sL -O https://flashphoner.com/downloads/builds/WCS/5.2/FlashphonerWebCallServer-5.2.470.tar.gz
tar -xzf FlashphonerWebCallServer-5.2.470.tar.gz
service webcallserver stop
cd FlashphonerWebCallServer-5.2.470
./install.sh
service webcallserver start