Skip to content
Snippets Groups Projects
  1. Mar 11, 2021
  2. Mar 10, 2021
  3. Mar 09, 2021
  4. Mar 08, 2021
    • Sébastien Blin's avatar
      pjproject: increase timer value for TURN connection timeout · 8d428f44
      Sébastien Blin authored and Adrien Béraud's avatar Adrien Béraud committed
      On some very slow network, the process to connect to a relay
      candidates can take a lot of time. Cause this timer includes
      the time between the ConnectionAttempt and sending the
      Binding response. With some packet loss it can quickly increase
      this delay.
      
      Example:
      Classic nego (Successful ICE):
      
      10:36:28.126 .RX 144 bytes STUN message from 51.222.10.40:3478:
      --- begin STUN message ---
      STUN ConnectionAttempt indication (...)
      
      10:36:29.378 .TX 84 bytes STUN message to IP:45320:
      --- begin STUN message ---
      STUN Binding success response
      
      Problematic case on a bad network:
      
      // Bad network peer
      09:39:10.910 .RX 288 bytes STUN message from 192.252.140.236:3478:
      --- begin STUN message ---
      STUN ConnectionAttempt indication
      
      // other PEER:
      09:38:51.855 192.252.140.236:11846 (nominated): connectivity check FAILED:
      STUN transaction has timed out (PJNATH_ESTUNTIMEDOUT)
      => The other peer close the socket
      
      // Bad network peer
      09:38:52.258 .RX 76 bytes STUN message from IP:36436:
      --- begin STUN message ---
      STUN ConnectionBind success response
      
      9:38:53.756   tcprel0x7f7098178460  .socket send(): Not found (PJ_ENOTFOUND)
      
      The value of 15 secs is chosen to follow ice_inactive_timeout in
      the webrtc's sources (CONNECTION_WRITE_TIMEOUT)
      
      Change-Id: Idc66f6cb2018fbf03e34059640fa91601535dcb1
      GitLab: #1201
      8d428f44
  5. Mar 06, 2021
  6. Mar 05, 2021
  7. Mar 04, 2021
  8. Feb 26, 2021
  9. Feb 25, 2021
  10. Feb 24, 2021
  11. Feb 22, 2021
  12. Feb 19, 2021
  13. Feb 18, 2021
Loading