Skip to content

Releases: 2600hz/kazoo

4.3.72

12 Dec 23:12
24f96e6
Compare
Choose a tag to compare

Generic badge

Changes for 4.3.72

Changes to branch 4.3 after version 4.3.71.

Commits
  • Kz cache ttl - by Shvein Anton

    This is a draft PR while we work out the specifics of how to accomplish this.

4.3.71

12 Dec 22:48
Compare
Choose a tag to compare

Generic badge

Changes for 4.3.71

Changes to branch 4.3 after version 4.3.70.

Commits

4.3.70

12 Dec 19:46
Compare
Choose a tag to compare

Generic badge

Changes for 4.3.70

Changes to branch 4.3 after version 4.3.69.

Commits
  • Im services 4.3 - by lazedo

    doodle refactor

    • listens to inbound and processes the textflow/callflow

    • removes dependency from callflow and kazoo_call

    • external bindings removed

    • model simplification

    crossbar cb_sms

    • publishes inbound/outbound sms requests instead of creating document that would be caught by doodle with the changes api

    created kazoo_im

    • external offnet bindings & routing

    • added kapps_im (as kapps_call)

    • added ledger creation for offnet inbound/outbound

    • moved kapps_sms_command & renamed to kapps_im_command

    kazoo_number_manager

    • added knm_sms & knm_mms for verification & activation of im features

    kazoo_services

    • added kz_services_im for im plan configuration

4.3.69

09 Dec 23:22
Compare
Choose a tag to compare

Generic badge

Changes for 4.3.69

Changes to branch 4.3 after version 4.3.68.

Commits
  • - kazoo_speech: ASR Billing Features and kazoo_asr Refactor - 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 togen_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.
    
    "asr": {
    
    "google": {
    
    "rate": 1,
    
    "name": "Google ASR"
    
    },
    
    "ispeech": {
    
    "rate": 1,
    
    "name": "ispeech ASR"
    
    }
    
    },
    
    "plan": {
    
    ....
    
    "voicemails": {
    
    "mailbox": {
    
    "name": "Voicemail Box",
    
    "rate": 1.99,
    
    "cascade": true
    
    },
    
    "transcription": {
    
    "cascade": true,
    
    "rate": 1,
    
    "name": "VMBox Transcription MRC"
    
    }
    
    },
    
    ....
    
    

    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'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'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'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 - 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.

4.3.68

05 Dec 00:11
Compare
Choose a tag to compare

Generic badge

Changes for 4.3.68

Changes to branch 4.3 after version 4.3.67.

Commits
  • make clear that the template is ignored, not disabled - by icehess

    Mark the notification as ignored when transaction templates (for successful transaction) or transaction failed template is not being processed.

    Binding for these two notifications is same, and the templates are checking success in DataJObj to see if the notification is for them to process or the other module. Previously if the notification is for example for failed transaction, the successful template mark itself as disabled which is miss leading, because the template is not disabled it is simply is being process as this notification is irrelevant to the template. With current implementation in teletype these multiple templates can mark them as ignore when they don't want to process the notification so notification publisher consider it as done.

    master pr: #6177

4.3.67

29 Nov 19:12
820d8b2
Compare
Choose a tag to compare

Generic badge

Changes for 4.3.67

Changes to branch 4.3 after version 4.3.66.

Commits
  • Do not honor privacy settings for emergency calls (#6139) - by Harenson Henao

    Master #6139

    If a user dials to an emergency number and the device, user, account,

    or carrier has Caller-ID Privacy enabled and/or the user uses *67

    feature code to perform the emergency call, disregard the privacy

    settings and use the configured caller-id for emergency calls.

4.3.66

19 Nov 21:47
Compare
Choose a tag to compare

Generic badge

Changes for 4.3.66

Changes to branch 4.3 after version 4.3.65.

Commits
  • Adjust page size based on chunked/pagination settings - by James Aimonetti

    Add tests for 4 scenarios from "big data" fetches:

    1. paginated and chunked

    2. paginated and unchunked

    3. unpaginated and chunked

    4. unpaginated and unchunked

    Wonderfully, 3 does not trip the memory limit while 4 does, so

    chunking is a nice benefit for unpaginated requests. Might consider

    defaulting to is_chunked=true when paginate=false...

4.3.65

15 Nov 23:42
Compare
Choose a tag to compare

Generic badge

Changes for 4.3.65

Changes to branch 4.3 after version 4.3.64.

Commits
  • expand summary to include other service sections - by bitbashing

    Master PR #6149

  • Protect system when pagination is disabled - by James Aimonetti

    When fetching large datasets with pagination turned off, it is

    possible to tank the system when the dataset causes memory pressure

    during loading.

    This change adds an optional system config parameter for determining

    the maximum memory allowed for the Erlang process handling the API

    request.

    Additionally, even requests with pagination=false (or /v1) will

    still be loaded on a per-page basis. Each page load will check the

    memory consumption and error with an HTTP 416 response if memory usage

    exceeds the configured maximum.

    Until the maximum is reached, however, the pages will continue to be

    fetched until exhausted as before.

    FixtureDB has an added utility to make mirroring an existing CouchDB

    database to the FixtureDB fixtures directory for easier conversion of

    testing data.

  • url decode push parameters - by lazedo

    • decode registration parameters

4.3.64

13 Nov 23:52
Compare
Choose a tag to compare

Generic badge

Changes for 4.3.64

Changes to branch 4.3 after version 4.3.63.

Commits
  • Conference related updates - by James Aimonetti

    If ecallmgrs don't respond, conference API requests could crash due to unhandled timeout clause.

    Improve logging around federated listeners.

  • knm maintenance fixes - by Hesaam Farhang

    • fix kazoo_number_manager_maintenance:fix_apps_* functions

    • add commands to operate on a list of numbers

    master PR: #6125

4.3.63

08 Nov 21:04
Compare
Choose a tag to compare

Generic badge

Changes for 4.3.63

Changes to branch 4.3 after version 4.3.62.

Commits