Hi all I see this old thread from 2015. - https://kamailio.org/mailman3/hyperkitty/list/sr-users@lists.kamailio.org/th...
It's about max_inv_lifetime not working properly. I have this problem today: SIP-180 responses from downstream apparently reset max_inv_lifetime, and the transaction can live for hours (apparently indefinitely) even though max_inv_lifetime is set to just over a minute. By spacing the SIP-180 responses (from downstream) slightly longer apart than than max_inv_lifetime in kamailio, I don't get the problem, so it looks to me that this is TM not matching what's in the documentation (which mentions that this should be a hard limit).
With this configuration, SIP-180 responses every minute result in the transaction never ending (until the client CANCELs the call). - kamailio.cfg:modparam("tm", "fr_timer", 3000) - kamailio.cfg:modparam("tm", "fr_inv_timer", 300000) - kamailio.cfg:modparam("tm", "max_inv_lifetime", 65000) - kamailio.cfg:modparam("tm", "noisy_ctimer", 1)
That other thread ends with Daniel mentioning that he'd have to look at the code, but nothing further.
Running "git log --grep max_inv_lifetime" shows me that the last/only update that wasn't just documentation was in 2007. Has anyone got an ideas?
James
Any reason your fr_inv_timer is both so high and more than the max timer?
Regards,
Fred Posner
On Sep 25, 2023, at 11:03 AM, James Browne via sr-users sr-users@lists.kamailio.org wrote:
Hi all I see this old thread from 2015.
It's about max_inv_lifetime not working properly. I have this problem today: SIP-180 responses from downstream apparently reset max_inv_lifetime, and the transaction can live for hours (apparently indefinitely) even though max_inv_lifetime is set to just over a minute. By spacing the SIP-180 responses (from downstream) slightly longer apart than than max_inv_lifetime in kamailio, I don't get the problem, so it looks to me that this is TM not matching what's in the documentation (which mentions that this should be a hard limit).
With this configuration, SIP-180 responses every minute result in the transaction never ending (until the client CANCELs the call).
- kamailio.cfg:modparam("tm", "fr_timer", 3000)
- kamailio.cfg:modparam("tm", "fr_inv_timer", 300000)
- kamailio.cfg:modparam("tm", "max_inv_lifetime", 65000)
- kamailio.cfg:modparam("tm", "noisy_ctimer", 1)
That other thread ends with Daniel mentioning that he'd have to look at the code, but nothing further.
Running "git log --grep max_inv_lifetime" shows me that the last/only update that wasn't just documentation was in 2007. Has anyone got an ideas?
James __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
No reason. It was just that I changed only the max_inv_lifetime for testing (and included all settings for completeness).
James
On Mon, 25 Sept 2023 at 15:30, Fred Posner fred@pgpx.io wrote:
Any reason your fr_inv_timer is both so high and more than the max timer?
Regards,
Fred Posner
On Sep 25, 2023, at 11:03 AM, James Browne via sr-users sr-users@lists.kamailio.org wrote:
Hi all I see this old thread from 2015.
It's about max_inv_lifetime not working properly. I have this problem today: SIP-180 responses from downstream apparently reset max_inv_lifetime, and the transaction can live for hours (apparently indefinitely) even though max_inv_lifetime is set to just over a minute. By spacing the SIP-180 responses (from downstream) slightly longer apart than than max_inv_lifetime in kamailio, I don't get the problem, so it looks to me that this is TM not matching what's in the documentation (which mentions that this should be a hard limit).
With this configuration, SIP-180 responses every minute result in the transaction never ending (until the client CANCELs the call).
- kamailio.cfg:modparam("tm", "fr_timer", 3000)
- kamailio.cfg:modparam("tm", "fr_inv_timer", 300000)
- kamailio.cfg:modparam("tm", "max_inv_lifetime", 65000)
- kamailio.cfg:modparam("tm", "noisy_ctimer", 1)
That other thread ends with Daniel mentioning that he'd have to look at the code, but nothing further.
Running "git log --grep max_inv_lifetime" shows me that the last/only update that wasn't just documentation was in 2007. Has anyone got an ideas?
James __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
-
Fred Posner -
James Browne