El Friday 16 November 2007 16:18:14 Richard Bennett escribió:
modparam("tm", "fr_inv_timer", 27) #modparam("tm", "fr_inv_timer_avp", "inv_timeout")
and in the route block; # avp_write("i:45", "inv_timeout");
So obviously at some point I stopped setting the inv_timeout in the route block. If I increase modparam("tm", "fr_inv_timer", 27) to modparam("tm", "fr_inv_timer", 120) then the problem seems to be a lot less... Does setting fr_inv_timer to 120 globally potentially cause other problems besides using more server resources?
Note that if you set: modparam("tm", "fr_inv_timer", 27) but don't set: modparam("tm", "noisy_ctimer", 1) <-- by default is 0 !!!
then after 27 seconds ringing TM module forgets the transaction, so it will not understand that CANCEL (and maybe because that the CANCEL is sent wronly by localhost).
But if you set: modparam("tm", "noisy_ctimer", 1) then after 27 seconds ringing OpenSer TM module will generate a CANCEL and end the transaction properly.