Preview Tool

Cisco Bug: CSCup00590 - RTSP log should include the session id in all log entries

Last Modified

Jun 21, 2020

Products (2)

  • Cisco Videoscape Distribution Suite for Television
  • Cisco TV Streamer Application

Known Affected Releases


Description (partial)

When reading rtsp.log, it is sometimes unclear for which session logs are printed.
If every log line would contain the session id, it would be easier to trace.

Worst things is when the RTSP messages do not contain any session id.
For example:
RTSP/1.0 453 Not Enough Bandwidth
CSeq: 851306

Here, we have to check via the cseq for which session this is.
Sometimes cseq number is the same for different sessions, so then it is impossible to see for which session this log was printed.

Normal behaviour of logging into rtsp.log
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.