RTSP Failure

[dhogan723]

Hello,

Our RTSP streams from Milestone have stopped working for the last week and we are hoping you can take a look remotely. Streams are OK playing in VLC, just not in the WebCall Server for some reason.

I will post remote connection and static RTSP URLs in the report for this ticket. Please let me know if you have any issues connecting.

Thanks!

 

[Max]

Good day.
Unfortunately, we cannot downdload remote connection client

Please check if you've updated WCS to at least to 5.2.971 (as on our demo server), this should help with most of RTSP cameras.

 

[LucasClarkson]

We upgraded WCS to 5.2.994, but we're still seeing the same behavior. The only non-info log we're seeing when trying to connect to the RTSP stream is:
RtspUtils - pool-59-thread-1 Auth: Content-base header null or empty

Does this mean there is an issue with the authentication?

Thanks!

 

[Max]

Does this mean there is an issue with the authentication?

It's possible.
Unfortunately we still cannot downdload remote connection client. So please collect traffic dump and logs on server side:
1. Switch server logs to INFO level in /usr/local/FlashphonerWebCallServer/conf/log4j.properties file

log4j.rootLogger=info, stdout, fAppender

2. Launch the command

tcpdump -npi any -B 10240 -w log.pcap

3. Play a problem RTSP stream
4. When FAILED is receiving, stop tcpdump
5. Collect a report

cd /usr/local/FlashphonerWebCallServer/tools
sudo ./report.sh --sysinfo --conf --stats --tar

Also, collect traffic dump playing the problem RTSP stream in VLC:
1. Start dump collection in Wireshark
2. Play the RTSP stream in VLC about a minute
3. Save dump as pcap
We could parse and play this dump to test on our servers.
Then send us report archive and traffic dumps using this form

 

[LucasClarkson]

Report, tcpdump capture, and wireshark capture sent via report form.

 

[Max]

Hello

We found issue related RTSP digest authentication
The cam sends two WWW-Authenticate headers: MD5 and SHA-256

It seems SHA-256 is not supported on our end and we do not form Authorization response properly.
We raised internal ticket WCS-3268. Will inform about progress.

As a workaround you can setup the cam for MD5 only and remove SHA-256 line if it is possible.

Affected packet where we can see two WWW-Authenticate headers

 

[LucasClarkson]

Has there been any progress on resolving WCS-3268? This is a critical issue for us as it is affecting hundreds of our cameras streaming through Milestone. Thanks in advance.

 

[Max]

Has there been any progress on resolving WCS-3268? This is a critical issue for us as it is affecting hundreds of our cameras streaming through Milestone. Thanks in advance.

The fix is on testing stage. We'll let you know about progress.

 

[Max]

Hello,

The issue has been fixed in WCS build 5.2.1002.