calls failing to backup G450 gateway?

[avayaaacc]

I was hoping someone might be able to explain call routing across multiple t1s/media gateways to me.

Some testing was recently done where each gateway was brought offline separately. The hope or expecation was that calls intended for the down gateway would start landing on the online gateway.

For instance, a toll free number usually comes in on trunk 1 on gateway 1. Since gateway 1 was shut down, we hoped to see calls for the toll free number come in on gateway 2. However, calls would return an "all circuits are busy message".


this lead us to look at the route patterns and incoming call treatments. The route patterns for each trunk seem to be the same, but I did notice that the incoming call treatments for the trunks on different gateways did not have the same numbers configured (such as the toll free referenced above).

I was suspecitng this may be the reason for the failure, but was hoping someone could confirm that, and also provide a little more detail on how the system handles calls via route patterns vs the incoming treatment plans, or any other routing analysis not considered

 

[joe2938]

Only the line provider can set this up so it is a out of service redirect, and you would need to set this up ahead of time with them

 

[avayaaacc]

thanks joe, would this also need to be done for non toll free numbers as well? Additionally, does this really need to be done via incoming call treatments as well, or is that unneccessary?
and finally, can you elaborate on why this would need to be setup ahead of time? Would it cause an outage if they added this redirect to the other circuit(s)?

 

[joe2938]

because you can not control calls to a gateway that is out of service, inc tables can steer calls when a gateway is in service, and yes for all calls. No it only comes into play when it can not route a call to a gateway so an out os service redirect by the line provider can do this