Facing problems during WMP RTSP Streaming

[venugopal_pai]

Hi everyone,
We are developing an RTSP Server to stream mpeg4 and h264 video data muxed in asf and receive them on Winows Media Player 11. The muxing is done by gstreamer's ffmpeg muxer element.

During the session establishment the following RTSP messages are exchanged between the server and the client:

accept()ed connection from 10.60.3.60
RTSPClientSession[0x208338]::incomingRequestHandler1() read 435 bytes:DESCRIBE rtsp://10.60.4.63/Codec10.asf RTSP/1.0
User-Agent: WMPlayer/11.0.5721.5145 guid/3300AD50-2C39-46C0-AE0A-96E496ED836B
Accept: application/sdp
Accept-Charset: UTF-8, *;q=0.1
X-Accept-Authentication: Negotiate, NTLM, Digest, Basic
Accept-Language: en-US, *;q=0.1
CSeq: 1
Supported: com.microsoft.wm.srvppair, com.microsoft.wm.sswitch, com.microsoft.wm.eosmsg, com.microsoft.wm.predstrm, com.microsoft.wm.startupprofile

parseRTSPRequestString() returned cmdName "DESCRIBE", urlPreSuffix "", urlSuffix "Codec10.asf"
sending response: RTSP/1.0 200 OK
Content-Type: application/sdp
Vary: Accept
X-Playlist-Gen-Id: 160
X-Broadcast-Id: 0
Content-Length: 1473
Date: Mon, Jan 05 1970 15:58:33 GMT
CSeq: 1
Server: WMServer/9.5.6001.18000
Content-Base: rtsp://10.60.4.63/Codec10.asf/
Last-Modified: Sat, 29 Nov 2008 13:26:55 GMT
Cache-Control: x-wms-content-size=1002571, max-age=86399, must-revalidate, proxy-revalidate
Etag:"1002571"

v=0
o=- 403067676132 1 IN IP4 10.60.4.63
s=Sony RTSP Server
c=IN IP4 0.0.0.0
i=Codec10.asf
b=AS:879
a=maxps:3200
t=0 0
a=control:rtsp://10.60.4.63/Codec10.asf/
a=etag:{2F39F95A-8E34-8833-5AA8-B9AC06FC4E8A}
a=range:npt=now-
a=recvonly
a=pgmpu:data:application/x-wms-contentdesc,8,language,31,0,,44,WMS_CONTENT_DESCRIPTION_SERVER_BRANDING_INFO,31,12,WMServer/9.5,51,WMS_CONTENT_DESCRIPTION_PLAYLIST_ENTRY_START_OFFSET,3,4,3100,47,WMS_CONTENT_DESCRIPTION_PLAYL IST_ENTRY_DURATION,3,5,14960,58,WMS_CONTENT_DESCRIPTION_COPIED_METADATA_FROM_PLAYLIST_FILE,3,1,1,42, WMS_CONTENT_DESCRIPTION_PLAYLIST_ENTRY_URL,31,27,Codec25.asf%0D%0A
a=pgmpu:data:application/vnd.ms.wms-hdr.asfv1;base64,MCaydY5mzxGm2QCqAGLObHkBAAAAAAAABAAAAAECodyrjEepzxGO5ADADCBTZWgAAAAAAAAAAAAAAAAAAAA AAAAAAAAAACsOAAAAAAAAAIA+1d6xnQEBAAAAAAAAANAO3gEAAAAAEAkFAAAAAAAcDAAAAAAAAAIAAACADAAAgAwAAAAAAQC1A79 fLqnPEY7jAMAMIFNlLgAAAAAAAAAR0tOruqnPEY7mAMAMIFNlBgAAAAAAkQfct7epzxGO5gDADCBTZYEAAAAAAAAAwO8ZvE1bzxG o/QCAX1xEKwBX+yBVW88RqP0AgF9cRCsAAAAAAAAAADMAAAAAAAAAAQAAAAAAAAUAANACAAACKAAoAAAAAAUAANACAAABABgAbXA0d gAwKgAAAAAAAAAAAAAAAAAAAAAAQFLRhh0x0BGjpACgyQNI9kQAAAAAAAAAQVLRhh0x0BGjpACgyQNI9gEAAAABAAYAbQBwAGUAZ wA0AAAAAAAEAG1wNHY2JrJ1jmbPEabZAKoAYs5ssgwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAABAQ==
m=video 0 RTP/AVP 96
b=AS:879
b=RS:0
b=RR:0
a=rtpmap:96 x-asf-pf/1000
a=control:video
a=stream:1
m=application 0 RTP/AVP 96
b=RS:0
b=RR:0
a=rtpmap:96 x-wms-rtx/1000
a=control:rtx
a=stream:65536

