Releases: 2600hz/kazoo
3.19.40
Kazoo Changes
Changes to 3.19 after version 3.19.39
Resolved Tickets
Major (1)
- KAZOO-3420 Sync services via the GUI is not working
Normal (1)
- KAZOO-3419 When storing email-to-fax the same _rev is used during the retry
Change Details
KAZOO-3420
Summary:
Sync services via the GUI is not working
Description:
When using the Sync button, the Braintree subscription is not being updated. I discussed this with Karl and provided examples, but basically, it seems that Braintree is never called but the rest of the sync process is working.
This only happens on SJC, not ORD.
Reporter:
Darren Schreiber <[email protected]>
KAZOO-3419
Summary:
When storing email-to-fax the same _rev is used during the retry
Description:
It was determined that when the system retries storing the fax attachment it is using the original _ref.
Reporter:
Karl Anderson <[email protected]>
3.19.39: KAZOO-3407 startup fix
Kazoo Changes
Changes to 3.19 after version 3.19.38
3.19.38
Kazoo Changes
Changes to 3.19 after version 3.19.37
Resolved Tickets
Major (1)
- KAZOO-3402 Downloading the per-minute CSV times out for more than a few rows
Change Details
KAZOO-3402
Summary:
Downloading the per-minute CSV times out for more than a few rows
Description:
We have received reports that some clients are not able to download large per-minute CSV. I will lookup some examples.
Reporter:
Karl Anderson <[email protected]>
Maintenance/Community Commits
- James Aimonetti 3.19: remove source_url if present
- James Aimonetti 3.19: fix doc for single app init
- James Aimonetti 3.19: import monster apps via SUP
3.19.37: HELP-15568 ensure document is saved in fax migration
Kazoo Changes
Changes to 3.19 after version 3.19.36
Maintenance/Community Commits
3.19.36
Kazoo Changes
Changes to 3.19 after version 3.19.35
Maintenance/Community Commits
- James Aimonetti 3.19: transfer to any extension
- James Aimonetti 3.19: scenario fixes
- James Aimonetti 3.19: handle takeback again
- James Aimonetti 3.19: add hangup_cause helpers
- James Aimonetti 3.19: track loopback channels
- James Aimonetti 3.19: swap attributes for leg_created events
- James Aimonetti 3.19: export on both legs
- James Aimonetti 3.19: updated logging and getting leg_created event
3.19.35
Kazoo Changes
Changes to 3.19 after version 3.19.34
Resolved Tickets
Normal (3)
- KAZOO-3408 PBX Connector Not Passing Caller ID - Caller ID is Defaulting to emergency_caller_id
- KAZOO-3390 As a front-end developer, I want the Users crossbar listing to return the presence_id field, so that I can display the User main extension in the SmartPBX listing
- KAZOO-3385 As a system_admin (or callflow user) I would like to know when I misconfigured a call record (missing url) so that I does not crash and alert me instead
Change Details
KAZOO-3408
Summary:
PBX Connector Not Passing Caller ID - Caller ID is Defaulting to emergency_caller_id
Description:
The default logic of trunkstore is to leave the outbound caller id empty if not set, when issuing a bridge request. However, the default for stepswitch is to try the outbound caller id and fail back to the emergency if missing. Therefore, when the emergency was provided stepswitch was failing back to this caller id. I updated trunkstore so rather than leave the outbound caller id empty, if it is not explicitly on the document then it will set it to the inbound caller id.
Reporter:
Karl Anderson <[email protected]>
KAZOO-3390
Summary:
As a front-end developer, I want the Users crossbar listing to return the presence_id field, so that I can display the User main extension in the SmartPBX listing
Description:
Acceptance Criteria:
- /accounts/accountId/users now returns the presence_id fields if it exists for each user
- Once this is done, tell JR so that they can start implementing the change in the Front-end
Reporter:
Jean-Roch Maitre <[email protected]>
KAZOO-3385
Summary:
As a system_admin (or callflow user) I would like to know when I misconfigured a call record (missing url) so that I does not crash and alert me instead
Description:
Right now when the url is missing it will crash in 'ecallmgr_call_events' line 1055. We should handle it prior to that in 'cf_record_call'.
- Log it as an error
- Let callflow execution continue
- Send an alert to system admin
Reporter:
Peter Defebvre <[email protected]>
Maintenance/Community Commits
- James Aimonetti 3.18: fix pattern match
- James Aimonetti 3.19: uniquely start event processes
- James Aimonetti 3.19: don't set the callee id
- James Aimonetti 3.19: set channel vars for connect_leg
- James Aimonetti 3.19: handle purgatory timeout
- James Aimonetti 3.19: only collect digits for armed leg
- James Aimonetti 3.19: updated accessors of default headers
- James Aimonetti 3.19: better event filtering of target events
- James Aimonetti 3.19: actually return gregorian seconds from now_s
- James Aimonetti 3.19: get list of buckets to stop don't iterate over the table, as it can crash during concurrent updates.
3.18.58
Kazoo Changes
Changes to 3.18 after version 3.18.57
Maintenance/Community Commits
- James Aimonetti 3.18: fix pattern match
3.17.26
Kazoo Changes
Changes to 3.17 after version 3.17.25
3.16.42
Kazoo Changes
Changes to 3.16 after version 3.16.41
3.19.34
Kazoo Changes
Changes to 3.19 after version 3.19.33
Maintenance/Community Commits
- James Aimonetti 3.19: spawn the set/bridge_export for connect_leg
- James Aimonetti 3.19: filter events by node
- James Aimonetti 3.19: clean up starting metaflows for legs