MWI not working - PBX Info :: Your Free PBX, PABX and Telephone Information Resource

calculan · 02-14-2008, 11:36 AM

I have a Merlin Legend R7 system that we are trying to partner with a Trixbox for voicemail. Everything seems to be working, but we can't get the MWI lights to work on our BIS-10 phones. Entering #53xxx on one of the phones, where xxx is another extension, seems to get accepted by the Legend, but the light at xxx never comes on. Any ideas as to why MWI may not be working?

dexman · 02-14-2008, 02:38 PM

I'm not familiar with Trixbox.

Generally speaking, for flawless operation, it pays to go with OME as opposed to aftermarket equipment.

Try contacting Trixbox and see if their customer/tech support can figure out the who’s. what’s & where’s.

calculan · 02-14-2008, 02:56 PM

Shouldn't the Trixbox be out of the picture? I thought the general troubleshooting technique was to verify if the light worked on the phone. I was led to believe that #53xxx should turn the light on regardless of the presence of a VM system. Is that incorrect?

calculan · 02-14-2008, 03:26 PM

The BIS-10 phones are identified as extension type ATL, should they be set to ATL-10?

dexman · 02-14-2008, 07:35 PM

I'll do some digging to see if ATLs inventory differently (based on the number of buttons). My inclination is to say no, but I want to be 100% sure.

dexman · 02-15-2008, 07:25 PM

As I suspected, the Legend does not differentiate between the various ATL desk sets.

#53+extension no. should turn the light on, and
#*53+extension number should turn it off so that IS the way to
troubleshoot the issue.

Is it possible that the calling group for the Trixbox
is not set to Integrated VMI, or the port that is setting the MWI is not
part of the VM calling group?

The LEGEND R7 Feature Reference does make note of some differences (not of ATL's but of MWI with and without voice mail) starting with 6.0 and 6.1. Avaya has the guide available on their website and you can download it for free.

calculan · 02-18-2008, 09:29 AM

Does #53EXT use the VM system? I thought it went directly to the extension.

dexman · 02-18-2008, 10:50 AM

#53 (+extension) simply signals the message waiting lamp to turn on. #*53 (+extension) signals the lamp to turn off.

calculan · 02-18-2008, 11:13 AM

I apologize for being dense or vague.
Normally the VM signals the extension port and the port turns on the lamp. I assume that the signal is a 53 or a *53. So if we manually enter the feature code, don't we bypass the VM entirely? Is the 53 telling the VM to tell the port to turn on the light, or is the command going directly to the port and telling the port to turn it on?
Just trying to figure out where to start looking.

dexman · 02-18-2008, 02:48 PM

If I'm not mistaken, the codes tell the processor to toggle the lamps on & off.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Conf Calling Scenero - working and not working	PBXChick	NORTEL	1	01-16-2007 11:09 AM
TIE/CDP not working..	justzikle	Meridian Systems	6	09-22-2005 03:39 PM
New PRI not working	Twisted	Meridian Systems	7	07-21-2005 07:49 AM
TTY NOT WORKING	brogers	Meridian Systems	5	02-22-2005 09:40 AM
NXX 641 not working	Tonka56	Meridian Systems	12	12-10-2002 09:24 AM

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)