Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
J
jami-daemon
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 141
    • Issues 141
    • 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-daemon
  • Issues
  • #14

Closed
Open
Opened Jun 13, 2018 by Sébastien Blin@sblinOwner

Incoherent packet loss and call fail

Sometimes, during the call connection, the daemon log an incoherent packet loss (integer overflow) and then the call fails.

This is due when TlsSession::TlsSessionImpl::flushRxQueue() receives the same packet sequence number twice.

Assignee
Assign to
Gnome 2018.07.15
Milestone
Gnome 2018.07.15 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: savoirfairelinux/ring-daemon#14