Class WebRtcEndpoint.Builder

java.lang.Object
org.kurento.client.AbstractBuilder<WebRtcEndpoint>
org.kurento.client.WebRtcEndpoint.Builder
Enclosing interface:
WebRtcEndpoint

public static class WebRtcEndpoint.Builder extends AbstractBuilder<WebRtcEndpoint>
  • Constructor Details

    • Builder

      public Builder(MediaPipeline mediaPipeline)
      Creates a Builder for WebRtcEndpoint
  • Method Details

    • withProperties

      public WebRtcEndpoint.Builder withProperties(Properties properties)
      Overrides:
      withProperties in class AbstractBuilder<WebRtcEndpoint>
    • with

      public WebRtcEndpoint.Builder with(String name, Object value)
      Overrides:
      with in class AbstractBuilder<WebRtcEndpoint>
    • recvonly

      public WebRtcEndpoint.Builder recvonly()
      Single direction, receive-only endpoint
    • sendonly

      public WebRtcEndpoint.Builder sendonly()
      Single direction, send-only endpoint
    • useDataChannels

      public WebRtcEndpoint.Builder useDataChannels()
      Activate data channels support
    • withCertificateKeyType

      public WebRtcEndpoint.Builder withCertificateKeyType(CertificateKeyType certificateKeyType)
      Sets a value for certificateKeyType in Builder for WebRtcEndpoint.
      Parameters:
      certificateKeyType - Define the type of the certificate used in dtls
    • withQosDscp

      public WebRtcEndpoint.Builder withQosDscp(DSCPValue qosDscp)
      Sets a value for qosDscp in Builder for WebRtcEndpoint.
      Parameters:
      qosDscp - DSCP value to be used in network traffic sent from this endpoint

      If this parameter is present with a value different to NO_VALUE, all traffic sent from this WebRTCEndpoint will be marked with the correspondent DSCP value according to the DiffServ architecture. This may provide better handling of network traffic according to its characteristics associated to its DSCP value. This better handling includes priority in forwarding traffic and probability of packet drop in case of network congestion.

      It must be taken into account that on Internet not all intermediate routers are guaranteed to enforce those DSCP values, even it is possible that certain routers just block traffic marked with specific DSCP values, as discussed here https://datatracker.ietf.org/doc/html/rfc8835#section-4.2.

      So, this feature must be managed with care and is mostly intended for private networks, where the network proprietor can configure and guarantee DSCP management in all routers.