All of this was the reason that the simcap specification was written, to handle capabilities, and in particular, this important one - that a single codec at a time can be supported. Please take a look at:
http://search.ietf.org/internet-drafts/draft-andreasen-mmusic-sdp-simcap-04.txt -Jonathan R. David Most wrote: > No. If your UAC has the ability to receive multiple codecs all at once, then by all >means send them all in your offer. If you cannot receive multiple codecs, then DO >NOT send them! > > Solution: send the preferred codec in the offer. If the UAS doesn't support that >codec, they'll send "options sdp" in the 4xx (forget which one) response the giving >reason they don't support the INVITE as is. The UAC may choose a codec from the >response sdp and re-invite. > > At 04:06 PM 12/13/01 +0000, Nick Hollinghurst wrote: > >>It's still not a complete solution, though: now it puts the pressure on >>the UAS. *Somebody* has to make an offer, and for maximal compatibility it >>should list as many codecs as it knows about; yet it can't be sure that >>the other end will pick only one, because SDP allows it to pick several. >> > > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Avenue Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 [EMAIL PROTECTED] FAX: (973) 952-5050 http://www.jdrosen.net PH: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
