Transfer * extension number doesn't transfer to voicemail. 1

[gbon851]

I using a Mitel 3300IP and Mitel 5330 IP Phone. I'm trying to transfer a call directly to voicemail without the user's extension ringing and her answering the extension. I hit (transfer * 141) the call transfers to the extension. It rings the extension but doesn't transfer directly to voicemail. What's wrong?

 

[Supernova99]

Does the voicemail answer with 'hello mailbox' ? if so you will need to dial **141 then release the call you should hear 'welcome' after you pressed the second *

Share what you know - Learn what you don't

 

[Supernova99]

I forgot to ask the obvious question does mailbox 141 exist?

Share what you know - Learn what you don't

 

[gbon851]

Yes mailbox 141 exists. When I dial (Transfer * 141), then extension 141 rings instead of going directly to voicemail.

 

[YnotPhone]

In the system speed call assignment form - under first alternate - that is pointing to the voicemail ports correct?

 

[YnotPhone]

Sorry I meant the Day/ Night1/ Night2 service... not the first alternate.

 

[Supernova99]

eed to dial the voicemail hunt group number first then dial *141 e.g. trans/conf 6000 *141

Share what you know - Learn what you don't

 

[kwbMitel]

I believe you may be trying to use the method laid out in this FAQ.

If so, make sure you have routed the hunt group *141 to VM

Hunt group *141 requires no members but I suspect that you have added 141 as a member which is why the phone is ringing.

Review the notes of this FAQ and make sure you have followed all the steps.

faq1329-6963

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

 

[Supernova99]

If you have used the shortcut method then does *1 clash with any feature access codes?

Share what you know - Learn what you don't

 

[gbon851]

Here's an example of the Hunt group listing. All other extensions seem to work OK. I must be missing something on another form.


Hunt Group Hunt Group Mode Hunt Group Name Hunt Group Priority Hunt Group Type Home Element Secondary Element
*136 Terminal 64 NameTag Btx Not Assigned
*137 Terminal 64 NameTag Btx Not Assigned
*138 Terminal 64 NameTag Btx Not Assigned
*139 Terminal 64 NameTag Btx Not Assigned
*140 Terminal 64 NameTag Btx Not Assigned
*141 Terminal 64 NameTag Btx Not Assigned
---------------------------------------------------------
Hunt Group Assignment

Hunt Group: *141
Hunt Group Mode: Terminal
Hunt Group Name:
Class of Service - Day:
Class of Service - Night1:
Class of Service - Night2:
Home Element: Btx
Secondary Element: Not Assigned
First RAD:
Second RAD:
Night Answer RAD:
Hunt Group Priority: 64
Hunt Group Type: NameTag
Phase Timer Ring:

 

[kwbMitel]

Check your call reouting assignment for *141.

The Day / N1 / N2 needs to be the same as the others.

If *140 works then the conflict that Supernova suggested is not a factor.

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

 

[gbon851]

Thanks that was the problem see below for *141. Thanks kwbMitel for your help. It was truely appreciated. After I correct *141 to all 2's worked fine. Thanks Again!

Number Call Rerouting - Day Call Rerouting - Night1 Call Rerouting - Night2 Call Rerouting DND Type Call Rerouting - 1st Alt. Call Rerouting - 2nd Alt.
*135 2 2 2 All 1 1
*136 2 2 2 All 1 1
*137 2 2 2 All 1 1
*138 2 2 2 All 1 1
*139 2 2 2 All 1 1
*140 2 2 2 All 1 1
*141 1 1 1 All 1 1