RFC 3264:
" However, in the case of RTP, the mapping from a particular dynamic payload type number to a particular codec within that media stream MUST NOT change for the duration of a session. For example, if A generates an offer with G.711 assigned to dynamic payload type number 46, payload type number 46 MUST refer to G.711 from that point forward in any offers or answers for that media stream within the session. " Mustafa Aydın NGN Services Verscom Solutions -----Original Message----- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Kumar, Puneet (Puneet) Sent: Wednesday, January 21, 2015 9:09 AM To: sip-implementors@lists.cs.columbia.edu Subject: [Sip-implementors] Is it allowed to use same rtp dynamic payload type for two different codecs. Hi All, Is below SDP valid: m=audio 5004 RTP/AVP 8 103 18 103 a=rtpmap:8 PCMA/8000/1 a=rtpmap:103 G726-32/8000/1 a=rtpmap:18 G729/8000/1 a=fmtp:18 annexb=no a=rtpmap:103 telephone-event/8000 Which RFC text is allowing or blocking it ? Thanks, Puneet _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu<mailto:Sip-implementors@lists.cs.columbia.edu> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
