Changing Disconnect cause on H.323 gateway in cas of ISDN failure
We're running CUCM 7.1.2 and H.323 Gateways in each office. We are already using the HQ Gateway as backup in case of an ISDN failure in a remote office. By default the H.323 Gateways are sending the disconnect cause of "1" (Hex 81, unallocated or unassigned number, see debug below) in case of an ISDN Port failure.
Is there a command to change the disconnect cause (the H.323 one, not the ISDN disconnect cause) to something more accurate like Hex A1 "circuit out of order" or Hex A6 "network out of order"?
I don't want to map disconnect causes, I really only like to change the disconnect cause when the ISDN interface is down because "unallocated or unassigned number" seems to be wrong in my opinion. Usually when an "unallocated or unassigned number" is received via ISDN there is no need to hunt to the next gateway because it will also receive "unallocated or unassigned number".
Anyway, you helped me again and maybe you'll find some other (maybe hidden command).
Re: Changing Disconnect cause on H.323 gateway in cas of ISDN fa
You're my H.323 gateway hero ;-)
With the "no dial-peer outbound status-check pots" the gateway sends a "Requested channel not available" (44, Hex AC) back to the CUCM when the ISDN interface is down. Which seems to be more appropriate to me.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...