Yes, You are correct. Now, SIP endpoint must commit the codec by sending re-INVITE/Update with either 729 or 711 as the codec.
________________________________________ From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Rashid Shakil [EMAIL PROTECTED] Sent: Tuesday, May 20, 2008 8:31 AM To: Vikram Chhibber Cc: [email protected] Subject: Re: [Sip-implementors] Codec Preference Option (RTP ProfileSelection) Thanks for prompt reply. Does it mean that in response to carrier’s INVITE my Softswitch reply with (200 OK) both 729 and 711 as the Codec choices with 729 as preference and 711 sets as fall back? Vikram Chhibber <[EMAIL PROTECTED]> wrote: This SDP seems to be correct. "rtpmap" is not mandatory for static payload types. Payload type 0 belongs in this range and corresponds to G.711 uLaw. Similar is the case for payload type 18 but not for 100 which is a dynamic payload type. On Tue, May 20, 2008 at 8:51 PM, Rashid Shakil wrote: > > Quick question I was analyzing the SDP which my softswtich is sending in > response to an INVITE for an inbound call I received from my SIP peer. I > noticed that I can see two codec choices in media description (m=) line but > the rtpmap attribute of the SDP just showing one. Can any one tell what does > it means and which one has precedence if I have media description and rtpmap > present in an SDP? > > c=IN IP4 5.5.5.2 > t=0 0 > m=audio 21092 RTP/AVP 18 0 100 > a=rtpmap:18 G729/8000 > a=rtpmap:100 telephone-event/8000 > a=fmtp:100 0-11 > > > _______________________________________________ > 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 "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility forloss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
