secure_context
Sets security levels for protecting confidential data in logs of text-to-speech conversions, typically for a single event.
Value |
open, encrypt, suppress DEFAULT: open (no security)
|
How to set |
In a VoiceXML application, using a <property> element. Set in the browser, using the Vendor-Specific-Parameters header in a SPEAK request (not SET-PARAMS). |
Usage |
Frequently set by applications for individual text-to-speech events. |
The spelling of this parameter uses "switts." and not underscore.
This parameter provides security for confidential data such as identification numbers or passwords that users might provide to applications. It hides the information in call logs and audio waveforms. For a description of protected data types, and the resulting strings and audio written to log files, see Protecting confidential data.
Note: The switts.secure_context parameter suppresses or encrypts information for the application only. To affect the caller's side of the conversation, use the swirec.secure_context parameter.
See Security levels to protect confidential data for an overview of how the switts.mute_wcr, switts.secure_context, and wcr_encrypt parameters interact with each other.