Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
I build kamailio from master
$ /usr/local/sbin/kamailio -v
version: kamailio 5.8.0-dev1 (x86_64/linux) 27f87c
and reproduce problem:
modparam("dispatcher", "event_callback", "ksr_evnt_dispatcher") # route actually named ksr_event_dispatcher
KSR.tm.t_on_reply('ksr_onreply_MANAGE') # route not existed.
KSR.tm.t_on_failure('ksr_failure_ROUTE') # route actually named ksr_failure_MANAGE
Patch work great - i get messages like
0bdb87a767b52b60-1028569@10.100.32.228 OPTIONS app_python3 [python_exec.c:100]: apy_exec(): ksr_evnt_dispatcher not found or is not callable ((nil))
DEBUG: 766520133 INVITE app_python3 [python_exec.c:100]: apy_exec(): ksr_onreply_MANAGE not found or is not callable ((nil))
DEBUG: 2039759053 INVITE app_python3 [python_exec.c:100]: apy_exec(): ksr_failure_ROUTE not found or is not callable ((nil))
and all forks still availible. But can those messages be at log level 'ERROR'? Without log level 'DEBUG' it's still hard to detect non-existed KEMI route
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.