when initiating a call;
- from header
- account
These 2 parameters are dependent from each other which makes tricky for
the core to know exactly which account to use and the correct from
address.
In most scenarios, the from address is the account's identity address
but it is not always the case such as in the case of a direct call.
Moreover, the account cannot be always deduced in a straightforward
matter such as if the core has no default account (but it is registered
with one or more accounts) and the call parameters have not set one.

The algorithm for choosing an account is the following:
1) search in the call parameters
2) get the default account
3) look up for the best guessed account based on the from (if known) or
   to address

The algorithm for known the from address is the following:
1) look for the from header in the call parameters
2) look up for the identity address of the account (if known)
3) get the core primary account

...

Adapt suites declarations.

Add property to disable deletion of empty chatrooms
Enable compiler option '-Wunused-parameter'
Fixed possible null pointer exception in Java wrapper for Android
Update copyright notice in wrapper files

johan authored 2 years ago and Andrea Gianarda committed 2 years ago

- remove useless rc files
- clean memory leak in secure message test
- remove useless usage of fixed filepath for zrtp db

- factory API to get/set the cache dir
- rename get plain file function to make more explicit that the function create a file
- empty cache on core stop
- belle-sip dir manipulation API moved to bctoolbox

Sylvain Berfini authored 3 years ago and Andrea Gianarda committed 3 years ago

Move ephemeral lifetime setting to ChatRoomParams
If admin force participants to use ephemeral messages, they can enable or disable ephemeral capabilities in two different ways:
- function enableEphemeral:
  - if used to enable ephemeral messages, it will set the ephemeral time to the value stored in the core configuration if the current value is 0
  - if used to disable ephemeral messages, it will disable the feature without changing the ephemeral lifetime
- function setEphemeralLifetime:
  - enable ephemeral if the new lifetime is different from 0, disable the feature otherwise

Split some common code between the XMLRPC and REST API in utils files
Do not create local variable named mRequestCallbacks in AccountCreatorFlexiAPI constructor
Do create objects with new and delete them using free
Complete endpoints integration
Add a new flexiapi_url config variable in the LinphoneCore configuration
Split account creator tests in two, local and xmlrpc ones
Cleanup and remove unused code
Echap some URL parameters in FlexiAPIClient
Rename XMLRPC specific methods
Implement more FlexiSIP endpoints in the account manager
Create a new Account Creator FlexiAPI test suit
Put in common some functions of the Account Creator test suits
Complete FlexiAPIClient and the related account creator connectors
Load libjsoncpp properly
Fix response parameter in FlexiAPIClient responses
Use the new callback event system in the XMLRPC tests
Rename a few methods
Add comments to make some code more explicit
Pass jsoncpp to object
Add XCODE static/object for jsoncpp
Move the account_creator files from coreapi to src
Add a ENABLE_FLEXIAPI toggle

Reorder declaration

Fix test crashes

- add some pointers test on testers

- Add missing assert/end

- Rewrite uwp switch
- Fix winsock redefinition
- Add windows switch on headers
- Add static libs in FindSoci search
- Fix cast error