Thanks for your reply. 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). 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. 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 ? 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. Thanks, TN
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ross Finlayson Sent: Saturday, March 01, 2008 6:17 PM To: LIVE555 Streaming Media - development & use Subject: Re: [Live-devel] streaming rtp packets containing analysis information through livemedia My need is to stream the rtp packets that possess analysis information. Which RTP payload format is this? I.e., which RFC (or Internet Draft) will you be implementing? -- Ross Finlayson Live Networks, Inc. http://www.live555.com/ 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
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
