Skip to content

STUN parameters not clear #239

@dberardo-com

Description

@dberardo-com

looking at the JVB configmap template is see

  {{- if and
         .Values.turnHost
         .Values.coturn.enabled
         .Values.jvb.useInternalStun
  }}
  JVB_STUN_SERVERS: {{ printf "%s:%v" .Values.turnHost .Values.coturn.service.ports.turn | quote }}
  {{- else if .Values.jvb.stunServers }}
  JVB_STUN_SERVERS: {{ .Values.jvb.stunServers | quote }}
  {{- else }}
  JVB_DISABLE_STUN: "true"
  {{- end }}

it is not clear to me:

  1. if useInternalStun is true, i believe one means that JVB should be pointing to coturn internal service name and not the public turnHost FQDN, or do i understand the semantic wrong ?
  2. i am exposing TURNS via 443 on the public turnHost FQDN ... in such case .Values.coturn.service.ports.turn is not 443 and therefore the resulting JVB_STUN_SERVERS is wrong
  3. i believe there should be a catch all variable jvb.disableStun to force JVB_DISABLE_STUN: "true"

also for my understanding:

is it important the JVB has access to a STUN server ? what if it cannot navigate on the public internet directly ? is it ok in such case to use coturn internal ClusterIP ? and what if JVB uses no STUN , what is the drawback ?

thanks you

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions