Actually after reading, so like you said $T_fr_inv_timeout is just a "dynamic" way to change the fr_inv_timeout setting for the tm module. BUT it seems by reading $T_fr_inv 'definition':
1.5.4. $T_fr_inv_timeout $T_fr_inv_timeout (R/W) - the timeout for the final reply to an INVITE request, after a 1XX reply was received It seems fr_inv_timeout is the timer I am looking for, so by setting the fr_inv_timeout at 5 seconds, it should NOT cut the call off if it receive 180/183 within 5 seconds of receiving 100 trying, correct? But yet, the call WAS CUT OFF. It seems Opensips wants the call be ANSWERED within 5 second. Anything else other then ANSWER, it will cut off in 5 second. So am I doing something wrong? Here are my original settings: modparam("tm", "fr_timer", 5) modparam("tm", "fr_inv_timer", 30) In this case, call will get cut off if not answer within 30 seconds. After change it to modparam("tm", "fr_timer", 5) modparam("tm", "fr_inv_timer", 5) Now call gets cut off within 5 seconds if no answer. So almost seems like fr_inv_timer is a RING NO ANSWER timer. Or a timer that is for between INVITE AND 200 OK? -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/fr-inv-timeout-tp7594633p7594643.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users