Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • All traffic is encrypted for client to control server communications (control traffic / passwords / etc.).
  • Vibe scrambles data packets using a proprietary encapsulation mechanism.
  • Vibe can optionally secure control traffic and RTP packet transmission (client to USHI) with AES 128.

SSL is used from API server to USHI server

...

  • All data is encapsulated so there are no standard RTP packets traversing the network between Vibe/Viewme client and servers.
  • In meetings SRTP encryption of  Audio Audio and/or Video with Vibe/Viewme client can be optionally enabled (it is not by default). This is for performance reasons. There is no interface or API to set these options however. This is not used frequently. The big drawback when enabled is the additional CPU cycles required by the clients and the servers to encrypt and decrypt everything.
  • WebRTC connections always utilize HTTPS and SRTP, that is mandatory. So packets are encrypted from the client to the WebRTC server and then not encrypted utilize the encapsulation mentioned before from there, unless the media is set to be SRTP encrypted as explained above.
  • For H.323/SIP, we don't connect in secure TLS/SRTP mode so no encryption is used. RTP from the SIP/H.323 client are not encrypted before reaching the server and then depending of the setting (above) could be encrypted or not.