Answer by Sandeep Agarwal · Mar 28, 2012 at 06:14 PM
I've a call-flow, where A tries to set up a live stream to Wowza server (using RTSP ANNOUNCE/SETUP/RECORD), which would reflect it to B. However, when B tries to setup the RTSP session using DESCRIBE, the 200 OK to DESCRIBE from Wowza only contains incomplete SDP, with no media attributes, which make B give up on trying to play the video.
Here is the SDP in ANNOUNCE sent by A to Wowza:
o=- 0 0 IN IP4 127.0.0.1
c=IN IP4 192.168.2.119
m=video 0 RTP/AVP 105
a=fmtp:105 profile-level-id=42e01e; packetization-mode=1; sprop-parameter-sets=Z0IACpZUCg+I,aM44gA==
m=audio 0 RTP/AVP 106
and here is the incomplete SDP sent by Wowza to B, in 200 OK to DESCRIBE:
o=- 235374812 235374812 IN IP4 127.0.0.1
c=IN IP4 0.0.0.0
I know that AMR as an audio codec is not supported by Wowza; however, even when I changed the audio codec to AAC also, the same problem persisted. One other thing of note is: in the SETUP(subsequent to ANNOUNCE) sent by A(handwritten client) to Wowza, A sends "mode=receive", and doesn't send the session ID sent back by Wowza in 200 OK to ANNOUNCE. Could this make Wowza refuse to reflect the session?
In the Wowza error logs, this is what I get:
WARN server comment 2012-03-27 18:57:16 - - - - - 11944.279 - - - - - - - - RTPStream.idle[235374812:live/_definst_:]: Close RTSP/RTP session. Session timeout: 90000
Could someone help? Thx.
Live Streaming recording on iOS 2 Answers
Live streaming with HTML5 3 Answers
RTMP vs RTSP 1 Answer