3300 - Overriding integration / Redirecting calls to specific voicemail boxes (Embedded Mail)

Update:Jan 2010 - There appears to be an issue when using Nametag groups where once the mailbox has answered, and the user chooses to be transfered, if the call returns to VM the Nametag integration still applies. As a result, I do not recommend this method when using MLAA.

Some of the information below appears in other FAQs and I have referenced them below. The difference in this FAQ is in how these methods can be combined to accomplish the task.

The following 2 FAQ's are both proven methods of "breaking" the Mitel integration with original dialed digits and forcing the call to integrate with a specific Number.

faq1329-6958

faq1329-6743

The disadvantage of these methods is that both have issues if you want to associate a message lamp with the destination mailbox.

The following FAQ explains how a Users mailbox can be accessed via a Quick Message dialed number.

faq1329-6963

By combining these methods, we now have a method where a call can be forced into a specific mailbox AND also have an associated message lamp.

Example
To Illustrate, I will use the example of a DID the comes into a Console during the day with overflow to an Autoattendant, but at night goes directly to a general delivery mailbox.

DID = 1000
Console DN = 1000
Phantom Key Appearance = 1001 (for Mailbox and lamp)
Nametag Huntgroup = *1001
Mailbox for night messages = 1001
Message notification for Night MB = (Key programmed as needed)
Call rerouting for 1000 = Day(none), Night (*1001)

Call flow Day:
Caller dials into 1000
Call rings Console and is answered
If unanswered, call routes to the voicemail autoattendant.

Call Flow Night:
Caller dials into 1000
Call routes to Nametag Huntgroup *1001
Call routes to voicemail (Quick message for mailbox 1001)
Mailbox 1001 answers and takes message
Message lamps are turned on where programmed.