Hi Daniel
thanks.
On 03/24/2011 09:26 AM, Daniel-Constantin Mierla wrote:
It was an issue related to time unit reported in that message, but
it got fixed and should work now -- since I did the fix I tested it,
hopefully there was no commit later to cause the regression. Can you
do avp_print() before t_relay() and check if the avp with the
timeout really exists? You have to run in debug mode.
Regarding the debug mode: i have following:
loadmodule "debugger.so"
modparam("debugger", "cfgtrace", 1)
#modparam("debugger", "breakpoint", 1)
#modparam("debugger", "log_level", 1)
#modparam("debugger", "log_facility", "LOG_DAEMON")
.....
dbg_breakpoint("1"); //set the break point here????
# avp_print();
xlog("my fr_inv_timer is $avp(i:2)\n");
t_set_fr($avp(i:2)*1000);
#t_set_fr(20000);
.....
when sip msg comes, somehow dbg.ls show all processes state
are 0. and passed that break point. does dbg_breakpoint suppose to
set the break point there?
maybe I misunderstand how to use debugger module?
/// see the log: the xlog printed out, it should stop at
Mar 24 10:51:49 sip1 /usr/sbin/kamailio[6055]: ERROR: *** cfgtrace:
c=[/etc/kamailio/kamailio.cfg] l=5517 a=26 n=xlog
Mar 24 10:51:49 sip1 /usr/sbin/kamailio[6055]: ERROR: <script>: my
fr_inv_timer is 20
Mar 24 10:51:49 sip1 /usr/sbin/kamailio[6055]: ERROR: *** cfgtrace:
c=[/etc/kamailio/kamailio.cfg] l=5524 a=26 n=t_on_failure
Mar 24 10:51:49 sip1 /usr/sbin/kamailio[6055]: ERROR: *** cfgtrace:
c=[/etc/kamailio/kamailio.cfg] l=5530 a=17 n=if
Mar 24 10:51:49 sip1 /usr/sbin/kamailio[6055]: ERROR: *** cfgtrace:
c=[/etc/kamailio/kamailio.cfg] l=5527 a=42 n=isflagset
Mar 24 10:51:49 sip1 /usr/sbin/kamailio[6055]: ERROR: *** cfgtrace:
c=[/etc/kamailio/kamailio.cfg] l=5530 a=25 n=t_relay
Kind regards / Mit freundlichen Grüßen
Min Wang
Cheers,
Daniel
A bug or my misuage the fr_inv_timer_avp?
thanks