Re: Difference between tech-prefix and zone prefix
You must have tech prefixes of some sort defined within the gatekeeper in order for calls to complete (unless all E164 addresses are registered with the gatekeeper). Upon receipt of an ARQ, the gatekeeper will first look to see if a tech-prefix is prepended to the E164 address. Typically this is not the case, then the gatekeeper will look to match a local zone. If there is a local zone then the gatekeeper will look to see if the destination E164 address is registered (once again, this is typically not the case). Then the gatekeeper will look to see if there are endpoints that are registered with default technology. This is seen with the show gatekeeper gw-type-prefix on the gatekeeper. If there are endpoints that are registered with the default tech prefix then it will round robin between gateways that are registered with this gatekeeper.
So the short answer to your question is that some sort of tech prefix is needed unless the E164 are registered.
The easiest config is to make each endpoint register to its own zone. Then have each endpoint register with the same default technology prefix. Once this is done, you use the zone prefix command to indicate to the gatekeeper which gateway can terminate a particular range of E164's.
zone local GW1 cisco.com
zone local GW2 cisco.com
gw-type-prefix 1# default-technology
zone prefix GW1 1*
zone prefix GW2 2*
You are now telling the gatekeeper to route any destination E164 that starts with a 1 to GW1 and any E164 address starting with a 2 to GW2.
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...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.