3300 - Redirecting calls to specific voicemail boxes 1

[kwbMitel]

I have proven the following concept in my lab.

By combining the process for Quick access to voicemail and the process for Using Nametag Huntgroups to override VM Integration, it is relatively simple to route a call to one station directly to the voicemail of another.

I have only tested this with the embedded mail.

If anyone has a Nupoint available for testing I would like to know if the process works for it as well.

Process to route ext 1000 into Mailbox 2000 (testing)


Create mailbox 2000
Create Namtag Huntgroup *2000
Create Always Reroute Point for *2000
Create 1st Alternative Reroute point for *2000
Set Routing for *2000 to always route to voicemail
Dial *2000 and verify call goes to mailbox 2000
Set Routing for Ext 1000 on 1st Alt to *2000
Dial 1000 and verify call goes to mailbox 2000 on no answer
Set DND on 1000
Dial 1000 and verify call goes to mailbox 2000 on Busy
Set routing for ext 1000 on Always to *2000
Dial 1000 and verify call goes to mailbox 2000 on Always

I will write up a FAQ once I know how the Nupoint responds.

Anyone willing to assist?



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitelpassion]

kwbmitel,

thanks for this. actually gonna use this method in an installation soon - THANKS!

I have a Nupoint in my lab but not fully set up though. Can't give an exact time frame but would like to test this if someone else doesn't get to it before I do.

could you however elaborate a little more on Using Nametag Huntgroups to override VM Integration? what do you mean override VM integration? are you saying that you can only use a nametag hg *xxxx and not an extension *xxxx in your scenario test above?

 

[kwbMitel]

What Using a nametag huntgroup to override VM integration Means:

By design, Mitel systems retain the original called digits for the purpose of Voicemail Integration regardless of the number of forwarding hops that take place in between.

E.g. A call to Set "A" Forwarded to Set "B" then Forwarded to Voicemail will answer with Voicemail "A"

If a Nametag huntgroup is introduced, the original dialed digits are replaced with the Nametag Groups' digits.

e.g. A call to set "A" forwarded to Set "B" then forwarded to Nametag Group "C" and finally to VM will integrate with Voicemail "C"
Note: the nametag does not need to be the last step for this to work.

I would expect all of the above to function on the Nupoint.

The question at hand is does the shortcut for Direct to voicemail work as well on the Nupoint. The Embedded Mail allows a shortcut to be created that has the extension preceeded by a * or #. This shortcut DN is then routed to vm and can be used to send calls directly to VM for specific extensions.

e.g. Call to Set "A" forwards to Set "B" then Forwards to nametag group "*B" which would integrate with Voicemail B.

This last example is a common ask of my customers.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitelpassion]

is your second example not the same as your first example if not what's the diffs except that you're forwarding to a *xxxx nametag and not a XXXX nametag?

never used this before so just wanna wrap my head around this

 

[kwbMitel]

Examples using nametag groups have different purposes and applications.

The first example using the Nametag group can easily be replaced with the second example as you've observed. In the first example the Nametag group is a unique number and it does not matter whether you use the * or not. Either is valid.

The second example Using Nametag allows you to integrate with a mailbox that already exists and is already associated with an existing extension. This method was not previously known to me and cannot be replaced with the first example (Which was known to me)

The only sticking point is whether the same process works on a Nupoint.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[paterson]

Mitelpassion, I think there is a small element that you are missing. The embedded VM on the 3300 does NOT recognize a * or a # as a valid digit. So, if the first digit of a DN is a * or #, the embedded VM will ignore it and focus on the other digits. That's how this works.

I thought that the Nupoint does recognize a * or #. My guess is that it will not work, but I am building a nupoint right now and may have time to try it out.

_______________________________________________________________

If you did not take enough time to get it right the first time...

What makes you think that you have time to fix it?

 

[kwbMitel]

Thanks Paterson,

In the good old days of the Nupoint/Mitelmail/Centigram with inband integration, you would send a * as part of the integration digit string.

Because the Embedded was developed to mirror the Nupoint Functions it works that way as well.

I have about 80% confidence that it will work.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitelpassion]

it's clear now.
The *XXXX for the nametag is cause the extension for a particular voicemail already has XXXX so nametag can't be XXXX, introducing a star avoids a dialling conflict.

embedded voicemail doesn't care about the star so no problems.

in your fist example assumption is no existing extension linked to a mailbox but by using nametag with or without star sends it to this specific unlinked mailbox number.

thanks for you patients guys. makes sense!

 

[mitelmitel]

I have proven the following concept in my lab."

I am glad you found it helpful. It works really well in the field.

 

[kwbMitel]

I had an opportunity to test on a Nupoint 11 without success. I am going to assume that this is not possible on the Nupoint. (Too Bad)

I'll write a FAQ soon.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitel100]

I have created this type of set up on a site, using Nametag hunt groups with Nupoint 11 and I did get it to work. Although with the *.

This is a very good example of the 3300's flexibility.

__________________________

There is no 'I' in 'Team'
__________________________

 

[Mitel100]

Sorry, It worked WITHOUT the star. Apologies for my typing.

__________________________

There is no 'I' in 'Team'
__________________________

 

[kwbMitel]

Thanks Mitel100.

Doing it without the star has been possible for some time. The advantage of being able to use the star allows you to have a nametag group force the call into an existing mailbox without conflicting with the original extension.

Another advantage to the star is the ability to force the call into a mailbox that has the capability of setting a message lamp. (with Nupoint there are other ways to overcome the Lamping issue but they are more complicated)

Here is a copy of the FAQ I just wrote:

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.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.