Working With Several Gatekeepers - RADVision L2W-323 User Manual

Overview
Service Access Control
You can control the access to services by defining them as Public, Default or both. The
availability of a service to an endpoint depends on the origin of the endpoint requesting the
call and the type of endpoint registration.
Public services are available to:
!" Service requests originating within the zone, if the endpoint requesting the service is
predefined and is allowed to use this service.
!" Service requests originating outside the zone. For example, a call originating in an
endpoint registered with another Gatekeeper on the network can access all services
defined as Public.
Default services are available to:
!" All endpoints within the zone, unless the endpoint is predefined with this service
disabled.
Public and Default services are available to:
!" All endpoints within or outside the zone, unless the endpoint is predefined with this
service disabled.

Working with Several Gatekeepers

The internal Gatekeeper can operate with other Gatekeepers in the H.323 network if you
configure it to recognize the Gatekeepers of other zones. This is achieved by creating a table
listing all other Gatekeepers in the network that the current Gatekeeper can access through
IP unicast. These Gatekeepers are Neighbor Gatekeepers of the current Gatekeeper. When a
call is directed to another zone, the Gatekeeper uses Neighbor Gatekeepers to resolve the
call request.
Neighbor Gatekeepers
Neighbor Gatekeepers are identified by their IP addresses. You can control dialing between
zones by defining neighbor prefixes. Neighbor prefixes should correspond with the zone
prefixes you defined for these Gatekeepers. For example, if you define a zone prefix of 02
for Gatekeeper A, Gatekeeper B can only reach Gatekeeper A if you have defined
Gatekeeper A as a neighbor Gatekeeper with a prefix of 02. You only need to define
neighbor prefixes when you have defined a zone prefix for this Gatekeeper.
2-20