Release Summary for 4.2.33
  Changes to 4.2 after version 4.2.32
  * Summary
      - cf_prepend_cid dies unexpectedly if invoked twice in the same callflow
  * Commits
      - [KAZOO-5873/SUPPORT-36464: Delete key instead of setting it as undefined when using prepend_cid&#039;s reset action (#4870)](https://github.com/2600hz/kazoo/commit/25a3ca7cb3e55a80fd5ccc2e235ad42c5e0f07a9) by Harenson Henao
  * [normalize capture group in cf_privacy (#4867)  fix did_us regex  normalize capture group in more cf modules  fix classifier regex again  what the hell fmt  fix to_npn and to_1npn  fix regexs in get_e164_converters test  update specs and log levels - james](https://github.com/2600hz/kazoo/commit/af067e355b279762f0158689db619027163ef868) by Hesaam Farhang
  * [HELP-37054-4.2: address ownership of conference dial channels (#4866)  * HELP-37054-4.2: address ownership of conference dial channels    When there are multiple ecallmgrs connected to a FreeSWITCH server, it  is possible that the conference dial occurs on ecallmgr1 and the fetch  request for the loopback-b channel comes in on ecallmgr2. This results  in the legs associated with the loopback (a and b) and the final  b-leg, are all considered &quot;local&quot; to ecallmgr2.    However, the conference dial needs to start a call control process on  ecallmgr1 to get a control queue for the add_participant API (used to  start a conf_participant process to manage the now-dialed  participant).    This means both ecallmgr1 and ecallmgr2 consider the b-leg to be  &quot;local&quot;. Metaflows checks the local ecallmgr&#039;s channel cache to  determine if it should repond to channel API actions - since both  ecallmgrs consider the channel local, both metaflow listeners publish  the payloads for konami to execute.    In this particular case, two CHANNEL_PIVOTs are picked up by the  cf_exe process and cause the conference action to be skipped (since  both &quot;set_variables&quot; actions call cf_exe:continue/1), the callflow is  exhausted, and cf_exe tears down the channel.    * HELP-37054-4.2: don&#039;t recurse into the Flow JSON object    The channels API should allow folks to include &quot;terminators&quot;:[] for  appropriate callflow actions. With the default  &quot;remove_recursive&quot;:true, the terminators key is removed; when  callflows executes the action, it sees the now-missing terminators key  and includes the default list (the exact opposite of what was  requested).    * HELP-37054-4.2: don&#039;t recurse to remove empties    metaflows uses kapi_route:publish_req/1 to include the metaflow (which  may contain empty terminators). Don&#039;t recursively strip empty values.    * HELP-37054-4.2: don&#039;t recurse on CHANNEL_PIVOT events    CHANNEL_PIVOT events will contain the flow, which may contain empty  terminators, which we don&#039;t want to strip.](https://github.com/2600hz/kazoo/commit/1caa2086426bd5e2583fd23d0ffe42ed4e1de639) by James Aimonetti
  * [teletype: pretty print caller/callee name and number (#4860)  make apis, spelling, deps  fix template  add email to field  change title for smtp error](https://github.com/2600hz/kazoo/commit/4904d7f904158923260e0685d332a1fb63b9f437) by Hesaam Farhang
  * [Kazoo-5901: Fixed faxbox email address comparision failing due to uppercase chars in user email address (#4863)](https://github.com/2600hz/kazoo/commit/37b7751d087ecc2e3f459feb09b016d3b6fd43ea) by Sean Wysor
 -- 2600Hz Official <packages@2600hz.com>  Fri, 25 May 2018 21:39:21 +0000
