19 Oct
2012
19 Oct
'12
9:55 p.m.
On 10/19/12 8:30 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
why is that? in failure_route I call
rtpproxy_mange() which calls
unforce_rtp_proxy() which destroys the initiated session.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - http://asipto.com/u/katu
Popping in late, maybe I missed some parts, but I
want to clarify that
all these cases discussed here were not tested with rtpproxy
application, right?
yes, they are all tested with real mediaproxy-ng rtpproxy
server.
For the archive, default config file destroys the
rtp relaying session
in failure_route, when all branches are completed, doing it in onreply
route exposes to a lot of troubles. It is how I use it for many years
(actually I haven't used something else in my deployments) and all seems
fine, no relevant troubles with rtpproxy
so you don't care when current
implementation makes it is possible to
pile up one hour's worth of un-used rtpproxy calls and there is nothing
in kamailio config you can do about it?