Release Summary for 4.0.6
  Changes to 4.0 after version 4.0.5
  * __KAZOO-5171__ as an admin i want auth profile updated based on configured claim value
  * __KAZOO-5168__ callflow caching not working
  * __KAZOO-5155__ e911 feature not listed as an available feature from GET /phone_numbers/{number} API
  * __KAZOO-5169__ fax processor keeps pending jobs forever if it doesn&#039;t receive feedback
  <table id='changeLog'>
  	<tr>
  		<th class='clName'>Name</th>
  		<th class='clReporter'>Reporter</th>
  		<th class='clSummary'>Summary</th>
  		<th class='clDescription'>Description</th>
  	<tr>
  	<tr>
  	    <td class='clName'>KAZOO-5171</td>
  	    <td class='clReporter'>Luis Azedo &lt;luis@2600hz.com&gt;</td>
  	    <td class='clSummary'>as an admin i want auth profile updated based on configured claim value</td>
  	    <td class='clDescription'>for external auth providers i want to configure a pair of fields from Claims/Profile to check if we should fetch the updated profile.
  </td>
  	    </td>
      </tr>
  	<tr>
  	    <td class='clName'>KAZOO-5168</td>
  	    <td class='clReporter'>sean anthony &lt;santhony@vinixglobal.com&gt;</td>
  	    <td class='clSummary'>callflow caching not working</td>
  	    <td class='clDescription'>Since the upgrade to v4.0 i am not able to move an existing DID to another callflow or group. When i remove the DID from an existing callflow and move it to another callflow/group, the number still rings the original callflow/group it was assigned too. I have even made the DID spare and it will still ring the original callflow it was assigned too. I have recreated this on multiple accounts with the same outcome in the smart PBX and advanced callflows sections.
  Advanced callflows
  - Went to existing callflow, removed DID, clicked save.
  - Went to new callflow, added DID, clicked save.
  - Called DID to make sure new callflow was working correctly, old callflow was still ringing.
  - Call logs show old callflow still being followed instead of new callflow.
  Smart PBX
  - Removed DID from user 1, saved.
  - Assigned same DID to user 2, saved.
  - Called DID, user 1 still rings instead of user 2.</td>
  	    </td>
      </tr>
  	<tr>
  	    <td class='clName'>KAZOO-5155</td>
  	    <td class='clReporter'>Jean-Roch Maitre &lt;jr@2600hz.com&gt;</td>
  	    <td class='clSummary'>e911 feature not listed as an available feature from GET /phone_numbers/{number} API</td>
  	    <td class='clDescription'>Now thare we&#039;re removing the provider specific stuff from the e911, we shouldn&#039;t return dash_e911 or vitelity_e911 in the &quot;available&quot; features. We should return &quot;e911&quot;. 
  The UI has been updated to remove the dash_e911 everywhere, so the UI is broken until that&#039;s fixed.</td>
  	    </td>
      </tr>
  	<tr>
  	    <td class='clName'>KAZOO-5169</td>
  	    <td class='clReporter'>Luis Azedo &lt;luis@2600hz.com&gt;</td>
  	    <td class='clSummary'>fax processor keeps pending jobs forever if it doesn&#039;t receive feedback</td>
  	    <td class='clDescription'>the fax_worker doesn&#039;t ack the request if it fails acquiring the fax job.
  this is by design due to possible process concurrency.
  if it fails because of database failure the controller keeps it pending.
  </td>
  	    </td>
      </tr>
  </table>
  * lazedo/bitbashing [qf-logs help debugging problems (#2787)  * qf-logs log more detail on service sync errors    * qf-logs log wrong database classification](https://github.com/2600hz/kazoo/commit/77afaa090e497b396107a8123bbda0da4afc1863)
  * lazedo/bitbashing [qf-publish fix account_id in kapi_conf publish (#2790)  * qf-publish fix account_id in kapi_conf publish    * qf-publish handle deleted accounts    * qf-publish fix formatting](https://github.com/2600hz/kazoo/commit/f4341e7dc787ddefbaf40661378523f7a301ca67)
 -- 2600Hz Offical <packages@2600hz.com>  Fri, 11 Nov 2016 18:15:54 +0000
