Hello,
these messages are printed by debugger module because you enabled cfgtrace and the log level for them is ERROR. But they are not real execution errors. If you set cfgtrace to 0 for debugger module, then you will not see them.
Cheers, Daniel
On 04.05.17 21:29, Samuel F. wrote:
Hi,
Using KEMI Python and doing serial forking via:
msg.call_function("t_load_contacts")
msg.call_function("t_next_contacts")
- I couldn't see that the functions are exported to KEMI yet. I'm not
great with C so I haven't tried exporting them myself.
I get the following in the log files:
PYT {INVITE}: 5(11963) ERROR: *** cfgtrace:request_route=[] c=[] l=0 a=26 n=t_load_contacts PYT {INVITE}: 5(11963) ERROR: *** cfgtrace:request_route=[] c=[] l=0 a=26 n=t_next_contacts
However, it seems to be working anyway. Is the ERROR because I use the msg.call_function() ? Is there any better way to do serial forking using KEMI?
Thank you,
Samuel F
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users