I am solving a subsequent problem. I have a H323GW connected to the CUCM 6.1.5. H323 GW has one E1 voice interface.
CUCM has three GWs in the route group.
If the E1 interface is down, GW returns release message with the release cause 1 (unallocated number) back to the cluster and cluster does NOT perform the reselect to the next gateway in the list. Do you have any idea how to force GW to send a different release cause in that particular case?
I have tried application map in order to re-map the release cause to the different one, but it seems that the mapping works the general way, so if the E1 interface is up and called number really does not exist, we have a problem. I have also tried to set the service parameter Stop Routing on Unallocated Number Flag to TRUE in the CUCMs config, but if I will do that the problem is similar in case the called number really does not exist.
Could you help me with this issue?
My best regards,