Sir, Thanks for the reply.
The following is an abstract from RFC3264 section 6.1 page 8: " The interpretation of fmtp parameters in an offer depends on the parameters. Inmany cases, those parameters describe specific configurations of the media format, and should therefore be processed as the media format value itself would be. This means that the same fmtp parameters with the same values MUST be present in the answer if the media format they describe is present in the answer. Other fmtp parameters are more like parameters, for which it is perfectly acceptable for each agent to use different values. In that case, the answer MAY contain fmtp parameters, and those MAY have the same values as those in the offer, or they MAY be different. SDP extensions that define new parameters SHOULD specify the proper interpretation in offer/answer. " Since the "config=" field in my example is specific configuration for MPEG4 simple profile video bitstream, its interpretation should "depends on the parameters", however, I can't find such interpretation in MPEG4 RTP RFC3016. Any of your advice is welcome! Thanks, Fan -----Original Message----- From: Somesh S Shanbhag [mailto:[EMAIL PROTECTED] Sent: Thursday, November 03, 2005 9:33 PM To: Ling, Fan; sip-implementors@cs.columbia.edu Subject: Re: [Sip-implementors] media description in SDP is for sender or receiver? Hi, RFC 3264 specifies sendonly, recvonly, sendrecv and inactive attributes. UA can specify any of these attributes according to it's preference. When no such attribute is present, it is assumed that the stream is "sendrecv" stream and whatever the encodings specified applies to both sender and receiver side. Regards Somesh S. Shanbhag --- "Ling, Fan" <[EMAIL PROTECTED]> wrote: > Hi, > > The following SDP message describes a MPEG4 video > bitstream: > > > > m=video 20000 RTP/AVP 98 34 > > a=rtpmap:98 MP4V-ES/90000 > > a=fmtp:98 > profile-level-id=8;config=000001B008000001B5090000010000000120008440FA28 > 2C2090A21F > > > > Does this SDP message describes the sender encoder > generated media > settings or the required media settings on the > receiver's encoder? Or > both? Can some one point me to the proper RFCs? I > believe this media > settings is for the sender side, but I can't find > definitely > description in any RFCs. > > Thanks a lot > > Fan > > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@cs.columbia.edu > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > ----------------------------------------- SIMPLICITY IS THE BEAUTY. BE NATURAL LIVE NATURAL. ----------------------------------------- Somesh S. Shanbhag Focus Area - VoIP Team (FA-VoIP) Mascon Global Communication Technologies Enterprise of Mascon Global Limited #59/2, 100Ft Ring Road Banashankari II stage Bangalore-560070 Karnataka INDIA Website: http://www.masconit.com ----------------------------------------- __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com _______________________________________________ Sip-implementors mailing list Sip-implementors@cs.columbia.edu http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
