Technical information

Chapter 3 - Before You Deploy

If the local zone prefixes are configured, requests from neighbor

gatekeepers with prefixes that match the local zone prefix will be

resolved. All other calls will be rejected.

Entity Addressing

An entity must have a network address and may have alias

addresses. These are defined as follows:

❑ Network address: This address relates to network transport. It

is usually a TCP/IP address. This address can either be

automatically issues via dynamic host configuration protocol

(DHCP), or statically assigned by the administrator from a pool

of available addresses.

❑ Alias address: This may be a telephone number (private

number or public E.164 address) or an H.323 identifier, which is

an alphabetic string such as a username, email-like address, or

H.323 URL.

❑ LAN host name: Any system connected to a LAN must have a

LAN host name (netBIOS name) defined. This is sometimes

called the computer name.

An alias address may represent a terminal or it may represent a

conference. Alias addresses must be unique within a zone. For

example, within a zone there may only be one entity that uses the

alias 3721005.

Table 3-3. Zone Identifiers and Neighbor Gatekeepers

Prefix

Milpitas

gatekeeper

Austin

gatekeeper

Atlanta

gatekeeper

Local zone prefix 408 512 770

Neighbor gatekeeper 1 prefix 512 408 408

Neighbor gatekeeper 2 prefix 770 770 512