Ok Eric. Thank you. I will try this and see what will be the result.
Thanks a lot. RODRIGO PIMENTA CARVALHO Inatel Competence Center Software Ph: +55 35 3471 9200 RAMAL 979 ________________________________ De: [email protected] <[email protected]> em nome de Eric Tamme <[email protected]> Enviado: terça-feira, 23 de fevereiro de 2016 17:23 Para: OpenSIPS users mailling list Assunto: Re: [OpenSIPS-Users] What does exactally mean lots of warnings about timer_ticker in the log (OpenSIPS 2.1)? I believe this has been refactored under 2.X as a result ofthe async work. I think the new settings are "timer partitions" here is the tm documentation discussing the timer partition setting: http://www.opensips.org/html/docs/modules/2.1.x/tm.html#id294483 tm Module - OpenSIPS<http://www.opensips.org/html/docs/modules/2.1.x/tm.html#id294483> www.opensips.org TM module enables stateful processing of SIP transactions. The main use of stateful logic, which is costly in terms of memory and CPU, is some services inherently ... -Eric On 02/23/2016 12:57 PM, Rodrigo Pimenta Carvalho wrote: Hi Eric Tamme. I have just searched about Timer in the module docs, but I didn't find any thing about how to manager Timers in OpenSIPS, as you commented. Do you know what part of the documentation tells about "dedicated timer processes"? BTW, my project is embedded. Any hint will be very helpful! Thanks a lot! RODRIGO PIMENTA CARVALHO Inatel Competence Center Software Ph: +55 35 3471 9200 RAMAL 979 ________________________________ De: [email protected]<mailto:[email protected]> <[email protected]><mailto:[email protected]> em nome de Eric Tamme <[email protected]><mailto:[email protected]> Enviado: segunda-feira, 22 de fevereiro de 2016 14:35 Para: OpenSIPS users mailling list Assunto: Re: [OpenSIPS-Users] What does exactally mean lots of warnings about timer_ticker in the log (OpenSIPS 2.1)? Many things share the same timer, dialog expiration cleanup, userlocation cleanup, nathelper pings etc. If one of the processes that is triggered by a timer route blocks for some period of time - aka a hung db query, it will cause the timer to "drift" and you will get logs indicating that a process that should have takeng X amount of time actually took Y amount of time - this is due to the blocking operation. I would suggest that you use dedicated timer processes for as many things as you can - dialog, tm etc. see the module docs for how to do this. -Eric On 02/22/2016 10:28 AM, Rodrigo Pimenta Carvalho wrote: Hi. The log of my OpenSIPS began to present thousands of warnings similar to: "WARNING:core:timer_ticker: timer task <nh-timer> already schedualed for 93991120 ms (now 248157560 ms), it may ove rlap.." What does exactly means it? Some discussions from the past said something about increasing the number in the global variable "children". Should I change the number for children? Before trying it i would like to hear something about, just to know better what I'm going to do. Any hint will be very helpful! Thanks a lot. RODRIGO PIMENTA CARVALHO Inatel Competence Center Software Ph: +55 35 3471 9200 RAMAL 979 _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
