Meeting Conference With Ant Media

1
Meeting Conference With Ant Media
2

• Stream-Based SFU Video Conference
• This is the first implemented solution in AMS. It
  works with WebRTC streams directly.
• When a participant joins a room, they will send a
  join request to AMS for the room.
• AMS responds with the stream ID(stream_id) for
  the participant and the list of the other
  participant's stream IDs(stream_id) in the room.
• He/She will start to publish a WebRTC stream with
  his stream ID(stream_id).
• He/She sends WebRTC play requests for each stream
  ID he gets one by one.
• The information for the newly joined/left
  participants he/she should get room info (which
  contains the stream IDs of the room) periodically
  and compare the returning current stream IDs with
  the previous list he has.
• He/She sends play requests for new stream IDs,
  and stops requests for removed IDs.
• The calling leave method in Ant Media is enough
  to leave the room. (no need to send a stop
  request for each ID).
• Stream-based SFU Video Conference solution works
  in the clustered mode. Publish and all play
  request sent by a participant is forwarded to the
  same node in the cluster. So, there is no need to
  make the origin-edge distinction in such type of
  a cluster.
• https//erpsolutions.oodles.io/developer-blogs/Mee
  ting-Conference-With-Ant-Media/

3

• Track-Based SFU Video Conference
• This is a recent conference solution in AMS. It
  works with WebRTC tracks instead of streams.
  Users can find more about multitrack streaming in
  this blog post.
• When a participant joins a room, he/she sends a
  join request to AMS for the room.
• AMS responds with the stream ID(stream_id) for
  the participant.
• He/She starts to publish a WebRTC stream with his
  stream ID(stream_id).
• He/She sends only one WebRTC play request for the
  room ID.
• AMS sends the notification in the app for the
  newly joined/left participants. (Used for UI).
• The calling leave method is enough to leave the
  room and leave the meeting.