Enabling and disabling SIP, H.323, WebRTC and RTMP

All call protocols, except for SIP over UDP, are enabled by default in your Pexip Infinity deployment.

If your deployment does not include any endpoints that support a particular protocol, for security reasons you may want to disable support for those protocols across your entire Pexip Infinity deployment.

SIP over UDP is disabled by default so as to reduce the impact of SIP spam which typically uses UDP.

The configurable protocols are:

  • SIP over TCP and TLS, including MS-SIP (Skype for Business / Lync)
  • SIP over UDP (for incoming calls)
  • H.323
  • WebRTC
  • RTMP

WebRTC calls can originate from the Infinity Connect desktop client, the Infinity Connect web app via Google Chrome, Microsoft Edge, Firefox, Opera and Safari (version 11 onwards) browsers, and the Infinity Connect mobile client.

RTMP calls can originate from the Infinity Connect web app via Internet Explorer and Safari (versions 6-10) browsers. The web app will attempt an encrypted RTMPS connection first. For a secure RTMP connection to be established, the SIP TLS FQDN must be configured on the Conferencing Node (via Platform configuration > Conferencing Nodes) and it must match the Common Name of its TLS server certificate. If RTMPS fails, it will use an unencrypted connection for media.

RTMP is also used when sending conference content to streaming and recording services.

The Live view page (Status > Live View) lets you review current and historic usage charts showing a breakdown of participants by location, protocol, license type and the different conference types being hosted.

To enable or disable a particular call protocol across your Pexip Infinity deployment:

  1. Go to Platform configuration > Global settings.
  2. Select or clear the following checkboxes, as appropriate:

    • Enable SIP — this affects both SIP and MS-SIP (Skype for Business / Lync) over TCP and TLS
    • Enable SIP UDP — this affects incoming calls only over SIP UDP
    • Enable H.323
    • Enable WebRTC
    • Enable RTMP
  3. After modifying any of these values, each Conferencing Node must be rebooted before the changes will take effect. (It will, however, have an immediate effect on outbound calls placed via the modified protocols.)