Show Posts
1
Mitel MiVoice Business/MCD/3300 / Conditional Forwarding?
« on: June 13, 2014, 04:02:05 PM »
We have a user that requested a forwarding profile that, while it seems to have been working for the past few months, has recently brought up a couple complaints. Let me first start by explaining what the user wanted in their own words:
“Please change the phone system so that when people are transferred to my extension (x124), it should do this in order of operations:
-ring Jane Doe’s extension first
-If Jane Doe doesn’t pick it up within 3 rings, it rings my extension.
-If after 3 rings on my extension no one picks up, it goes to my voicemail (triggering the email .wav message as it currently does).”
This is currently set up as follows (as done by a Mitel technician):
If someone calls extension 124, the extension is set to always forward to extension 167.
The issue that the users are reporting is that if someone calls either the main building number (xxx)xxx-xxxx, which goes to extension 167, or extension 167 itself, the calls are still being forwarded to extension 124 even though the call is not intended for that user. As far as we can tell, this is an unavoidable side-effect of the way the Mitel technician set up the forwarding due to extension 102 being the first call alternative of extension 167. Is there a way to fix this problem via something like a conditional forwarding option?
If 167 is called, do not forward. If 167 doesn’t pick up, send to 167 voicemail.
If (xxx)xxx-xxxx is called, forward to 167, then do not forward again. If 167 doesn’t pick up, send to 167 voicemail.
If 124 is called, always forward to 167. If 167 doesn’t pick up, forward call to 124. If 124 doesn’t pick up, send to 124 voicemail.
“Please change the phone system so that when people are transferred to my extension (x124), it should do this in order of operations:
-ring Jane Doe’s extension first
-If Jane Doe doesn’t pick it up within 3 rings, it rings my extension.
-If after 3 rings on my extension no one picks up, it goes to my voicemail (triggering the email .wav message as it currently does).”
This is currently set up as follows (as done by a Mitel technician):
If someone calls extension 124, the extension is set to always forward to extension 167.
- On extension 167, the first call alternative is set to “4,” which is set to be extension 102.
- Extension 102 is a number that is not in use on our system and only seems to exist in the “Call Rerouting” area.
- Though unsure of the exact method, extension 102 is somehow forwarding to extension 124
The issue that the users are reporting is that if someone calls either the main building number (xxx)xxx-xxxx, which goes to extension 167, or extension 167 itself, the calls are still being forwarded to extension 124 even though the call is not intended for that user. As far as we can tell, this is an unavoidable side-effect of the way the Mitel technician set up the forwarding due to extension 102 being the first call alternative of extension 167. Is there a way to fix this problem via something like a conditional forwarding option?
If 167 is called, do not forward. If 167 doesn’t pick up, send to 167 voicemail.
If (xxx)xxx-xxxx is called, forward to 167, then do not forward again. If 167 doesn’t pick up, send to 167 voicemail.
If 124 is called, always forward to 167. If 167 doesn’t pick up, forward call to 124. If 124 doesn’t pick up, send to 124 voicemail.