Call Server Configuration
Polycom, Inc. 261
See also:
Hunt Groups on page 258
Add Hunt Group Dialog Box on page 259
Edit Hunt Group Dialog Box on page 260
Edit Alias Dialog Box
The Edit Alias dialog box lets you change an alias value assigned to the hunt group. Edit the alias in the
Value box and click OK.
Aliases should be specified by their fully qualified dial string. For example, to specify that H.323 callers can
call the hunt group by dialing 1234, enter 1234. To specify that SIP callers can call the hunt group by dialing
1234, enter sip:1234@mydomain.com.
See also:
Hunt Groups on page 258
Add Hunt Group Dialog Box on page 259
Edit Hunt Group Dialog Box on page 260
Device Authentication
Device authentication enhances security by requiring devices registering with or calling the Polycom
RealPresence DMA system to provide credentials that the system can authenticate. In turn, the Polycom
RealPresence DMA system may need to authenticate itself to an external SIP peer or gatekeeper.
All authentication configurations are supercluster-wide, but note that the default realm for SIP device
authentication is the cluster’s domain as specified on the Admin > Local Cluster > Network Settings page
(or sip.dma if no domain is specified). This allows each cluster in a supercluster to have its own realm for
challenges.
The Device Authentication page has two tabs, Inbound Authentication and Shared Outbound
Authentication.
Inbound Authentication
On the Inbound Authentication tab, you can:
● Configure specific SIP digest authentication settings for SIP devices.
● Maintain the Call Server’s local inbound device authentication list. This list is used for both H.235
authentication (H.323 devices) and SIP digest authentication (SIP devices).
● Click the Signaling settings link to go to the Signaling Settings page, where you actually enable
device authentication for H.323, SIP, or both (see Signaling Settings).
Shared Outbound Authentication
On the Shared Outbound Authentication tab, you can maintain the Call Server’s general list of
authentication credentials, which it uses to authenticate itself on behalf of calling devices to external SIP
peers for which the appropriate device-specific credentials haven’t been defined.