RADVision L2W-323, User Manual

Page: 135 / 253

Zone Definition
6-15
2. Select the service you do not want this endpoint to use and click the Enable/Disable
toggle button.
3. Click OK to confirm and return to the Predefined Properties screen. You have finished
predefining this endpoint. Predefine other endpoints or exit the Zone Definition Table
by clicking
OK .
Note: When the Zone Definition Table screen is open, endpoints cannot register
dynamically with the Gatekeeper. Exit the Zone Definition Table screen to allow new
registrations.
Predefining Endpoints in a Dynamic IP Environment
The Gatekeeper allows you to work in a dynamic IP mode. In a dynamic IP mode the
endpoint does not have a fixed IP address, and the Gatekeeper identifies the endpoint
according to its aliases. To work in a dynamic IP environment you have to select the
Dynamic IP Environment check box in the Network Control screen. Even if a dynamic IP
environment does not govern your network, you can benefit from this feature and allow
users to migrate between workstations. Since the Gatekeeper will identify the endpoint by
alias and not IP address, users can switch workstations without worrying about not receiving
their calls. See “Registration Policy Parameters,” page 6-29 for details about working in a
dynamic IP environment.
#"
To predefine an endpoint in a dynamic IP environment
1. In the Configuration Source screen click Gatekeeper Setup . The Gatekeeper
Application Parameters screen is displayed.
2. In the Application Parameters screen click Network Control . The Network Control
screen is displayed.
3. Select the Dynamic IP Environment check box. Click OK .
4. In the Application Parameters screen click Zone Definition . The Zone Definition
Table screen is displayed.
5. Click Add . The Predefined Properties screen is displayed. Follow the steps as for
“Defining the Properties of a New Endpoint , ” page 6-13 with the following exceptions:
!"
Enter any number in the IP Registration field.
!"
Define at least one unique terminal ID or phone number.
Note: If this endpoint can dynamically register with the Gatekeeper, at least one of the
aliases you define should correspond to one of the online aliases. Otherwise, the
Gatekeeper cannot match the predefined properties to the endpoint.