Polycom 7000 manual Embedded DNS, Edit Vertical Service Code Dialog

Call Server Configuration

See also:

Call Server Configuration

Prefix Service

Edit Vertical Service Code Dialog

The Edit Vertical Service Code dialog lets you edit a call forwarding or hunt group service invoked when callers dial the vertical service code (VSC) for that service followed by the alias. These services are included on the Prefix Service page and can’t be deleted. But you can disable them or change their names, descriptions, or VSCs (shown in the Prefix Range column of the Prefix Service page). If you change the VSCs, be sure to inform users of the change.

The following table describes the fields in the dialog.

Column

Type

Name

Code

Description

Enabled

Description

The type of service. Display only.

A display name for this service.

The vertical service code (VSC) for this service. Must consist of an asterisk/star (*) followed by two digits.

Registered endpoints can activate this feature by dialing the VSC followed by the alias. They can deactivate it by dialing the VSC alone.

Brief description of the service.

Clearing this check box lets you turn off the service.

See also:

Call Server Configuration

Prefix Service

Embedded DNS

In a superclustered configuration, the clusters that make up the supercluster automatically take over for each other in the event of an outage. In order to gain the full benefit of this feature, however, the endpoints that are registered to each cluster must re-register to a new cluster when the new cluster takes over.

This can be accomplished by specifying the gatekeeper or SIP proxy that each endpoint will register to as a site’s domain name, rather than an IP address. Then, when there is a failover, the DNS A record for that site’s domain name can be mapped to a different IP address, changing the Call Server that each endpoint is registered to.

The embedded DNS capability of the Polycom RealPresence DMA system automates this procedure.

Each Polycom RealPresence DMA server hosts its own embedded DNS server. It publishes a DNS CNAME record for each site. That CNAME record maps to the active cluster with which endpoints at the site should register. Whenever responsibility for the site moves from one cluster to another, the change is automatically published by the embedded DNS server. Endpoints will automatically re-register to the correct cluster.

Polycom, Inc. 278