Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Crazy Mitel Call flow
- Thread starter tommylux
- Start date
- Thread starter
- #2
- Thread starter
- #3
Hi
Yeah it will do beccause it's re-routed from path 2305 not interflowed. When re-routed it keeps the original dialled digits. When it's overflowed it doesn't and uses the new dialled digits.
For example you;ve got an interflow from path 2302 to path 2305. if you didn't then the call would actually go into mailbox 2302!
You can test this by breaking your system briefly and setting an interflow of 1 sec from 2305 to 2303 rather than a reroute and see what happens
Just a brief look and thought!
Yeah it will do beccause it's re-routed from path 2305 not interflowed. When re-routed it keeps the original dialled digits. When it's overflowed it doesn't and uses the new dialled digits.
For example you;ve got an interflow from path 2302 to path 2305. if you didn't then the call would actually go into mailbox 2302!
You can test this by breaking your system briefly and setting an interflow of 1 sec from 2305 to 2303 rather than a reroute and see what happens
Just a brief look and thought!
- Thread starter
- #6
Thanks for the quick reply.
I managed to fix this by adding another dummy path, See link:
This seems to work great apart from the annoying 3 rings before it goes through to the path (for internal calls)
Is there a better way to achieve the same results?
Thanks
I managed to fix this by adding another dummy path, See link:
This seems to work great apart from the annoying 3 rings before it goes through to the path (for internal calls)
Is there a better way to achieve the same results?
Thanks
- Thread starter
- #8
In the Call flow, you receive 1 ring when interflowing after 1 second from the first path 2302, 2nd ring when interflowing from path 2310 after 1 second (to remove digits for the call) 3rd ring when interflowing from the 2303 (Service message path) after 1 second then 4th ring when ringing for ACD Agents.
The ringing sounds funny because they are all cut off (when they get answered by the path)
Maybe if I put a dummy rad on the first path, from previous experience, this usually puts the call on MOH whilst ringing.
The ringing sounds funny because they are all cut off (when they get answered by the path)
Maybe if I put a dummy rad on the first path, from previous experience, this usually puts the call on MOH whilst ringing.
- Thread starter
- #10
Early release 8. I Think on the latest release they decided to change how the vm chooses the mailbox extension. eg, the first DN rather than the last DN in a call flow.
Example:
Person A has Voicemail, Person B doesnt.
Person B diverts to Person A and when Person A doesnt answer,
Before: the call goes through to Person A's Voicemail.
Release 8: the call goes to a VM port, saying "please enter the extension of the person you wish to contact"
Personally, I liked the original method.
Could someone confirm that it used to work like this? or have I got my wires mixed up?
Example:
Person A has Voicemail, Person B doesnt.
Person B diverts to Person A and when Person A doesnt answer,
Before: the call goes through to Person A's Voicemail.
Release 8: the call goes to a VM port, saying "please enter the extension of the person you wish to contact"
Personally, I liked the original method.
Could someone confirm that it used to work like this? or have I got my wires mixed up?
Mitel has always integrated with the original called party. You are not remembering correctly.
Couple of suggestions:
Get rid of the favouritism for the interal callers and give them the same spiel for "your call may be recorded". If it's good enough for the customers why should internal callers get special treatment.
Move the decision point for emergency routing right to the front and control it by the 6160 emergency routing. activates from the 6160 web page with a click of the mouse and removes an entire tier of complex routing.
I notice that voicemail is only accessed when a caller chooses to dial out of queue. This will accomplish the same purpose of breaking the integration if you route the call to a phantom local that integrates with voicemail.
The suggestions above would greatly reduce the complexity of your call flow. (Not Crazy anymore)
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
Couple of suggestions:
Get rid of the favouritism for the interal callers and give them the same spiel for "your call may be recorded". If it's good enough for the customers why should internal callers get special treatment.
Move the decision point for emergency routing right to the front and control it by the 6160 emergency routing. activates from the 6160 web page with a click of the mouse and removes an entire tier of complex routing.
I notice that voicemail is only accessed when a caller chooses to dial out of queue. This will accomplish the same purpose of breaking the integration if you route the call to a phantom local that integrates with voicemail.
The suggestions above would greatly reduce the complexity of your call flow. (Not Crazy anymore)
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
- Thread starter
- #12
Were doing all this without a 6160, Our company decided not to buy this product, although we have 6100 and 6150.
Its a shame cause I think the 6150 would save a bit of time.
It was nice not to play the message internally, especially as calls can only be recorded on trunks (third party solution)
Its a shame cause I think the 6150 would save a bit of time.
It was nice not to play the message internally, especially as calls can only be recorded on trunks (third party solution)
The first stage Path 2302 managed by 6100.
Does this mean you have the 6115 interactive call control?
Assuming this is the case:
I would still remove the Internal Flow Decider and instead allow callers to "Accept" the calls may be recorded with a dial out of queue route to 2303. Again this treats everybody equally, and gives the benefit to repeat outside callers to "Accept" (Skip) the message. Your wording could include something to the affect as "Dial X or wait to accept"
I don't see anywhere else to simplify.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
Does this mean you have the 6115 interactive call control?
Assuming this is the case:
I would still remove the Internal Flow Decider and instead allow callers to "Accept" the calls may be recorded with a dial out of queue route to 2303. Again this treats everybody equally, and gives the benefit to repeat outside callers to "Accept" (Skip) the message. Your wording could include something to the affect as "Dial X or wait to accept"
I don't see anywhere else to simplify.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
- Thread starter
- #14
- Status