Releases: 2600hz/kazoo
3.18.56
Kazoo Changes
Changes to 3.18 after version 3.18.55
Resolved Tickets
Normal (1)
- KAZOO-3313 Outbound virtual fax stopped processing jobs until the whapp was restarted
Change Details
KAZOO-3313
Summary:
Outbound virtual fax stopped processing jobs until the whapp was restarted
Description:
As reported:
The case was: all the outbound virtual fax stopped working. The bigcouch servers are fine and we have lots of outbound fax pending there. At the same time, I could not find the line "fetched <number> jobs, attempting to distribute to workers" in our log file anymore. Instead, I see lines like "fax_jobs:121 (<0.1270.0>) unhandled message: timeout" in the log file every 5 seconds. I know kazoo server tries to grab fax job every 5 second(timeout). Based on this log line, we know the info is 'timeout'. My question is how come the function "handle_info('timeout', #state{jobs=[]}=State)" defined before the "handle_info(_Info, State)" was not called. Everything went back to normal(no such weird log anymore) after we restart the whistle_apps on that server. That server is running version kazoo 3.12.
Reporter:
Karl Anderson <karl@2600hz.org>
3.17.25
Kazoo Changes
Changes to 3.17 after version 3.17.24
Resolved Tickets
Normal (1)
- KAZOO-3313 Outbound virtual fax stopped processing jobs until the whapp was restarted
Change Details
KAZOO-3313
Summary:
Outbound virtual fax stopped processing jobs until the whapp was restarted
Description:
As reported:
The case was: all the outbound virtual fax stopped working. The bigcouch servers are fine and we have lots of outbound fax pending there. At the same time, I could not find the line "fetched <number> jobs, attempting to distribute to workers" in our log file anymore. Instead, I see lines like "fax_jobs:121 (<0.1270.0>) unhandled message: timeout" in the log file every 5 seconds. I know kazoo server tries to grab fax job every 5 second(timeout). Based on this log line, we know the info is 'timeout'. My question is how come the function "handle_info('timeout', #state{jobs=[]}=State)" defined before the "handle_info(_Info, State)" was not called. Everything went back to normal(no such weird log anymore) after we restart the whistle_apps on that server. That server is running version kazoo 3.12.
Reporter:
Karl Anderson <karl@2600hz.org>
3.16.41
Kazoo Changes
Changes to 3.16 after version 3.16.40
Resolved Tickets
Normal (1)
- KAZOO-3313 Outbound virtual fax stopped processing jobs until the whapp was restarted
Change Details
KAZOO-3313
Summary:
Outbound virtual fax stopped processing jobs until the whapp was restarted
Description:
As reported:
The case was: all the outbound virtual fax stopped working. The bigcouch servers are fine and we have lots of outbound fax pending there. At the same time, I could not find the line "fetched <number> jobs, attempting to distribute to workers" in our log file anymore. Instead, I see lines like "fax_jobs:121 (<0.1270.0>) unhandled message: timeout" in the log file every 5 seconds. I know kazoo server tries to grab fax job every 5 second(timeout). Based on this log line, we know the info is 'timeout'. My question is how come the function "handle_info('timeout', #state{jobs=[]}=State)" defined before the "handle_info(_Info, State)" was not called. Everything went back to normal(no such weird log anymore) after we restart the whistle_apps on that server. That server is running version kazoo 3.12.
Reporter:
Karl Anderson <karl@2600hz.org>
3.19.14
Kazoo Changes
Changes to 3.19 after version 3.19.13
Resolved Tickets
Blocker (1)
- KAZOO-3289 User groups "next action" does not play
Normal (1)
- KAZOO-3296 As a developer, would like data payload for timezone to be sent under settings
Change Details
KAZOO-3289
Summary:
User groups "next action" does not play
Description:
When creating a 'next action' in a user group, the proposed action does not occur when nobody picks up. It simply ends the call.
Reporter:
Richard Hurlock <richard@2600hz.com>
KAZOO-3296
Summary:
As a developer, would like data payload for timezone to be sent under settings
Description:
Currently being sent as :
settings['timezone']
would like:
settings['settings']['timezone']
Reporter:
Ricky Ing <ricky@2600hz.com>
3.19.13
KAZOO-3296: spec updates
3.19.12
KAZOO-3297: update cb_context usage
3.19.11: Merge pull request #757 from 2600hz/KAZOO-3212
Kazoo 3.19.11
Resolved Tickets
Normal (1)
- KAZOO-3212 Konami transfer. Transfer initiated by call originator results in dead air between transferee and target
Change Details
KAZOO-3212
Summary:
Konami transfer. Transfer initiated by call originator results in dead air between transferee and target
Description:
3 sip phones within the same account A (5511, transferor) , B (5520, transferee), C (5519, target)
Master branch with changes provided by onnet at #685 tested
- A calls B
- B answers A
- A dials *45519 and calls C (5519)
- B listens to MOH, C rings, A listens to dead air
- C answers and talks to A, B still listens to MOH
- A hangs up, C listens to dead air, B still listens to MOH
7a. B hangs up, C also hangs up
7b. C hangs up, B still listens to MOH
If in point number 3 the phone B (instead of A) dials *45519 and calls C (5519), transfer process proceeds sucesfully (with exception of dead air to B (transferor) during transfer which is already mentioned in KAZOO-3210)
Reporter:
Kirill Sysoev <iam@onnet.su>
3.19.10: KAZOO-3301 optionally use 'override_existing_document' in migrate_faxes
to override existing docs in modb. sup fax_maintenance migrate override_existing_documents added migrate/2 for sup fax_maintenance migrate accountid override_existing_documents
3.18.55: KAZOO-3301 optionally use 'override_existing_document' in migrate_faxes
Kazoo Changes
Changes to 3.18 after version 3.18.54
Resolved Tickets
Normal (3)
- KAZOO-3301 override existing document option in copy/move document
- KAZOO-3227 Creat superadmin in 3.18 broken
- KAZOO-3183 Cache flush on number reassign
Change Details
KAZOO-3301
Summary:
override existing document option in copy/move document
Description:
couch_mgr / couch_util havge copy_doc and move_doc that copying/moving docs between databases. this is useful for moving operational documents to modb databases.
when a copy_doc / move_doc tries to save the doc to the new destination and that document id already exists it returns 409 error.
implement a change such as a 'override_existing_document' option would mean that the save operation will call ensure_saved instead of save_doc
Reporter:
Luis Azedo <luis@2600hz.com>
KAZOO-3227
Summary:
Creat superadmin in 3.18 broken
Description:
On a fresh install from yesterday from the 2600hz packages.
On trying to create a superduper user it tries to access a view in accounts that does not exist.
https://gist.github.com/anonymous/a0b7f8c662db4209605b
If the missign view is created it works. The account is unique and creation continues.
Create this view in /accounts
https://gist.github.com/anonymous/3d493cbea61e3cc67e4a
This is probably not the "right fix" for this issue.
tx
Reporter:
stormqloud.ca <wlloyd@stormqloud.ca>
KAZOO-3183
Summary:
Cache flush on number reassign
Description:
Hi
Removed number from an account and reassigned it to another one immediately.
Calls was blocked till command sup wh_cache flush was issued
I am using ensure_valid_caller_id flag at trunkstore and since cache was filled with previous number's owner information call was blocked because of illegal CID
Seems like cache flush should be added on reassign
Regards,
Kirill
Reporter:
Kirill Sysoev <iam@onnet.su>
3.19.9
KAZOO-3247: correct typo