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 wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

3300 call reroute

Status
Not open for further replies.

cinter

Programmer
Jun 20, 2014
49
GB
Hi, I'm new here, but definately impressed by the knowledge displayed by you guys...

I'm having a problem with call rerouting: I want to pass a call from the external nubmer to pilot hunt group number 1280, whith an always reroute to extention 128382, then if no answer there to ring group 128105 (1st alt.) which includes a number of extentions who can all pick up the call.

Call rerouting seems to die at extention 128382, which just rings even though there is a call forward no answer 1st alternative set.

If I call 128382 directly, it reroutes after it's no answer timer perfectly! I've scoured the cos options, but all seems to be set right. Any tips?
Thanks in advance!
 
why not just do a speed call from the external number (I assume a DID/DDI to extension 128382? this will then re route 1st Alt to the ring group. Otherwise you may well have to mess about with second alternatives in call re route. If there is any vM involved then it becomes more difficult.
 
that's what i've done for now, but the question is also simply why it does not seem to be possible to reroute an rerouted call (does that make sense?)...
If I call the extention directly, it reroutes, but if I call a hunt group that forwards to that extentions it does not reroute. Is that just a standard Mitel anoyance?
 
Its how rerouting on the system works. Call rerouting will not follow another extensions rerouting. Each number can has two reroute points ( reroute 1 and reroute 2 ). If a call reroutes to another number and then would follow that numbers rerouting it would never use reroute #2. If you need this kind of "hopping" you need to use call forwarding. With call forwarding a forwared call from one device to another will then follow the forwarding on the second device.

An apple a day keeps the doctor away. Anyone else and you need to throw it harder.
 
@LoopyLou

You said "Call rerouting will not follow another extensions rerouting." - I Agree with this

Then You said "If a call reroutes to another number and then would follow that numbers rerouting it would never use reroute #2." - I do not agree with this unless this is supporting the first statement.

@cinter

All of the call rerouting needs to be set against the original called station
1280 always reroute to 128382 [highlight #FCE94F]AND[/highlight] 1st alt to 128105

**********************************************
What's most important is that you realise ... There is no spoon.
 
You can't reroute a reroute
Reroute 1st alternative, then Reroute second alternative, end.

Try reroute always alternate to HUNT group, RING group or ACD path to get the various options

NO GOOD DEED GOES UNPUNISHED!
 
Re: you can't reroute a reroute

It depends on how you mean that statement

Agreed, the destination of a reroute does not have any control but the originally dialed station can have up to 3 defined actions via reroute

Device can reroute as follows:
[ul]
[li]always to 1st destination[/li]
[li]to ist alternative after a ring no answer timer[/li]
[li]to 2nd alternative after the 2nd alternative timer[/li]
[/ul]

You can ring up to different 3 devices using rerouting.

**********************************************
What's most important is that you realise ... There is no spoon.
 
kwbMitel said:
All of the call rerouting needs to be set against the original called station
1280 always reroute to 128382 AND 1st alt to 128105

That would work great, but the user at 128382 wants to be able to turn a reroute to vm on and off with a button press, I added a DND button and reroute on busy, but the call stops there and gives a station busy/DND tone. If I use a call forwarding profile instead, the vm server sees extension 1820 coming in and doesn't send the call to the right mailbox...
 
You need to break the intergration on the system in this case using nametag hunt groups. Go to FAQ for instructions on how to do it. This will allow you drop the VM into the correct box.
 
Go to FAQ for instructions on how to do it"... [blush] where? excuse a nb
 
RE:Doesn't send the call to the right mailbox

Your setup assumes that 1280 is required for something but is appears it does not.

Instead of creating a station 1280 and routing to the next hop use a speedcall.

Speedcall 1280 would dial 128382.

128382 would then be the first termination point for the call and VM integration would follow it.

**********************************************
What's most important is that you realise ... There is no spoon.
 
OK, that's what I've done, and it works well.
Thanks for the help!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top