Configure Sip Settings For Integration With Microsoft Servers - Polycom RealPresence Group 550 Administrator's Manual

Realpresence group series video conferencing system
Hide thumbs Also See for RealPresence Group 550:
Table of Contents

Advertisement

Administrator's Guide for the Polycom RealPresence Group Series
Setting
Registrar Server
Proxy Server
For more information about this and other Microsoft/Polycom interoperability considerations, refer to the
Polycom Unified Communications Deployment Guide for Microsoft Environments.
Points to note about SIP:
The SIP protocol has been widely adapted for voice over IP communications and basic video
conferencing; however, many of the video conferencing capabilities are not yet standardized. Many
capabilities also depend on the SIP server.
The following are examples of features that are not supported using SIP:
Cascaded multipoint in SIP calls.
Meeting passwords. If you set a meeting password, SIP endpoints will be unable to dial in to a
multipoint call.
For more information about SIP compatibility issues, refer to the Release Notes for Polycom
RealPresence

Configure SIP Settings for Integration with Microsoft Servers

Integration with Microsoft Lync Server 2010 and 2013 allows Microsoft Lync and Polycom RealPresence
Group system users to place audio and video calls to each other.
Because Polycom RealPresence Group systems run in dynamic management mode, they cannot be
simultaneously registered with Lync Server and the presence service provided by the Polycom
Converged Management Service (CMA) or Polycom RealPresence Resource Manager system.
RealPresence Group systems can obtain presence services from only one source: Lync Server, or the
presence service provided by the CMA or RealPresence Resource Manager system.
Polycom, Inc.
Description
Specifies the IP address or DNS name of the SIP Registrar Server. The address can be
specified as either an IP address or a DNS fully qualified domain name (FQDN). If
registering a remote RealPresence Group System with an Lync Server Edge Server,
use the FQDN of the edge server.
By default for TCP, the SIP signaling is sent to port 5060 on the registrar server. By
default for TLS, the SIP signaling is sent to port 5061 on the registrar server.
Enter the address and port using the following format:
<IP_Address>:<Port>
<IP_Address> can be an IPv4 or IPv6 address, or a DNS FQDN such as
servername.company.com:6050.
Syntax Examples:
To use the default port for the protocol you have selected:
10.11.12.13
To specify a different TCP or UDP port:
10.11.12.13:5071
Specifies the DNS FQDN or IP address of the SIP Proxy Server. If you leave this field
blank, the address of the Registrar Server is used. If you leave both the SIP Registrar
Server and Proxy Server fields blank, no Proxy Server is used.
By default for TCP, the SIP signaling is sent to port 5060 on the proxy server. By default
for TLS, the SIP signaling is sent to port 5061 on the proxy server.
The syntax used for this field is the same as for the Registrar Server field.
®
Group Systems.
Networks
®
40

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents