I am trying to understand the usage of the alias command. I have two CMs and H323 ATA registered to the gatekeeper. I don't want to use tech-prefixes and I want gatekeeper to make all of its routing decisions based on the registered E164IDs. As CM does not register the E164 #s , I configured the following alias entry but it does not seem to work. Can somebody enlighten me about the usage of this command ? Thanks
zone local home cisco.com
zone local office cisco.com
alias static 172.25.3.102 1720 gkid office gateway voip ras 172.25.3.102 1719 e164 3903
no use-proxy office default inbound-to terminal
no use-proxy office default outbound-from terminal
Router#sh gatekeeper endpoints
GATEKEEPER ENDPOINT REGISTRATION
CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags
I suspect the problem is not with the alias statement but rather with anonymous device support in CCM.
Alias statements provide the simplest form of RAS. They tell the GK to return a specific IP when a particular e164 is ARQed. No tech prefix is required, and default tech prefixes are not used in matching the e164. However, aliases _do_not_ depend on a endpoint be registered. Indeed, aliases are ideal for situations where an endpoint doesn't support ras. So there is no call state maintained in the GK.
I believe you are seeing the failure of Anonymous Device support in CCM. CCM will not accept h225 call setups from devices it is not aware of. There are three ways to get the CCM to accept a call from an h323 endpoint:
1) Configure the device in CCM as a h323 gateway. When a new CS from a h323 endpoint arrives, CCM compares the source IP address against those configured as gateways. If the IP is unknown, it will
2) ARQ its GK controlled trunks. If a GK responds with an ACF, then CCM will accept the call. If it receives an ARJ, or there are no GK controlled trunks, CCM will reject the Call. Also, since aliases don't require the GK to maintain call state information,
3) You may override this behavior in CallManager Service parameters by setting "Accept Unknown TCP Connection" to true. This is not a good idea as it could open you up to toll fraud.
IOS upgrade on asr9xx mandates rommon upgrades sometimes while they can be optional at other times. You may land up in unwanted situation if proper procedure is not followed during upgrades.
This article will include complete details about rommon ...
In some situation NCS560 RP become unresponsive after reload or powercycle.
In many deployments NCS560 far edge, deployment is large and human intervention should be kept at minimum
Engineering team have been working on a strategy to have functi...
In simple terms, 'Route Churn' is defined as the 'rate of change of prefixes'. Different XR versions across 4.x to 7.x have differing behavior & support for the BGP churn handling and some enhancements made from 6.5.3 onwards (listed in appendix) mak...
Prior to Cisco IOS XR Software Release 7.1.2, XR dual RP devices did not support file mirroring from active RP to standby RP. Administrators had to manually perform the task or use EEM scripts to sync files across active RP and stand...
Hi Everyone, Would like to extend my thanks in advance for anyone offering assistance. As the subject hints, anyone here know of a way to convert IOS configs to XR config? I seen and heard about SOX tool but i am unable to find it. I also tried ...