Skip to main content

MWI stuck on for new extensions - how to update?

Posted by jkeegan123 on Thu, 04/06/2017

Hello,

For all new extensions in a multi-tenant edition of Thirdlane, the handset starts with MWI lit. When they check the voicemail, they do not have any messages in the mailbox. The MWI indicator never turns off, and this is for multiple types of handsets (Yealink and Cisco 524G so far ...).

Can anyone tell me where I can configure this ?


Submitted by eeman on Tue, 04/11/2017 Permalink

I would start with the device configuration files. Each device has their own expected behavior for MWI. Its possible that the current implementation is not correct for Asterisk. I had people test the Yealink and Cisco configs and so far no one reported this, but that does not mean the same thing as confirmed working. If you do discover that an entry is getting created in error let me know as I can get an updated RPM built fairly quickly.

Submitted by jkeegan123 on Tue, 05/23/2017 Permalink

I found that, for this particular issue, it was on Yealink phones. As you suspected, the device config file was causing an issue. The line that needed to be changed was:

phone_setting.common_power_led_enable = 1

I had to change "1" to "0", and everything was resolved.