RTSPClientSession[0x208338]::incomingRequestHandler1() read 364 bytes:SETUP rtsp://10.60.4.63/Codec10.asf/rtx RTSP/1.0
User-Agent: WMPlayer/11.0.5721.5145 guid/3300AD50-2C39-46C0-AE0A-96E496ED836B
Accept-Charset: UTF-8, *;q=0.1
X-Accept-Authentication: Negotiate, NTLM, Digest, Basic
Accept-Language: en-US, *;q=0.1
CSeq: 2
X-Playlist-Gen-Id: 160
Transport: RTP/AVP/UDP;unicast;client_port=1890-1891;ssrc=6a777272;mode=PLAY

RTSP/1.0 200 OK
Transport: RTP/AVP/UDP;unicast;server_port=6970-6971;client_port=1890-1891;ssrc=6e5c2f2f;mode=PLAY
Date: Mon, Jan 05 1970 16:03:03 GMT
CSeq: 2
Session: 1;timeout=60
Server: WMServer/9.5.6001.18000
Supported: com.microsoft.wm.srvppair,com.microsoft.wm.sswitch,com.microsoft.wm.eosmsg,com.microsoft.wm.fastcach e,com.microsoft.wm.packetpairssrc,com.microsoft.wm.startupprofile
Last-Modified: Sat, 29 Nov 2008 13:26:55 GMT
Cache-Control: x-wms-content-size=1002571, max-age=86399, must-revalidate, proxy-revalidate
Etag: "1002571"



RTSPClientSession[0x208338]::incomingRequestHandler1() read 428 bytes:SET_PARAMETER rtsp://10.60.4.63/Codec10.asf RTSP/1.0
Content-Length: 43
User-Agent: WMPlayer/11.0.5721.5145 guid/3300AD50-2C39-46C0-AE0A-96E496ED836B
Accept-Charset: UTF-8, *;q=0.1
X-Accept-Authentication: Negotiate, NTLM, Digest, Basic
Accept-Language: en-US, *;q=0.1
Session: 1
Content-Type: application/x-rtsp-udp-packetpair;charset=UTF-8
CSeq: 3
X-Playlist-Gen-Id: 160

parseRTSPRequestString() returned cmdName "SET_PARAMETER", urlPreSuffix "", urlSuffix "Codec10.asf"
sending response: RTSP/1.0 405 Method Not Allowed
CSeq: 3
Date: Mon, Jan 05 1970 15:58:34 GMT
Allow: OPTIONS, DESCRIBE, SETUP, TEARDOWN, PLAY

RTSPClientSession[0x208338]::incomingRequestHandler1() read 373 bytes:SETUP rtsp://10.60.4.63/Codec10.asf/video RTSP/1.0
User-Agent: WMPlayer/11.0.5721.5145 guid/3300AD50-2C39-46C0-AE0A-96E496ED836B
Accept-Charset: UTF-8, *;q=0.1
X-Accept-Authentication: Negotiate, NTLM, Digest, Basic
Accept-Language: en-US, *;q=0.1
Session: 1
CSeq: 4
X-Playlist-Gen-Id: 160
Transport: RTP/AVP/UDP;unicast;client_port=1848;ssrc=4d499696;mode=PLAY

