Tags: rozanecm/kazoo
Tags
[4.3] KZOO-163: change users and vmboxes cb_listing to emit id as key (… …2600hz#6707) * change user cb_lists view key to id to avoid repeat Emitting last/first name as key in view is just unique enough to avoid crossbar pagination problem with repeating key. Change this to use DocId as view's key * change vmbox cb_list to emit id as key
[4.3] HELP-19729: handle orphaned cf_exe processes (2600hz#6702) There is potential for a callflow executor leak when sending a default error response. In the field, we found inbound calls that were forwarded to a number which canceled the request almost immediately. When this happens, callflows gets a message back from stepswitch that the bridge was unsuccessful, then looks up the children in the callflow to see if any handle that specific hangup cause. In this case (and most configurations) there are no special branches so it performs a default action which is to send back a SIP error message. However, while that process is happening, FreeSWITCH has already forwarded the cancel from the B leg back to the A leg and out to the carrier. The particular carrier in this incident then immediately retries the same call in another zone. When that call gets created in the other zone, the ecallmgr call control usurps any other call control processes for that call id, terminating the ecallmgr call control in the first zone. It is only then that the first callflow sends the command to publish the SIP error, but with no ecallmgr control process in that zone anymore, nothing is there to process it. Callflows then waits indefinitely to hear back if the SIP error message was processed. As a general avoidance of similar situations the all infinite wait times in call command have also been reduced to one day by default, however if the cluster is servicing things like turret phones they can set it back to infinity.
Added missing blacklist list to the account doc schema and (2600hz#6696) updated relevant calls
[4.3] KZOO-96: Resolve emergency email number (2600hz#6678) When e911 call is made from number different than number which has e911 active, make sure to resolve proper address and info. Also make sure to not try to send emails for e911 calls made using local carrier as we only care about numbers which have e911 activated and have email address setup for that.
[4.3] PISTON-1170: Update content type on media attachments (2600hz#6674 ) The `kzm_message:forward_message/4` function branches, depending on whether the user has recorded an additional message to be prepended to the voicemail message being forwarded. Prepending the additional message requires the two media files to be merged into a temporary file. This is then written to the database as an attachment. Prior to this fix, the code assumed that the merged media file has an `mp3` format, which is not necessarily true. In addition, it did not pass any content-type option to the `kz_datamgr:put_attachment/5` function which actually writes the attachment. As a result, the attachment metadata in the database always indicated a content-type of `application/octet-stream`. Calls to `kz_media_util:join_media_files/2` now ensure that the merged output format is specified explicitly, rather than relying on default behaviour. The same format is also mapped to the corresponding MIME type which is passed to `kz_datamgr:put_attachment/5` to ensure the attachment metadata is correct.
[4.3] KZOO-76: added support for IBM speech to text (2600hz#6669) * [4.3] KZOO-76: added support for IBM speech to text * remove author from copy-paste * KZOO-76: address CI findings * KZOO-76: more ci fixes
PreviousNext