Possibility for routing between Mitel nodes at WAN failure

[SpongeVoIP]

Following scenario:
- Headquarter with MXe, PSTN connected
- 30+ branches equipped with CXi's, local PSTN for breakout
- 500 users across all these locations BUT in normal state connected to the central MXe
- sites connected through WAN

Normal situation:
- all DDI (DNIS) traffic arriving at MXe and routed to the (direct connected) users on all locations -> so far so good

WAN failure:
- if WAN fails, all users on the branch location rehome to their local CXi

Question; in this situation we want to have the relevant DDI (DNIS) calls rerouted across the PSTN arriving at the local PSTN (ISDN2) of the CXi systems. Can this be setup? If so how? (NO XNET available)
Hope description is clear, if not please let me know.

Thanks

 

[kwbMitel]

What trunking, if any, is on the local cx's

Do you have sufficient trunking on the MXe to allow conferencing to the remote sites.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[SpongeVoIP]

The complete network is a cluster, so main office (MX) en CXi's are part of a cluster managed through Ent/OPS. IP trunking between all locations. But as said all users are connected to the MX in normal state and all DDI (DNIS) traffic is offered at the MX. Only in case of WAN failure users will rehome, and we need the DDI traffic from MX rerouted to the remote ISDN2 connections.

 

[kwbMitel]

I was asking if the remote sites had local trunking so that they can be called directly.

I also asked if the MX had enough trunks to allow inbound to outbound conferencing.

I do have a potential solution for you that does not use Xnet or IP trunks but I need to know the trunking and traffic situation.

Each call to a remote site would use 2 PSTN channels for voice at the MX and 1 at the remote site.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[kwbMitel]

I had to review my notes on this one.

I am assuming that you have sufficient trunking.

You set up DISA on the remote system

You set up a route to delete zero and dial the DISA number for each remote system.

You set up a list including your IP route as the first choice and the DISA route as your second choice.

If IP is down the system dials the DISA number and delivers the cluster code and extension same as over IP.

The call is conferenced thru the intitiating system.

On my systems I also included verified account codes on the DISA route for security and if you want that as well just ask.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[SpongeVoIP]

Thanks for the info up till now. Enough trunking indeed.
One key thing which I seem to miss.
In normal sitation the user at the branch office is directly reached by ARS translation, nut no IP trunk involved. How do I program the 2nd route, ie the route when the WAN fails so the PSTN route will be active?
More looking to where you program what.

Thanks

 

[kwbMitel]

Sorry, I missed the part where the phones register normally to the MXe so I was assuming calls to remote sites used clustering and IP Trunking.

This makes the situation very difficult indeed.

Because the phone's primary controller is local to the inbound DID I can't think of a simple way to trigger the failover to ARS as a secondary route.

Do we have the option of using one of the night service modes to re-route the station?

If so, I think I can make it work.

If not, I think you're out of luck.


*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitelpassion]

kwbmitel,

thanks. I think I could your DISA solution.