Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-client-android
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 199
    • Issues 199
    • 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-client-android
  • Issues
  • #254

Closed
Open
Created Apr 15, 2016 by RingBot@RingBotOwner

daemon: unable to handshake with gnutls on 3G mobile network

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

When an Android device uses a 3G connection to call a peer (anykind of plateform), the certified and encrypted gnutls handshake fails.
The anonymous handshake succeed, but right after, the rehandshake with certificate fails.
Using a wireshark on the remote peer, we can see non-ordered packet (>1s of delay) reception.

Assignee
Assign to
Time tracking