Merlin Mail R3.0 Standalone MW Lights

[drewmich]

One of our West Coast interconnects just called me with a strange one about his Merlin Mail R3.0 - 4 port. The MM R3.0 is working fine - all ports test properly via Brooktrout's internal voice card diagnostics. All 4 ports go green and pass basic diagnostics - direct intercom dial to each port - each answers properly and hangs up and releases the port.

He is connected to the 016TR and he tested each of the 4 ports and says they are working properly. The client has 8 VM boxes setup and just a single AA with overflow as their receptionist answers to 4 rings - not a port congestion problem.

Oh - the problem is that none of the phones/stations w/ VM can receive a MW signal when a message is left on their mailbox. Even after 8 hours of waiting?

Any ideas on what the problem might be? Has good line cords or so he says. Is it possibly a programming step he has missed?

Thanks for any help!

Andrew Roach
President - Drew Telecom Group, Inc.
Lucent/Avaya Voice Mail-Component-Transtalk Repair Specialists
Lucent/Avaya Telecom Brokers/Resellers
drew@triton.net
269-685-5400 - voice
269-685-5500 - fax

 

[Telecomboy]

Make sure your hunt group for voice mail is set up "Linear" with the extensions assigned first to last. The reason being is that the last port on the mail is used to light message waiting lights and if it is being busied out more often than not, the system will not be able to activate message waiting lights.

if that is not the case, try sending a message waiting refresh through the pbx, Menu, maint, system, MWLP Update, then refresh.

 

[exsmogger]

Also make sure the voicemail hunt group (770) is set to Group Type: Integrated VMI

Brian Cox

http://www.jandjcommunications.com

 

[jgideon]

Don't the instructions say to change the t/r ports to be rotary for MWI?

 

[jgideon]

I only have experience with Merlin Legend Messaging.... I also discovered that you have to tell it that there is a phone associated with a mailbox to get it to light. Do you have to do that on this system?

 

[Telecomboy]

You don't need to rotary enable the ports for Merlin Mail. You can change the phone status though, so you may want to make sure the mailboxes were set up with telephones associated with them.

 

[jgideon]

Thanks for clarifying that Telecomboy... does anyone know why the Merling Legend Messaging wants rotary enabled ports? That just seems strange to me....

 

[merlinman]

Andrew,

Going further with what "Telecomboy" said, insure that the system is set for LINEAR.

ALSO, insure that the 4th port is in the VM Calling Group, AND IS WORKING !!!.

Here's how it works:

(WITH MM, forget what was written about Messaging, doesn't apply!!!)

THe LAST PORT (4th in a 4 Port system, 6th in a 6 port system, etc.) does the Light turning on and off job & and outcalling too, if that's programmed.

So, if the last MM port is busy or out of service, NO LIGHTS ! !

This can be verified by using MONITOR, but very few techs know how to do that.

jgideon - (ROTARY ENABLED) Because, it does not use TOUCH TONES, thus, the LACK OF TOUCH TONE RECEIVERS is a NON ISSUE for Messaging.

That was done by design..... AND - YOU CAN ONLY USE MESSAGING in an R7 or LATER, (Which means MAGIX)

 

[jinxs]

Merlinman,

what is the command to check MWI in monitor?

Drewmich, the best way I have found to test the MWI to determine if it is phone equipment or VM is to take an analog set or butt-set to the 4th or 6th port. Go off-hook and type in #53{ext} to turn on the lamp of an ext. #*53{ext} to turn off the lamp. If you can do this, your phone equipment is fine. Being that it is in the West Coast, you would have to find someone capable of doing this. Hope this helps.

 

[merlinman]

jinxs,

Based on the last post that talked about MONITOR, I must say, I am NOT AT LIBERTY TO SAY....

AVAYA considers that HIGHLY PROPRIETARY, and they would SPANK MY HAND SEVERLY should I divulge their secret info...

Thus, I must decline an informative answer....

 

[drewmich]

AFter many differing troubleshooting steps - processor & 016TR mods swapped & restart of all VM programming, the interconnect did what I had originally advised him to do .... check the (4) line cords especially the 4th port which carries the MW signal. He called me today apologizing like a fallen preacher that he had even bothered us with the MW problem as he discovered the 4th port line cord had a small "nick" in the cable. Good lesson for all of us ... cabling should always be our first check when basic functions don't work and programming seems correct.

Thanks for all the troubleshooting ideas ... still wondering about Merlin Man's last post. Its not like passing the info on how to monitor the MWI light is causing Avaya to lose major revenue or to allow someone to hack a switch. But I also know that alot of the ex-Lucent/Avaya techs still protect their secrets. We've been blessed to have a few ex-Avaya Tier 3/4 techs consult for us on projects and pass most of those tips along. Would be interesting to learn what the MWI monitoring tip is though. Maybe another day .....

Andrew Roach
President - Drew Telecom Group, Inc.
Lucent/Avaya Voice Mail-Component-Transtalk Repair Specialists
Lucent/Avaya Telecom Brokers/Resellers
drew@triton.net
269-685-5400 - voice
269-685-5500 - fax

 

[Pepperz]

TTR testing is in a post on 2/21, by ScotTel. At the bottom is a detailed description of the TTR testing sequence.

Pepperz@charter.net