Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • jami-project jami-project
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 155
    • Issues 155
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-projectjami-project
  • Issues
  • #209

Closed
Open
Created 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
Time tracking