Current Publication | x
Close

Registration Policies

In the RealPresence DMA system, you can configure multiple policies to control registration by endpoints. The system comes with two default registration policies. These can be used as-is or you can edit them. You can also define custom registration policies.

A registration policy must be assigned to all listening SIP and H.323 ports. When you initially install your system, the default registration policy that’s applied to ports is based on your system configuration – core or edge. You can keep your system’s default registration policy or you can create custom policies to fit your needs.

Each registration policy contains the following components:

Compliance policy: Includes an executable script (using the Javascript language) that specifies the criteria for determining whether an endpoint is compliant or non-compliant with the registration policy.

Admission policy: Specifies the action the system takes when an endpoint is compliant or non-compliant. You can choose from the following actions:

Ø Accept registration – The endpoint’s registration request is accepted and its status becomes Active.

Ø 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. The status remains unchanged until you manually unblock the endpoints.

Ø Quarantine registration – The endpoint’s registration request is accepted, but its status becomes Quarantined. It cannot make or receive calls. The system processes registration attempts (and unregistration attempts) from quarantined endpoints, but does not apply the registration policy. An endpoint’s status remains either Quarantined if registered or Quarantined (Inactive) if unregistered until you manually remove it from quarantine.

Ø 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. If the endpoint sends another registration request, the system applies the registration policy to that request.

Related Topics

Machine Translation

You are cautioned that the translation of this document is generated by a machine; therefore, the translated document may have errors and be inconsistent with the original English language version of the document.

The English language version of this document shall be considered the governing document related to the Polycom product.

If there is any contradiction between the English language version of the document and the translated version of the document, the English language version of the document shall take precedence.

The translation is provided for your convenience only. Neither Google nor Polycom shall be responsible for translated content or for the performance of the translation tool. If you require further assistance on non-translation issues, please contact Polycom support.

Translated documents are not available in PDF format.