One of the most annoying tasks within Asterisk (or VoIP in general) is the task of CDR and event processing. Why is processing these so annoying? Well, depending on your infrastructure, problems can arise because of any of the below: Row locking within the database Handling of multiple input points Handling a constantly changing data
In the previous post on contributing to Asterisk, we set up the Asterisk Test Suite and wrote a test for the CDR dialplan function that reproduced the bug in ASTERISK-25179 and failed. In this post, we will: Figure out where the bug is in the code base Write a patch that fixes it, and passes
In the previous post, we: Picked out a bug to fix, ASTERISK-25179 Signed up for an Asterisk account, signed a CLA, and created our profile in Gerrit Cloned Asterisk from its Git repo, installed its dependencies, built and installed it Run the Asterisk unit tests After doing all that, we concluded that we’d be better
Have you ever run into a bug in Asterisk? If so, don’t despair. Asterisk is software, and despite anyone’s claims to the contrary, all software contains bugs. While you can – and should! – simply file a bug in the Asterisk issue tracker, you may decide that you’d like to try your hand at fixing
