is there a means to check if reply to t_relay()ed request is retransmission? there is t_is_retr_async_reply(), but that does not apply to regular transactions.
i would like to avoid double calling of rtpengine_answer().
-- juha
Den 2014-11-05 14:35, Juha Heinanen skrev:
is there a means to check if reply to t_relay()ed request is retransmission? there is t_is_retr_async_reply(), but that does not apply to regular transactions.
i would like to avoid double calling of rtpengine_answer().
-- juha
t_check_trans() will consume retransmissions.
http://www.kamailio.org/docs/modules/stable/modules/tm.html#tm.f.t_check_tra...
Johan Wilfer writes:
t_check_trans() will consume retransmissions.
http://www.kamailio.org/docs/modules/stable/modules/tm.html#tm.f.t_check_tra...
i don't get that impression:
* For a SIP Reply it returns true if the reply belongs to an existing transaction and false otherwise.
if i get two 200 oks to the same invite, both of them belong to an existing transaction. the thing i want to know is if reply is the first reply or a retransmission of the reply.
-- juha
On Wednesday 05 November 2014 14:35:45 Juha Heinanen wrote:
is there a means to check if reply to t_relay()ed request is retransmission? there is t_is_retr_async_reply(), but that does not apply to regular transactions.
I don't think there is a built-in for that. I ended up storing the Via branch parameter of the reply in a htable.
On 06/11/14 09:44, Juha Heinanen wrote:
Alex Hermann writes:
I don't think there is a built-in for that. I ended up storing the Via branch parameter of the reply in a htable.
thanks for your reply. i'll then just call rtpengine_answer again and hope that it will notice that it is a recall.
Indeed it is no function in config to detect if a reply was retransmitted. Alex's suggestions could be a way.
But, iirc, some of the retransmitted replies have to be just forwarded and for them, the rtp proxy needs to be engaged again in order to update the sdp. The rtpproxy (and expect the same from rtpengine) handles it properly, because it detects existing session by call id and tags.
Cheers, Daniel
-
Alex Hermann -
Daniel-Constantin Mierla -
Johan Wilfer -
Juha Heinanen