> > Does somebody else have other opinions? > > Well, we can use user SDP with hairier cases. > > The problem with SOATAG_MODE is the duplicated media, but I guess that > in 99 % of those cases where we have more than one m= line per media > (e.g., separate m= line for DTMF tones) all the m= lines for a > specific media follow the same mode setting.
perhaps we should think about that because it is not possible in this version but if we add a new function we should also try to solve this issue, too > > > I dont know if the sofia-sip politic side is able to remove the > > SOATAG_HOLD but I think this option is not able to implement the > > required stuff for changing the media mode to every required state. If > > we would only change SOATAG_HOLD to deprecated and add the new > > SOATAG_MODE we will have to implement the new functionality but have > > take care of not breaking the old SOATAG_HOLD. > > We certainly have to keep the API/ABI compatibility (till 1.13, > whenever that will be.), so breaking SOATAG_HOLD() is not an option. OK. I thought that. Or is it better to creae only a function for setting the (or one specific) media to sendrecv (like SOTAG_ACTIVE)? And later on we can change SOTAG_HOLD that it is able to change the media mode of one specific stream. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
