28 Jan
2010
28 Jan
'10
12:33 a.m.
It is the expected behavior. You can do that on failure_route (if you arm one).
And if you do redirection based on 3xx, there's no need to terminated
the rtp session and start a new one.
Regards,
Ovidiu Sas
On Wed, Jan 27, 2010 at 8:27 AM, Iñaki Baz Castillo <ibc(a)aliax.net> wrote:
Hi, I'm realizing that rtpproxy session is not
automatically terminated when
an outgoing INVITE transaction fails ([3456]XX response received from
downstream), so the rtpproxy session dies after a while due to time
expiration.
So I've added the following code to my on_reply_route:
------------
onreply_route[X] {
if is_method("INVITE") && status =~ "[3456][0-9][0-9]"
unforce_rtp_proxy();
------------
It seems to do the job. However I expected this to be done automatically by
rtpproxy module when an INVITE transaction for which a rtpproxy session has
been created fails.
Do I miss something? or is it the expected behavior?
Thanks a lot.
--
Iñaki Baz Castillo <ibc(a)aliax.net>
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users