Re: [Astlinux-devel] Grrr I cant get Voicemail MWI status to refresh

[Michael K. <mic...@ip...>]

Ok you have concerned me enough to test on Asterisk 13.23.1.
Mailbox polling works great and 10 seconds is a good number.
On an APU1 there was about a 0.1% increase in CPU for a 5 extension system. 
Yes I'm getting too concerned about resource usage, especially considering the grunty boxes we are installing now.

PS just for fun I changed it to 1 second and frankly I didn't see much difference in CPU usage.

Regards
Michael Knill

On 22/4/19, 1:08 pm, "Lonnie Abelbeck" <li...@lo...> wrote:

    Michael,
    
    I would suggest not doing a 'voicemail reload' and rely on pollmailboxes/pollfreq, IMO.
    
    There may be other (bad) side-effects performing a 'voicemail reload' at random times.
    
    Lonnie
    
    
    
    > On Apr 21, 2019, at 10:02 PM, Michael Knill <mic...@ip...> wrote:
    > 
    > No I didn't actually try that but I have a sneaking suspicion it will.
    > I would actually rather do a 'voicemail reload' when I needed to with immediate status change rather than polling every 10 seconds unnecessarily though anyway.
    > 
    > Regards
    > Michael Knill
    > 
    > On 22/4/19, 12:46 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
    > 
    >    Michael,
    > 
    >    Doesn't this work in 13.23.1 ?
    >    -- voicemail.conf --
    >    pollmailboxes = yes
    >    pollfreq = 10
    >    --
    > 
    >    You should not have to mess with other refresh methods, unless you are manually moving VM files around.
    > 
    >    Lonnie
    > 
    > 
    >> On Apr 21, 2019, at 9:36 PM, Michael Knill <mic...@ip...> wrote:
    >> 
    >> Thanks Lonnie
    >> 
    >> Well never having used AMI: VoicemailRefresh, I don't know if it ever worked or used for something else e.g. external MWI.
    >> I basically want to be able to perform an MWI refresh for a specific mailbox and it seems to be more difficult than it should be.
    >> I would rather not turn on FOP to do this (although that didn't seem to work for me either). Quite annoying.
    >> 
    >> Were you just using the UserEvent: FOP2RELOADVOICEMAIL?
    >> 
    >> As it currently stands, I will be implementing 1.3.6-13se when released and doing a 'voicemail reload'. 
    >> PS I do like the concept of an SE variant now actually.
    >> 
    >> Thanks
    >> 
    >> Regards
    >> Michael Knill
    >> 
    >> On 22/4/19, 12:20 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
    >> 
    >>   Hi Michael,
    >> 
    >>   Good work, fortunately Asterisk 13.23.1 (13se) does not have this (28340) bug.  Are you saying VM MWI still has issue in 13.23.1 (13se) ?
    >> 
    >>   This (28340) bug has been fixed in 13.26.0 and 16.3.0, but only available in the current Pre-Release.
    >> 
    >>> Does this seem reasonable?
    >> 
    >>   We need to understand this VM MWI issue(s) more.
    >> 
    >>   I have tested Asterisk 13.23.1 and found a seeming obscure bug, but in general no issues.
    >> 
    >>   Lonnie
    >> 
    >> 
    >> 
    >>> On Apr 21, 2019, at 8:15 PM, Michael Knill <mic...@ip...> wrote:
    >>> 
    >>> DoH! I posted this on the forum and Josh responded saying it was a bug fixed in the latest release.
    >>> Looks like it is bug 28340 which I assume will be fixed in 13.25.1?
    >>> Is this bad enough to defer or note for 1.3.5.2?
    >>> 
    >>> In Asterisk 13.23.1 however, AMI: VoicemailRefresh still does not work still but doing a voicemail reload does refresh the status. Although this is still not great, its far more tolerable than a sip reload.
    >>> 
    >>> So it looks like my new release will be either 1.3.4 or 1.3.6 - 13se (preferred).
    >>> 
    >>> Does this seem reasonable?
    >>> 
    >>> Regards
    >>> Michael Knill
    >>> 
    >>> On 21/4/19, 11:21 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
    >>> 
    >>>  Hi Michael,
    >>> 
    >>>  Are you saying MWI eventually works (say in 30 seconds) or does it seemingly never work ?
    >>> 
    >>>  Is this Voicemail Portal basically pure AstLinux, if so you could quickly try the latest 13se pre-release with Asterisk 13.23.1 .
    >>> 
    >>>  https://www.astlinux-project.org/dev.html
    >>> 
    >>>  As it turns out Asterisk 13.24.0 had changes that caused issues with VM MWI, Michael Keuter and I spent a lot of time tracking the issue, reported to Digium and "fixed" in 13.24.1 .  As such a lot of extra testing was spent wrt VM MWI before the release of Astlinux 1.3.5.2 ... it should work for you.
    >>> 
    >>>  Michael, when loading the voicemail module, are there any errors or warnings ?
    >>> 
    >>>  Look for typos, make sure pollmailboxes and pollfreq are in the [general] section of voicemail.conf .  Try pollfreq=20 instead.
    >>> 
    >>>  Lonnie
    >>> 
    >>> 
    >>> 
    >>> 
    >>>> On Apr 21, 2019, at 6:38 AM, Michael Knill <mic...@ip...> wrote:
    >>>> 
    >>>> We have built a separate Voicemail Portal but frankly I cant even get the standard Astlinux Voicemail Tab refreshing the status of MWI in any reasonable amount of time.
    >>>> I don't know if its something funny in Asterisk 13.24.1 (Astlinux 1.3.5.2).
    >>>> 
    >>>> I have tried to use the AMI: VoicemailRefresh which does nothing and also setting pollmailboxes=yes and pollfreq=10 and still it does not change the MWI status on the phone for ages. I have also tried the UserEvent: FOP2RELOADVOICEMAIL and I still cant get that to work.
    >>>> 
    >>>> Any ideas where the problem could be or what I can try next?
    >>>> The only thing that seems to work is a module reload chan_sip.so but I really dont want to be doing that every time someone uses my voicemail app.
    >>>> 
    >>>> Regards
    >>>> Michael Knill
    >>>> _______________________________________________
    >>>> Astlinux-devel mailing list
    >>>> Ast...@li...
    >>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
    >>> 
    >>> 
    >>> 
    >>>  _______________________________________________
    >>>  Astlinux-devel mailing list
    >>>  Ast...@li...
    >>>  https://lists.sourceforge.net/lists/listinfo/astlinux-devel
    >>> 
    >>> 
    >>> 
    >>> _______________________________________________
    >>> Astlinux-devel mailing list
    >>> Ast...@li...
    >>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
    >> 
    >> 
    >> 
    >>   _______________________________________________
    >>   Astlinux-devel mailing list
    >>   Ast...@li...
    >>   https://lists.sourceforge.net/lists/listinfo/astlinux-devel
    >> 
    >> 
    >> 
    >> _______________________________________________
    >> Astlinux-devel mailing list
    >> Ast...@li...
    >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
    > 
    > 
    > 
    >    _______________________________________________
    >    Astlinux-devel mailing list
    >    Ast...@li...
    >    https://lists.sourceforge.net/lists/listinfo/astlinux-devel
    > 
    > 
    > 
    > _______________________________________________
    > Astlinux-devel mailing list
    > Ast...@li...
    > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
    
    
    
    _______________________________________________
    Astlinux-devel mailing list
    Ast...@li...
    https://lists.sourceforge.net/lists/listinfo/astlinux-devel