GVP MCP:mpc:recordpostfailover
| (7 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
|valid=Choose between: 0 or 1 | |valid=Choose between: 0 or 1 | ||
|takeseffect=At start/restart | |takeseffect=At start/restart | ||
| − | |shortdesc=This parameter controls the record post failover behavior in case of MSML call recording. When the value of this parameter is set to "1", MCP on startup scans the directory specified by the configuration parameter mpc.recordcachedir and tries to recover recording files present in that directory. Recovery is attempted for recording files with final destination one out of Amazon s3, Call Recording API, HTTP/HTTPS or FILE URI. No recovery attempt is made for SpeechMiner recording files. When the value of this parameter is "0", MCP on startup ignores the scanning of the above directory and no reovery is attempted. | + | |shortdesc= |
| + | This parameter controls the record post failover behavior in case of MSML call recording. When the value of this parameter is set to "1", MCP on startup | ||
| + | scans the directory specified by the configuration parameter mpc.recordcachedir and tries to recover recording | ||
| + | files present in that directory. Recovery is attempted for recording files with final destination one out of Amazon s3, Call Recording API, HTTP/HTTPS or FILE URI. | ||
| + | No recovery attempt is made for SpeechMiner recording files. | ||
| + | When the value of this parameter is "0", MCP on startup ignores the scanning of the above directory and no reovery is attempted. | ||
| + | |||
}} | }} | ||
{{DraftOption}} | {{DraftOption}} | ||
| − | |||
| − | |||
| − | |||
| − | |||
{{PubExtended}} | {{PubExtended}} | ||
| − | |||
| − | |||
| − | |||
{{DraftExtended}} | {{DraftExtended}} | ||
| − | |||
| − | |||
| − | |||
| − | |||
{{OptionCreate | {{OptionCreate | ||
Latest revision as of 15:59, June 29, 2020
View in ref guide.
Edit this option Publish this option Clear draft content
Published Option
Draft Option
No draft option
This page was last edited on June 29, 2020, at 15:59.
Comments or questions about this documentation? Contact us for support!