sundance-communications.com/forum Forums TDM Business Telephone Systems Toshiba Telephones & Systems Message waiting indicator on another extension

Have a Toshiba CIX100 + LUCA Strata messaging voicemail
Extension 100

Sorry, posted by mistake and then timed out for editing!

Have a Toshiba CIX100 + LUCA Strata messaging voicemail
Extension 724 has did
Extension 725 no did
Hunt group 510, 724 and 725 as members
When a call comes in both sets ring, perfect
Trying to put 724 message waiting indicator on 725 in EManager but get an error, The Prime DN entered conflicts with a value of an existing numbering scheme.
What is the correct way to get a message waiting light for another extension on an extension with no voice mailbox?

Thanks

George

Here is what I would do.
Have 1 mailbox 724.
Set bot VMID codes to 724
In the voicemail box 724, add 725 in the additional MWI

A message comes in, both MSG lights come one. Either phone can log in and clear the message and both lights

Thanks David

Tried that and no mwi on 725
btw - 724 is a digital phone and 725 is an IP phone
Not sure if that makes a difference

George

I'm not sure what you could be missing. I used this same method a couple times, and I have used it to light up over 10 message lights on a single mailbox.

It does not matter if the extensions are IP or digital.

you could always use the message cascading from 724 to 725

cascading is how I do it

Problem is 725 does not have a mailbox so cannot use cascading

Any other ideas?

I checked settings as per David and they seem correct

Thanks

George

Probably a dead post but figured I'd add the tweak I had to do to get it working. I had to add the VM hunt group DN in the Station assignment VM MW Center Port (260-FB20), it wouldn't light for me.

-W

That is a good point. I did not even think to ask about the center port, since it is automatically set when assigning VMID codes using the wizard.

I had a customer with an extension that would not light the message light on there phone. Their internal IT person created the extension and did not set the VM MW Center Port. Once set MWI worked fine.

This could have been this OP's issue.

This is an older (2 year old) post but sometimes people (like me) will search the forums, or Google.