Polycom 3725-76302-001O manual Registration Policy Scripting, Noncompliant

Call Server Configuration

Field	Description
Allow site-less registrations	If this option is selected, endpoints that don’t belong to a configured site or
	territory can register with the Call Server. Otherwise, only endpoints in a
	subnet configured in the site topology can register.
When compliant	Select the action to take when the registration policy script returns
	COMPLIANT.
When noncompliant	Select the action to take when the registration policy script returns
	NONCOMPLIANT.
Policy Applies	Select whether to apply the registration policy script only to new registrations
	or also to changed re-registrations.
	If you choose the latter, you can optionally select Ignore IP and port
	changes so that the registration policy script is not applied if those are the
	only changes.
Registration policy compliance	Type (or paste) the registration policy script you want to apply. Then click
script	Debug this script to test the script with various variables.
	Click Reapply policy to run the script, applying any changes you’ve made to
	existing registered endpoints.
Inactive registration deletion days	Select to specify that endpoints whose status is Inactive (that is, their
	registrations have expired) are deleted from the system after the specified
	number of days.
	Some dial rule actions, such as Resolve to registered endpoint, can route
	calls to endpoints with an inactive registration. Deleting the registration record
	is the only way to prevent resolution to an inactive endpoint.

See also:

Call Server Configuration on page 233

Script Debugging Dialog Box for Registration Policy Scripts on page 268

Sample Registration Policy Scripts on page 268

Registration Policy Scripting

A registration policy script is an executable script, written in the Javascript language, that defines the criteria to be applied to registration requests in order to determine what to do with them. The script can specify any number of criteria, and they can be as broad or narrow as you want.

A script can return COMPLIANT or NONCOMPLIANT. The corresponding settings on the Registration Policy page let you specify what action to take for each of these return values.

A script can also assign a value (up to 1000 characters) to the EP_EXCEPTION variable. This variable’s initial value is blank (empty string). Assigning a non-blank value to it causes an exception to be recorded for the endpoint being processed. Exceptions appear on the Endpoints page, and you can search for endpoints with exceptions. See Endpoints on page 91.

Exceptions can serve a variety of purposes, from specifying the reason a registration was rejected to simply recording information about the request for future reference. For instance, you may want all endpoints to conform to a specific alias dial string pattern, but not want to quarantine those that don’t comply. Assigning

Polycom, Inc. 265