It is recommended that the latest software versions are used, especially for components such as the TURN server, SIP proxy and XMPP server as these components need to achieve connectivity with a wide range of peers on the public Internet.

This does not imply using an unstable or beta version of your preferred Linux distribution, such as Debian sid or Fedora rawhide. Rather, it is recommended that the current stable release of the operating system is used and the RTC components can then be installed from a source such as Debian's stable-backports or Red Hat's EPEL.

Sometimes stable-backports or EPEL won't have the latest version of a particular package or you want to test some bleeding edge version of the package to see if it fixes a particular bug. Many of the packages can be built manually from the source code. All the leading RTC server projects make this very easy as they support tools like debuild for Debian/Ubuntu (see Appendix A, Building reSIProcate packages on Debian/Ubuntu) or rpmbuild for RedHat/CentOS/Fedora (see Appendix B, Building reSIProcate RPMs on RHEL and CentOS).