1. 08 May, 2018 1 commit
    • Philippe Gorley's avatar
      media: add filters · ea2933d4
      Philippe Gorley authored
      Adds dependency to libavfilter, which provides many useful utilities
      such as hardware encoding, mixing audio or rotating video.
      Access to libavfilter is done through the MediaFilter class, which takes
      a filter graph string and AVFrames as input and outputs filtered
      Adds unit tests for MediaFilter.
      Change-Id: I0bf3869a9f19ad9cbbe1fc5e2d37eb83ece66ccc
      Reviewed-by: Sébastien Blin's avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
  2. 07 May, 2018 4 commits
    • Philippe Gorley's avatar
      media: use av_find_best_stream · 524daf8d
      Philippe Gorley authored
      Change-Id: I6ab8a0078f7b67b2342859e216ab4ff02d721736
      Reviewed-by: Sébastien Blin's avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
    • Adrien Béraud's avatar
      pjsip: use ring log methods · ebd3e4b8
      Adrien Béraud authored
      Allows to get PJSIP logs on Android, where stdout is not logged.
      Change-Id: I6db7734dd608f3c8085bc7ed6cf0341ff3c9c787
      Reviewed-by: Sébastien Blin's avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
    • Sébastien Blin's avatar
      datatransfer: add a 10 minutes timeout when awaiting peer · 1bebb458
      Sébastien Blin authored
      Currently, when a file is sent, the peer needs to accept the transfer.
      So, connections with this peer will be opened until the peer accepts or
      not the file. Since the multi-device support, it's a problem because
      the peer has to accept/refuse the transfer on each devices.
      To avoid to leave unused connections while we are using the turn,
      we need to close these connections. This patch add a timeout to
      outgoing file transfers. So, after 10 minutes with the status
      awaiting peer, the connection is closed and the transfer canceled.
      NOTE: the peer will still see the awaiting_host status even if the
      connection is closed, but it's a known bug and it will need a major
      change of the blocking startNewFile function in FtpServer.
      Change-Id: Ic6e3a2bfebad92cc5c64f5ac2355c3c3765752c9
      Reviewed-by: Philippe Gorley's avatarPhilippe Gorley <philippe.gorley@savoirfairelinux.com>
    • Sébastien Blin's avatar
      datatransfer: multi devices support when sending files · 55be1e14
      Sébastien Blin authored
      With the current implementation, when a user send a file to a contact
      who got several devices connected, a request will be sent to all of
      these devices and the first which answer will get the transfer. So,
      a user can't know on which device they will get the file.
      With this patch, in the same configuration the peer will receives
      the file on all of its devices and add the possibility to accept
      or refuse the file. To avoid to see multiple file transfers because
      a peer has several devices, I introduced a OptimisticMetaOutgoingInfo
      which represents the best current state of the transfer (for example,
      if one subtransfer is ongoing and one failed (cause refused) it will
      show the outgoing one).
      This is an ongoing work, in the near future we must:
      + Give the ability to clients to see the real status of each
      subtransfer (with the ability to cancel/retry transfer by devices)
      + Add a timer to close awaiting transfers to avoid to let a unused
      connection for too long.
      Change-Id: I84eb243bff2bfdc087a83dd7eced45c361f27d16
      Reviewed-by: Philippe Gorley's avatarPhilippe Gorley <philippe.gorley@savoirfairelinux.com>
  3. 26 Apr, 2018 2 commits
  4. 24 Apr, 2018 3 commits
  5. 23 Apr, 2018 1 commit
  6. 22 Apr, 2018 1 commit
  7. 20 Apr, 2018 1 commit
    • Sébastien Blin's avatar
      message cache: change failure status after one minute · bdf1b3d8
      Sébastien Blin authored
      Before this patch a message got a failed status after 3 minutes
      (3 retries x 1 min). Moreover, if no devices was found, the message
      is keeped in the cache and wait for the next reboot. So it results in
      extremely long sending status, which is not really useful for the user.
      With this patch, the message fails to send after approximately one
      minute, if the user is connected and we do not receive an answer
      or if no device is found.
      Change-Id: I41171be2ebfebc424f96b4a4d42c360ad35ede86
  8. 19 Apr, 2018 1 commit
  9. 17 Apr, 2018 1 commit
  10. 13 Apr, 2018 1 commit
    • Sébastien Blin's avatar
      manager: auto-answer if two daemons are trying to call each other · 1aa43c00
      Sébastien Blin authored
      When two persons are trying to call each others, we can assume they
      want to talk together. So, the daemon should automatically answer.
      It avoids some weird case where they both see the outgoing call view,
      but cannot answer to the incoming call.
      There is several scenarios.
      1. Both are trying to make a video call, in this case, the daemon
      with the incoming call from the higher ring_id should answer and drop
      its outgoing call resulting in a video call.
      2. Both are trying to make an audio call, same behavior as scenario 1,
      resulting in an audio call.
      3. One device is trying to make a video call, the other an audio call,
      audio call is prioritary here, and the daemon with an incoming audio only
      call should answer and drop the outgoing video call.
      Change-Id: Id1e639448243c19bf492f2d057496cab6d05de8c
      Reviewed-by: Philippe Gorley's avatarPhilippe Gorley <philippe.gorley@savoirfairelinux.com>
  11. 11 Apr, 2018 2 commits
  12. 10 Apr, 2018 1 commit
    • Sébastien Blin's avatar
      datatransfer: avoid mismatch family errors using RFC 6156 · 1302c1d9
      Sébastien Blin authored
      RFC 6156 propose to use REQUESTED-ADDRESS-FAMILY to be able to
      communicate beetween a IPv6 network and a IPv4 network. Because
      this parameter is negociated during the allocation we should use
      two control channels to be able to communicate with all address
      Change-Id: Ie1659b20c4c7170697e4ad2949a519b0e87e35ae
  13. 09 Apr, 2018 1 commit
  14. 07 Apr, 2018 1 commit
  15. 06 Apr, 2018 1 commit
  16. 05 Apr, 2018 2 commits
  17. 04 Apr, 2018 1 commit
  18. 29 Mar, 2018 1 commit
  19. 28 Mar, 2018 2 commits
  20. 26 Mar, 2018 1 commit
  21. 23 Mar, 2018 2 commits
  22. 22 Mar, 2018 1 commit
  23. 21 Mar, 2018 1 commit
  24. 20 Mar, 2018 1 commit
  25. 19 Mar, 2018 2 commits
  26. 18 Mar, 2018 2 commits
  27. 16 Mar, 2018 1 commit
  28. 02 Mar, 2018 1 commit