Re: health check to remote dial-peer on voice gateway
you have several workarounds:
1. If you change your call routing mode not to be direct "GW-GW signalling", but "gatekeeper routed signalling", then both Pod-A and Pod-B must be registered to a gatekeeper. If the Ethernet interface of Pod-B goes down, then it will be un-registered from the H.323 gatekeeper. And if at this time Pod-A sends a call for Pod-B, then it will be sent through the gatekeeper. The gatekeeper knows that the call can not be routed to Pod-B, because it is disconnected (not registered) and will either return a disconnect reason to Pod-A (+ARJ --> Admission Reject), or will try to route the call to another registered gateway/endpoint if its destination prefix matches the call number :)
2. I suppose that you want to know that the remote gateway is down, so to be able to route the call at Pod-A to another location (another voice gateway, or PSTN). In this case, just configure another dial-peer matching the same call pattern, but with higher preference (lower priority). Pod-A will try to place a call to Pod-B, if Pod-B does not reply to the H.323 Q.931 SETUP, then Pod-A will try to route the call to the secondary dial-peer.
1. Introduction Internet security is important with the increasing
attacks that are happening every day. Many internet and browsing
security solutions exist, but some are not very easy to use or maybe the
question is how can I enable them? In this referen...
Cisco Software Manager Server API Guide This document describes the
programmatic interfaces, RESTful APIs, which are supported by Cisco
Software Manager Server (CSM Server). Overview CSM Server supports a set
of finite RESTful APIs. The first step to use ...
If you are using Cisco's new linux-based Cisco Software Manager server,
then you probably want to make sure there is a startup service for
it.I'll assume that you've already installed the CSM server on a
systemd-based linux system. The commands given belo...