Audix messsage light issue on Legend

[Tripoth]

Ok,
Location has 2 sets of extensions.
Ones with a phone and the other are virtual.

Client dislikes have voicemail on the 2 sets fo extensions because they have to continue to check the virtual ones without the benefit of a messaging light coming up on a phone.

The virtual ext. can go to an extension with a phone. They are OK with that. They do not want to give up the virtual numbers because the general public knows them.

I think I have a solution, but I wanted to run it past the pros.

Give the virtual extensions auth codes, call into the programming of the virtual extension and forward it to an extension with a phone. This eliminates the 2nd mailbox and should be seemless as long as the voicemail on the real extension reflects the change.

Sound good?
Any other suggestions?

 

[merlinman]

Or use out calling to turn the Message Light on at the REAL EXTENSION.

-OR- Have out calling CALL the real extension for the Virtual.

http://home.comcast.net/~merlinman

 

[dagwoodsystems]

Build a "real" mailbox for the extension with a telephone, i.e. the real extension.

Next, build the phantom extension mailbox as an Automated Attendant with no selector options. Set the zero/timeout action to one second (which is the shortest you can make it in AUDIX), and the behavior to Call-Answer on the "real" mailbox.

Unanswered calls to the real extension will land in the real extension's mailbox. Callers tring to reach the phantom extension will hear a brief "please wait" before being dropped into the real extension's mailbox.

Make sense?

Tim Alberstein

http://www.dagwoodsystems.com

 

[Tripoth]

Might this work....

Give the extensions with a real phone a coverage button that has the virtual number on it.

Go into the audix and on the first field of the extension with a phone, place the real extension in the primary slot and the virtual extension into the secondary slot.
Then remove the voicemail box for the virtual extension altogether?