2011/4/14 Ali Kemal MAYUK <alikemalma...@gmail.com>: > I have searched the RFC2327 and RFC3264 but couldn' find the answer. What if > an SDP request has requested one codec type but it include more than one > rtpmap codec details headers. Does it suitable? Does it cause an codec error > with 4XX response ? > > Below is an example; > > v=0 > o=8355420 2735943290 2735943290 IN IP4 192.168.2.85 > s=Session SDP > t=0 0 > *m=audio 43192 RTP/AVP 18* > c=IN IP4 91.93.89.98 > *a=rtpmap:18 G729/8000/1* > *a=rtpmap:4 G723/8000/1* > *a=rtpmap:2 G726-32/8000/1* > *a=rtpmap:0 PCMU/8000/1* > *a=rtpmap:8 PCMA/8000/1* > a=nortpproxy:yes
"a=rtpmap" lines just add more information about codecs listed in the "m" line. If such codec is not listed in "m" the receiver should ignore the "a=rtpmap" line (as it is not useful at all). I don't think this case should produce a SDP parsing or procesing error. -- Iñaki Baz Castillo <i...@aliax.net> _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
