Typically this is implementation dependent. As by the saying "Be liberal in receiving and strict in sending", we have to ignore the a= lines which are extra and take only those lines which are specified in the codec list. Typically the implementation will be such that you read the codec list and move on to the rtpmap.
Also, if the application is SBC, you may want to decide wheather to forward the extra rtpmap or send only which are relevant. Regards, Somesh -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ext Ali Kemal MAYUK Sent: Thursday, April 14, 2011 12:01 PM To: [email protected] Subject: [Sip-implementors] Multiple rtpmap header for only one codec typein Media header Hi; 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 -- Regards Kemal _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
