Difference between revisions of "GstWebRTC - Elements"

From RidgeRun Developer Connection
Jump to: navigation, search
Line 6: Line 6:
  
 
==Elements==
 
==Elements==
The GstWebRTC plugin consists in three elements:
+
The GstWebRTC plugin consists in three elements, each is explained with more detail in the next subsections.
 
* [[GstWebRTC_-_GstWebRTCSrc|GstWebRTCSrc]]
 
* [[GstWebRTC_-_GstWebRTCSrc|GstWebRTCSrc]]
 
* [[GstWebRTC_-_GstWebRTCSink|GstWebRTCSink]]
 
* [[GstWebRTC_-_GstWebRTCSink|GstWebRTCSink]]
Line 12: Line 12:
  
 
==Common Properties==
 
==Common Properties==
start-call: Its used to set which endpoint is in charge of start the call and to send the offer SDP to the another one. This property must be set to true to only one endpoint.
+
All the plugin elements share the following important properties:
signaler: This property is in charge of setting the desired signaler to use in the application as a GObject. Each signaler has their own child properties, you should be careful to set the correct ones.
+
 
stun-server: Property used to set the STUN server address and port in case you want to change to use your own or a different one. Usage: <stun-server-address>:<stun-server-port>
+
===start-call===
turn-server: Property used to set the TURN server address and port in case you want to change to use your own or a different one. Usage: <user>:<password>@<turn-server-address>:<stun-server-port>
+
Its used to set which endpoint is in charge of start the call and to send the offer SDP to the another one. This property must be set to true to only one endpoint.
certificate-pem: With this property you are able to set you own certificate and private key (in PEM format) for the DTLS negotiation.
+
 
 +
===signaler===
 +
This property is in charge of setting the desired signaler to use in the application as a GObject. Each signaler has their own child properties, you should be careful to set the correct ones.
 +
===stun-server===
 +
Property used to set the STUN server address and port in case you want to change to use your own or a different one. Usage: <stun-server-address>:<stun-server-port>
 +
 
 +
===turn-server===
 +
Property used to set the TURN server address and port in case you want to change to use your own or a different one. Usage: <user>:<password>@<turn-server-address>:<stun-server-port>
 +
 
 +
===certificate-pem===
 +
With this property you are able to set you own certificate and private key (in PEM format) for the DTLS negotiation.
 
}}
 
}}

Revision as of 17:47, 11 July 2017


WebRTC Fundamentals


Home

Evaluating GstWebRTC



This page provides an overview of the common properties of the GstWebRTC plugin elements.

Elements

The GstWebRTC plugin consists in three elements, each is explained with more detail in the next subsections.

Common Properties

All the plugin elements share the following important properties:

start-call

Its used to set which endpoint is in charge of start the call and to send the offer SDP to the another one. This property must be set to true to only one endpoint.

signaler

This property is in charge of setting the desired signaler to use in the application as a GObject. Each signaler has their own child properties, you should be careful to set the correct ones.

stun-server

Property used to set the STUN server address and port in case you want to change to use your own or a different one. Usage: <stun-server-address>:<stun-server-port>

turn-server

Property used to set the TURN server address and port in case you want to change to use your own or a different one. Usage: <user>:<password>@<turn-server-address>:<stun-server-port>

certificate-pem

With this property you are able to set you own certificate and private key (in PEM format) for the DTLS negotiation.



WebRTC Fundamentals


Home

Evaluating GstWebRTC