Why should I tag the remote end point type as peer or server?

 

 

Callstats gives you the ability to filter by peer-to-peer conferences or conferences where a media server was used. To correctly visualize this, you need to define the end point type for the connection when integrating callstats.js library.

 

The optional parameter FabricAttributes, in the addNewFabric API, has the remoteEndPointType attribute which is used to tag the end point type.

 

The remoteEndPointType tag options are peer and server, and you must consider the following when setting the endPointType:

 

1. Endpoint type is peer by default if it is not set. 

2. Endpoint type is peer when the remote endpoint is expected to be a peer (it might go through a TURN—UDP or TCP or TLS). 

 

Therefore in case 1 and 2, the setting could be skipped. 

 

3. Endpoint type is set to server when the remote endpoint is expected to be RTCP terminating server, such as an SFU or MCU. 

 

In a conference when an endpoint switches from peer to peer to a server-assisted approach, you need to mark the peer connections appropriately by marking the remoteEndPointType attribute.