Before this callcenter_config queue reload [queuename] only reloads the queue
parameters and now it'll include a CC-Queue header with the queuename when using
mod_xml_curl and request a new config for updating agents and tiers related to the
queue.
If you are using mod_xml_curl please make sure to return the raw xml config file
with all the settings, queues, agents and tiers tags when we request the config
without a CC-Queue specified. If this header is present you can build the xml with
items only related to the queue requested.
* commit '98cb363f187a8ba5ad21b5a722a4f6dcaac21243':
FS-9148: add new voicemail.conf.xml param `send-full-vm-header` - if enabled, `Voice-Message` header sends urgent new and urgent saved
Do not set "_invalid" in case var_name is empty or unset. While at it,
clear the "foo_invalid" variable before doing anything else when a regex
is passed, this ensures that the variable really reflects the current
run.
Fixes an issue in original FS-7783 feature.
A new strategy is now available through mod_callcenter, which aim
is to provide a mix between top-down and ring-all strategies.
If set to ring-progressively, the strategy will call an agent, and
then a second agent, and then a third agent, without cancelling
previous calls.
The delay between each call is 10 sec by default, but it can be
changed using the queue variable ring-progressively-delay.
Sofia will unpredictably close a tls transport during call setup. This
occurs when the epoll event loop wakes up the socket reader and SSL_read
returns an error because there is no packet on the socket. Normally
sofia will read the last error using SSL_get_error and return
SSL_ERROR_WANT_READ. Sofia gracefully handles this error and the
transport stays open. Sometimes, however, the worker thread will call
SSL_shutdown for a different transport, which can write an error to the
internal openssl error queue. If that error is not read off the queue,
the next time that SSL_get_error is called, it will read that unrelated
error.
The documentation for SSL_shutdown explains that there are three
possible results -1, 0 and 1 with, oddly, 1 indicating success. The -1
result code occurs when there is no handshake callback registered on the
connection. It can return 0 when there is still work to be done. The
documentation suggest that it is insufficient to call it just once. This
is why I added the do {} while () construct.
Although just the fix to SSL_shutdown was enough to resolve my issue, I
a also audited other calls to SSL_* functions and found a few other
cases where an error may be generated, but was not handled.
Merge in Ubuntu Packaging changes
* commit '7375ad9e89679bf546fcaaeb2706a9adc405abd9':
FS-9081 [Ubuntu Packaging] WIP Patches to build system and configure to allow FS to build on 14.04
Revert "FS-9081 to build all modules for trusty needs the universe components"
Revert "FS-9081 Correction to e8f83d0"
Spencer Thomason
Italo Rossi
Anthony Minessale
Anthony Minessale II
Emmanuel Schmidbauer
Michael Jerris
Piotr Gregor
Ken Rice
Seven Du
Travis Cross
Hesaam Farhang
William King
Peter Wu
Stanislav Sinyagin
Brian West
Moishe Grunstein
Florent Krieg
Ethan Atkins