Results 1 to 5 of 5

Thread: RTSP SETUP Response takes 5 seconds

  1. #1
    Join Date
    Nov 2013

    Default RTSP SETUP Response takes 5 seconds


    I'm pushing an INGRESS RTSP over TCP stream to my application. It's functional, but I want to understand what can affect the SETUP response to be delayed by 5 seconds, which is happening now.

    Sent: Date: Tue, 29 Apr 2014 08:02:53 PDT

    SETUP rtsp:// RTSP/1.0
    CSeq: 3
    Session: 2018567636
    Transport: RTP/AVP/TCP;unicast;interleaved=0-1;mode=receive

    Response comes from Wowza 5 seconds later.

    RTSP/1.0 200 OK
    Date: Tue, 29 Apr 2014 08:02:58 PDT
    Transport: RTP/AVP/TCP;unicast;interleaved=0-1;mode=receive
    Session: 2018567636;timeout=60
    Expires: Tue, 29 Apr 2014 08:02:58 PDT
    Cseq: 3
    Server: Wowza Media Server build8074
    Cache-Control: no-cache

    Am I possibly doing something that can throw this off? I expected this to be immediate.


  2. #2
    Join Date
    Sep 2011


    Do you have any custom code running on the server?
    If so, does this behave the same without the custom code?

    If this is causing an issue we may need to take a look through your configuration and log files.
    If you need further assistance, please open a ticket by sending an email to

    When opening a ticket, please include a description of the issue, steps you have taken to resolve the issue and attach a zipped copy of the [Wowza-install]/conf/ and [Wowza-install]/logs/ directories for analysis.


  3. #3
    Join Date
    Nov 2013


    Hi Jason,

    Yes, there is custom code. It was done by someone else and I'm trying to understand the interfaces for the INGRESS stream so I can review the configuration and the code. Can you point me to documentation on how an INGRESS RTSP stream is negotiated within Wowza and its customizable interfaces? Also, what configuration can affect this?


  4. #4
    Join Date
    Dec 2007



    Take a look at IRTSPActionNotify and IMediaCasterNotify2, which might help you debug this


  5. #5


    If you custom code is doing some sort of external lookup (database or remote web service) to validate the connection, this could be the cause of the delay.

    Also, if the stream that it is requesting is a remote stream that needs starting, it could also be the cause. Does this only happen on the first request or does it happen on subsequent requests?


Similar Threads

  1. How to change RTSP Describe response.
    By jhlee1th in forum Wowza Streaming Server Java API
    Replies: 1
    Last Post: 08-24-2014, 11:05 PM
  2. Is it possible, RTSP custom response message?
    By shshin in forum Wowza Streaming Server Java API
    Replies: 3
    Last Post: 03-06-2014, 11:50 AM
  3. 4 seconds delay in RTSP stream using Wowza media server with Axis Q7401 video encoder
    By majidkhan in forum Live Streaming and Encoder Discussion
    Replies: 5
    Last Post: 11-08-2013, 03:30 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts