There is a technical limitation to what SDP can legally convey. A single SDP document can contain only one end of media "conversation". Therefore it is technically impossible to setup streaming with just one SDP document there have to be an exchange. When using RTSP or SIP terminals exchange their SDP information and thus get to know where to stream to and from where to accept the stream.
MediaPlayer could accept just one SDP (i.e. streamer's), but then how would streamer would know where to transmit? Both of them have to exchange at least supported CODEC information and connection information (port and IP). Maybe I am just not aware of SDP format with two node's information. Can someone share an example? On May 27, 3:22 pm, debelyoo <[email protected]> wrote: > I agree with Andy's comment: > > On May 25, 8:36 am, Andy Savage <[email protected]> wrote: > > > There seems to be a limitation that means that it will only accept SDP > > information with RTP streams inside if it gets them from the RTSP stream > > (e.g. it gets this information from SETUP in the RTSP protocal). > > It is possible to play a stream by requesting it via a RTSP request > (both audio and video are sent over RTP and the MediaPlayer is able to > decode and play them). > But it is not possible to play live RTP stream by requesting the SDP > file directly (via an HTTP request). The RTP streams (audio and video) > are sent to the device from the server. The MediaPlayer should "just" > get the SDP file, listen on the proper ports and decode the streams. > But it generates an error and do not play the streams. > > Jean -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