Sending response:RTSP/1.0 200 OK
Blocksize:1452
Transport: RTP/AVP/UDP;unicast;server_port=6972;client_port=1848;ssrc=6e5c2f2f;mode=PLAY
Date: Mon, Jan 05 1970 15:58:34 GMT
CSeq: 4
Session: 1;timeout=60
Server: WMServer/9.5.6001.18000
Supported: com.microsoft.wm.srvppair,com.microsoft.wm.sswitch,com.microsoft.wm.eosmsg,com.microsoft.wm.fastcach e,com.microsoft.wm.packetpairssrc,com.microsoft.wm.startupprofile
Last-Modified: Sat, 29 Nov 2008 13:26:55 GMT
Cache-Control: x-wms-content-size=1002571, max-age=86399, must-revalidate, proxy-revalidate
Etag: "1002571"

PLAY rtsp://10.60.4.63/Codec10.asf RTSP/1.0
X-Playlist-Seek-Id: 160
User-Agent: WMPlayer/11.0.5721.5145 guid/3300AD50-2C39-46C0-AE0A-B12B4F58DFE5
Accept-Charset: UTF-8, *;q=0.1
X-Accept-Authentication: Negotiate, NTLM, Digest, Basic
Accept-Language: en-US, *;q=0.1
Session: 1
CSeq: 5
Range: npt=0.000-
Bandwidth: 450923
X-Accelerate-Streaming: AccelDuration=8000;AccelBandwidth=383284

RTSP/1.0 200 OK
Date: Mon, Jan 05 1970 16:03:04 GMT
CSeq: 5
Session: 1;timeout=60
Server: WMServer/9.5.6001.18000
Supported: com.microsoft.wm.srvppair, com.microsoft.wm.sswitch, com.microsoft.wm.eosmsg, com.microsoft.wm.fastcache, com.microsoft.wm.packetpairssrc, com.microsoft.wm.startupprofile
Range: npt=0.000-
Scale: 1.000
X-Accelerate-Streaming: AccelBandwidth=1975040;AccelDuration=8000
Speed:1.000
X-StartupProfile: Rate=10,12,15,20,30;MaxBytes=14328,14328,14328,14328,14328;Time=0,0,0,0,0;StartTime=3100;LastTime=80 00;MaxDiffTime=0;MaxDiffSndTime=0;ByteRate=8763,8763,8763,8763,8763;
RTP-Info: url=rtsp://10.60.4.63/Codec10.asf/video;seq=0;rtptime=0

After these exchanges our Gstreamer pipeline starts streaming RTP data to the client port number 1848. We are confirming this after capturing the packets using wireshark .But the WMP isnt' playing back the data. The statistics in WMP show the "packets received" as 0.

We have tried all the possible means but still in vain. Please send me some advises so that this issue can be resolved asap.

Thanks in Advance

Venu

