Multiple Extensiosn to One Mailbox 1

[rdpayne]

I found a great thread from last May (posted below) which has some good instructions on how to do this. I understand why it should work, but the problem is that the rerouting is sending back to the autoattendant. This is what I done:

Set up (both ways) phantom extension / phantom hunt group = #10101 (user's mailbox)

Call Reroute Always to 2 (Call Reroute Always Assigment for our VM pilot)

If I call #10101, it get dumped right into the user's mailbox, works fine.

Tested my extension (10132) to call forward to #10101, goes to my own mailbox every time.

Tested it with another extension without existing mailbox (10204) and it goes to the autoattendant.

So, in both instances, it knows to send it to the VM pilot, but no further. IT does not send it to the VM for 10101.

What am I doing wrong? I've tried both Call Rerouting first alternative, and call forwarding no answer / busy using existing Feature Code. Same problem both ways. Thanks in advance.

TheMitelGuy (IS/IT--Management) 27 May 06 20:03
1st) I would use the *EXT solution here to forward multiple extensions to a specific mailbox. If you had 101, 102, 103, 104, 105 and 106 and you want them all to go into 101's mailbox, you can setup extension *101 and call forward (RNA or BUSY, OR BOTH) to *101. That would work there. I have to admit that *EXT solution is amazing and is an excellent posting.

2nd) I don't think you can manipluate what is sent to voice mail. The EMEM works with a basic API with the switch. The EMEM actually emulates a 4150 to the switch - yes that is how even Mitel does it. You would have to know how to change/modify the display prompts.

 

[kwbMitel]

There is a relatively simple method to use ACD Paths to redirect your calls. The primary reason you are having difficuly is the Mitel retains the originally dialed ext regardless of the number of forwarding hops. This means that if you call ext A which is forwarded to Ext B and then forwarded to VM, Ext a's VM will pick up.

The only way I know to override the Mitel is Via ACD Paths. If an ACD path is the last point before voicemail the integration will occur with the ACD Path's DN and not the original dialed extension as usual.

You need to set up an ACD Agent Group. DN does not matter. The only thing you need to select is allow calls to path with no agents logged in.

Next set up your ACD Path. The DN can be the number as you describe above #EXT. Assign the agent group set up above to the Path, then enable interflow after 1 second to your voicemail pilot.

Any calls forwarded or rerouted to the Path number will integrate the way you want.

Good Luck.

There is an island of opportunity in the middle of every difficulty.
Miss that though, and you're pretty much doomed!

 

[rdpayne]

That worked perfectly. And since this was specifically for the CEO, I can come back to work tomorrow. Thanks again. rp

 

[MitelInMyBlood]

Dunno about the MEM or NuPoint, but on an Octel (250 & 350)you can accomplish the same thing with a type 34 transfer mailbox. I have several execs who have two or more phones in their office, i.e., a Polycom + their regular ext & maybe a guest phone in the larger suites, etc. By putting Transfer Mailboxes on all of the subordinate extensions, any call to any one of them will land in the Exec's mailbox (or wherever we need them to go). The Octel also does not consider Transfer Mailboxes (or even menu trees) as a system resource therefore you can have as many of them as you want without impacting the number of mailbox licenses. On the Octel your mailbox licenses are only consumed by mailboxes that have the ability to actually collect messages.

 

[rdpayne]

That is great to know about the Octel. We've got a tenant who wants a crazy complicated menu tree, and with several giving messages or transfering. I was able to mimic what they want with a ACD path and using a RAD to give the menu options, and using interdigit dialing list for the options, but the problem is I am using up a vm port for the rad instead of vm boxes, which we would have to charge for. rp

 

[MitelInMyBlood]

Back many years ago when the Octel 250 was first installed the Octel folks had us dedicating ports (via port monitoring) to do things that we later learned to do within the system without burning up these valuable ports. We also used the multiline sets that were assigned as ports as the "host device" for pilot numbers into menu trees & announce-only mailboxes. Only word of caution here is to disallow "msg wtg" on any of these key appearances else it will break the integration (learned that the hard way).