On 01.09.2009 12:19 Uhr, Klaus Darilion wrote:
Juha Heinanen schrieb:
i checked the host hw and it is a normal intel dual core processor, so normal debian i386 package should be fine for it.
i also added more logging to config file like this:
... xlog("L_INFO", "INFO: : Request URI when leaving Initial_Tasks: <$ru>\n"); route(2);
and in front of route block 2:
route [2] { xlog("L_INFO", "INFO: : Request URI when entering Other_Requests: <$ru>\n"); ...
and here is what comes to syslog:
Sep 1 09:01:12 /usr/sbin/kamailio[25325]: INFO: : Request URI when leaving Initial_Tasks: sip:foo.bar@movial.com Sep 1 09:01:12 /usr/sbin/kamailio[25325]: INFO: : Request URI when entering Other_Requests: sip:foo.bar@contact-ip-address:5060;transport=UDP
thus somehow lookup() was done in between leaving a route block and entering the next.
there is only one route block where lookup() calls appears and i have added a xlog call as first thing in it. i have also added another xlog call just before lookup() call. neither is ever executed.
so how can it be possible that lookup gets executed without calling lookup() function?
debugging at level 7 does not give any clues. any ideas on how to get to the bottom of this?
Maybe there is a problem when the cfg is parsed and the order of processing is defined. So that lookup is executed at the wrong place.
In Asterisk I would use "dialplan show <context>" to debug this - is there a similar tool (e.g. FIFO command) in Kamailio to dump the parsed config?
the cfg tree is printed at startup, but pretty cryptic.
There is a fifo command that prints the arguments, iirc -- so if the cfg was given with -f you can see where is located, otherwise, is the default one.
Cheers, Daniel