[MPlayer-dev-eng] Re: FYI: Overview of Microsoft Windows Media 9 Serie

[Ross Finlayson]

> > BTW, if anyone knows a publically accessible "rtsp://..." URL for a Windows
> > Media 9 session, just let me know, and I'll see if the LIVE.COM RTSP client
> > code (which is use in mplayer's optional RTSP streaming support) can be
> > made to stream it.
> >
> >          Ross.
>
>
>MSNBC is running WM9 servers.
>For example:
>mms://od-msnbc.msnbc.com/msnbc/video/100/dl_kotb_kids_020813.asf
>
>Just replace mms by rtsp if you see that the server's name is Cougar/9.0.0.x
>It gives you the session below.
[...]
>Sending request: DESCRIBE
>rtsp://od-msnbc.msnbc.com/msnbc/video/100/dl_kotb_kids_020813.asf RTSP/1.0
>CSeq: 1
>Accept: application/sdp
>User-Agent: mplayer (LIVE.COM Streaming Media)
>
>
>Received DESCRIBE response: RTSP/1.0 200 OK
>Content-Type: application/sdp
>Vary: Accept
>X-Playlist-Gen-Id: 2017491
>X-Broadcast-Id: 0
>Content-Length: 2400
>Date: Mon, 09 Sep 2002 01:37:14 GMT
>CSeq: 1
>Server: WMServer/9.0.0.3191
>Supported: com.microsoft.wm.srvppair, com.microsoft.wm.sswitch,
>com.microsoft.wm.eosmsg, com.microsoft.wm.fastcache,
>com.microsoft.wm.packetpairssrc
>Last-Modified: Wed, 14 Aug 2002 03:09:08 GMT
>Cache-Control: x-wms-content-size=2230625, max-age=599,
>x-wms-event-subscription="remote-log", must-revalidate, proxy-revalidate
>Etag: "2230625"
>
>v=0
>o=- 200209021720130500 200209021720130500 IN IP4 127.0.0.1
>s=<No Title>
>c=IN IP4 0.0.0.0
>b=AS:101
>a=maxps:1252
>t=0 0
>a=control:rtsp://od-msnbc.msnbc.com/msnbc/video/100/dl_kotb_kids_020813.asf/
>a=etag:{9B64042C-0E85-B1DB-D47E-FE6786DA5D08}
>a=range:npt=5.102-183.494
>a=recvonly
>a=pgmpu:data:application/x-wms-contentdesc,8,language,31,0,,5,title,31,0,,6,author,31,0,,9,copyright,31,0,,35,WMS_CONTENT_DESCRIPTION_DESCRIPTION,31,0,,30,WMS_CONTENT_DESCRIPTION_RATING,31,0,,44,WMS_CONTENT_DESCRIPTION_SERVER_BRANDING_INFO,31,12,WMServer/9.0,51,WMS_CONTENT_DESCRIPTION_PLAYLIST_ENTRY_START_OFFSET,3,4,5102,47,WMS_CONTENT_DESCRIPTION_PLAYLIST_ENTRY_DURATION,3,6,178392,58,WMS_CONTENT_DESCRIPTION_COPIED_METADATA_FROM_PLAYLIST_FILE,3,1,1,42,WMS_CONTENT_DESCRIPTION_PLAYLIST_ENTRY_URL,31,23,dl_kotb_kids_020813.asf%0D%0A
>a=pgmpu:data:application/vnd.ms.wms-hdr.asfv1;base64,MCaydY5mzxGm2QCq
>No stream found

The problem here is that the SDP description (the text beginning "v=0") 
that's returned by Microsoft's RTSP server does not contain any media 
description(s) - these would be lines beginning "m=".  Therefore, the RTSP 
client code can't do anything with this.


>I also attached a valid rtsp session between a WMP9 and a WMS9
>as you can see they added some proprio fields in the headers.

Yes, thanks for sending this.  I see that in this case there are "m=" lines 
in the returned SDP:
         m=audio 0 RTP/AVP 96
         a=rtpmap:96 x-asf-pf/1000
         m=application 0 RTP/AVP 96
         a=rtpmap:96 x-wms-rtx/1000
         m=video 0 RTP/AVP 96
         a=rtpmap:96 x-asf-pf/1000
However, this uses a different "rtsp://" URL: rtsp://BLUEDOG/od

>BTW if you try to get the session working make sure that you duplicate all the
>fields as the ones you can find in the attached session.
>The session might simply failed because you put mplayer as an user-agent
>instead of :
>User-Agent: WMPlayer/9.0.0.2773 guid/3300AD50-2C39-46C0-AE0A-D929F06A1DE1
>That's the case for the "old" server and player. They will not work if the
>user agent of the server or the client is not one they know.

Yes, this is no surprise :-)  It will be interesting to see if they - like 
RealNetworks - also include some sort of challenge/response mechanism to 
ensure that only 'authorized' clients can access their streams.

>It's why I asked you if there is a way of adding/removing fields in the
>headers with the live rtsp library.

You can do this easily by modifying "liveMedia/RTSPClient.cpp" as appropriate.

         Ross.