Hey folks,
Got a scenario here that I'm fairly sure isnt correct, but thought I'd each out to the community for some opinions. It concerns how 2nd alternativ eshould behave. So the scenario is as follows:
We have 3 Mitel 3300 controllers in play here: 3300 A (Calling party 3300), B (Called Party 3300) & C (Nupoint gateway 3300). We also have 3 extensions in play. Calling party extension 1 (on 3300 A), called party extension 2 and ext 2's 1st alternative extension 3 (on 3300 B).
Call originates from Extension 1 on 3300 A, ringing on Extension 2 on 3300 B. 2 doesn't answer, so the call correctly reroutes to extension 3 where it also rings out. Now here's where it gets weird. 2nd alternative is the VM hunt group on 3300 C, the pilot number of which is n both 3300 A & B as a remote DN and is dialable from all 3 3300 systems. When the call has gone unanswered on ext 3 on 3300 B, rather than 3300 B placing the call to the Vm hunt group, it sends the digits BACK to 3300 A, where the call to the 2nd alternative VM hunt group is then placed directly to 3000 C from 3300 A and NOT 3300 B as I would expect. After all, the 2nd alternative is referenced on 3300 B as part of extension 2's call rerouting.
Surely the call flow should be:
Call from 3300 A lands on 3300 B, goes unanswered on both extensions, call is then placed from 3300 B to the 2nd alt destination which is on 3300 C.
Any ideas?
Got a scenario here that I'm fairly sure isnt correct, but thought I'd each out to the community for some opinions. It concerns how 2nd alternativ eshould behave. So the scenario is as follows:
We have 3 Mitel 3300 controllers in play here: 3300 A (Calling party 3300), B (Called Party 3300) & C (Nupoint gateway 3300). We also have 3 extensions in play. Calling party extension 1 (on 3300 A), called party extension 2 and ext 2's 1st alternative extension 3 (on 3300 B).
Call originates from Extension 1 on 3300 A, ringing on Extension 2 on 3300 B. 2 doesn't answer, so the call correctly reroutes to extension 3 where it also rings out. Now here's where it gets weird. 2nd alternative is the VM hunt group on 3300 C, the pilot number of which is n both 3300 A & B as a remote DN and is dialable from all 3 3300 systems. When the call has gone unanswered on ext 3 on 3300 B, rather than 3300 B placing the call to the Vm hunt group, it sends the digits BACK to 3300 A, where the call to the 2nd alternative VM hunt group is then placed directly to 3000 C from 3300 A and NOT 3300 B as I would expect. After all, the 2nd alternative is referenced on 3300 B as part of extension 2's call rerouting.
Surely the call flow should be:
Call from 3300 A lands on 3300 B, goes unanswered on both extensions, call is then placed from 3300 B to the 2nd alt destination which is on 3300 C.
Any ideas?