Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-plugins-bad gst-plugins-bad
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 973
    • Issues 973
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 104
    • Merge requests 104
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamerGStreamer
  • gst-plugins-badgst-plugins-bad
  • Issues
  • #1146
Closed
Open
Issue created Dec 12, 2019 by Nazar Mokrynskyi@nazar-pc

webrtcbin: connection is not established without remote candidates (even when they are not needed)

If add-ice-candidate is not called, connection will not be established. However, if running with public IP address (on a server) it is not needed.

As a proof, this nonsense is sufficient to trick GStreamer into not requiring real proper candidates and establish connection successfully:

webrtcbin
    .emit(
        "add-ice-candidate",
        &[&0u32, &"candidate:0 1 udp 0 0.0.0.0 0 typ host".to_string()]
    )
    .unwrap();

Would be nice to remove the need for such a hack entirely.

Edited Dec 12, 2019 by Nazar Mokrynskyi
Assignee
Assign to
Time tracking