|Summary:||ASTERISK-20064: Can MWI frequency be reduced? pollmailboxes=yes results in double MWI|
|Reporter:||Henry Fernandes (usinternet)||Labels:|
|Date Opened:||2012-06-27 16:02:07||Date Closed:|
|Versions:||184.108.40.206 13.18.4||Frequency of|
|Description:||I have 'pollmailboxes=yes' in voicemail.conf. When someone leaves a new VM, Asterisk sends out MWI as per usual. The problem is that it sends out MWI once again when it polls the voice mailboxes. The same thing happens when I delete a VM. Asterisk sends MWI once at that point and then again when it polls.|
We have our Polycom phones set to beep when when MWI is received, so this is causing the phones to beep frequently.
|Comments:||By: Kerry (kerry) 2012-09-03 18:56:26.129-0500|
I debugged this problem with pollmailboxes extensively. It is strangely compounded if you have more than one phone subscribed to the same mailbox. I have 19 phones and use one common mailbox, which caused a huge number of packets to be repeatedly sent out (something like 19^3 times) and even crashed some of my ATAs every time someone left a message. Some clients dealt with the problem with no unusual side-effects. Polycom 501s make a strange stutter-tone instead of the usual MWI sound, as the repeated packets arrive.
[Inline patch removed]
By: Richard Mudgett (rmudgett) 2012-09-04 11:22:35.213-0500
You cannot post a patch inline.
By: Kerry (kerry) 2012-09-04 17:34:31.656-0500
I'm not interested in giving up personal info to "sign" the license agreement.
This project has adopted far too high a barrier to entry to continue encouraging community involvement. No wonder I'm finding increasing numbers of unfixed bugs in asterisk. It's a sinking ship. Is this really how open-source is supposed to work?
What alternative can you give me to submit a patch anonymously?
By: Matt Jordan (mjordan) 2012-09-04 18:17:05.487-0500
None. As much as we'd love to have your patch for an improvement to Asterisk, its not worth threading the licensing needle to guarantee that we have not stolen yours - or someone else's code. One of the many reasons why we ask contributors to sign a license agreement.
If you'd rather not sign a license contributor agreement, you're more than welcome to maintain your patch outside of the Asterisk source tree.
Note that this is not a new restriction - the license contributor agreement has been around for quite some time. Plenty of folks have been willing to work within it. If you don't want to, that is your decision.
As far as the number of issues on the issue tracker, well, the 30-day average is a little high right now, but that's due in large part to having just released Asterisk 11 in beta. In general, over a given sprint, we close a lot more bugs than what gets opened. And, of course, we do strive to incorporate new features as well. You're more than welcome to view the Asterisk 11 new features list to see what got included over the past year.