Thanks for the very informative packet log, it makes interesting
reading (though, I'm easily amused ;-)

The best place to ask this though is on the newsgroup
microsoft.public.windowsmedia.sdk

It's possible Alessandro there may have some ideas about the ASF
packetisation.

It's not straightforward to write those packets correctly, so if it's
a homebrew server you may have errors in the code which causes the ASF
parser to not actually fail, but to not report the packet number.

HTH
Cheers - Neil

On Wed, 3 Dec 2008 11:24:41 +0530, venugopal_pai
<venugopal_pai.3jtxbe@DoNotSpam.com> wrote:

>
>Hi everyone,
> We are developing an RTSP Server to stream mpeg4 and h264 video
>data muxed in asf and receive them on Winows Media Player 11. The muxing
>is done by gstreamer's ffmpeg muxer element.
>
>During the session establishment the following RTSP messages are
>exchanged between the server and the client:
>
>accept()ed connection from 10.60.3.60
>RTSPClientSession[0x208338]::incomingRequestHandler1() read 435
>bytes:DESCRIBE rtsp://10.60.4.63/Codec10.asf RTSP/1.0
>User-Agent: WMPlayer/11.0.5721.5145
>guid/3300AD50-2C39-46C0-AE0A-96E496ED836B
>Accept: application/sdp
>Accept-Charset: UTF-8, *;q=0.1
>X-Accept-Authentication: Negotiate, NTLM, Digest, Basic
>Accept-Language: en-US, *;q=0.1
>CSeq: 1
>Supported: com.microsoft.wm.srvppair, com.microsoft.wm.sswitch,
>com.microsoft.wm.eosmsg, com.microsoft.wm.predstrm,
>com.microsoft.wm.startupprofile
>
>parseRTSPRequestString() returned cmdName "DESCRIBE", urlPreSuffix "",
>urlSuffix "Codec10.asf"
>sending response: RTSP/1.0 200 OK
>Content-Type: application/sdp
>Vary: Accept
>X-Playlist-Gen-Id: 160
>X-Broadcast-Id: 0
>Content-Length: 1473
>Date: Mon, Jan 05 1970 15:58:33 GMT
>CSeq: 1
>Server: WMServer/9.5.6001.18000
>Content-Base: rtsp://10.60.4.63/Codec10.asf/
>Last-Modified: Sat, 29 Nov 2008 13:26:55 GMT
>Cache-Control: x-wms-content-size=1002571, max-age=86399,
>must-revalidate, proxy-revalidate
>Etag:"1002571"
>
>v=0
>o=- 403067676132 1 IN IP4 10.60.4.63
>s=Sony RTSP Server
>c=IN IP4 0.0.0.0
>i=Codec10.asf
>b=AS:879
>a=maxps:3200
>t=0 0
>a=control:rtsp://10.60.4.63/Codec10.asf/
>a=etag:{2F39F95A-8E34-8833-5AA8-B9AC06FC4E8A}
>a=range:npt=now-
>a=recvonly
>a=pgmpu:data:application/x-wms-contentdesc,8,language,31,0,,44,WMS_CONTENT_DESCRIPTION_SERVER_BRANDING_INFO,31,12,WMServer/9.5,51,WMS_CONTENT_DESCRIPTION_PLAYLIST_ENTRY_START_OFFSET,3,4,3100,47,WMS_CONTENT_DESCRIPTION_PLAYL IST_ENTRY_DURATION,3,5,14960,58,WMS_CONTENT_DESCRIPTION_COPIED_METADATA_FROM_PLAYLIST_FILE,3,1,1,42, WMS_CONTENT_DESCRIPTION_PLAYLIST_ENTRY_URL,31,27,Codec25.asf%0D%0A
>a=pgmpu:data:application/vnd.ms.wms-hdr.asfv1;base64,MCaydY5mzxGm2QCqAGLObHkBAAAAAAAABAAAAAECodyrjEepzxGO5ADADCBTZWgAAAAAAAAAAAAAAAAAAAA AAAAAAAAAACsOAAAAAAAAAIA+1d6xnQEBAAAAAAAAANAO3gEAAAAAEAkFAAAAAAAcDAAAAAAAAAIAAACADAAAgAwAAAAAAQC1A79 fLqnPEY7jAMAMIFNlLgAAAAAAAAAR0tOruqnPEY7mAMAMIFNlBgAAAAAAkQfct7epzxGO5gDADCBTZYEAAAAAAAAAwO8ZvE1bzxG o/QCAX1xEKwBX+yBVW88RqP0AgF9cRCsAAAAAAAAAADMAAAAAAAAAAQAAAAAAAAUAANACAAACKAAoAAAAAAUAANACAAABABgAbXA0d gAwKgAAAAAAAAAAAAAAAAAAAAAAQFLRhh0x0BGjpACgyQNI9kQAAAAAAAAAQVLRhh0x0BGjpACgyQNI9gEAAAABAAYAbQBwAGUAZ wA0AAAAAAAEAG1wNHY2JrJ1jmbPEabZAKoAYs5ssgwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAABAQ==
>m=video 0 RTP/AVP 96
>b=AS:879
>b=RS:0
>b=RR:0
>a=rtpmap:96 x-asf-pf/1000
>a=control:video
>a=stream:1
>m=application 0 RTP/AVP 96
>b=RS:0
>b=RR:0
>a=rtpmap:96 x-wms-rtx/1000
>a=control:rtx
>a=stream:65536
>
>RTSPClientSession[0x208338]::incomingRequestHandler1() read 364
>bytes:SETUP rtsp://10.60.4.63/Codec10.asf/rtx RTSP/1.0
>User-Agent: WMPlayer/11.0.5721.5145
>guid/3300AD50-2C39-46C0-AE0A-96E496ED836B
>Accept-Charset: UTF-8, *;q=0.1
>X-Accept-Authentication: Negotiate, NTLM, Digest, Basic
>Accept-Language: en-US, *;q=0.1
>CSeq: 2
>X-Playlist-Gen-Id: 160
>Transport:
>RTP/AVP/UDP;unicast;client_port=1890-1891;ssrc=6a777272;mode=PLAY
>
>RTSP/1.0 200 OK
>Transport:
>RTP/AVP/UDP;unicast;server_port=6970-6971;client_port=1890-1891;ssrc=6e5c2f2f;mode=PLAY
>Date: Mon, Jan 05 1970 16:03:03 GMT
>CSeq: 2
>Session: 1;timeout=60
>Server: WMServer/9.5.6001.18000
>Supported:
>com.microsoft.wm.srvppair,com.microsoft.wm.sswitch,com.microsoft.wm.eosmsg,com.microsoft.wm.fastcac he,com.microsoft.wm.packetpairssrc,com.microsoft.wm.startupprofile
>Last-Modified: Sat, 29 Nov 2008 13:26:55 GMT
>Cache-Control: x-wms-content-size=1002571, max-age=86399,
>must-revalidate, proxy-revalidate
>Etag: "1002571"
>
>
>
>RTSPClientSession[0x208338]::incomingRequestHandler1() read 428
>bytes:SET_PARAMETER rtsp://10.60.4.63/Codec10.asf RTSP/1.0
>Content-Length: 43
>User-Agent: WMPlayer/11.0.5721.5145
>guid/3300AD50-2C39-46C0-AE0A-96E496ED836B
>Accept-Charset: UTF-8, *;q=0.1
>X-Accept-Authentication: Negotiate, NTLM, Digest, Basic
>Accept-Language: en-US, *;q=0.1
>Session: 1
>Content-Type: application/x-rtsp-udp-packetpair;charset=UTF-8
>CSeq: 3
>X-Playlist-Gen-Id: 160
>
>parseRTSPRequestString() returned cmdName "SET_PARAMETER", urlPreSuffix
>"", urlSuffix "Codec10.asf"
>sending response: RTSP/1.0 405 Method Not Allowed
>CSeq: 3
>Date: Mon, Jan 05 1970 15:58:34 GMT
>Allow: OPTIONS, DESCRIBE, SETUP, TEARDOWN, PLAY
>
>RTSPClientSession[0x208338]::incomingRequestHandler1() read 373
>bytes:SETUP rtsp://10.60.4.63/Codec10.asf/video RTSP/1.0
>User-Agent: WMPlayer/11.0.5721.5145
>guid/3300AD50-2C39-46C0-AE0A-96E496ED836B
>Accept-Charset: UTF-8, *;q=0.1
>X-Accept-Authentication: Negotiate, NTLM, Digest, Basic
>Accept-Language: en-US, *;q=0.1
>Session: 1
>CSeq: 4
>X-Playlist-Gen-Id: 160
>Transport:
>RTP/AVP/UDP;unicast;client_port=1848;ssrc=4d499696;mode=PLAY
>
>Sending response:RTSP/1.0 200 OK
>Blocksize:1452
>Transport:
>RTP/AVP/UDP;unicast;server_port=6972;client_port=1848;ssrc=6e5c2f2f;mode=PLAY
>Date: Mon, Jan 05 1970 15:58:34 GMT
>CSeq: 4
>Session: 1;timeout=60
>Server: WMServer/9.5.6001.18000
>Supported:
>com.microsoft.wm.srvppair,com.microsoft.wm.sswitch,com.microsoft.wm.eosmsg,com.microsoft.wm.fastcac he,com.microsoft.wm.packetpairssrc,com.microsoft.wm.startupprofile
>Last-Modified: Sat, 29 Nov 2008 13:26:55 GMT
>Cache-Control: x-wms-content-size=1002571, max-age=86399,
>must-revalidate, proxy-revalidate
>Etag: "1002571"
>
>PLAY rtsp://10.60.4.63/Codec10.asf RTSP/1.0
>X-Playlist-Seek-Id: 160
>User-Agent: WMPlayer/11.0.5721.5145
>guid/3300AD50-2C39-46C0-AE0A-B12B4F58DFE5
>Accept-Charset: UTF-8, *;q=0.1
>X-Accept-Authentication: Negotiate, NTLM, Digest, Basic
>Accept-Language: en-US, *;q=0.1
>Session: 1
>CSeq: 5
>Range: npt=0.000-
>Bandwidth: 450923
>X-Accelerate-Streaming: AccelDuration=8000;AccelBandwidth=383284
>
>RTSP/1.0 200 OK
>Date: Mon, Jan 05 1970 16:03:04 GMT
>CSeq: 5
>Session: 1;timeout=60
>Server: WMServer/9.5.6001.18000
>Supported: com.microsoft.wm.srvppair, com.microsoft.wm.sswitch,
>com.microsoft.wm.eosmsg, com.microsoft.wm.fastcache,
>com.microsoft.wm.packetpairssrc, com.microsoft.wm.startupprofile
>Range: npt=0.000-
>Scale: 1.000
>X-Accelerate-Streaming: AccelBandwidth=1975040;AccelDuration=8000
>Speed:1.000
>X-StartupProfile:
>Rate=10,12,15,20,30;MaxBytes=14328,14328,14328,14328,14328;Time=0,0,0,0,0;StartTime=3100;LastTime=8 000;MaxDiffTime=0;MaxDiffSndTime=0;ByteRate=8763,8763,8763,8763,8763;
>RTP-Info: url=rtsp://10.60.4.63/Codec10.asf/video;seq=0;rtptime=0
>
>After these exchanges our Gstreamer pipeline starts streaming RTP data
>to the client port number 1848. We are confirming this after capturing
>the packets using wireshark .But the WMP isnt' playing back the data.
>The statistics in WMP show the "packets received" as 0.
>
>We have tried all the possible means but still in vain. Please send me
>some advises so that this issue can be resolved asap.
>
>Thanks in Advance
>
>Venu
------------------------------------------------
Digital Media MVP : 2004-2008
http://mvp.support.microsoft.com/mvpfaqs

[venugopal_pai]

We are using the same ASF parser to stream to VLC player and we get a perfect playback. So i don't think there is a problem with the ASF parser.

Even if there is a prob WMP should receive the packets and drop them. But it aint receiving any.

Or is it that WMP expects the data to be packetized and streamed differently from the normal packetization method?

One more observation:- When WMP sends a SET_PARAMETER we replay with a 405 Method Not Supported. Will this affect the streaming of data in any way?

And thanks for giving me the right resource.

[Lmss]

Hi There!

I'm developing a streaming server, and I'm also stuck with the same problem.
I managed to implement at least the minimum "non-standard" RTSP negotiation, to make windows media player happy :) , but after the PLAY message, my server starts to send the x-asf VIDEO/AUDIOoRTPoRTSP interleaved to the player, but nothing happens, wmp doesn't decode the stream received but doesn't give any error also.

