3300 Message Waiting Lamp Issues after Upgrade 1

[kwbMitel]

I replaced a 3300 Mx on Friday with a MXe.

Everything went perfectly except for the lamps.

I have phones with lamps flashing that, when the message key is presses, the system say "No Messages"

Cycling a message thru the mailbox does not seem to be the answer.

it looks very similar to what you get on a 2K if you do a move swap with a message indicator active on one of the ports.

I need to flush the message waiting indicators completely.

Any thoughts?

(don't everyone rush in at once ;-)

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[slapin]

try
LOCATE FEATURE EXT <number>
where <number> is extension number with a lamp.
post the result

 

[MitelInMyBlood]

You have basically two types of message waiting;

- a "message"
and
- a "callback" message

Unfortunately either one will cause the lamp to come on and equally unfortunately there is no global command to extinguish them.

The ESM doesn't support this command but it should work in the 2K and via the telnet interface: LIST SHO FLIST FOR 9

That will tell you how many lights are on (and thus how big the problem is).

In the 2K you could partition the machine, perform a data restore and jump it across the partition (causing all your pers to reload) and that would solve errant MW lamps because the lamp status was not retained across the datasave/restore. I'm a little unsure how to tell you to solve this in the 3300, but would think a similar approach would work.

 

[kwbMitel]

Finally got to site to look into this.

The voicemail for some reason was setting Dailed message waiting and not callback messaging.

As part of the upgrade, I had increased the port capacity of the voicemail to 30 ports without issue.

Thinking this might be related as the voicemail uses the last port for messaging I removed the last 10 ports.

When I tested, the lamp didn't turn on right away so I restored the 10 ports.

Now I'm getting the Callback messaging the way I should but the lamp isnt engaged for up to 60 seconds.

I can live with 60 second delay but am curious if anyone else is noticing a delay in lamping with embedded.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[MitelTech]

The m/w port (port 20 or 30 depending) needs to be in the vmail hunt group for it to set callbacks. If the m/w lamp is not in the hunt group it sets dialed message waiting. If you change it, one way or the other, while lamps are on, they will not clear once checked.
If you get some dialed and some callback, then the only real way to fix is fix your hunt group then give users the message waiting dialed deactivate code and instructions on how to use, as well as enable multiline set voicemail callback erasure allowed in the COS' and teach them how to use.
Have fun!

PS-no one should ever pull the last ports out of the vmail hunt group. If you are removing ports, for say RAD duties, on an active system you should always start with port 1 and work up from there.

 

[MitelTech]

That should say "If the m/w PORT is not in the hunt group...

 

[kwbMitel]

MitelTech, your information matches very closely with reality but not quite. Close enough to deserve a star though, thanks.

When I increased the port count my intent was to leave them out of the hunt group and reserve them for future RAD use. I was aware of the issue of using the last port for a RAD but for some reason did not remember it.

I had not placed the port in the hunt group and thought this must be the issue. Not quite.

Once everything was put the way it should be I had no lamps at all.

I finally said the hell with it, reduced my port count to 20 and restored everything the way it was and everything is now good.

Troubleshooting is for another day .



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[MitelTech]

That falls in line with what I said. As soon as you increased to 30, it started using port 30 for lamps. Without it in a hunt group, it started setting dialed message waiting. Decreasing to 20 would fix any lamps set with callbacks, but should have left any lamps set by port 30 (dialed).
This has been tested and documented by many of us, it is a known caveat with the system.
As long as you know what is happening with the system you should be able to fix it no problem.