update hupall API to support multiple variables
hupall [cause] [[var1] [val1]] [[var2] [val2]] ...
added switch_core_session_hupall_matching_vars_ans() which will hang up all channels that match each variable(s) value
Channel variables in dial strings can be set through <>, {} or [].
<foo=bar> applies to every channel.
{foo=bar} applies to every channel, excluding channels delimited by :_:.
[foo=bar] only applies to the channel that follows [foo=bar].
Before this patch, group_call looked up users in the directory and
replaced {} with []. This logic does not work if the user has more than
one dial string, e.g. if multiple-registrations is set to true, and more
than two devices register under the same user.
This patch fixes the issue by stripping <> and {}, and inserting the
dial string before each individual dial string for each user. The
semantics of the "local_clobber" variable and the '|', ',' and ':_:'
delimiters are fully supported.
Port video buffer to also support audio and remove original STFU jitter buffer
Add some more resilience to video packet loss
Add codec control mechanism for both call-specific debug and codec/call specfic params
Make opus function better in packet loss and latent situations
Use new codec control prams to make JB lookahead FEC optionally enabled or disabled mid-call
Add Param to allow JB lookahead to be enabled.
The new C compiler breaks a lot of things. snprintf and timespec now exist, and redefining causes an error.
Many more things are warnings, so warnings-as-errors will fail - remove it from some projects for now.
V8: don't pass VS version to build batch file.
mod_sofia: Config has too-long if/elseif chain. Break this up to avoid "parser stack overflow; program too complex".
Add mod_conference.h to project and dir to includes.
* commit '2cad5a6940bb76458e909a56c5e5e35e622467ed':
more whitespace cleanup
fixed indentation
cleanup
cond api return -ERR on all syntax errors
FS-5945 - cond api improved
FS-5945 - cond api escape special charactars
If you start freeswitch with -reincarnate or -reincarnate-reexec, FS
will restart automatically in the event of an unexpected exit.
Currently, you can cause FS to immediately call exit(0) with `fsctl
shutdown now`, or you can have it call abort() with `fsctl crash`.
Which are both nice, but if you have reincarnation engaged, you really
might want FS to call exit([non-zero]) so the great supervisor
immediately breathes life back into your system.
This is now available via `fsctl shutdown reincarnate now`.
