I have programmed an extension with a star in front. [*1234] that i need to strip it because it's a forward to voice mail. Where in mitel can i strip the star?
Thanks for your reply. I use * plus extension to direct transfer call into voice mail.
*XXXX (that's star followed by any 4-digits) has direct forward to Exchange UM Auto Attendant.
With this setup, a user can dial *1234 and have the call get sent to VM; Exchange VM picks up the call as being last redirected by 1234, so it dumps the caller into 1234's voicemail box.
So i need to strip the * before it reaches Exch UM.
Is *1234 a more specific form of *XXXX or is *1234 being used for a different purpose than *XXXX
It would seem that *1234 ending up in mailbox 1234 is exactly what you are trying to do if 1234 is a users mailbox.
It seems you are trying to do something similar to a FAQ, FAQ1329-6963, and my confusion may be due to that assumption. Please read the FAQ and advise if this is what you are trying to do.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
yes, that answer was given by MitelInMyBlood. and it worked but now it gives access denied, after many researchs is due that Exchange UM, can't read the *, so I need to strip it somewhere ..but where?
That solution was designed for the Embedded voicemail not an Exchange UM.
When it was working before was it integrated with the Exchange?
Assuming yes, should you not be looking for what has changed on the Exchange rather than adjusting the Mitel?
Assuming you can't do that, the only way you can strip a digit is by using loopback trunking and ARS. There are some helpful FAQ's that utilize loopback trunking that will give you the concept. I've made a lot of assumptions to get to this point so I'll wait for your next response.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
Thanks for your help. Our vendor simple replied 'this can't be done'..but it was working before. Not many Mitel vendors around and yes, we already changed vendors. I ccall Mitel too, but they don't like to play with Exchange..hehe... and asked me to contact our vendor...it is just a loop. I find most of my answers from 'help' in the 3300 which actually helps! and from reading here..tek-tips!
I will check ARS anyways. If anybody has some other suggestions I would appreciate it. Thanks.
I still think you're looking for the wrong solution. If it worked before, it should work now. What you are trying to change in the Mitel does not make sense on several levels.
I think you really need to look harder at the exchange and try and understand what changed and why.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
I don't think you can strip the star if it's in front of the extension number. You'll have to change the extension number but having said that it should work because it used to.
I think what you should do is go the the class of service for the phone and check to see if 'public access via dpnss" is yes. check this for your trunks (sip or other) too.
Also as a test clear your class of restriction groups. make a note of what was in there as you would want to put it back.
rarely have I seen access denied and not have something to do with barring. someone's changed something if it used to work.
to be honest I've never done Exchange UM so not even sure how it's integrated, maybe give a run down of this.
Thank you Mitelpassion. I checked COS and 'public access via dpnss' and is set to 'yes'
Something had definitely changed. We changed our PRI vendor, so to test the new one, our telco support enabled some access code so we would use it before migrating to the new PRI. [that is my guess] or I did something while cleaning some bugs in the system …buuuuuuuuuu
I will sooner or later find out what it was changed. I had it set to Exchange 2007 UM through a SIP trunk, so we would get rid of our 6500 voice mail system. Now with version 9.0 out our mitel 3300 will be able to do fax to Exchange UM too..so sooner or later, I will have to say bye, bye to 6500.
Oh by the way, for testing purposes, I enabled embedded vm just for my extension, since kwbMitel mentioned ‘that solution was designed for the Embedded voicemail not an Exchange UM.’ Same error ‘access denied’ I looked for documentation and found nothing about it either. .
I had Avaya before, and it was hard for me to let that system go, I grabbed to it with my nails!..LOL..but I learned to love Mitel, it is a pretty good system. It has his glitches but it is steady as rock so far.
I can tell you one thing about the Mitel, you will find many ways it doesn't work for you but it will almost never fail to do what you need to. Some of the guys on this forum are absolute geniuses when it comes to making things work.
back to the topic though. If you are saying that you get access denied when you try doing this to voice mail something is very wrong.
do you have your class of restriction group form populated. if so note what's where and deleting everything. then try again.
usually access denied (assuming it's displayed on the phone) has something to do with barring or the public access via dpnss not set to yes. you saying that you get the same message to embedded vm makes no sense.
check the dpnss setting on your SIP trunks and other trunks COS's too.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.