Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
jami-project
jami-project
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 181
    • Issues 181
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • savoirfairelinux
  • jami-projectjami-project
  • Issues
  • #209

Closed
Open
Opened Sep 16, 2016 by RingBot@RingBotOwner

daemon: ICE init fails when TURN server is not accessible

Issue generated from Tuleap's migration script. Originally submitted by: Guillaume Roguez (guillaume)

When a TURN server is given to use for an account, the ICE initialization will fails (by timeout) if the TURN server is not accessible (i.e. not resolvable or not responding to STUN registers msg).
As it's the init step of ICE and not negotiation, the ICE may negotiate but we don't let a chance to do it.
As example, this causes calls to failed even when peers are both joinable with their private host addresses

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: savoirfairelinux/ring-project#209