  Release Summary for 4.3-69
  [![Generic badge](https://img.shields.io/badge/release_status-building-lightgrey.svg)](https://shields.io/)
  Changes to branch `4.3` after version `4.3.68`.
  * [- kazoo_speech: ASR Billing Features and kazoo_asr Refactor](https://github.com/2600hz/kazoo/pull/6185) - _by John White_
      This PR enhances the kazoo_speech application by augmenting the
      `kazoo_asr` abstraction as well as introduce new billing features.
      - Add `transcribe` field to the mailbox schema
      - Add and export callbacks to`gen_asr_provider` for content-types
      - Enhance the `kazoo_asr` behavior to handle default and accepted
      content types on behalf of the specific providers
      - Create an abstraction for ASR requests
      - Create account ledger entries on successful transcription as well as
      the impact the reseller ledgers.
      - Create `asr_flat_rate` module to handle flat rate billing of ASR
      requests.
      - Create quantifiers in `kz_services` for asr transcriptions.
      ```
      &quot;asr&quot;: {
      &quot;google&quot;: {
      &quot;rate&quot;: 1,
      &quot;name&quot;: &quot;Google ASR&quot;
      },
      &quot;ispeech&quot;: {
      &quot;rate&quot;: 1,
      &quot;name&quot;: &quot;ispeech ASR&quot;
      }
      },
      &quot;plan&quot;: {
      ....
      &quot;voicemails&quot;: {
      &quot;mailbox&quot;: {
      &quot;name&quot;: &quot;Voicemail Box&quot;,
      &quot;rate&quot;: 1.99,
      &quot;cascade&quot;: true
      },
      &quot;transcription&quot;: {
      &quot;cascade&quot;: true,
      &quot;rate&quot;: 1,
      &quot;name&quot;: &quot;VMBox Transcription MRC&quot;
      }
      },
      ....
      ```
      The only configuration change in this PR is adding the `transcribe`
      flag to the JSON schema.
      Two new callbacks have been added to `gen_asr_provider` to help
      facilitate a more generic approach to handling the preferred
      content-types for a provider as well as act as a gatekeeper and help
      identify if conversion is required or even currently supported for the
      submitted media.
      - preferred_content_type/0
      - accepted_content_types/0
      This callback is designed to return the ASR provider&#039;s preferred
      content-type for requests.
      This callback is designed to return the accepted content-types and
      assist in determining if the media payload will require conversion.
      The content-type callbacks have been added to `kazoo_asr` as well any
      `kapps_config` calls from the current providers in favor of keeping
      with the abstraction.
      Originally the ASR logic was hardcoded into the voicemail notify and
      save logic in `kvm_util`.  I&#039;ve removed that and replaced it with an
      asr_request.
      The `asr_request` module is designed to be a generic request type to
      handle creating and servicing ASR requests which are proxied with
      `kazoo_asr` to the configured provider..  Additionally it also handles
      the billing and services logic and introduces a `asr_flat_rate` module
      that can consult an ASR service plan item for rates.
      The long term vision is to create a primitive that can in the future
      could be augmented to handle multiple types of ASR requests apart from
      file conversion (i.e. streaming from an active call).
      I&#039;ve added some placeholder fields in `#asr_req` record should metered
      billing be desired.
      `asr_flat_rate` is the only and default `billing_method` for an
      `asr_request`.
      It is patterned after jonny5 and aims to perform the following actions
      on an `asr_req`:
      - **authorize**
      *account and reseller have funds*
      - **debit**
      *ledger entries created for account and reseller if configured*
      Some ASR primitives have been gently introduced into `kz_services`: -
      `asr` getter methods have been added to `kzd_service_plans` and
      `kz_service_plans` - default quantifiers for transcribe enabled
      maiboxes in `services.hrl` - `kz_services_asr` module for interacting
      with the transcription usage ledgers
  * [Include custom SIP headers in Pivot request](https://github.com/2600hz/kazoo/pull/6182) - _by James Aimonetti_
      When the INVITE arrives with custom SIP headers, include those in the Pivot request so the receiving web service can make appropriate decisions.
  -- 2600Hz Official <packages@2600hz.com> +Mon, 09 Dec 2019 23:37:09 
