On 09/21/2010 11:27 AM, Daniel-Constantin Mierla wrote:
personally I haven't tested much those functions. Maybe is better for now to mark it obsolete and add a warning message at startup (via fixup), then remove it with next release, allowing some maturity tests for new ones. I am saying that also because most of existing configs out there are using this function and new people will look for it.
I agree.
All of our configs use force_rtp_proxy(), but I would be happy to migrate them; however, I need some reasonable assurance that rtpproxy_offer/answer() will actually work.
As can be seen from a number of previous threads on the list, I had to call force_rtp_proxy() to get several common scenarios to work, even though supposedly rtpproxy_offer/answer() are just wrappers (the code would suggest that), and even though the 'nathelper' documentation says that supposedly they will accept and use the same flags as those listed for force_rtp_proxy() the same way. It has not been true in my experience.