Voicemailbox 0 message wait light

[OzzieGeorge]

Ok I've searched and searched but haven't found an answer. so at the risk of asking something I should already know......

I have a customer that I have inherited where calls come in on 666 (numbers have been changed to protect the innocent) this is set up as a speed dial which dials 500. 500 is the number of a hunt group with members 501, 502, 503 & 504, these appear on all phones as keysystem keys. At night the system is put into Night 2 and 500 is rerouted to the voicemail where 500 is the extension number associated with mailbox 0. When a message is left the message waiting light on extn 622 lights up.

Now to my problem, the customer wants the extension that gets the lamp lit changed but I can't for the life of me work out how 622 is being lit now.

Any pointers gratefully recieved!

 

[wireman50]

Probably a message waiting key associated with the mailbox.

Go into the voicemail setup for that box and see what is entered as the 'Meswsage Notification/number and that should be 622.

On the phone the key will be programmed as a MWI indicator for the message box above. Look in the divices/iptelephones/multiline ip sets/ multiline set key assignment form.

 

[OzzieGeorge]

Sorry,

No message wait key programmed. The main message light (top right) flashes and the Normal message key (the one with the envelpe) flashes. However when you press the message key it takes you to 622s mailbox. Also the notification settings in mailbox 0 are blank (default).

Thanks though.

 

[sarond]

The extension for 0 maybe for someone to go to operator for assistance rather than a MWI.

Is there a mailbox that mathces the speedcall (666 in your eg.) Check what parameters are associated to that if there is.

 

[wireman50]

anything programmed in mailbox 0? wrt the message notification?

 

[wireman50]

oops, just reread your reply. sorry. Could you give us real extn numbers?

 

[OzzieGeorge]

Sarond

No And in the mailboxes 666 is set as the operator extension.

wireman50

The numbers are close enough to the real ones and are in direct relation.

 

[dryaquaman]

As an experiment try this:
Dial <MWI-on-feat-code>+<666>
See if the light on 622 comes on. Betting it will. (Then turn it off the same way.)
If yes, go to multiline appearance groups form and look up 501. See what phone it shows up on 1st. Again betting it's 622.
If yes, Delete 501 from ext 622 and then retry the Feature code test again.

Dry Aquaman

http://www.university-music-on-hold.com

 

[LoopyLou]

As dryaquaman says, I have seen where if there is not a real extension associated with a mailbox the system can do some weird this with message waiting. In your case you have a hunt group 500 with the extension set to 500. 500 is a hunt group that has members 501, 502 etc that appear on a bunch of phones includeing 622 I would guess. What I have seen is that when the voicemail issues the message waiting on code against ext 500, then the system places the message waiting against the first extension it has in its database with key appearance of 501. As dryaquaman says remove the keys from 622 and see if suddenly another set gets the message waiting indication.

to fix your problem you could change the extension number in 500 to a dummy extension and then use a message waiting key for that extension on whatever set or group of sets you want the MWI indication on.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[kwbMitel]

500 is the number of a hunt group with members 501, 502, 503 & 504, these appear on all phones as keysystem keys.

When a mailbox is associated with a hunt group, the first member of the hunt group will receive the MWI indicator.

When the first member is a keyline, then the first phone that was programmed with the keyline will receive the MWI.

If you want MWI, maintaining this scenario can be very confusing. I recommend a minor change.

Change the hunt group to 1*500 (number does not matter but this is what I would use.

Create a new keyline on the system numbered 500 (Location does not matter.)

Route 500 Always to 1*500 and also First Alternative to Voicemail.

Create MWI keys associated with 500 on the phones that require it.



**********************************************
What's most important is that you realise ... There is no spoon.

 

[kwbMitel]

Oh, And OzzieGeorge - I believe your issue with timezones on Survivable Gateways has now been resolved in Rel MCD 5.0

**********************************************
What's most important is that you realise ... There is no spoon.

 

[OzzieGeorge]

kwbMitel

Would you believe that the same week MCD 5.0 came out I changed jobs and now don't have to worry about it!