I missed your first reference to FreePBX, and was going on your original request for a patch. If you had mentioned FreePBX from the start, I might have realised you couldn’t cope with a patch. (Microsoft use patch rather differently from its original meaning, as they replace whole modules. A patch is a sticking plaster approach. The microsoft way is more like a transplant.)
The particular change you reference looks like it will not appear in a released version until Asterisk 12. Also, it is not useful without the changes in ASTERISK-20157, as it is a correction to those changes. Asterisk-20157 is recorded as an “improvement”, not a bug fix.
I believe that alarmreceiver is a community supported module, so updates are less predictable than for core modules. However the fact that it is only in trunk could be:
- an oversight by its maintainer;
- because ASTERISK-20157 is not recorded as a bug fix, it will not be eligible for applying to released versions, and the possibility of it actually containing bug fixes as well was overlooked, or they could not be separated from the other changes;
- the maintainer didn’t have the resources to deal with the back porting.
Especially if it is community supported, you need to take this up with the maintainer. However, as your issue is recorded as a regression in the changes for an unreleased issue (i.e the released version should not have the bug that it fixes), it is likely that you have incorrectly identified the fix that for your problem.