Pushing events is optional. If you don't have audio to process, then you can skip this step.
Setting the timestamp for
speakerEvent is optional but it's recommended to provide accurate timestamps in the events when they occurred to get more precision.
Events can be pushed to an on-going connection to have them processed. The code snippet to the right shows a simple example.
Every event must have a type to define the purpose of the event at a more granular level, usually to indicate different activities associated with the
event resource. For example - A "speaker" event can have type as
started_speaking. An event may have additional fields specific to the event.
Currently, Symbl only supports the speaker event which is described below.
The speaker event is associated with different individual attendees in the meeting or session. An example of a speaker event is shown below.
In the code example the user needs to have a
userId field to uniquely identify the user.
Speaker Event has the following types:
This event contains the details of the user who started speaking with the timestamp in ISO 8601 format when he started speaking.
This event contains the details of the user who stopped speaking with the timestamp in ISO 8601 format when he stopped speaking.
As shown in the above examples, it's okay to reuse the same
speakerEvent instance per user, by changing the event's type to optimize by reducing the number of instances for
startedSpeaking event is pushed on the on-going connection. You can use
pushEventOnConnection() method from the SDK to push the events.