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
  • #237

Closed
Open
Created Oct 18, 2016 by RingBot@RingBotOwner

multidevice: client not acknowledged when ICE nego timeout

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

The caller's client continue to display "searching for" status after the daemon has deleted a terminated call due to ICE timeout (negotiation timeout of 60s).

Steps to reproduce the bug

  • call a valid Ring device but do not answer on it
  • wait 1 minute
  • the caller log shows the ICE negotiation timeout and the "subcall" destruction the client continue in "searching for" state

Result (vs. expected result)

  • the client loops in "searching for" state indefinetly
Assignee
Assign to
Time tracking