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:
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 wrote:
> Hi, I'm realizing that rtpp
Hello All!
2010/1/27 Iñaki Baz Castillo :
> 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
El Miércoles, 27 de Enero de 2010, Ovidiu Sas escribió:
> 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.
Good point. Terminating the rtpproxy session u
On Wed, Jan 27, 2010 at 9:04 AM, Iñaki Baz Castillo wrote:
> El Miércoles, 27 de Enero de 2010, Ovidiu Sas escribió:
>> 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
El Miércoles, 27 de Enero de 2010, Ovidiu Sas escribió:
> In most of this cases (if not all) the rtp session should not be opened.
Well, the case is that when invoking force_rtpproxy() for the INVITE, RtpProxy
already allocates 2 file descriptors (UDP sockets for RTP and RTCP) so we can
get int
This is the expected behaviour, but seems different from how the
mediaproxy module handles the issue.
On 01/27/2010 08:27 AM, Iñaki Baz Castillo wrote:
Hi, I'm realizing that rtpproxy session is not automatically terminated when
an outgoing INVITE transaction fails ([3456]XX response received
On 1/27/10 9:19 PM, Alex Balashov wrote:
This is the expected behaviour, but seems different from how the
mediaproxy module handles the issue.
On 01/27/2010 08:27 AM, Iñaki Baz Castillo wrote:
Hi, I'm realizing that rtpproxy session is not automatically
terminated when
an outgoing INVITE t
Alex Balashov writes:
> This is the expected behaviour, but seems different from how the
> mediaproxy module handles the issue.
even in case of mediaproxy, media sessions needs to be released using
end_media_session() call.
-- juha
___
Kamailio (Op