<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Re: [Live-devel] streaming rtp packets containing analysis</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<STYLE type=text/css>BLOCKQUOTE {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
DL {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
UL {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
OL {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
LI {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
</STYLE>
<META content="MSHTML 6.00.2900.3059" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=167313504-03032008><FONT face=Arial
color=#0000ff size=2>Thanks for your reply.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=167313504-03032008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=167313504-03032008><FONT face=Arial
color=#0000ff size=2>I am planning to define new rtp payload. The analytics
information is niether audio nor video but could be some binary data or text
string ... this is still undecided. Since the data wont be a standard audio or
video, I am planning to define new rtppayload (in the range between 96-127,say
99).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=167313504-03032008><FONT face=Arial
color=#0000ff size=2>For this should I need to implement a particular RFC ? I
already have the implementation code for payloadformat type 98 and
hoping to implement on the same lines.But I dont know what all should I
typically implement....especially to wrap the packet into a standard rtp header
which must eventually be streamed to my client.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=167313504-03032008><FONT face=Arial
color=#0000ff size=2>Or is there a different approach to achieve this, like use
any of the existing field in the rtp header (in my existing implementation)to
identify these special packets and handle them accordingly in my client
?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=167313504-03032008><FONT face=Arial
color=#0000ff size=2>I tried changing the mime type text string(while streaming
these special packets which occurs once in a while) in the existing
implementation but the streaming stopped.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=167313504-03032008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=167313504-03032008><FONT face=Arial
color=#0000ff size=2>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=167313504-03032008><FONT face=Arial
color=#0000ff size=2>TN</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=167313504-03032008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> live-devel-bounces@ns.live555.com
[mailto:live-devel-bounces@ns.live555.com] <B>On Behalf Of </B>Ross
Finlayson<BR><B>Sent:</B> Saturday, March 01, 2008 6:17 PM<BR><B>To:</B> LIVE555
Streaming Media - development & use<BR><B>Subject:</B> Re: [Live-devel]
streaming rtp packets containing analysis information through
livemedia<BR></FONT><BR></DIV>
<DIV></DIV>
<BLOCKQUOTE cite="" type="cite"><FONT face=Arial size=-1>My need is to stream
the rtp packets
that possess analysis information.</FONT></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>Which RTP payload format is this? I.e., which RFC (or Internet Draft)
will you be implementing?</DIV><X-SIGSEP><PRE>--
</PRE></X-SIGSEP>
<DIV><BR>Ross Finlayson<BR>Live Networks,
Inc.<BR>http://www.live555.com/</DIV><pre>SASKEN BUSINESS DISCLAIMER
-------------------------
This message may contain confidential, proprietary or legally privileged information. In
case you are not the original intended Recipient of the message, you must not, directly or
indirectly, use, Disclose, distribute, print, or copy any part of this message and you are
requested to delete it and inform the sender. Any views expressed in this message are
those of the individual sender unless otherwise stated. Nothing contained in this message
shall be construed as an offer or acceptance of any offer by Sasken Communication
Technologies Limited ("Sasken") unless sent with that express intent and with due
authority of Sasken. Sasken has taken enough precautions to prevent the spread of
viruses. However the company accepts no liability for any damage caused by any virus
transmitted by this email
</pre></BODY></HTML>