[Home]

Summary:ASTERISK-29224: asterisk-16 takes over an hour to clear the MWI light
Reporter:Syscon (syscon)Labels:
Date Opened:2020-12-25 15:27:09.000-0600Date Closed:2021-01-04 04:57:49.000-0600
Priority:MinorRegression?
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:16.13.0 Frequency of
Occurrence
Constant
Related
Issues:
Environment:Gentoo LinuxAttachments:( 0) debug_log_MWI
( 1) debug_log_mwi.0
( 2) log-from_audiocodes_MP114.txt
( 3) sip.conf
( 4) voicemail.conf
Description:asterisk-16 takes over an hour to clear the MWI light

In astersik-11 MWI light was cleared as soon as I checked the message.
In asterink-16 it takes about 20min to set the light ON and the light
takes over an hour to clear. (I've standard POTS phones)

What had changed?

In sip.cong

[400]
...
mailbox=400

voicemail.conf
[default]
400 => ,user, email

I've tried to enable in sip.conf "subscribemwi=yes" but it doesn't help.
The same was with asterisk-13.  It seems to me the MWI was never fixed just carry over from Ver. 13 to 16 (on channel SIP) or there is poor instruction how to make it work.  The strange part is that MWI in Asterisk pre 12 work like a charm (there was never a problem).  

I couldn't use Asterisk-13 in production because of this issue and it has not been fixed in Asterisk-16 either.
Comments:By: Asterisk Team (asteriskteam) 2020-12-25 15:27:11.614-0600

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

By: Joshua C. Colp (jcolp) 2020-12-25 17:27:20.495-0600

We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information



By: Syscon (syscon) 2020-12-25 17:56:23.938-0600

Please find attached logger file: debug_log_mwi.0

By: Syscon (syscon) 2020-12-25 18:00:16.175-0600

debug.log

By: Joshua C. Colp (jcolp) 2020-12-25 18:59:04.124-0600

That is not sufficient information. You need to ensure debug is enabled with the issue reproduced. For example leave a voicemail with it enabled and then subsequently listening to it and SIP logging enabled to show it is not being updated. As well the specific configuration information and environment details would be needed (is voicemail being stored as files?) to give a chance for someone to reproduce the issue.

This issue is not being experienced by others, so every amount of information available is needed to determine precisely what is unique about your environment/situation. The more the better.

By: Syscon (syscon) 2020-12-25 19:51:31.936-0600

Joshua, thank you for looking into it. Tell me how do I supply you information you need.  I turn the debugger on as from the link you provided.  
I left myself a message and the MWI light on my phone doesn't turn ON instantly.  The light goes ON after about 20-30min.
When I clear the message; the light on the phone is still blinking for another 1-hr or so.
I'm running latest version available on Gentoo Astersik-16.13.0

Please provide information how to turn the relevant debugging ON.  

By: Joshua C. Colp (jcolp) 2020-12-26 04:50:58.681-0600

The wiki page I linked has step by step instructions. Did you follow them? As well you need to provide configuration that reproduces the issue, and also describe your environment as I stated.

By: Syscon (syscon) 2020-12-26 11:55:05.460-0600

Yes, I followed these instructions from the link you provided on wiki.

By: Joshua C. Colp (jcolp) 2020-12-26 14:02:04.392-0600

What about the SIP traffic when a message is left or deleted? As well - are you using files for storing voicemail? Are you externally modifying the voice mailboxes? Are the phones subscribing for MWI or not (this would be controlled on each endpoint, Asterisk can't tell the device to subscribe)?

By: Joshua C. Colp (jcolp) 2020-12-26 14:05:31.365-0600

And can you state exactly what you did to collect debug info? Did you add it to logger.conf, or use the CLI? Did you ensure the verbose and debug level were set? And in the future attach files, don't put configuration and things into comments.

By: Syscon (syscon) 2020-12-26 14:26:41.377-0600

I just run debug (file name: debug_log_MWI attached).
I left debug running but I don't know if it will point to anything.
I activated the debug at: (filename stamp: Dec 26 11:20 debug_log_MWI) left it it running though the cycle:
- left a voicemail message at : 11:22am
- the light on the phone didn't start blinking until: 11:55am
- at 11:55am I check the message (delete it via asterisk voice response)
- the light on the phone did not turn OFF until exactly 1hr later: 12:55am

I do not touch those file (voice messages) externally in any way.  My Audiocodes-MP-114 subscribe to VMS.
When I switch Audiocodes to Asterisk-11.25 (still running as a production unit).  The MWI light on the phone appear almost instantly and is cleared as soon as I check the message.  So it is working.  When I switched to Asearisk-13 I notice this strange behavior with MWI light, so I upgraded to Asterisk-16.13 and same thing is happening with MWI-light on the phones.  

The log file I created with debug at 11:20am was not updated with anything so I don't know how to provide relevant information.  
This is not the only bug I've noticed with Asterisk-13 (no longer supported) and Asterisk-16.  
The is problem during installation with correct file permission during installation on Gentoo as I described on Gentoo bugs:
 https://bugs.gentoo.org/761442

But that issue was easy to correct, the MWI light is a bit harder to troubleshoot.  


By: Syscon (syscon) 2020-12-26 14:33:02.160-0600

To create the debug-file (I attached earlier) I run:
asterisk -vvvvvr
logger add channel debug_log_MWI notice,warning,error,debug,verbose,dtmf
core set verbose 5
core set debug 5
module reload logger
sip set debug on



By: Syscon (syscon) 2020-12-26 14:40:25.414-0600

Please find attached log from Audiocodes-MP114 unit, it might provide a bit more clue what is going on.  

By: Joshua C. Colp (jcolp) 2020-12-26 16:17:43.117-0600

It only shows that the Audiocodes did not receive a SIP NOTIFY with MWI information. For debug can you instead try adding the debug to the logger.conf configuration file and reloading?

By: Joshua C. Colp (jcolp) 2020-12-26 16:18:34.703-0600

As well, I should add that this process is merely for collecting information so if someone would like to work on this issue they could. The chan_sip module is community supported, so there's no timeframe or guarantee on something looking into it.

By: Joshua C. Colp (jcolp) 2020-12-26 16:21:27.435-0600

[~jkroon] You wanted to be poked on this according to the Gentoo report as well?

By: Joshua C. Colp (jcolp) 2020-12-26 16:48:35.062-0600

Another thing to try - if you add "@default" to the end of your mailbox as configured in sip.conf, does that help? I ask because of this from the UPGRADE.txt notes for going from 11 to 12:

{noformat}
VoiceMail:
- Mailboxes defined by app_voicemail MUST be referenced by the rest of the
  system as mailbox@context.  The rest of the system cannot add @default
  to mailbox identifiers for app_voicemail that do not specify a context
  any longer.  It is a mailbox identifier format that should only be
  interpreted by app_voicemail.
{noformat}

I've been out of habit adding context to mine, but upon removal saw similar issues and then remembered the context became necessary.

By: Syscon (syscon) 2020-12-26 17:18:15.508-0600

WOW! You solved the problem, thank you! thank you!
You are correct, something had change in configuration and it sip.conf context entry must have eg.
mailbox=55@default

in old configuration this was enough.
mailbox=55

So we can mark it as solved.
Thank you again. I hope it will save someone some time, looking for the solution.