Page 9 of 9 FirstFirst ... 789
Results 81 to 89 of 89

Thread: RTSP/RTP improvements including video on demand support (patch15 or greater)

  1. #81

    Default

    String rangeStr = req.getHeader("range");
    Thank you, Charlie! It was what I wanted.

    Quote Originally Posted by rrlanham View Post
    http://www.wowzamedia.com/downloads/...2.3-patch7.zip

    It should fix the rtpSession.getServerIp() bug.
    It is a bit strange, but it seems that it returns null now...
    I use Motorola Defy (Froyo) and connect to local Wowza over WiFi.
    Am I doing something wrong?

  2. #82

    Default

    Redownload patch7 and re-apply. I made a mistake in the fix. It is fixed now.

    Charlie

  3. #83

    Default

    Thank you! It worked!
    Next question - how to stop the RTSP session/stream correctly (I mean in something like Pay-per-minute model, when after some play time stream should be automatically closed).
    I used:

    - rtpsession.rejectSession();
    - rtpsession.shutdown();
    - rtpsession.getRTSPStream().shutdown(new RTPRequestStatus(403, "Forbidden"));
    - rtpsession.getRTSPStream().getStream().close();

    .. but all these methods have bug: in player audio and video stop, but timebar continues moving. Instead, logically there might be some total disconnection with window or msg like "Connection was closed".
    This was reproduced with Android player, QuickTime(Windows).
    VLC sometime crashes, and sometimes totally stops as needed

    I suppose I need to send some message to the player in my code so it will close connection.
    Please advice..

  4. #84
    Join Date
    Dec 2007
    Posts
    25,673

    Default

    There is not a way to send a message the client in RTSP streaming.

    I think rtpSession.shutdown is the right option.

    seek bar still moving a particular player is a player issue.

    Richard

  5. #85

    Default

    the right method is to get the RTPContext from the vhost and call:

    RTPContext.shutdownRTPSession(RTPSession rtpSession);

    Charlie

  6. #86

    Default

    RTPContext.shutdownRTPSession(RTPSession rtpSession);
    thank you, Charlie! However, I see player still does not stop..

    I suppose some shutdown request should be sent to the player.
    It seems that it is really a player "bug", probably it is based on UDP nature or something like this.. Same results I've got by simply closing Wowza.

    I tried some other hacks, but still with no luck..
    Any ideas?

  7. #87

    Default

    I don't know of any other way to do this. We don't have as much control over RTSP/RTP as we do Flash. There is also is not very much consistency between the players. So all we can do is drop the connection.

    Charlie

  8. #88
    Join Date
    Mar 2012
    Posts
    12

    Default

    Hi,

    Does this configuration applicable to audio streaming (live/re-stream)?

  9. #89
    Join Date
    Dec 2007
    Posts
    25,673

    Default

    If for RTSP streaming, yes it is applicable for audio.

    Richard

Page 9 of 9 FirstFirst ... 789

Posting Permissions

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