On Mon, Oct 23, 2006 at 05:47:56PM -0500, Kevin P. Fleming wrote: > > (However, I have no idea what these devices would do if you completed the > > call, and then they had to use the 'WIBBLE' codec to send audio...) > > I don't think that my proposal is practical; instead, what I am going to > do is to modify the channel drivers to not offer formats (audio or video > codecs) which either don't match the incoming channel's format, or are > not transcodable to that format. The translation core already has all > the information needed to do this. > > While this won't have the complete effect you wanted (forcing the 'B' > endpoint to only select the no-transcode-needed format), it will be > close, given that we put the no-transcode-needed format at the top of > that list in the SDP.
OK, that's good (it looks like our mails crossed) > If the 'B' endpoint chooses another format which > requires transcoding in spite of our stated preference, there's no > simple way for us to deal with it. Yep. So if you've already offered all those codecs to the second phone, and with a direct RTP path back to the first phone, you'd better reinvite quickly to make the RTP path go via Asterisk. Regards, Brian. _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
