How MSDN behave when ARS Lists

[danramirez]

Guys,

I am reprograming four 3300s that were supposed to be initially programmed as in cluster.

All running MCD 4.2, two of the PBXs are ISS Servers where all IP phones are registered, the other two are MXe´s with additional E2Ts, Echo Cancellers, DSPs, etc.

Trunks from two different providers are connected to each MXe, i.e. 1E1 from Provider A, and 1E1 from provider B are connected to MXe A, also 1E1 from Provider A, and 1E1 from Provider B are connected to MXe B.

Let´s concentrate on the 2 MXe´s and one of the ISSs.

Note that I have an ARS list on ISS which have a 1st alternative to MXe A, and a second alternative to MXe B.

But also, on MXe A, I have a list, that if trunk group from provider A is Busy, it will follow to trunk group from provider B.

The question is: if trunk group A connected to MXe A is busy or out of service, and someone on ISS tries to place a call to the outside, what will MSDN do?.

- Option A. Will the call follow second alternative from ARS on ISS and end up in MXe B
- Option B. Will the call arrive at MXe A and take second alternative on its ARS list?

Please let me know if I haven´t made myself clear enough with discribing this.

Regards,

Daniel

 

[kwbMitel]

MXe A - All IP Trunks Busy or MXe A OOS
Call will proceed to 2nd route defined in list on ISS
Call Routes from ISS to MXe B to PSTN

MXe A - All PSTN trunks Busy
Call will proceed to 2nd route defined in list on MXe A
Call Routes from ISS to MXe A to MXe B to PSTN

**********************************************
What's most important is that you realise ... There is no spoon.