Getting MWI on Polycom Phones to work with Asterisk
Getting MWI on Polycom Phones to work with Asterisk
MWI is a feature that will flash the LED, and display an icon on the phone display when there's a voicemail message waiting.
On the Asterisk side of things, there's nothing special that needs to be done. Just make sure the mailbox parameter is set right in the phone's sip.conf entry.
You may have to add @context to the mailbox entry. This seems to fix things for many users. Note that this context is the context specified in voicemail.conf for the extension, not the context specified in sip.conf
Before you start editing config files on the Polycom side of things, you should read the Soundpoint IP SIP Admin Guide, or at least familiarize yourself with the per-phone config file, as covered in section 4.6.3.
Section 4.6.3.5 of the Guide covers the Messaging functions, and 4.6.3.5.1 covers the <mwi/> tag, which is what you need to edit.
Here's an example (change from the defaults in your firmware rev):
sip.cfg:
up.oneTouchVoiceMail="1"
phone1.cfg:
<msg msg.bypassInstantMessage="1">
<mwi msg.mwi.1.subscribe="" msg.mwi.1.callBackMode="contact" msg.mwi.1.callBack="8500"/>
</msg>
Replace 8500 with your VM extension.
You may have to set reg.1.displayName="username", which is an attribute of phone1/reg (for each line used) in your phonexxxx.cfg file to get the MWI to light. Setting bypassInstantMessage="1" doesn't affect the light, it changes the message key behavior to go directly to voicemail instead of giving you a choice.
That should do it!
Now that you've got MWI setup, you may find yourself annoyed by the periodic tone that the phone will play when a message is waiting, even in DND mode! See these notes about Polycom SoundPoint IP MWI audio if you want to disable it.
One other note: If you have a multiline phone with newer SIP software (2.2.0) and want your Messages button to call into a generic Voice Mail extension, yet want your MWI's to show up for a few different lines, you have to set your user_preferences and set the mwiVisible="1" this allows for MWI's on lines defined in the MWI section that their callBackMode="disabled"
<user_preferences
up.oneTouchVoiceMail="1"
up.welcomeSoundOnWarmBootEnabled="1"
up.backlight.onIntensity="2"
up.backlight.idleIntensity="0"
up.mwiVisible="1"
/>
See Also
- Asterisk | Tips & Tricks | FAQ | VOIP Phones

Comments
333
22
username=22
type=friend
blah...blah...blah...
mailbox=22@device
The "mailbox=22@device" seemed to point to my problem. Normally voicemail would fall somewhere like /var/spool/asterisk/voicemail/default/22/INBOX. Well, apparently I also needed to have a /var/spool/asterisk/voicemail/device directory as well. Each entry in that directory was a symlink back to /var/spool/asterisk/voicemail/default. e.g. here's how I put it all in place by hand:
$ mkdir -p /var/spool/asterisk/voicemail/device
$ mkdir -p /var/spool/asterisk/voicemail/default/22
$ ln -s /var/spool/asterisk/voicemail/default/22 /var/spool/asterisk/voicemail/device/22
$ chown -R asterisk:asterisk /var/spool/asterisk/voicemail
333MESSAGE WAITING SOLVED
507
type=friend
host=dynamic
callerid="SIP Phone 507" <507>
callgroup=1
pickupgroup=1
which is the default dial plan that comes with the xorcom rapid distro, the lights WILL NOT WORK.
on the other hand, a sip.conf entry such as
501
username=501
context=default
type=friend
secret=501
qualify=no
port=5060
pickupgroup=1
nat=no
mailbox=501
host=dynamic
dtmfmode=rfc2833
canreinvite=no
callgroup=1
callerid="501" <501>
The light DOES WORK in this case.. Try to copy and paste the above config into sip.conf, reload asterisk, and see if your phone will register.
type sip show peers and see if there is an IP address next to your extension.
if there is an ip address, is it a public(68.225...) or private address (192.168...) and is that what you really wanted to have happen?
if not, check the NAT=YES/NO option to be correct....
333presence and IM
hello
can we set up presence and im with polycom and asterisk?
harry
333Re: Message waiting is a pain in the a...
in sip.conf
mailbox=102@blowmeup
333Message waiting is a pain in the a...
Using Polycom IP 500 phones with SIP. Basic instructions work perfectly.
MWI is another kettle of problems. Following the instructions here, do bypass the IM menu item, and will call back the VM if you try it. But with "contact" it never gets a message from the asterisk server V1.0.0 and V1.0.2). "registration" does yield a message indicator, but with wrong number of messages (Urgent, Old, New) as well no way to clear it. Deleting messages are useless. Clearing light from phone, just returns.
Sigh.