without the GRUU parameter therefore it must be pruned from the
conference address should it be present

enabled

Make more robust database migration code as the user may set database
paths but instruct the core not to initialize the database. This
behaviour can de achieved by the following lines in the rc file:
[misc]
use_database=1

[storage]
uri=null

By not explicitely disabling friends, call log and chat database, the
SDK assumes that they are enabled and migration sould be carried out

as well as public API linphone_core_create_chat_room_7 functions.
In fact, the conference parameters already have an account member
therefore it is redundant to take the local address in as it might lead
to an unexpected behaviour if not set correctly
Rework me conference parameter member as it is not required anymore as
the address of the me participant is the account identity address

Do not queue a task to dleete a conference if the core is shutting down
Delay by one iteration the Terminated state in the ClientConference
class. In fact, this state transition is done in a state changed
callback, therefore the application may be notified of a state or an
incorrect sequence of them

for basic chatroom. Flexisip based chatroom will set it to the contact
address of the account.
As RFC3428 doesn't allow MESSAGE requests to have a Contact header, the
account contact address is the only way for the server to know which
device sent it.

+ better migration testing

void making the assumption that the first 2 video streams are the main stream the the thumbnail of the local participant

Fix typo

Delete findOneToOneChatRoom from private API
Do not check subject for one to one chats

Add boolean value to know when the addition of a new endpoint has already been notified by the user XML

(cherry picked from commit c26adf04)

EndToEnd

This is a simple way for applications to index a chatroom or
conference provided by the SDK.
Applications can also retrieve a chatroom or conference object by providing its identifier

Ensure that linphone_core_search_chat_room_2 doesn't do a SIP address comparison as stated in the RFC. In fact, doing that leads to being too exposed to server instabilities.
For example, if a server for whatever reason removes the conf-id parameter from the chatroom peer address, it will prevent to client to join any new chatroom as all will match the corrupted chat

Add class ConferenceContext to easily compare two chatrooms or
conference based on the parameters, local and remote address and the
participants

state change

At startup, set all media conference supporting chat capabilities to
Terminated and reset the last notify ID

Free transient messages and events as soon as the chatroom moved into the Deleted state. The application might still keep a reference preventing the immediate destruction

scenarios:
- the client requested a full state
- the server sends a full state to catch up a big number of missed
  events.

In order to detect the latter case, the client looks if its current last
notify ID is not 0

Use parameters passed down by the application to join a group call after it has been created on the server

Rework impromptu conference tests to avoid using the conference
scheduler to create such conferences. Use instead the method
linphone_conference_invite_participants

- Added a null check for `remoteAddress` before using it.
- Now logs an error and skips `authenticationRejected()` if `remoteAddress` is null,
but still ensures `propagateEncryptionChanged()` is executed.

Added a null check in `CorePrivate::registerListener` to avoid registering a `nullptr`.
Logs an error message and returns early if `listener` is null.

Take into account conference capabilities in the NOTIFY full state if
the conference supports medias

Modified `Core::createXmlFromEktInfo` to take an explicit `Account` parameter instead of retrieving the default account internally.

iOS: make the IosPlatformHelper a CoreListener, in order to register for push only when core is in GlobalOn state. This fixes a bug where, when using remote provisioning, push token could be lost.