Accepted Solutions
The SBC would report to the CM that it failed to route the call and based on this the route group logic would kick in and route the call via the second option in the RG. If you do not see that you would likely have to modify service parameters to get the CM to do this. I can look up the parameters once I’m in front of a CM.
This information would not be passed from the "E" to "I" trunk. If you have independent setup routers that act as a SBC for each of your trunks to your service provider you have a few options at hand. If you have these defined as trunks in CM and put them into a route group with Top Down routing algorithm it would always first try the SBC that is first in the list. If that fails because of the E trunk is marked as down the hunting distribution in the route group will try the next in list. This is often quite enough as the added time for the call setup is usually not relevant.
If you really want to get the I trunk to also go down you could be inventive and write a EEM script that runs on the router to check if it has reach ability to the service provider and if it doesn't shutdown the inbound dial peer that is used for the connection from CM. That would indicate the trunk to be down in CM as it to can be setup to use SIP option ping.
The SBC would report to the CM that it failed to route the call and based on this the route group logic would kick in and route the call via the second option in the RG. If you do not see that you would likely have to modify service parameters to get the CM to do this. I can look up the parameters once I’m in front of a CM.
