Can you please send the offer SDP and answer SDP? Thanks, Somesh
-----Original Message----- From: ext Aman Aggarwal [mailto:[email protected]] Sent: Friday, October 14, 2011 11:47 AM To: Shanbhag, Somesh (NSN - IN/Bangalore); sip-implementors Subject: RE: [Sip-implementors] Dynamic codecs having same payload name as of static codecs Thanks Somesh for the inputs. Can you provide some reference for that? Here, we are facing the issue while negotiating codecs with media manager. Media manager has suggested to use codec 8 but UA is sending 8 and 98 towards it for final commitment as 98 has the same name of 8. For dynamic codecs, we are matching payload names with the suggested codecs from media manager. -----Original Message----- From: Shanbhag, Somesh (NSN - IN/Bangalore) [mailto:[email protected]] Sent: Friday, October 14, 2011 11:15 AM To: Aman Aggarwal; sip-implementors Subject: RE: [Sip-implementors] Dynamic codecs having same payload name as of static codecs Yes, they can have the same. While parsing, a=rtpmap takes the highest precedence. We had encountered a similar situation in iterop where in we had to change the code to take from the a=rtpmap as the precedence, rather than static payload numbers. But yes, if a=rtpmap for the corresponding number is absent, we can go according to RFC 3550/RFC551. Regards, Somesh -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ext Aman Aggarwal Sent: Friday, October 14, 2011 11:11 AM To: sip-implementors Subject: [Sip-implementors] Dynamic codecs having same payload name as of static codecs Hi All, Can the dynamic codec have the same payload name as that of static codec in rtpmap attribute? Please check the below SDP format:- m=audio 32420 RTP/AVP 8 0 98 99 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:98 PCMA/8000 a=rtpmap:99 PCMU/8000 RFC 3264 do mention that dynamic codecs must have rtpmap attribute but can they have same name. Please provide some inputs. Regards, Aman Aggarwal =============================================================================== Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. =============================================================================== _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors =============================================================================== Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. =============================================================================== _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