The connection timeouts after 60s, and wmp terminates the TCP connection, saying that couldn't found the media file ...a very weird error.

The streaming is being relayed from a Windows Media Services server, I have the suspicion that may have something to do with the RTP timestamps.

Using VLC I can receive and decode the stream correctly... :S

Could you manage to found a solution to your problem?

Because I think the cause of our problem is the same of mine.

ps) Going back to MS documentation ...


Best Regards,
Luis Silva

[venugopal_pai]

Hi Luis,
Yes we were facing the same problems during development. Now we are on the right track. I have got a few doubts regarding your query.
1) Did you follow MS-RTSP document completely while implementing the streaming server? I asked this because many often forget to send the UDP packets and the 'rtx' response during session establishment. Even if we dont send this the player ends up till the "PLAY" request but does not accept the streamed data.
2) If you are streaming from Windows Media Server and WMP is able to playback the file then there is no problem with the timestamp. And about packetization if your packet has the same structure as mentioned in MS-RTSP then that should not be a hindrance.
3) Which video format is used in ASF container? If it is MPEG-4 then the header needs to be set properly for playback. If it it H-264 then a codec needs to be installed.

Waiting for your reply
Regards
Venu

[Lmss]

Dear Venu,

Thank you very much for your fast reply, about your questions
answers below:

