Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: rebeccafox on July 15, 2008, 07:21:01 AM
-
I wonder if anyone can help me
We have a Mitel 3300 controller and 5224 IP Phones.
All ou users use the call forward - follow me feature access code to forward all their calls to voicemail, mobile or assistant straight from their phone.
This has worked brilliantly but we have discovered a problem in that when the phone is forwarded to mobile, the controller rings the mobile and if it gets a busy or no answer signal, it puts the call back to the voicemail on the office phone. This is obviously not ideal and what we need is for the controller to pass the call to the mobile and it to either ring until the caller hangs up or for it to go to voicemail on the mobile.
Anyone have any ideas how to achieve this.
Thanks
-
This is actually a feature most people want. (I know, I know, it's hard to believe...)
What is actually happening is the Mitel is waiting for answer supervision. If it doesn't get it then it follows the forwarding of the phone that was called.
A couple of ways around this. Send the calls out loop start trunks. These trunks will not provide answer supervision so the call will do as you asked. This means you have to have loops start analog trunks in the system and special routing will have to be made to route those types of calls out those lines - not simple if you don't work on these lines normally.
Secondly, in the COS of the trunks and phone, set the call forwarding timer to be longer than the time it takes the cell phone vm to answer. Then when you get the cell phone VM you have answer supervision and the call won't be pulled back. You may have to lengthen the system reroute timer in the system options form (this will apply to the second alternative routing). You also may have to remove all call rerouting and use the feature codes to forward Busy/RNA to internal vm if you're going to use that.
Hope that helps.
Ralph
www.Nortelphones.biz
-
Before you try that in the class of service of your PRI try changing "supress simulated CCM after ISDN progress" and see what happens.
-
Before you try that in the class of service of your PRI try changing "supress simulated CCM after ISDN progress" and see what happens.
Oooo.... Didn't know that one. Thats what happens when you're out of the field for so long.
Thanks
Ralph
-
thanks v2win - i have tried that and will do some testing. i'm assuming i need to change it to yes - as it is currently on no.
thanks ralph aswell - appreciate you guys responding so fast
-
Did this end up fixing your problem?
I have another thing you can try if it didn't fix the problem.
-
I have another thing you can try if it didn't fix the problem.
v2win,
I actually stumbled into this issue just this AM. Tried the CCM Suppression. Didn't work.
What is your other solution?
Ralph
-
Holy revived threads batman! Just wanted to thank V2Win on this one. I would have never thought to flip that bit to fix this problem.
-Chak
-
I spoke too soon - user had disabled call forwarding right as I did the test. Then when they answer their desk, I thought I had them on their cell.
Now I'm grasping at straws on this one - any ideas out there?
-Chak
-
Chak,
Under ISDN protocol look for "Replace External CLID" and set to false.
Ralph
-
No love - couldn't find that setting, but this system is running version 7. I just learned that they took advantage of the SA re-enlistment offer so am looking at upgrading. At this point I suspect a bug....
-Chak
-
What I've done in these types of cases is to open a ticket with the carrier and ask them what they see when it fails.
That at least points me in the right direction.
Ralph