These are the parameters that are required for TTS using MRCPv2
The parameters associated with the Call Features options are :
| Name | Description |
|---|---|
| Name | Name of the call feature |
| Type | TTS_MRCPv2 |
| url | The url of the MRCP V2 resource, typically a URL with this format, sip:speech@mrcpv2.blueworx.com |
| locale | The locale that this Call Feature will be used for. This is used to determine which TTS resource is used when a voice application attempts to do TTS. For further details on how locale works for call features, please refer to BAM Command Line Utility Call Features Panel. |
| keep_session | Associated with TTS type call features. Boolean, specified as true or false. Determines whether to hold onto TTS sessions for the duration of a call |
| OPTIONS Ping Enabled | Boolean, specified as true or false. Used to determine whether we use SIP OPTIONS messages to determine if the resource is UP or DOWN. When true BVR will periodically send an OPTIONS message to the call feature url and update UP/DOWN status based on response. |
| OPTIONS Ping Frequency If UP | If OPTIONS are enabled and BVR considers the resource to be working then this is the time in seconds between OPTIONS messages being sent to check status. |
| OPTIONS Ping Frequency If DOWN | If OPTIONS are enabled and BVR considers the resource to be currently not working then this is the time in seconds between OPTIONS messages being sent to check status. |
| Description | Description of the call feature |
| SIP Proxy Group | SIP Proxy Group to use for this call feature. Note this is an optional parameter and can only be set using the update action once the call feature has been created. |
| Weight | A value determining how often to use the Call Feature, when multiple features of the same functionality, locale and priority are present. The higher the weight in relation to weights of these other features, the more often this feature will be used. For more information on how BVR uses Weight and Priority to provide load balancing and redundancy, please refer to Weight and Priority usage in the Blueworx Platform |
| Priority | Features with a lower priority value will be used before features with a higher priority value. Only if all relevant Call Features of a lower priority are DOWN will a higher priority number Call Feature be used. It is recommended to use bigger numbers when setting up priorities (i.e. 10, 20, 30 instead of 1, 2, 3) to allow for inserting Call Features inbetween existing priority levels. For more information on how BVR uses Weight and Priority to provide load balancing and redundancy, please refer to Weight and Priority usage in the Blueworx Platform |
| Down Retry Interval | The amount of time before trying to use a Call Feature again once it has been determined to be DOWN. BVR will attempt to use it again sooner if no alternative options exist for the task on the application. |