1. 02 Mar, 2021 1 commit
  2. 23 Feb, 2021 1 commit
  3. 19 Feb, 2021 1 commit
  4. 04 Feb, 2021 1 commit
  5. 03 Feb, 2021 1 commit
  6. 02 Feb, 2021 2 commits
  7. 29 Jan, 2021 1 commit
  8. 28 Jan, 2021 1 commit
  9. 26 Jan, 2021 1 commit
  10. 20 Jan, 2021 1 commit
  11. 13 Jan, 2021 1 commit
  12. 12 Jan, 2021 2 commits
  13. 11 Jan, 2021 1 commit
  14. 05 Jan, 2021 1 commit
  15. 14 Dec, 2020 1 commit
  16. 03 Dec, 2020 2 commits
  17. 25 Nov, 2020 1 commit
    • Andrea Gianarda's avatar
      Store current list of active participants in the object conference and... · a18679e3
      Andrea Gianarda authored
      Store current list of active participants in the object conference and participant that are currently active or in the process of being removed in the object server group chat room
      Change participant device state only if core state is GlobalOn
      Remove participant from mainDb only if its state moves to Left
      Update test "group_chat_room_creation_server" to restart focus while participant that is offline has been removed
      a18679e3
  18. 24 Nov, 2020 2 commits
  19. 23 Nov, 2020 1 commit
  20. 22 Nov, 2020 2 commits
    • Sylvain Berfini's avatar
    • Simon Morlat's avatar
      Modify ServerGroupChatRoom behavior about 1-1 chatroom, incrementing "groupchat" capability to 1.1 · 5016cc29
      Simon Morlat authored
      Previously, a 1-1 chatroom was deleted only if it were BYEd by every device. A device that BYEd previously was re-INVITED by the chatroom in case messages had to be delivered. In addition, a device that BYEd the chatroom was given back the same chatroom ID when trying to re-create a new chatroom to the same other participant.
      Doing all this required to store 1-1 chatroom in a specific table, so that they could be retrieved fastly.
      Unfortunately this design totally breaks a federated system, since each domain may be entitled to create a 1-1 chatroom to communicate with a participant from another domain. As a result, the unicity of the one to one chatroom is not achievable in a federation of SIP domains.
      
      Now, the ServerGroupChatRoom conforming to groupchat/1.1 treats 1-1 chatroom similarly as real group chat rooms, with only one exception: when a device leaves the chatroom, then the chatroom is terminated, ie the server sends BYE to every device.
      In contrat, the client are then expected to restart the INVITE procedure if they want to send message through a chatroom whose session has been terminated by a BYE. The chatroom ID will of course change.
      
      Thanks to "org.linphone.specs" (capability descriptor), backward compatibility is preserved: the ServerGroupChatRoom keeps the old behaviour if one of the device doesn't conform to 1.1 specification.
      5016cc29
  21. 20 Nov, 2020 1 commit
  22. 17 Nov, 2020 1 commit
  23. 16 Nov, 2020 1 commit
  24. 12 Nov, 2020 2 commits
  25. 10 Nov, 2020 1 commit
  26. 04 Nov, 2020 2 commits
  27. 29 Oct, 2020 1 commit
  28. 22 Oct, 2020 1 commit
    • Andrea Gianarda's avatar
      Fix crash of conference when creating it before the proxy config is available · 3d8d6431
      Andrea Gianarda authored
      Take into account conf-id when adding, searching and deleting conferences in the map
      Do not set conf_ctx to NULL when callign linphone_core_terminate_conference
      Test conference in server mode
      Verify that 2 conferences with local participant enabled cannot be created at the same time
      Do not update proxy config when creating a local conference
      Add LINPHONE_PUBLIC to linphone_conference_params_new
      3d8d6431
  29. 21 Oct, 2020 1 commit
  30. 20 Oct, 2020 1 commit
  31. 16 Oct, 2020 1 commit
  32. 15 Oct, 2020 1 commit
  33. 07 Oct, 2020 1 commit