Originally Posted by venugopal_pai

Hi Luis,
Yes we were facing the same problems during development. Now we are on the right track. I have got a few doubts regarding your query.
1) Did you follow MS-RTSP document completely while implementing the streaming server? I asked this because many often forget to send the UDP packets and the 'rtx' response during session establishment. Even if we dont send this the player ends up till the "PLAY" request but does not accept the streamed data.

lmss> Nope, I will check this then, we have noted inspecting the connection establishment between wmp -> wms, that the 1st RTP packet is a little odd, since it has a strange size...maybe is the packet you are talking about ... thanks :)

Originally Posted by venugopal_pai

2) If you are streaming from Windows Media Server and WMP is able to playback the file then there is no problem with the timestamp. And about packetization if your packet has the same structure as mentioned in MS-RTSP then that should not be a hindrance.

lmss> We are relaying the asf-x stream directly from windows media service, over the RTSP tcp connection, using of course the same packetization mencioned in MS-RTSP (rfc2326). What we wan't to build is a relaying server, for I&D purposes, we want to latter inspect the rtp stream and manipulate it, to implement some special features. (We have already done it, using mp4, and with other players like quicktime and vlc, we are facing problems only with wmp).

Originally Posted by venugopal_pai

3) Which video format is used in ASF container? If it is MPEG-4 then the header needs to be set properly for playback. If it it H-264 then a codec needs to be installed.

