22 Sep
2010
22 Sep
'10
6:05 p.m.
On Wed, Sep 22, 2010 at 3:42 AM, Klaus Darilion
<klaus.mailinglists(a)pernau.at> wrote:
Am 21.09.2010 17:12, schrieb Ovidiu Sas:
What you propose is a new functionality. I would prefer a new name
(engage_rtp_proxy) for this function and still drop the old
force_rtp_proxy.
Regards,
Ovidiu Sas
Hello all,
I would like to propose the removal of force_rtp_proxy function from
the rtpproxy (k) module.
Instead, the rtpproxy_offer/rtpproxy_answer should be used.
Why?
- force_rtp_proxy no longer support 200ok/ACK SDP negotiation ('s'
flag was deprecated);
- all functionality of force_rtp_proxy is provided by
rtpproxy_offer/rtpproxy_answer;
- rtpproxy_offer/rtpproxy_answer is easier to use in the config.
Objections?
I would prefer to keep force_rtp_proxy and make it detect late-offer-answer
automatically. So just calling force_rtp_proxy() on INVITE, 200 and ACK and
it should work in all cases. (just like mediaproxy)