Polycom 7000 manual Registration Policy Scripting, Epdefinedincma

Call Server Configuration

See also:

Call Server Configuration

Script Debugging Dialog for Registration Policy Scripts

Sample Registration Policy Scripts

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.

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 an exception to non-compliant endpoints allows you to find them on the Endpoints page so that you can contact the owners.

Note: Registration policy scripting tips

When you click Update, a Javascript parser evaluates the registration policy script. If there is a syntax error in the script, an error message reports the problem and asks if you still want to update. You may do so in order to save a work in progress, but the script won’t be used until it’s valid. Note that the parser’s capabilities are limited and its error messages may not pinpoint the problem as clearly as you might like. More capable script testing services are available, such as JSLint.

We also encourage you to use Debug this script to test your script thoroughly with various dial strings and other parameters. See Script Debugging Dialog for Preliminaries/Postliminaries.

See Sample Registration Policy Scripts for some script examples.

The following table describes the other predefined variables you can use in a registration policy script. Each time the script runs, it gets the initial values for these variables from the registration request being processed. The script can evaluate a variable or change its value (the change isn’t preserved after the script completes).

Variable	Initial value
EP_DEFINED_IN_CMA	“TRUE” if the Polycom RealPresence DMA system is
	integrated with a RealPresence Resource Manager system
	and the endpoint is defined in that system.
EP_H323_DIALEDDIGITS_ALIAS	Endpoint alias value associated with H.323 dialedDigits or
	blank.
	This is an array that can contain multiple values. Separate the
	values with commas.
Polycom, Inc.	270