Re: Helix server sending(RDT over UDP) big size packets

You are using unsupported content.

 > a=mimetype:string;"video/X-HX-AVC1"

This means that you are streaming h.264 using the helix
client side
packetizer. This will certainly have large packets, as the
"packets" are
not intended to ever be sent on the wire, only passed
between components
on the client while playing back from a file.

h.264 is supported by the helix server *only* in hinted
files (or live
streams). The server *should* log an error and fail to
stream in case
unhinted h.264 streaming is attempted. It's possible that
some versions
will stream non-hinted streaming using the client side
packetization and
you are using one such server, so the content problem is not
obvious.
Or you may be using a client side mp4 file format plugin on
your server,
which you should definitely not do, since all mp4/3gp files
would then
be stream using client side packetizers rather than correct
server
packetizers or hint tracks.

Thanks,
Jamie

ext-saleem.adookkattilnokia.com wrote:
> It's a a/v clip with H264 and AAC coding. The file
format is mp4. Below
> given is the SDP received from the server.
> 
> v=0
> o=- 1177572840 1177572840 IN IP4 195.134.224.30
> s=h264_qvga_aac_48khz_768kbits_30fps.mp4
> i=<No author> <No copyright>
> c=IN IP4 0.0.0.0
> t=0 0
> a=SdpplinVersion:1610641560
> a=StreamCount:integer;2
> a=control
> a=DefaultLicenseValue:integer;0
> a=FileType:string;"MPEG4"
>
a=LicenseKey:string;"license.Summary.Datatypes.RealMPEG
4.Enabled"
> a=range:npt=0-56.298000
> m=video 0 RTP/AVP 96
> b=AS:781
> b=RR:28936
> b=RS:9645
> a=control:streamid=1
> a=range:npt=0-53.686000
> a=length:npt=53.686000
> a=rtpmap:96 X-HX-AVC1/90000
> a=fmtp:96 
> a=mimetype:string;"video/X-HX-AVC1"
> a=AvgBitRate:integer;771642
> a=Width:integer;320
> a=Height:integer;240
> a=HasOutOfOrderTS:integer;1
> a=Preroll:integer;1000
>
a=OpaqueData:buffer;"AAAAKWF2Y0MBTQAo/+EAEmdNACiadAoP0I
AHoxQA5OGxQgEABGj
> uPIA="
> a=StreamName:string;"Video Track"
>
a=ASMRuleBook:string;"Marker=0,AverageBandwidth=771642,
TimeStampDelivery
>
=TRUE;Marker=1,AverageBandwidth=0,TimeStampDelivery=TRUE;&qu
ot;
> m=audio 0 RTP/AVP 97
> b=AS:169
> b=RR:5999
> b=RS:2000
> a=control:streamid=2
> a=range:npt=0-56.298000
> a=length:npt=56.298000
> a=rtpmap:97 MP4A-LATM/48000
> a=fmtp:97 object=2; cpresent=0; profile-level-id=15;
config=400023203fc0
> a=mimetype:string;"audio/MP4A-LATM"
> a=AvgBitRate:integer;160000
> a=MaxBitRate:integer;160000
> a=HasOutOfOrderTS:integer;1
> a=Preroll:integer;1000
>
a=OpaqueData:buffer;"AxkAAgAEEUAVAAAAAAJxAAACcQAFAhGQBg
EC"
> a=StreamName:string;"Audio Track"
>
a=ASMRuleBook:string;"Marker=0,AverageBandwidth=160000,
TimeStampDelivery
>
=TRUE;Marker=1,AverageBandwidth=0,TimeStampDelivery=TRUE;&qu
ot;
> SETUP
>
rtsp://195.134.224.30:554/sppr/h264_qvga_aac_48khz_768kbits_
30fps.mp4/st
> reamid=1 RTSP/1.0
> CSeq: 3
> RealChallenge2:
84d115e6f25d090d1c389bf2509a217f01d0a8e3, sd=81f01952
> RDTFeatureLevel: 3
> Transport:
>
x-real-rdt/udp;client_port=6970;mode=play,x-pn-tng/udp;clien
t_port=6970;
>
mode=play,RTP/AVP;unicast;client_port=6970-6971;mode=play
> User-Agent: RealMedia Player HelixDNAClient/10.0.0.6839
(symbian)
> If-Match: 1693003572-1
> 
> -----Original Message-----
> From: ext Greg Wright [mailto:gwrightreal.com]

> Sent: Friday, December 21, 2007 12:19 PM
> To: Adookkattil Saleem (EXT-Infovision-MSW/Dallas)
> Cc: nokia-private-devhelixcommunity.org;
> datatype-devhelixcommunity.org; helix-server-devhelixcommunity.org; Yu
> I-Chin (Nokia-TP-MSW/Dallas)
> Subject: Re: [Helix-server-dev] Helix server
sending(RDT over UDP) big
> size packets
> 
> ext-saleem.adookkattilnokia.com wrote:
>> Hi,
>>
>> I am working on an error report and noticed helix
server sending big 
>> size RDT packets from the server. My helix client
streaming protocol 
>> setup is RDT over UDP and the read socket buffer
size upper limit is
> 4K.
>> Sometimes the client receives packet size that is
greater than 4K and 
>> the client failed to get one complete RDT packet at
time. It causes 
>> the client to process partial RDT packet and
crashes when it processes
> 
>> the second part of the packet. I am able to receive
packets and play 
>> the clip fine if I increase the buffer size to
handle these packets. 
>> My concern is that why do we transmit such a big
size RDT packet over 
>> UDP from the server. I would like to know whether
it is a server 
>> failure. I am sending network log along with the
mail. Any suggestion 
>> to fix this error is appreciated. I don't see this
problem happening 
>> when streaming same clip with RTP over UDP.
> 
> I have never seen the server send a UDP packet bigger
then the MTU. As
> far as I know it is up to the file format to create the
packets that the
> server sends. The file formats usually know if they are
in a
> streaming(server) or local(client) environment and
generate packets of
> sizes that make sense for each case. What data format
are you playing
> with? What is the content?
> 
> Server team might know more,
> --greg.
> 
> 
>> Thank you
>> Saleem
>>
>>
>> <<probe.cap>>
>>
>>
>>
------------------------------------------------------------
----------
>> --
>>
>> _______________________________________________
>> Helix-server-dev mailing list
>> Helix-server-devhelixcommunity.org
>> http://lists.helixcommunity.org/mailman/listinf
o/helix-server-dev
> 
> 
> _______________________________________________
> Datatype-dev mailing list
> Datatype-devhelixcommunity.org
> http://lists.helixcommunity.org/mailman/listinfo/da
tatype-dev

_______________________________________________
Helix-server-dev mailing list
Helix-server-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinf
o/helix-server-dev