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 these contacts are online. Users can display up to five contacts on the system home screen.

The H.263 codec has been deprecated, and the system requires a Skype for Business Interoperability License to integrate with the 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.
Setting Description
Enable SIP Enables the system to make and receive SIP calls.
SIP Server Configuration Specifies how your system discovers the Skype for Business Server.
  • Select Auto if you set up your Skype for Business Server configuration for automatic discovery. Automatic discovery requires you to correctly configure the Skype for Business SRV records.
  • If you didn’t configure the Skype for Business Server for automatic discovery, select Specify.
Transport Protocol The SIP network infrastructure that your RealPresence Group Series system operates in determines the required protocol.
  • Auto enables an automatic negotiation of protocols in the following order: TLS, TCP, and UDP. Polycom recommends this setting for Microsoft environments.
  • TLS provides secure communication for SIP signaling. TLS is available only when you register the system with a SIP server that supports TLS. When you choose this setting, the system ignores TCP/UDP port 5060. Skype for Business requires TLS to connect.
  • TCP provides transport via TCP for SIP signaling. Skype for Business requires signaling encryption, so TCP doesn’t apply for Skype for Business.
  • UDP provides transport via UDP for SIP signaling.
Force Connection Reuse

This setting is disabled by default (recommended). When disabled, the system uses an ephemeral source port for all outgoing SIP messages.

When enabled, the system uses 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 Preference Controls the negotiation behavior for content sharing using 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 some deployments don’t support it, 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 you enable SIP.
  • 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, users can’t share content in a separate video stream.
  • TCP Only—Shares resources only through TCP. If TCP is unavailable, users can’t share content in a separate video stream.
Sign-in Address The system’s SIP name (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 Name 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\user name format. If the SIP server requires authentication, you can’t leave this field and the password blank.

Password When enabled, you can specify and confirm a new password that authenticates the system to the SIP server.
Registrar Server

If you select Specify in the SIP Server Configuration field, you must 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 FQDN of the Access Edge Server. The port for the Edge Server role is usually 443 and you must enter it explicitly.

Polycom recommends using the DNS name. Use the following format for entering the address and ports:

  • DNS_NAME
  • TCP_Port
  • TLS_Port

Syntax Examples:

  • To use the default port for the protocol you select, enter the following: pool.corp.local
  • To specify a different TLS port and use the default TCP port, enter the following: pool.corp.local:443
Proxy Server

The DNS name or IP address of the SIP proxy server.

If you leave this field blank, the system uses the registrar server. Note that in a Microsoft environment, the proxy server and registrar server are always the same, so you need to fill out only one server address field.

If you select Auto in the SIP Server Configuration field and leave the Proxy Server field blank, the system doesn’t use a proxy server.

Default proxy server ports:

  • For TCP, the system sends SIP signaling to port 5060 on the proxy server.
  • For TLS, the system sends SIP signaling to port 5061 on the proxy server.

The syntax for this field is the same as the Registrar Server field.

Registrar Server Type For the Skype for Business Server, select Microsoft.