After a recent upgrade from 1.8 to Asterisk 13, most of the functionalities work as expected except for the the way CDRs are kept for queues because it crashes the server.
I know that there are different CDRs per queue call – one per ring/per phone, basically. The problem is that whenever the number of CDRs “to be recorded” for a call exceeds 5000, Asterisk stop responding for a while. I get this message in the console: “task processor queue reached 5000 scheduled tasks again.”
It is easy to reproduce this scenario: a queue, with simultaneous ring, 20 devices/phones, all unreachable, 1 second between attempts. After 250 (5000 / 20) seconds of waiting asterisk becomes unresponsive.
The reason might be that all multiple CDRs get stacked somewhere until the end of the call and that breaks some inner limit.
I want to know if it is possible to force the CDR`s to be written as while the queue app it’s working, instead of waiting until the end of the call? Is there any workaround to this limit or some fix/patch/configurable-item?
By the way, and talking about Asterisk 13, I stumbled upon this book that teaches you how to work with it. It is tailored for beginners, so no prior telecommunications knowledge is required. The book covers Asterisk 13 LTS and describes the process of installing, configuring, and maintaining your own Asterisk system.
The topics covered in this book are:
– downloading and installing Asterisk from source
– customizing your Linux environment
– configuring devices to register to Asterisk
– writing your first dialplan
– useful Asterisk applications such as Playback, Background, and Goto
– using pattern matching in your dialplans
– voicemail configuration
– auto-attendants and queues
If you are looking for a resource that will get your started with Asterisk, then this book is for you.