DVSinchClientPlatform

To provide video call functionality, our user controls use the infrastructure and SDKs of Sinch

https://www.sinch.com/

So in order to use WorkWithPlus for VideoCall, the user must first register on the Sinch platform 

https://dashboard.sinch.com/dashboard

After you register on the platform, you must create an application and retrieve the associated information.

This information will be needed in order to configure the user controls:

  • Hostname
  • Application Key
  • Application Secret

 

e.g.

The Sinch developer dashboard "Credentials & Info" tab for the app "GxVideoConfTest" shows Application Credentials fields Hostname ("clientapi.sinch.com"), Key and Secret both redacted, and a JS Auth Yes/No toggle, plus Application Info fields Name and Description both set to "GxVideoConfTest".

The general architecture is the following:

An architecture diagram shows the Work With Plus VideoCall feature spanning three boxes: GeneXus Smart Device App (Android and iOS with Sinch SDKs and WorkWithPlus VideoCall) connecting over HTTPS to REST SD Services and Web Backend in the GeneXus Web Server (deployable On Premises, Azure, or Amazon Web Services), which connects over HTTPS to the GeneXus Web Client (Sinch JavaScript SDK and WorkWithPlus VideoCall). Both device and client sides also connect directly to the Sinch service via HTTPS, with a point-to-point call over UDP between them.

You can also, visualize the communication diagram:

Sequence diagram of the WorkWithPlus VideoCall architecture shows Peer A and Peer B, each running a GeneXus Smart Device/Web App with a 'WorkWithPlus VideoCall' component. Arrows depict each peer registering its device over HTTPS, Peer A initiating a call that reaches Peer B as an incoming call, Peer B answering, and the answer reaching Peer A, followed by a direct point-to-point call established over UDP between the peers, coordinated through the 'Sinch Servers' box shown below.