The automake project is apparently changing behavior in their next
major version and warning everyone who relies on subdir-options to add
it explicitly.
Copy URI params from Refer-To header into custom header in subsequent INVITE
sip_h_X-FS-Refer-Params is set to show up in the INVITE as X-FS-Refer-Params
rtp_secure_media=mandatory
rtp_secure_media=optional
rtp_secure_media=mandatory:AES_CM_256_HMAC_SHA1_80,AES_CM_256_HMAC_SHA1_32
rtp_secure_media=optional:AES_CM_256_HMAC_SHA1_80
rtp_secure_media=forbidden
true implies mandatory
false implies forbidden
not set implies optional
rtp_secure_media_inbound or rtp_secure_media_outbound take precedence and are treated the same way based on leg direction
This was added as part of a mass copyright header update in commit
6e7d5d089. That's obviously not the right way to add features, so
we're reverting this.
If this feature is actually desired, it should be added in its own
commit, properly described in the commit message, and documented.
(The commit added a "tool" flag that could be applied to a conference
participant to mess with that person by disrupting his or her audio.)
This partially reverts commit 6e7d5d0897d253c5151b720327241e4bf03e0483.
This feature earlier tried to sneak in under the guise of a whitespace
cleanup in commit a000749e701dbb38130ec40fb592ce00da43eac9 which
Anthony reverted at commit a24f9aa8bc9a9e20d8c424ed69a9c63ecf2b9ede.
Let's not play these games.
We were handling the "send silence but not comfort noise" case in both
silence_stream_file_read and switch_generate_sln_silence. This
changes the former to rely on the latter.
write(3) can write fewer bytes than was requested for any number of
reasons. The correct behavior is to retry unless there is an error.
If there is an error, try to unlink the file; no sense in leaving
corrupted data laying around.
