Mitel Forums - The Unofficial Source

Mitel Forums => MiVoice Office 250/Mitel 5000 => Topic started by: bll0059 on August 12, 2015, 10:27:28 AM

Title: Auto Attendant to Extention to Voicemail
Post by: bll0059 on August 12, 2015, 10:27:28 AM

I am a new end-user administrator and have been alerted that when a customer calls in on our main line they are not able to leave voicemail easily.

We have an auto attendant programmed on our main line from which you can choose listen to the directory or enter extension at any time. This works fine but when the line is not answered the customer is routed to the "mitel voice processing system". Is there a way to have customer auto routed to desired extensions' voicemail?

Title: Re: Auto Attendant to Extention to Voicemail
Post by: Tech Electronics on August 12, 2015, 12:58:28 PM

bll0059,

You will need to identify the Call Routing Announcement that is used as your Auto Attendant then change the Timeout value to where you want it to go.

Thanks,

TE

Title: Re: Auto Attendant to Extention to Voicemail
Post by: dwayneg on August 12, 2015, 01:39:53 PM

Check the phones, make sure they have a system forward path to voice mail and that the path is yes for RING NO ANSWER and CO TRANSFER/AA/VM (SYSTEM/DEVICES/PHONES/<EXT>/FORWARDING PATHS).  Also make sure SYS FWD is not disabled (SYSTEM/PHONE RELATED INFO/FLAGS/SYSTEM FORWARDING, ext should be in list).  Make sure each ext does have a voice mail account.  Make sure SYS FWD INITIATE timer is shorter than TRANSFER - VOICE PROCESSOR (SYSTEM/TIMERS AND LIMITS).

If a live person transfers a call does it go to VM box if unanswered?

Title: Re: Auto Attendant to Extention to Voicemail
Post by: DND ON on August 12, 2015, 02:36:09 PM

Also, make sure the Identification Prompt is turned off on the main Voice Processor screen.

Title: Re: Auto Attendant to Extention to Voicemail
Post by: bll0059 on August 12, 2015, 05:43:47 PM

No forwarding path the voicemail system ended up being the issue, (issue was isolated not system wide). I created the path and now we are back up. Thanks for all of your help!