How to light MWI on 2 separate PBXs?

[drsprite]

Hello,

We have 2 PBXs, which are running DCS over IP with the use of 2 MedPros. We also have Modular Messaging 4.0.

We are running into a situation where we have 2 extensions associated to 1 mailbox. They are 61000 on PBX A and 51000 on PBX B. Since these 2 stations are not on the same PBX, how can we light the MWI for both phones on separate PBX systems?

We've tried a ticket to Avaya with no help, so I am looking to the community for help. Avaya's suggestion was to FCE, but that's not an option for us.

I'm sure we're not the only corporation out there that needs to light 2 phones on 2 separate PBXs with 1 mailbox.

Thanks!

 

[DontDeleteMeAgain]

what happens if on 1 station you put the MWI light on page 1 as the others number? know what i mean>?

 

[drsprite]

If on station 61000, we put in 51000 for the light, it doesn't work because these 2 stations aren't on the same PBX system. See the attachement for the locations I'm referring to..

 

[testLED]

What happens if you dial the LWC activation feature access code from 61000 to 51000 eg...*40 51000 does the lamp light up.

 

[DontDeleteMeAgain]

modualr messaging has secondary extensions for each mailbox, maybe you can use that as a dummy number OR if it's on your LAN use email notification to a distribution list that goes to both people.

 

[lexcruz]

We have Intuity, but if Modular Messaging is like Intuity, you should be able to go to that voicemail system and look for a field called Secondary ext: In that field you should be able to enter the other extension number.

In modular mesasging, change sub 61000 and under secondary extension, enter 51000.

It's done in the voicemail server not on the pbx.

 

[drsprite]

testLED: if I do *4 51000, it'll turn on the MWI from 61000, and #4 will turn it off. This is helpful, but doesn't seem to be working with Modular Messaging.

DontDeleteMeAgain & lexcruz: In Modular Messaging I have the primary extension as 61000, and the secondary at 51000, and we can see in the logs that the command is sent from the server to try and turn the light on for both extensions, but it fails to light the light on the secondary extension of 51000.

We believe we have the MM server and Account configured correctly, and think this may be a configuration issue within CM.

Thoughts?

 

[testLED]

Have you tested the same scenario locally with two phone to make sure the MM is functioning?
Also what side of the network is your MM and if you leave a voicemail for 51000 does the MM set the light just for that station alone?

 

[drsprite]

The MM is on the 61000 side.

We have tested locally (e.g. 61000 primary, and 61001 secondary) and it works. It's failing when it tries to go to the 51000 site to light the MWI there.

 

[testLED]

Are you using Qsig over your DCS...can you post your Qsig option features..normally page 8 of system customer options.

 

[testLED]

Also what platform are both ends?

 

[phoneguy55]

I don't think this can be done with stand alone PBX's. You can have MWI in one site or the other. Not both.

 

[lexcruz]

It can work with 2 stand alone PBX's because I have it working that way on my phone using 2 PBX systems and one voicemail server.

Check the LWC Reception and the Audix Name fields on page 2 of the station form to make sure they say the name of your voicemail server.

For our system, they both say Audix
AUDIX Name: audix

 

[drsprite]

The station forms have Audix in for the audix name on page 2. Modular Messaging in our setup can light the MWI fine over our 3 campuses via DCS.

What we're having an issue with is trying to light 2 phones for 1 mailbox, over 2 PBX systems. It can light the first light fine (61000), and it sends the command to the 2nd light (51000), but it never gets turned on.

Interestingly enough, if we swap the primary and secondary extensions around, it will still work in the method that the light turns on for the primary extension - regardless of PBX location. (So swapped would be 51000 primary lights, and 61000 doesn't).

So we're thinking the CM isn't correctly passing the MWI command for the secondary extension. We believe this because in the log file for MM we can see the command was sent.

 

[AvayaTier3]

The reason it's not working is the subscriber information has a pbx id for the primary and there is no way to program a different pbx id for the secondary extension. MM is sending the message to turn on the light, to the wrong pbx.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting

http://bshtele.com

 

[drsprite]

Thanks bsh, do you know of a fix?

Like I said, if I change the primary extension to either PBX A or PBX B, it'll work for that primary extension regardless of PBX. It's the secondary MWI that's failing.

Is there something that can be programmed to fix this?

This is for our CEO of a Fortune 100 company, and we're trying to find a fix.

 

[lexcruz]

Ok, that's a little different. A temporary workaround until someone figures this out is to turn on the message notification function in the mailbox. Tell the system to call 51000 when new messages are waiting on 61000 or vice versa. It will call the other extension and alert them that messages are waiting.

 

[AvayaTier3]

I have been waiting for lexcruz to respond. I have never seen this work. It would be a most valuable post if there's a way to do this.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting

http://bshtele.com

 

[drsprite]

lexcruz,

I don't believe we want to do that because the system will ultimetly be calling itself right? The secondary extension goes RNA which then the MM will answer.

He technically has "notification" in his Outlook Inbox since our MM has Exchange back end.

We're just trying to turn on the light to have the visual aspect of it.

 

[lexcruz]

AvayaTier, are you referring to the message waiting notification or splitting the mailbox?