DigiEye's streams cant be played

Max

Administrator
Staff member
We're testing the fix. Perhaps it will be released next week. Please be patient.
 

fercospos

New Member
Hello Max! May we have a time estimate for the new version? I have a lot of patience, but the client does not stop urging and I need to give them any updates. Thanks!
 

Max

Administrator
Staff member
We're on the final testing stage before release. The fix will be released this week.
 

Max

Administrator
Staff member
We fixed the issue in build 5.2.1988. Please update and set the following parameter:
Code:
jitter_buffer_strictness=TOLERANT
The stream should play.
Please also check if the green flickering occurs with this build and setting.
 

fercospos

New Member
Thanks for the notification Max.

We can't update online because the server is on an isolated network, may we get a way to install offline?

Thanks and best regards,
 

Max

Administrator
Staff member
We can't update online because the server is on an isolated network, may we get a way to install offline?
Please do the following:
1. Download the WCS installastion archive here: 5.2.1988
2. Place the archive to the server
3. Unpack the archive
Code:
tar -xvzf FlashphonerWebCallServer-5.2.1988.tar.gz
4. Stop WCS
Code:
sudo systemctl stop webcallserver
5. Launch the installation script
Code:
cd FlashphonerWebCallServer-5.2.1988
sudo ./install.sh
The script will update the current installation on the server
6. Start WCS
Code:
sudo systemctl start webcallserver
 

fercospos

New Member
Hello Max!

We were able to update the server, but still we can't see the video stream. Checking today's logs I see this info entries:


18:42:29,872 INFO RetryExec - API-ASYNC-pool-7-thread-42 I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://localhost:8081: The target server failed to respond
18:42:29,872 INFO RetryExec - API-ASYNC-pool-7-thread-42 Retrying request to {}->http://localhost:8081

From our installation notes, we have the port 8081 available as public zone on the firewall, and I see it's in use by "tproxy":

[root@MEDIASERVER server_logs]# cat /etc/services | grep "8081"
tproxy 8081/tcp sunproxyadmin # Transparent Proxy
tproxy 8081/udp sunproxyadmin # Transparent Proxy

What may I be missing?
 

Max

Administrator
Staff member
The port 8081/tcp should be listened by WCS process itself:
Code:
sudo netstat -nlp | grep java | grep 8081
If not, please check the WCS configuration in flashphoner.properties file: did you changed the parameter http.port? If yes, revert in back to
Code:
http.port=8081
and restart WCS.
If port is listened, but no streams can be played at all, please check if you activated a license on the server.
 

fercospos

New Member
Hello Max! We checked ports and licenses and all is OK. Stream works with the other vendor (Ganz). I've just attached a couple dump files when we try to play the same stream from VLC and Flasphoner so you can compare both.

Thanks!
 

Max

Administrator
Staff member
Hello

We have checked logs.
It looks like WebRTC connection issue.

Please make the report
1. Try to play stream.
2. Then gather the report:
Code:
cd /usr/local/FlashphonerWebCallServer/tools
sudo ./report.sh --sysinfo --conf --tar
 

Max

Administrator
Staff member
Hello

Related to the report. Please double check the following logs:
logs/server_logs/flashphoner.log

1) What was the server time of incident?
2) What was the stream name or RTSP URL of incident?

We have to match Time and URL with logs.

Please check also
/usr/local/FlashphonerWebCallServer/logs/cdr/sdr.log
This log is being rotated hourly.
Please attach sdr hourly log including the Time and URL(or stream name) of the incident.

Private Form to submit Time and URL
 

fercospos

New Member
Hello team, we just uploaded both flashphoner and SDR logs from the same timeframe, they include the details about the RTSP URL also.

Thanks for checking!
 

Max

Administrator
Staff member
Good day.
Unfortunately, the logs contain a different events: the flashphoner.log file contains events since 13:03 to 13:07 according to the server clock
1728610341579.png

but sdr.log contains the event happened in 15:21 according to the server clock
1728610473079.png

So we can't match neither time nor RTSP URL nor media session Id.
Please do the following:
1. Update WCS to the build 5.2.2096 which includes some RTSP related fixes
2. Reproduce the problem if persists
3. Collect the report as described.
4. Do not obfuscate anything in the report, otherwise we can't match session Ids
5. Send the report. Don't forget to set server time of issue in Comment field.
 
Top