[OpenSIPS-Users] Proper way to handle BYE retransmissions

[Nick Altmann]

I've checked this problem again. Everything is not so easy.
t_check_trans() really doing retransmit, but now we use topology_hiding()
and half-manual routing for NATted users, saving params in dialogs.
Because dialog destroyed after first BYE, we cannot handle retransmits
because we don't have routing info from dialog variables.

Is it possible to add parameter to delay dialog destroying after BYE for n
seconds?

--
Nick


2013/12/16 Răzvan Crainea <razvan at opensips.org>

> Hi, Nick!
>
> The t_check_trans() function should absorb BYE retransmissions too. Are
> you sure your BYE messages reach that function call?
>
> Best regards,
>
> Razvan Crainea
> OpenSIPS Core Developer
> http://www.opensips-solutions.com
>
>
> On 12/16/2013 01:09 PM, Nick Altmann wrote:
>
>> Hello!
>>
>> What is proper way to handle BYE retransmit? Dialog and transaction will
>> be destroyed after first BYE and we cannot detect BYE with
>> t_check_trans(), for example.
>> Of course, we could use cachedb, but I think it's not true way. Maybe
>> add option to delay dialog/transaction destroying?
>>
>> --
>> Nick
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20131216/76872722/attachment.htm>