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!

SX2000 LW34 - MWI will not light on some 4025s

Status
Not open for further replies.

tundranugget

Technical User
Sep 4, 2003
98
US
Hi. I have SOME extensions (4025 Supersets) where the MWI will not light even when there is voice mail in the mailbox. I tried replacing the sets with ones that I knew had working lights, then I checked the light by turning the light on and off using feature codes. Then I dialed the extensions and left messages. I checked visually and nothing - no light flashing. Then I checked with "loc fea ext 2xxx" and nothing - no "Message Waiting Indicator" message. As far as I can tell, the settings for both working and non-working extensions are the same: same COS, same COR, etc. I tried deleting the offending mailboxes and recreating them with no change.

To repeat: This is only affecting SOME of the 4025s.

Any ideas? Could there be problems with NuPoint Messenger? I hope not - I know very little about NuPoint.
 
I would suspect that the issue is certainly with the NuPoint. More specifically, the individual mailboxes. What version of NuPoint do you have?

I would go to the mailbox of an extension that has the mwi light working and look at the options carefully. Then compare with a mailbox not setting the mwi light. Pretty sure you will see that the mailbox is not set up for message notification. Change to the type of notification in the working mailbox and test.

Without knowing what NuPoint version or integration you are using, I can't give more specific help than that. If you at least know how to look at mailboxes, then you should be able to edit them.

_______________________________________________________________

If you are not part of the solution...

Then there's good money to be made in prolonging the problem.
 
The system displays "OS VSN: 4.23G". Is that the version I am looking for?

I (M)odified a problem mailbox so that it matches the settings for a working mailbox. The problem remains. Could there be some sort of maintenance I should be running? I was "given" the phone system to administer about four months ago - aside from adding new mailboxes and changing VM passwords, I have done no maintenance.

I did extract a report, "Mailbox data". It seems that one difference may be that working maiboxes read "Day:5 Night:5" and non-working ones read "Day:M Night:M". But, when I modify the problem mailbox to "Day:5 Night:5", I still get no MWI. When I create a new mailbox from the Superset 4025 using "Administration", I get "Day:M Night:M".

When I login to NuPoint and Modify a mailbox, some items are presented for change that do not seem to be displayed, such as:
New message waiting type #1:
New message waiting type #2:
New message waiting type #3:

Any ideas?
 
There needs to be an entry in "New Message Waiting Type #1".

I'm not much of NuPoint guy, but I think that you can enter a ? at that prompt and find with number to put in for the different types.

Hopefully someone else here can take you further.

_______________________________________________________________

If you did not take enough time to get it right the first time...

What makes you think that you have time to fix it?
 
The message waiting type could be your culprit, this needs to be set correctly for the MWI to work. Compare the existing settings between a working an non-working user, easiest way to do this is press "D" from the Mailbox Menu and plug in the mailbox number. D is the delete function, but it displays all of the current mailbox info, then asks for confirmation, so it's good for looking at existing settings. Check to make sure the FCOS, LCOS, and MWI types are the same on the working & non-working mailboxes.

You can also try using the light test feature in NP to check MWI, it's under (S)ystem -> Additional (O)ptions in the menu tree. You plug in the MB number, and what you want to do with the light (on, off, or current value).

Also, to see what version you are running, you'd need to run a System Information report under (R)eports -> System (I)nformation. The most current data will be at the end, which is important to know if the system has been upgraded a few times, this report will show all upgrades since the system was first built.
 
Thanks for the "?" hint. One of the options (#26) is: "Mitel DNIC Inchannel". 26 is what we enter for Message Waiting Type when adding a mailbox from the Supersets. Once I saw that, I (finally) notice an entry in both working and non-working mailboxes that reads: "MWI #01: Mitel DNIC Inchannel", so I guess that is not the problem.

I tried testing the lights using (S)ystem -> Additional (O)ptions -> (L)ights, but the MWI on the phone was unaffected.

When I tried to report Sys Info, I got: "sinfo: Operation not permitted". I guess the login I was given does not have enough authority. I am trying to get another login to try.

Attached file has configuration of a working mailbox and a non-working mailbox.
 
 http://www.fileqube.com/hl/GsGoTQsa186377/mwi.txt
What happens when you try to dial the MWI on from a phone? Assuming you have a test/MDF room phone, change the COS of that phone to match the COS of the MWI ports (usually the first or last few ports for the NuPoint server, or one on each line card). Then dial the message waiting on code + DN and see what happens.

Also, is this a networked environment w/ multiple 2K's? Or is there anything else unique to only the non-working sets (all on the same card, same firmware, etc.)?
 
OK, sorry. Out of curiosity, I dialled the numbers for Voice Mial - 7001 through 7026. Discounting 6 ports for MWI, leaves 18; of those, 9 were displaying "OOS" or "No Distb". Without knowing totally what I am doing, I Shutdown Voice Mail; Re-Booted the VM server; re-loaded the 3 DNI cards in Mitel and now everything is OK.

Thanks for all your help, even if I apparently approached this all bass ackwards.

BTW, I was totally unable to determine what was unique to the failing sets. I have to assume it was because those ports were "hung".

Thanks.
 
mw ports in Nupoint should always be in DND. A seperate port COS would have permanent DND enabled.

NO GOOD DEED GOES UNPUNISHED!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top