3.19.21
Kazoo Changes
Changes to 3.19 after version 3.19.20
Resolved Tickets
Major (1)
- KAZOO-3250 As a sysadmin, I'd like the callflow app callflow submodule not to allow a call to be transferred to another callflow if the call is hungup
Normal (4)
- KAZOO-3353 As a front-end dev, I want to be able to set a key with an array of emails on a voicemail box, so that I can notify multiple persons when this voicemail box receives a message
- KAZOO-3352 As a front-end developer, I want the back-end to let me set a prepend feature on a phone number document, so that I can build the SmartPBX prepend feature easily
- KAZOO-3307 omnipresence notifies
- KAZOO-3270 The preview API copies the default notification to the current account if it doesn't exist.
Change Details
KAZOO-3250
Summary:
As a sysadmin, I'd like the callflow app callflow submodule not to allow a call to be transferred to another callflow if the call is hungup
Description:
To prevent loops, I'd like it if the callflow module in the callflow app (the action in the UI which lets you transfer calls to another callflow) to not actually process the request if the current channel is not active.
Reporter:
Darren Schreiber <darren@2600hz.org>
KAZOO-3353
Summary:
As a front-end dev, I want to be able to set a key with an array of emails on a voicemail box, so that I can notify multiple persons when this voicemail box receives a message
Description:
Acceptance Criteria:
- The Voicemail box document now validates a new key that is an array of string like : ['jr@2600hz.com', 'peter@2600hz.com'], name it how you/Karl want it, it's supposed to be a list of addresses that will be notified whenever a voicemail is received on this vmbox. It is very important to still get the e-mail from the owner of the vmbox and notify him as well (but you don't have to add it to the array)
- If one of the e-mail fails to be sent, then the overall process should be considered as a failure
Reporter:
Jean-Roch Maitre <jr@2600hz.com>
KAZOO-3352
Summary:
As a front-end developer, I want the back-end to let me set a prepend feature on a phone number document, so that I can build the SmartPBX prepend feature easily
Description:
Acceptance Criteria:
- The PUT/POST API on /phone_numbers allow developers to set a prepend key ({ ..., prepend: { name: 'JR', enabled: true }, .... } (In theory that should already work and don't need any change on the back-end?)
- If the prepend key is set and if the enabled key is set to true, then the /phone_numbers view, should add the "prepend" value to the "features" array.
UI Ticket matching this back-end ticket is UI-1219
Reporter:
Jean-Roch Maitre <jr@2600hz.com>
KAZOO-3307
Summary:
omnipresence notifies
Description:
with the addition of force_dummy_dialog parameter to kamailio there is no longer the need to notify kamailio on initial subscribe.
also, kamailio does not honor the send_fast_notify parameter on re-subscribes, therefore omnipresence should not send the notify to avoid duplicate notifies
Reporter:
Luis Azedo <luis@2600hz.com>
KAZOO-3270
Summary:
The preview API copies the default notification to the current account if it doesn't exist.
Description:
When sending a preview API request on a notification that is not present on the current account, the default notification is automatically copied to the current account.
Is that an intended behavior? Is it necessary?
If yes, then the UI needs to be re-worked, as it can be confusing for the end user.
Note: this happens whether the API sends back an error (500) or a success (200). See KAZOO-3267 & KAZOO-3269 for more info.
Reporter:
Maxime Roux <max@2600hz.com>