Skip to content

This sample app uses EnableX SDK to showcase key functionalities essential for any RTC application. These include token acquisition, session management, and multiple client-side actions such as audio/video mute/unmute, session recording, and screen sharing.

Notifications You must be signed in to change notification settings

EnableX/One-to-One-Video-Sample-Web-Application-with-annotation

Repository files navigation

1- to- 1 Video Calling Application with Annotations in JavaScript using EnableX Toolkit for Web

One to One Video Calling Application with Annotationsin JavaScript using EnableX Toolkit for Web This is a sample one to one video calling client application written in JavaScript that allows developers to implement video calling capabilities along with Annotations in their websites. The application runs on the web browsers (referred as client end point) and utilizes EnableX Web SDK to conduct an RTC session with its peers through EnableX Video Services.

The client application performs the following tasks to facilitate an RTC session:

Get token from the application server Connect to the room using the token Publish audio/video streams in the room Subscribe to remote audio/video streams in the room Listen to any session related events

1 Get Started

1.1 Pre-Requisites

1.1.1 App Id and App Key

1.1.2 Requirement

1.1.3 SSL Certificate

Use a valid SSL Certificate for your Domain and use it to configure your Web Service to make your domain accessible on HTTPS.

1.1.4 Sample Application Server

While this GitHub repository provides sample client code, you require an application server to provision video room on EnableX server. Use any of the Repository listed below to setup your application server:

Clone or download repository of your choice and configure the server as per the instructions given in the respective README document.

To directly try the sample code without having to configure an application server, you can also use the EnableX test server as explained in section 2. However, it is recommended to configure your own application server to build a video calling web app.

1.2 Test

  • Open the web browser and go to https://your-domain-name/path/client/ to load the application.
  • If you don't have a Room ID, then create by clicking on the “Create Room” button. The Room ID will get prefilled in the form.
  • Save the Room ID and share it with others along with the URL to join the Same Room.
  • Enter your Name and choose your role, either as a Moderator or a Participant
  • Allow access to the microphone when prompted.
  • You are now in a video call with others, who have joined the same room.

Note: This sample application creates a virtual room with limited Participants and 1 Moderator for demonstration purposes.

2 Testing Environment

As mentioned in section 1.1.4 above, you have an option to run your client application on EnableX pre-configured environment [https://try.enablex.io/] instead of setting up your own application server.

This allows you to quickly test the performance of EnableX audio calls before getting into the development of your application.

As the EnableX test server has been configured for demonstration purpose only, it only allows to:

  • Conduct a single session with a duration lesser than 10 minutes.
  • Host a multiparty call with less than 3 participants.

Refer to the Demo App Server [https://developer.enablex.io/docs/guides/video-guide/sample-codes/video-calling-app/] for more information.

Once you have successfully tested your application on the test server, you can set up your application server as explained in section 1.1.4 above.

3 Adding Annotations

Annotations can be implemented with the help of the following APIs:

EnxRoom.annotateToolAction(action, value) EnxRoom.startAnnotation(EnxStream,Callback) EnxRoom.stopAnnotation(Callback)

Learn How to Implement Annotations in detail here [https://developer.enablex.io/docs/references/sdks/video-sdk/web-sdk/in-session-communication/index/#start-annotation].

4 Learn more about Client API

The client APIs are called from the EnableX Web SDK (EnxRtc.js) which runs on the client browser. The client APIs are used to communicate with the EnableX video services and monitor the client-side state of the RTC session.

The client APIs are typically used to:

  • Connect to the desired room using the token received from the application server
  • Manage local audio and video
  • Handle room and stream related events initiated by the user

The client APIs handle four major entities:

  • EnableX Room: It handles room/session related events like connection, local stream publication, and remote stream subscription.
  • EnableX Stream: It identifies audio/video/data stream published by the user.
  • Events: It represents the events related to the room and the stream.
  • Player: It represents the customizable UI element used to render the audio/video stream in the DOM.

In addition to the features demonstrated in this sample program, the SDK has many helpful APIs available for the developers to utilize like:

  • File sharing
  • Streaming
  • Annotation
  • Canvas

And many more such exciting features.

Read Web Toolkit Documentation [https://developer.enablex.io/docs/references/sdks/video-sdk/web-sdk/index/] for more details.

Download Web Toolkit [https://developer.enablex.io/downloads/EnxRtc.js.v2.3.30.zip] to get the latest version of Web SDK.

5 Support

EnableX provides a library of Documentations, How-to Guides, and Sample Codes to help software developers, interested in embedding RTC in their applications.

Refer to the Complete Developer’s Guide [https://developer.enablex.io/] for more details.

You may also write to us for additional support at [email protected].

About

This sample app uses EnableX SDK to showcase key functionalities essential for any RTC application. These include token acquisition, session management, and multiple client-side actions such as audio/video mute/unmute, session recording, and screen sharing.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published