30 May
2011
30 May
'11
12:54 p.m.
On 5/30/11 9:50 AM, Alex Hermann wrote:
On Saturday 28 May 2011 18:42:07 Daniel-Constantin
Mierla wrote:
in
failure_route you enable a branch_route execution and there you call
rtpproxy_maange() -- this is the way of avoiding conflict decision with
failure_route for the cases when it is a new relay or not.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
http://linkedin.com/in/miconda -- http://twitter.com/miconda
rtpproxy: close rtpproxy session for INVITE req
in failure route
- update of rtpproxy_manage() to close rtp relay session when executed
in failure route
Maybe i misunderstood the concept of this new function, but
how is this patch
compatible with the scenario in which the first branch does not need rtpproxy,
so rtpproxy_manage() is not called, but the second branch launched from
failure_route does. I suppose that with this patch, you can't use
rtpproxy_manage() from failure_route anymore to enable the rtpproxy?