Register a System with Skype for Business

When you register a RealPresence Group Series system with a Skype for Business Server, users can see a list of Skype for Business contacts to call and whether contacts are online. They can display up to five contacts on the home screen.

The H.263 codec has been deprecated and a Skype for Business Interoperability License is required for integration with Skype for Business Server.

Procedure

  1. Open a browser window and enter the system IP address or host name in the Address field.
  2. Go to Admin Settings > Network > IP Network and select SIP.
  3. Configure the following SIP settings for your Skype for Business environment.
SettingDescription
Enable SIPSelect to enable the system to make and receive SIP calls.
SIP Server ConfigurationSelect Auto if your Skype for Business Server configuration is set up for automatic discovery, which requires you to correctly configure Skype for Business SRV records. If the Skype for Business Server is not configured for automatic discovery, select Specify.
Transport ProtocolThe SIP network infrastructure in which your RealPresence Group Series system is operating determines the required protocol.
  • Auto enables an automatic negotiation of protocols in the following order: TLS, TCP, and User Datagram Protocol (UDP). This is the recommended setting for Microsoft environments.
  • TLS provides secure communication of the SIP signaling. TLS is available only when the system is registered with a SIP server that supports TLS. When you choose this setting, the system ignores TCP/UDP port 5060. TLS is required when connecting to Skype for Business.
  • TCP provides transport via TCP for SIP signaling and is not applicable for Skype for Business. Signaling encryption is mandatory.
  • UDP provides transport via UDP for SIP signaling.
Force Connection ReuseThis setting is disabled by default (recommended). When disabled, it causes the system to use an ephemeral source port for all outgoing SIP messages. When enabled, it causes the system to use the active SIP listening port as the source port (5060 or 5061, depending on the negotiated SIP transport protocol in use). This can be useful to establish correct operation with remote SIP peer devices, which require that the source port match the contact port in SIP messages.
BFCP Transport PreferenceControls the negotiation behavior for content sharing using the Binary Floor Control Protocol (BFCP). Establishes the relationship between the floor control server and its clients, while the available settings determine how network traffic flows between the server and clients.

TCP is typically known as the older, slightly slower, and more reliable method, but is not supported under some circumstances, such as with session border controllers (SBCs).

  • Prefer UDP—Starts resource sharing using UDP but falls back to TCP if needed. This is the default value when SIP is enabled.
  • Prefer TCP—Starts resource sharing using TCP but falls back to UDP if needed.
  • UDP Only—Shares resources only through UDP. If UDP is unavailable, content sharing in a separate video stream is not available.
  • TCP Only—Shares resources only through TCP. If TCP is unavailable, content sharing in a separate video stream is not available.
Sign-in AddressSpecifies the system's SIP name. This is the SIP URI or Skype for Business sign-in address. Specify the address for the conference room or user account created for the Polycom system.
User NameSpecifies the name and Windows Domain to use for authentication when registering with a SIP Registrar Server, for example, user@windowsdomain.local.

RealPresence Group Series systems support the User Principal Name format (username@domain.com) and legacy Microsoft DOMAIN\username format. If the SIP server requires authentication, this field and the password cannot be blank.

PasswordWhen enabled, allows you to specify and confirm a new password that authenticates the system to the SIP server.
Registrar ServerIf you selected Specify in the SIP Server Configuration field, you need to specify the DNS name of the SIP Registrar Server.

In a Skype for Business environment, specify the DNS name of the Front End Pool or Director. The default port is 5061.

If registering a remote RealPresence Group Series system with an Edge Server, use the fully qualified domain name (FQDN) of the Access Edge Server. The port for the Edge Server role is usually 443 and must be entered explicitly.

Polycom recommends using the DNS name. The format for entering the address and port is the following:

DNS_NAME

TCP_Port

TLS_Port

Syntax Examples:

  • To use the default port for the protocol you selected, enter the following:

    pool.corp.local

  • To specify a different TLS port and use the default TCP port:

    pool.corp.local:443

Proxy ServerSpecify the DNS name or IP address of the SIP Proxy Server. If you leave this field blank, the Registrar Server is used. Note that in a Microsoft environment, the Proxy server and Registrar server are always the same, so only one server address field is required. If you selected Auto in the SIP Server Configuration field and leave the Proxy Server field 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 for this field is the same as the Registrar Server field.

Registrar Server TypeFor Skype for Business Server, select Microsoft.