lmss> We are using wmv9 codec, our aim is to use vc-1 codec, but since wmv9 is vc1 compliant, for now we use this as our initial testing base. Since we are for now just forwarding the stream received, wms is responsable for the ASF stream construction.

Originally Posted by venugopal_pai

Waiting for your reply
Regards
Venu

[venugopal_pai]

lmss> Nope, I will check this then, we have noted inspecting the connection establishment between wmp -> wms, that the 1st RTP packet is a little odd, since it has a strange size...maybe is the packet you are talking about ... thanks :)
Venu> I think this maybe the problem. Just to make things easier for you i ll give you a small summary of RTSP interaction between server and wmp.
The WMP sends the DESCRIBE request for which the server should respond with 200 OK along with the SDP information. WMP then sends a SETUP message for retransmission. The server should respond with 200 OK on the port number mentioned in SETUP request. WMP then send a SET PARAMETER request with "Content-Type: application/x-rtsp-udp-packetpair;charset=UTF-8" message. This means the server is supposed to send 3 udp packets in the port number mentioned in SETUP request. The size of each packet should be 1307, 1308 and 1309 bytes respectively and they should be filed with highly entropic data. This is done so that wmp can calculate the bandwidth of the network.
After this WMP sends SETUP request for audio and video and then the PLAY request.
The above steps are a must if we have to successfully establish the connection with WMP .Also while sending RTP data see to it that the size of RTP payload packets between marker bits add upto 3200 bytes.

Regards
Venu