Configure various CCXML parameters
This section is OPTIONAL
The header for this section is [ccxml]
| Name | Mandatory | Type | Default | Description |
|---|---|---|---|---|
| ccx_min_threads | no | integer | 5 | CCXML can spawn message handling threads as needed. This defines the minimum to keep in low-traffic periods. Must be at least 1. Min: 1 |
| ccx_max_threads | no | integer | 600 | CCXML can spawn message handling threads as needed. This defines the maximum to allow to be created, to avoid running out of threads in the java instance. Must be at least 100 Min: 100 |
| connection_signal | no | boolean | false | This parameter was introduced in version 7.9.0 If enabled BVR will generate connection.signal events when DTMF keys are pressed, enabling processing key presses without the need for VXML. |
| idle_timeout | no | time | 0 milliseconds | This parameter was introduced in version 7.22.0 If set to a number higher than 0, the length of time in minutes to wait after a CCXML session has all calls terminated before automatically exiting the session This is a time unit value and can be written in human readable form (e.g. "1 day", "3 weeks" etc.) If just a number is supplied, it will be interpreted as MINUTES Min: 0 milliseconds, Max: 1 year |
| fetch_timeout | no | time | 5 minutes | This parameter was introduced in version 7.25.0 Used to define the default fetch timeout in seconds. The default fetch timeout is used to determine the amount of time to wait for a resource to be fetched. If a value is not supplied by the application (for example, if this is the first fetch) then this value is used. This is a time unit value and can be written in human readable form (e.g. "1 day", "3 weeks" etc.) If just a number is supplied, it will be interpreted as SECONDS Min: 10 milliseconds, Max: 1 day |
| redact_logs | no | boolean | false | This parameter was introduced in version 7.26.0 Redacts all content of VXML2 <log> tags |