Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mitel 3300 Message Waiting (MWI) has changed.

Status
Not open for further replies.

MitelEngineering

Technical User
Oct 12, 2006
42
GB
Since upgrading a Mitel 3300 from 8.0(UR?) to 9.0(UR1), the customer has noticed a change in the way they have to access messages. Before the upgrade, when a message was left, the message key would flash as normal and they would press the button and that would make a call straight to the voicemail hunt group, where they would enter the passcode. Since the upgrade, they now have to press the message button and it asks them to confirm that they wish to call voicemail, either with a hash or some other button (depending on handset). They have a mixture of 5212 and 5330 handsets. I've tried changing/removing the class of service settings such as visual voice, etc.., also the visual voice hunt group in the users mailboxes.. but no luck. Any responses would be most welcome. Thanks
 
I know that 5330's and 5340's key now needs to be set up thru the Applications Page (directly on the set) to choose the MWI mode. My experience is that it defaults to visual mail mode.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
It seems you now have to go off-hook and then press the message button for it to call voicemail directly (or just use visual voice). Mitel said this may have changed between versions, I tested and it does work fine if done using this method.
 
lifting the handset turns off Visual VM.

It can also be changed via the Applications page as mentioned earlier.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Not too sure if this will help:

The usage of a new maintenance command is to turn on/off default setting of Visual Voicemail for both 5340 and 5235s
Format of command usage:
SacSetVmButtonCfg <enable>, <deviceType> (optional)

enable is: 0 to turn off launching the VVM app with the message key
1 to turn on the VVM app with the message key

deviceType is : optional - if not specified the default is 0
0 - all devices
1 - 5340s
2 - 5235s
e.g
-> SacSetVmButtonCfg 0,1
Setting visual voicemail launch via mail button to : 0
Setting VM Button Cfg for all 5340 devices
Finished configuring launch VM button
 
It has never been the design intent to have the message waiting key work by simply pressing it. You have always had to seize dial tone (speaker phone, handset, headset). It has never worked any differently. I too have had many people call and complain of this, but it has never worked this way.

There is something on the road mapp, but nothing for 9.1.
 
Most likely the confusion stems from the use of an explicitly programmed Message Waiting Indicator key, which DOES work to take the user straight-in to his mailbox (only when flashing).

In the opinion of many people (me included) the MWI hardkey on those sets where offered, should (logically) work in the same manner. That it does not, or requires a series of steps, is unintuitive (and frustrating).
 
MitelInMyBlood: How did you program a 3300 to call the devices (VM) by simply pressing the FLASHING VM key? What steps did you complete to make this happen?
 
I think you misunderstood.

I make a KEYLINE MWI appearance of the number (mine, for example... 6666 the devil himself)

When MW flag is set both the hardkey & the KEYLINE MWI appearance flash.

Press the flashing KEYLINE appearance to go to the user's mailbox with full integration.

 
I just configure a speed dial button with printed label "Voicemail" and instruct users to use this button instead. Never had problems from day one.
Using VM key has too many conditions such as on/off hook, visual mail, responding to call backs and etc. Overcomplicated for an average user.
 
On occasions when our customers dial the voicemail hunt group directly from a speed dial and delete a message the mwi stays on. Then I have to tell them to use the message button to delete the 'call back' message sent to the phone to turn off the flashing light.
 
mwi key works great. program a message waiting indication key and use you're own set directory number as the DN for the button. you press this button when flashing and dials straight into voicemail.

is this what your were asking MitelGuy, don't think MIMB was talking about the transparent flashing envelope key..

I think it also stems from the fact that the key has a dual purpose. it displays who has 'enabled' the flashing. another set or voicemail. dialling an extension and pressing this button with the other extension being busy or not turns the mwi lamp on. pressing the button tells you who left a call me back message. in some cases it's the voicemail hunt group in other cases it could be an extension.
 
There is something on the road map for customers to program the Message Waiting key to go to a specific DN each time. I don't think we are going to see it until RLS 11.0. 10.0 is due out mid-summer, 9.1 will not make an appearance (everything from 9.1 will be bumped to 10.0).
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top