Redownload patch7 and re-apply. I made a mistake in the fix. It is fixed now.
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).
- rtpsession.getRTSPStream().shutdown(new RTPRequestStatus(403, "Forbidden"));
.. 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.
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.
the right method is to get the RTPContext from the vhost and call:
thank you, Charlie! However, I see player still does not stop..RTPContext.shutdownRTPSession(RTPSession rtpSession);
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..
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.
Does this configuration applicable to audio streaming (live/re-stream)?
If for RTSP streaming, yes it is applicable for audio.