Entity Addressing; Table 3-3. Zone Identifiers And Neighbor Gatekeepers - Polycom SoundStation2 EX, FX, VS4000 Integrator's Reference Manual

Polycom integrators' reference manual for for viewstation ex, viewstation fx, and vs4000
Table of Contents

Advertisement

Prefix
Local zone prefix
Neighbor gatekeeper 1 prefix
Neighbor gatekeeper 2 prefix

Entity Addressing

© Polycom, Inc.

Table 3-3. Zone Identifiers and Neighbor Gatekeepers

Milpitas
gatekeeper
408
512
770
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.
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.
Chapter 3 - Before You Deploy
Austin
Atlanta
gatekeeper
gatekeeper
512
770
408
408
770
512
61

Advertisement

Table of Contents
loading

Table of Contents