"Imagine that i have LAN connectivy on GW1 but i put on shutdown state the 3 E1lines..If a make a call and i have my GW1 the first priority on Rg.
The process is go to GW2 right?"
With h323 CM sends the call to the gateway. The gateway will respond with a cause code.
Depending on the CM version there is a CM service parameter that determines if CM continues hunting based on the cause code. In older versions there are parameters such as:
stop routing on user busy
stop routing on unalloacted number
stop routing on out of bandwidth
In newer versions there is a single advanced service parameter with open text field to specify stop routing conditions, "Stop Routing on Q.931 Disconnect Cause Code".
Depending on your specific gateway config and how the call is disconnected you can adjust these parameters so hunting continues.
Really the only way CM will NOT continue hunting is when media lock occurs. For h.323 this is typically associated with a proceeding, alerting, disconnect, or release_complete message that includes a progress indicator value that requests to cut through audio. Once media is locked to a gateway (or endpoint) CM still not hunt any further. There is an outstanding feature request to address this:
CSCsb22055 CCM shoudl reroute to next route list member after media established
"Out of bandwith" is determined by Call Adminissions Control mechanisms such as the Locations feature in CM or IOS Gatekeeper functionality. I doubt this would come into play for the scenariou you describe where a voice E1 is taken out of service.
Regarding "intercluster" I believe that is incorrect documentaiton on the service parameter. The parameters affect all calls routed via H.323. This includes H.323 endpoints, H.323 gateways, and Intercluster Trunks.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...