Polycom 3725-76302-001O Microscope & Magnifier User Manual


 
Call Server Configuration
Polycom, Inc. 264
See also:
Device Authentication on page 261
Registration Policy
On the Registration Policy page, you can specify policies to control registration by endpoints. To do so,
you define the following:
Compliance policy: Write an executable script (using the Javascript language) that specifies the
criteria for determining whether an endpoint is compliant or noncompliant with the registration policy.
Admission policy: Select the action to be taken when an endpoint is compliant, and the action to be
taken when an endpoint is noncompliant.
The actions that may be taken are:
Accept registration — The endpoint’s registration request is accepted and its status becomes
Active (see Endpoints for more information about endpoint status values).
Block registration — The endpoint’s registration request is rejected and its status becomes
Blocked. The system automatically rejects registration attempts (and unregistration attempts)
from blocked endpoints without applying the registration policy. Their status remains unchanged
until you manually unblock them.
Reject registration — The endpoint’s registration request is rejected and its status remains not
registered. It doesn’t appear in the Endpoints list. Whether it can make and receive calls depends
on the system’s rogue call policy (see Call Server Settings on page 234). If the endpoint sends
another registration request, the registration policy is applied to that request.
Quarantine registration — The endpoint’s registration request is accepted, but its status becomes
Quarantined. It can’t make or receive calls. The system processes registration attempts (and
unregistration attempts) from quarantined endpoints, but doesn’t apply the registration policy.
Their status remains either Quarantined if registered or Quarantined (Inactive) if unregistered until
you manually remove them from quarantine.
You can also specify whether the policy is to be applied only to new registrations, or also to re-registrations
with changed properties.
The following table describes the fields on the page.
Field Description
Device Authentication
Name The name that the device includes in registration and signaling requests or
responses to authentication challenges.
Note: The name and password for a device are whatever values the person
who configured it specified. They don’t uniquely identify a specific device;
multiple devices can have the same name and password.
Password
Confirm password
The password that the device includes in registration and signaling requests
or responses to authentication challenges.